[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Will this also be released for focal? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled" otherwise if APICv is disabled in this vcpu it will trigger warning messages in vmx_sync_pir_to_irr() of vmx.c: WARN_ON(!vcpu->arch.apicv_active); With warnings like: [ cut here ] WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] ? xfer_to_guest_mode_work+0xe2/0x110 Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad vcpu_run+0x4d/0x220 [kvm] acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic #44-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 RAX: RBX: 99c552942640 RCX: 99c5043a72f0 RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 R10: 4228 R11: 000a R12: 99c552942640 R13: R14: ae4d8d1a63e0 R15: 99c552942640 FS: 7f6ae9be7640() GS:99c86f68() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: CR3: 00010b8a6006 CR4: 001726e0 Call Trace: kvm_vcpu_ioctl+0x243/0x5e0 [kvm] vcpu_enter_guest+0x383/0xf50 [kvm] ? xfer_to_guest_mode_work+0xe2/0x110 ? kvm_vm_ioctl+0x364/0x730 [kvm] ? __fget_files+0x86/0xc0 vcpu_run+0x4d/0x220 [kvm] __x64_sys_ioctl+0x91/0xc0 do_syscall_64+0x61/0xb0 ? fput+0x13/0x20 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6aebce1a2b Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b RDX: RSI: ae80 RDI: 000c RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] R10: 0001 R11: 0246 R12: R13: 0001 R14: 3000 R15: ---[ end trace 5b722d71a78069b1 ]--- This warning message will be flooding in system log files and eventually eat up all the disk space then crash the server. This issue will gone by either reverting it or adding the fixes below. Reference: https://patchwork.kernel.org/project/kvm/patch/2028072531.1534938-1-pbonz...@redhat.com/ [Fixes] * 0b8f11737 KVM: Add infrastructure and macro to mark VM as bugged * 673692735 KVM: x86: Use KVM_BUG/KVM_BUG_ON to handle bugs that are fatal to the VM * 7e1901f6c KVM: VMX: prepare sync_pir_to_
[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Similar configuration with Windows guests (6 total): root@cluster-05:/var/log# virsh dumpxml guest1 |grep -A 4 '' This is the first error, just after starting the first vm. Mar 28 06:27:17 cluster-05 systemd[1]: Started Virtual Machine guest1. Mar 28 06:27:17 cluster-05 kernel: [ 21.227759] [ cut here ] Mar 28 06:27:17 cluster-05 kernel: [ 21.227762] WARNING: CPU: 21 PID: 5027 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel] Mar 28 06:27:17 cluster-05 kernel: [ 21.227779] Modules linked in: vhost_net vhost vhost_iotlb tap ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua zfs(PO) zunicode(PO) zzstd(O) ipmi_ssif zlua(O) intel_rapl_msr zavl(PO) intel_rapl_common icp(PO) zcommon(PO) znvpair(PO) spl(O) isst_if_common skx_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ast kvm crct10dif_pclmul drm_vram_helper ghash_clmulni_intel joydev drm_ttm_helper ttm rapl drm_kms_helper input_leds intel_cstate cec rc_core i2c_algo_bit efi_pstore fb_sys_fops syscopyarea sysfillrect sysimgblt mei_me ioatdma mei intel_pch_thermal dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler bridge acpi_pad acpi_power_meter mac_hid sch_fq_codel mii 8021q garp mrp stp llc bonding tls drm ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear Mar 28 06:27:17 cluster-05 kernel: [ 21.227848] hid_generic usbhid hid raid1 crc32_pclmul aesni_intel crypto_simd i40e mpt3sas cryptd nvme raid_class i2c_i801 scsi_transport_sas ahci nvme_core xhci_pci i2c_smbus lpc_ich libahci xhci_pci_renesas wmi Mar 28 06:27:17 cluster-05 kernel: [ 21.227865] CPU: 21 PID: 5027 Comm: CPU 0/KVM Tainted: P O 5.13.0-37-generic #42~20.04.1-Ubuntu Mar 28 06:27:17 cluster-05 kernel: [ 21.227868] Hardware name: Supermicro SYS-5019P-M/X11SPM-F, BIOS 3.0c 03/27/2019 Mar 28 06:27:17 cluster-05 kernel: [ 21.227870] RIP: 0010:vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel] Mar 28 06:27:17 cluster-05 kernel: [ 21.227879] Code: 83 c4 10 5b 5d c3 48 89 df e8 5d 1c 30 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 75 d2 89 c7 e8 f6 fd ff ff 8b 45 ec eb c6 <0f> 0b eb 86 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb Mar 28 06:27:17 cluster-05 kernel: [ 21.227881] RSP: 0018:b6e7c1f97cf0 EFLAGS: 00010246 Mar 28 06:27:17 cluster-05 kernel: [ 21.227884] RAX: RBX: 9cd2b0a5a640 RCX: 0006 Mar 28 06:27:17 cluster-05 kernel: [ 21.227886] RDX: fffe2b98 RSI: c0e9c509 RDI: 9cd2b0a5a640 Mar 28 06:27:17 cluster-05 kernel: [ 21.227887] RBP: b6e7c1f97d08 R08: 0400 R09: Mar 28 06:27:17 cluster-05 kernel: [ 21.227889] R10: R11: R12: 9cd2b0a5a640 Mar 28 06:27:17 cluster-05 kernel: [ 21.227890] R13: 7f62755ec140 R14: 9cd113f99800 R15: 9cd2b0a5a640 Mar 28 06:27:17 cluster-05 kernel: [ 21.227892] FS: 7f62755ed700() GS:9cff80c8() knlGS: Mar 28 06:27:17 cluster-05 kernel: [ 21.227894] CS: 0010 DS: ES: CR0: 80050033 Mar 28 06:27:17 cluster-05 kernel: [ 21.227896] CR2: 7f6278c1b001 CR3: 0002a5ba6006 CR4: 007726e0 Mar 28 06:27:17 cluster-05 kernel: [ 21.227897] DR0: DR1: DR2: Mar 28 06:27:17 cluster-05 kernel: [ 21.227899] DR3: DR6: fffe0ff0 DR7: 0400 Mar 28 06:27:17 cluster-05 kernel: [ 21.227900] PKRU: 5554 Mar 28 06:27:17 cluster-05 kernel: [ 21.227901] Call Trace: Mar 28 06:27:17 cluster-05 kernel: [ 21.227903] Mar 28 06:27:17 cluster-05 kernel: [ 21.227906] kvm_arch_vcpu_ioctl+0x8fd/0x1260 [kvm] Mar 28 06:27:17 cluster-05 kernel: [ 21.227973] ? kvm_vcpu_ioctl+0x2ef/0x5f0 [kvm] Mar 28 06:27:17 cluster-05 kernel: [ 21.228014] ? kfree+0xd8/0x2a0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228020] ? kvm_vcpu_ioctl+0x2ef/0x5f0 [kvm] Mar 28 06:27:17 cluster-05 kernel: [ 21.228060] kvm_vcpu_ioctl+0x3a7/0x5f0 [kvm] Mar 28 06:27:17 cluster-05 kernel: [ 21.228100] ? __fget_light+0xce/0xf0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228104] __x64_sys_ioctl+0x91/0xc0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228108] do_syscall_64+0x61/0xb0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228111] ? do_syscall_64+0x6e/0xb0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228113] ? syscall_exit_to_user_mode+0x27/0x50 Mar 28 06:27:17 cluster-05 kernel: [ 21.228116] ? do_syscall_64+0x6e/0xb0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228118] ? do_syscall_64+0x6e/0xb0 Mar 28 06:27:17 cluster-05 kernel: [ 21.228119] ? asm_exc_page_fault+0x8/0x30 Mar 28 06:27:17 cluster-05 kernel: [ 21.228123] entry_SYSC
