[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
This bug was fixed in the package linux-azure - 5.4.0-1065.68 --- linux-azure (5.4.0-1065.68) focal; urgency=medium * focal/linux-azure: 5.4.0-1065.68 -proposed tracker (LP: #1952290) * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] azure: enable CONFIG_DEBUG_INFO_BTF * Support builtin revoked certificates (LP: #1932029) - [Config] azure: set CONFIG_SYSTEM_REVOCATION_KEYS * Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 (LP: #1952621) - PCI/sysfs: Convert "config" to static attribute * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.4.0-92.103 ] * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent - net: nxp: lpc_eth.c: avoid
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
This bug was fixed in the package linux - 5.4.0-92.103 --- linux (5.4.0-92.103) focal; urgency=medium * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent - net: nxp: lpc_eth.c: avoid hang when bringing interface down - net/tls: Fix flipped sign in async_wait.err assignment - phy: phy_ethtool_ksettings_get: Lock the phy for consistency - phy: phy_start_aneg: Add an unlocked version - sctp: use init_tag from inithdr for ABORT chunk - sctp: fix the processing for INIT_ACK chunk - sctp: fix the processing for COOKIE_ECHO chunk - sctp: add vtag check in sctp_sf_violation - sctp: add vtag check in sctp_sf_do_8_5_1_E_sa - sctp: add vtag check in sctp_sf_ootb - net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT - cfg80211: correct bridge/4addr mode check - KVM: s390: clear kicked_mask before
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
Microsoft tested and approved. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 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 crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 284.769564] RSP: 002b:7f4bc4c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 284.769565] RAX: ffda RBX: ae41 RCX: 7f4bcf01d317 [ 284.769566] RDX: RSI: ae41 RDI: 000b [ 284.769566] RBP: R08: 5596f71e0ec0 R09: 5596f896c170 [ 284.769567] R10: 5596f77fb8e0
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
This bug is awaiting verification that the linux/5.4.0-92.103 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 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 crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 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 crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 284.769564] RSP: 002b:7f4bc4c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 284.769565] RAX: ffda RBX: ae41 RCX: 7f4bcf01d317 [ 284.769566] RDX: RSI: ae41 RDI: 000b [ 284.769566] RBP: R08: 5596f71e0ec0 R09: 5596f896c170 [ 284.769567] R10: 5596f77fb8e0 R11: 0246 R12:
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 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 crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 284.769564] RSP: 002b:7f4bc4c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 284.769565] RAX: ffda RBX: ae41 RCX: 7f4bcf01d317 [ 284.769566] RDX: RSI: ae41 RDI: 000b [ 284.769566] RBP: R08: 5596f71e0ec0 R09: 5596f896c170 [ 284.769567] R10: 5596f77fb8e0 R11: 0246 R12: 5596f892ae90 [ 284.769568] R13:
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 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 crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00
