[Bug 99861] New: KVM: Linux host warns user requested TSC rate below hardware speed on the Baytrail-I platform when start a guest
https://bugzilla.kernel.org/show_bug.cgi?id=99861 Bug ID: 99861 Summary: KVM: Linux host warns user requested TSC rate below hardware speed on the Baytrail-I platform when start a guest Product: Virtualization Version: unspecified Kernel Version: 4.1.0-rc3+ Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: chao.z...@intel.com CC: tianyu@intel.com Regression: No Environment: Host OS (ia32/ia32e/IA64): ia32/ia64 Guest OS (ia32/ia32e/IA64): ia32/ia32e/IA64 Guest OS Type (Linux/Windows): Linux/Windows kvm.git Commit: c0655fe9b0901a968800f56687be3c62b4cce5d2 qemu-kvm Commit: f053f6b83d01b47adf3b8f29eb0c0769755d1f9c Host Kernel Version: 4.1.0-rc3+ Hardware: Baytrail-I platform Bug detailed description: -- Linux host warns user requested TSC rate below hardware speed on the Baytrail-I platform when start a guest. The warning is caused by guest tsc setting mismatch with host tsc. KVM records tsc value during Arch init stage while the tsc value may be changed during tsc clock source driver is loaded and refine tsc freq calibration. KVM starts a guest with old tsc value and trigger the warning. Attach a draft patch to fix the issue. Reproduce steps: Run a guest Current result: Linux host produce warning Expected result: No warning. Basic root-causing log: -- [ 1042.255614] [ cut here ] [ 1042.260804] WARNING: CPU: 2 PID: 5232 at arch/x86/kvm/vmx.c:2272 vmx_set_tsc_khz+0x3e/0x50() [ 1042.270266] user requested TSC rate below hardware speed [ 1042.276222] Modules linked in: [ 1042.279657] CPU: 2 PID: 5232 Comm: qemu-system-x86 Tainted: G D W 4.1.0-rc3+ #2 [ 1042.288923] Hardware name: Huawei Technologies Co., Ltd. AR16XA OSP/Aptio CRB, BIOS 5.6.5 04/17/2015 [ 1042.299160] 81f453f8 88026655fbc8 81b5eb8a [ 1042.307498] 88026655fc18 88026655fc08 810e6f8a 8802 [ 1042.315834] 001d3300 88027410 0001 88027410 [ 1042.324169] Call Trace: [ 1042.326926] [81b5eb8a] dump_stack+0x45/0x57 [ 1042.332693] [810e6f8a] warn_slowpath_common+0x8a/0xc0 [ 1042.339432] [810e7006] warn_slowpath_fmt+0x46/0x50 [ 1042.345884] [81253c9e] ? alloc_pages_current+0x10e/0x1d0 [ 1042.352913] [8101e48b] ? kvm_arch_vcpu_init+0x6b/0x230 [ 1042.359754] [8104676e] vmx_set_tsc_khz+0x3e/0x50 [ 1042.366005] [810112f7] kvm_set_tsc_khz.part.106+0xa7/0xe0 [ 1042.373136] [8101e628] kvm_arch_vcpu_init+0x208/0x230 [ 1042.379877] [81003bf9] kvm_vcpu_init+0xc9/0x110 [ 1042.386037] [81049fd0] vmx_create_vcpu+0x70/0xc30 [ 1042.392390] [8112a5c8] ? pick_next_task_fair+0x1d8/0xc50 [ 1042.399420] [8101dc9e] kvm_arch_vcpu_create+0x3e/0x60 [ 1042.406157] [81009f00] kvm_vm_ioctl+0x1a0/0x770 [ 1042.412313] [8129f395] ? __fget+0x5/0x200 [ 1042.417886] [81293448] do_vfs_ioctl+0x308/0x540 [ 1042.424044] [8129f301] ? expand_files+0x1f1/0x280 [ 1042.430395] [8147836b] ? selinux_file_ioctl+0x5b/0x100 [ 1042.437231] [81293701] SyS_ioctl+0x81/0xa0 [ 1042.442900] [81b6a72e] system_call_fastpath+0x12/0x76 [ 1042.449639] ---[ end trace 93158310429e56fc ]--- -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 99861] KVM: Linux host warns user requested TSC rate below hardware speed on the Baytrail-I platform when start a guest
https://bugzilla.kernel.org/show_bug.cgi?id=99861 Lan Tianyu tianyu@intel.com changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|virtualization_kvm@kernel-b |tianyu@intel.com |ugs.osdl.org| -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 99861] KVM: Linux host warns user requested TSC rate below hardware speed on the Baytrail-I platform when start a guest
https://bugzilla.kernel.org/show_bug.cgi?id=99861 --- Comment #1 from Lan Tianyu tianyu@intel.com --- Created attachment 179781 -- https://bugzilla.kernel.org/attachment.cgi?id=179781action=edit draft fix patch -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 98841] android emulator broken since d7a2a24 kernel commit
https://bugzilla.kernel.org/show_bug.cgi?id=98841 Adrian Sandu adrian.sa...@asandu.eu changed: What|Removed |Added Kernel Version|4.0.4 |4.1 --- Comment #1 from Adrian Sandu adrian.sa...@asandu.eu --- Still happening on 4.1-rc6 and all before since ~ 3.17 .. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 98841] android emulator broken since d7a2a24 kernel commit
https://bugzilla.kernel.org/show_bug.cgi?id=98841 Adrian Sandu adrian.sa...@asandu.eu changed: What|Removed |Added Kernel Version|3.17|4.0.4 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 98841] New: android emulator broken since d7a2a24 kernel commit
https://bugzilla.kernel.org/show_bug.cgi?id=98841 Bug ID: 98841 Summary: android emulator broken since d7a2a24 kernel commit Product: Virtualization Version: unspecified Kernel Version: 3.17 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: adrian.sa...@asandu.eu Regression: No Hello, For a while now I've noticed the android emulator not wanting to work anymore .. With a lil' bit of git bisect I've found this kernel commit https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=d7a2a246a1b5a0b0c803e800019600051e1e6f1a that seems to break it. I've mailed the author .. submited a report to the google guys ( not sure if I did it right ) https://code.google.com/p/android/issues/detail?id=174557 ... The problem was first reported by someone @ fedora .. https://bugzilla.redhat.com/show_bug.cgi?id=1187982 Alot of details ( run logs ) are there. Let me know if I can help test stuff. Thanks in advance. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 98741] New: Cannot boot into kvm guest with kernel = 3.18.x on el6.6 qemu-kvm host with virtio-blk-pci.x-data-plane=on and virtio-blk-pci.ioeventfd=on
https://bugzilla.kernel.org/show_bug.cgi?id=98741 Bug ID: 98741 Summary: Cannot boot into kvm guest with kernel = 3.18.x on el6.6 qemu-kvm host with virtio-blk-pci.x-data-plane=on and virtio-blk-pci.ioeventfd=on Product: Virtualization Version: unspecified Kernel Version: 3.18.x, 3.19.x, 4.0.x Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: jaroslav.pulch...@gooddata.com Regression: No Hello, I'm experiencing problem with latest kernel during testing of new features in virtual guests running at EL6.6 host in KVM with Virtio PV drivers and enabled datapalane (virtio-blk-pci.x-data-plane=on) feature to provide best IO performance. The issue cause that qemu-kvm process is stopped during quest boot. Host log: -- qemu-kvm: /builddir/build/BUILD/qemu-kvm-0.12.1.2/hw/msix.c:645: msix_set_mask_notifier: Assertion `!dev-msix_mask_notifier' failed. 2015-05-18 08:45:48.102+: shutting down --- Guest log: --- ... initcall virtio_pci_driver_init+0x0/0x1000 [virtio_pci] returned 0 after 82556 usecs calling ata_init+0x0/0x5d [libata] @ 204 libata version 3.00 loaded. initcall ata_init+0x0/0x5d [libata] returned 0 after 11641 usecs [drm:drm_framebuffer_reference] 8800da0c5ea0: FB ID: 21 (2) [drm:drm_framebuffer_unreference] 8800da0c5ea0: FB ID: 21 (3) calling ata_generic_pci_driver_init+0x0/0x1000 [ata_generic] @ 204 initcall ata_generic_pci_driver_init+0x0/0x1000 [ata_generic] returned 0 after 146 usecs calling init+0x0/0x1000 [virtio_blk] @ 250 virtio-pci :00:04.0: irq 24 for MSI/MSI-X virtio-pci :00:04.0: irq 25 for MSI/MSI-X ... END ... --- * Reproducible with this setup: Quest kernel versions: kernel 3.18, 3.19, 4.0 qemu-kvm: virtio-blk-pci.x-data-plane=on, virtio-blk-pci.ioeventfd=on * Not reproducible: Quest kernel versions: kernel 3.17 or older * Not reproducible: Quest kernel versions: kernel 3.18, 3.19, 4.0 qemu-kvm: virtio-blk-pci.x-data-plane=on + virtio-blk-pci.ioeventfd=off virtio-blk-pci.x-data-plane=off + virtio-blk-pci.ioeventfd=on I found this: 1/ shutting down is triggered by reentrancy into of qemu's virtio_blk_data_plane_start() function (see RedHat's bug #1222574), 2/ commits which introduced this issue are virtio_blk: enable VQs early on restore (6d62c37f1991aafc872f8d8be8ac60e57ede8605) virtio_net: enable VQs early on restore (e53fbd11e983e896adaabef2d2f1695d6e0af829) virtio_blk: enable VQs early (7a11370e5e6c26566904bb7f08281093a3002ff2) virtio_net: enable VQs early (4baf1e33d0842c9673fef4af207d4b74da8d0126) found by deep drive into git history of virtio drivers and several rebuilds with commits reverts (from 3.17-3.18) kernel 3.18.x build with reverted mentioned commits can successfully boot and run without issues. Best regards, Jaroslav -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 65081] Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow)
https://bugzilla.kernel.org/show_bug.cgi?id=65081 --- Comment #5 from Daniel Haid d.h...@gogi.tv --- The problem seems to be fixed with linux 3.19 and qemu 2.2.1. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 65081] Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow)
https://bugzilla.kernel.org/show_bug.cgi?id=65081 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC||bonz...@gnu.org Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #15 from Igor Mammedov imamm...@redhat.com --- Fixed in v4.0 commit 744961341d472db6272ed9b42319a90f5a2aa7c4 kvm: avoid page allocation failure in kvm_set_memory_region() -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53651] nVMX: L1 crashes with no-kvm-irqchip
https://bugzilla.kernel.org/show_bug.cgi?id=53651 Jan Kiszka jan.kis...@web.de changed: What|Removed |Added CC||jan.kis...@web.de --- Comment #1 from Jan Kiszka jan.kis...@web.de --- Steffen once did these tests for me. They were done on a now very old software stack, I no longer remember the precise details nor could I reproduce the same scenario. I can just confirm that I'm running nested with -no-kvm-irqchip regularly on a - granted - more modern host without problems. Therefore, I would suggest to close this issue. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug 94971 depends on bug 53621, which changed state. Bug 53621 Summary: nVMX: MSR_IA32_FEATURE_CONTROL https://bugzilla.kernel.org/show_bug.cgi?id=53621 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53601] nVMX meta-bug
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 54471, which changed state. Bug 54471 Summary: nVMX: TRUE* MSRs unnecessary https://bugzilla.kernel.org/show_bug.cgi?id=54471 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54471] nVMX: TRUE* MSRs unnecessary
https://bugzilla.kernel.org/show_bug.cgi?id=54471 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC||bonz...@gnu.org Kernel Version||3.19 Resolution|--- |INVALID --- Comment #2 from Paolo Bonzini bonz...@gnu.org --- TRUE_* is needed to tell the guest that it can disable CR3 load/store exits. We were enabling this control by exposing a broken MSR_IA32_VMX_PROCBASED_CTLS value, but commit 560b7ee12ca5 (KVM: nVMX: Fix returned value of MSR_IA32_VMX_PROCBASED_CTLS, 2014-06-16). So we can no longer remove the TRUE_* MSRs. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug 94971 depends on bug 54141, which changed state. Bug 54141 Summary: nVMX: Support TPR shadow https://bugzilla.kernel.org/show_bug.cgi?id=54141 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54141] nVMX: Support TPR shadow
https://bugzilla.kernel.org/show_bug.cgi?id=54141 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC||bonz...@gnu.org Kernel Version||3.19 Resolution|--- |CODE_FIX --- Comment #1 from Paolo Bonzini bonz...@gnu.org --- Fixed by commit a7c0b07d5708 (KVM: nVMX: nested TPR shadow/threshold emulation, 2014-08-21). -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug 94971 depends on bug 53611, which changed state. Bug 53611 Summary: nVMX: Add nested EPT https://bugzilla.kernel.org/show_bug.cgi?id=53611 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53611] nVMX: Add nested EPT
https://bugzilla.kernel.org/show_bug.cgi?id=53611 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC||bonz...@gnu.org Kernel Version||3.19 Resolution|--- |CODE_FIX --- Comment #2 from Paolo Bonzini bonz...@gnu.org --- Fixed by commit afa61f752ba6 (Advertise the support of EPT to the L1 guest, through the appropriate MSR., 2013-08-07) -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53601] nVMX meta-bug
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 53611, which changed state. Bug 53611 Summary: nVMX: Add nested EPT https://bugzilla.kernel.org/show_bug.cgi?id=53611 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug 94971 depends on bug 54471, which changed state. Bug 54471 Summary: nVMX: TRUE* MSRs unnecessary https://bugzilla.kernel.org/show_bug.cgi?id=54471 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53631] nVMX: Support exit/entry MSR load/store
https://bugzilla.kernel.org/show_bug.cgi?id=53631 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC||bonz...@gnu.org Kernel Version||3.19 Resolution|--- |CODE_FIX --- Comment #2 from Paolo Bonzini bonz...@gnu.org --- Fixed by commit ff651cb613b4 (KVM: nVMX: Add nested msr load/restore algorithm, 2014-12-11). -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53601] nVMX meta-bug
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 53621, which changed state. Bug 53621 Summary: nVMX: MSR_IA32_FEATURE_CONTROL https://bugzilla.kernel.org/show_bug.cgi?id=53621 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53621] nVMX: MSR_IA32_FEATURE_CONTROL
https://bugzilla.kernel.org/show_bug.cgi?id=53621 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC||bonz...@gnu.org Kernel Version||3.19 Resolution|--- |CODE_FIX --- Comment #2 from Paolo Bonzini bonz...@gnu.org --- Fixed by commit b3897a49e22f (KVM: nVMX: Fix read/write to MSR_IA32_FEATURE_CONTROL, 2013-07-08). -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53601] nVMX meta-bug
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 53631, which changed state. Bug 53631 Summary: nVMX: Support exit/entry MSR load/store https://bugzilla.kernel.org/show_bug.cgi?id=53631 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug 94971 depends on bug 53631, which changed state. Bug 53631 Summary: nVMX: Support exit/entry MSR load/store https://bugzilla.kernel.org/show_bug.cgi?id=53631 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53601] nVMX meta-bug
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 54141, which changed state. Bug 54141 Summary: nVMX: Support TPR shadow https://bugzilla.kernel.org/show_bug.cgi?id=54141 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
https://bugzilla.kernel.org/show_bug.cgi?id=82211 Zhou, Chao chao.z...@intel.com changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug 94971 depends on bug 82211, which changed state. Bug 82211 Summary: Cannot boot Xen under KVM with X2APIC enabled https://bugzilla.kernel.org/show_bug.cgi?id=82211 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |CODE_FIX -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #12 from Thomas Stein himbe...@meine-oma.de --- Hello Igor. Is this bug in 3.18 also present? I'm asking because i consider a downgrade. thanks and cheers t. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #13 from Igor Mammedov imamm...@redhat.com --- Nope, it's only since 3.19. Could you test patch in comment 11? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #14 from Thomas Stein himbe...@meine-oma.de --- I have patch from comment 11 already running on two machines. No problems so far. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #11 from Igor Mammedov imamm...@redhat.com --- (In reply to Thomas Stein from comment #10) Hello. I suppose this patch is not included in 3.19.3? Nope, I've posted v2 of the patch fixing problems Marcelo pointed out: https://www.marc.info/?l=kvmm=142685412907951w=3 so it' needs to be reviewed/tested. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #10 from Thomas Stein himbe...@meine-oma.de --- Hello. I suppose this patch is not included in 3.19.3? thanks and cheers t. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #8 from Igor Mammedov imamm...@redhat.com --- (In reply to Thomas Stein from comment #7) Hello. After reverting commit 1d4e7e3c0bca747d0fc54069a6ab8393349431c0 i had no problem any more. But we have to keep in mind this error only happend now and then. Especially creating snapshots of running vm's triggered the error but this runs without crashing the vm now. I tested it a few times. cheers t. Could you try following patch without reverting 1d4e7e3c0bca ? http://article.gmane.org/gmane.comp.emulators.kvm.devel/134191 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #9 from Thomas Stein himbe...@meine-oma.de --- Hello. I applied the patch to vanilla 3.19.2. No problems so far. Did a few snapshots and vm restarts. cheers t. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #7 from Thomas Stein himbe...@meine-oma.de --- Hello. After reverting commit 1d4e7e3c0bca747d0fc54069a6ab8393349431c0 i had no problem any more. But we have to keep in mind this error only happend now and then. Especially creating snapshots of running vm's triggered the error but this runs without crashing the vm now. I tested it a few times. cheers t. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 Igor Mammedov imamm...@redhat.com changed: What|Removed |Added CC||imamm...@redhat.com --- Comment #6 from Igor Mammedov imamm...@redhat.com --- Since commit 1d4e7e3c increased struct kvm_memslots size from order 2 to order 4, like-hood of above failure grew in ~2x times (there where 90 order 2 free pages) Looking at log from comment 1 allocation failure shouldn't happened since there are still 40 Order 4 free pages: úno 13 18:10:27 argus kernel: Normal: 18555*4kB (UEMC) 145*8kB (UMC) 92*16kB (UM) 54*32kB (UM) 40*64kB (UM) 9*128kB (UM) 2*256kB (U) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 82804kB Anyway I'll post patch that changes allocation vmalloc-ed memory as quick fix and look for possibility of allocating actual amount of slots instead of possible maximum like it's done now. -- You are receiving this mail because: You are watching the assignee of the bug.-- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #5 from Thomas Stein himbe...@meine-oma.de --- Hi. Reverted the commit right now. I have to boot with this kernel. More tomorrow. Thanks and cheers t. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
https://bugzilla.kernel.org/show_bug.cgi?id=82211 --- Comment #12 from Zhou, Chao chao.z...@intel.com --- (In reply to Radim Krčmář from comment #11) Should be fixed with KVM: x86: call irq notifiers with directed EOI, (http://www.spinics.net/lists/kernel/msg1949367.html) can you check if it is? Thanks. test this patch with kvm.git:4ff6f8e61eb7f96d3ca535c6d240f863ccd6fb7d kernel version: 4.0.0-rc1+ qemu.git:cd232acfa0d70002fed89e9293f04afda577a513 test on Haswell_EP and Ivytown_EP L1(xen on kvm) guest works fine when boot up L1 guest -- You are receiving this mail because: You are watching the assignee of the bug.-- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 Thomas Stein himbe...@meine-oma.de changed: What|Removed |Added CC||himbe...@meine-oma.de --- Comment #3 from Thomas Stein himbe...@meine-oma.de --- Hello. I have the very same error on my kvm machines. Mar 19 20:35:07 hn kernel: qemu-system-x86: page allocation failure: order:4, mode:0x40d0 Mar 19 20:35:07 hn kernel: CPU: 0 PID: 7029 Comm: qemu-system-x86 Not tainted 3.19.2 #1 Mar 19 20:35:07 hn kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 0802 08/29/ 2011 Mar 19 20:35:07 hn kernel: 88038857f9d8 81711fce 0001 Mar 19 20:35:07 hn kernel: 40d0 88038857fa68 81108d4e 88042fded838 Mar 19 20:35:07 hn kernel: 0380 03c0 0286 ffff Mar 19 20:35:07 hn kernel: Call Trace: Mar 19 20:35:07 hn kernel: [81711fce] dump_stack+0x45/0x57 Mar 19 20:35:07 hn kernel: [81108d4e] warn_alloc_failed+0xce/0x120 Mar 19 20:35:07 hn kernel: [8110bc24] __alloc_pages_nodemask+0x614/0x850 Mar 19 20:35:07 hn kernel: [8140da5f] ? megasas_fire_cmd_gen2+0x3f/0x50 Mar 19 20:35:07 hn kernel: [8114783c] alloc_pages_current+0x8c/0x100 Mar 19 20:35:07 hn kernel: [81108eac] alloc_kmem_pages+0x2c/0xd0 Mar 19 20:35:07 hn kernel: [811227f3] kmalloc_order+0x13/0x50 Mar 19 20:35:07 hn kernel: [8112284f] kmalloc_order_trace+0x1f/0x90 Mar 19 20:35:07 hn kernel: [811511b9] __kmalloc_track_caller+0x159/0x250 Mar 19 20:35:07 hn kernel: [8111ce1b] kmemdup+0x1b/0x40 Mar 19 20:35:07 hn kernel: [a0004aab] __kvm_set_memory_region+0x1eb/0x950 [kvm] Mar 19 20:35:07 hn kernel: [8115aca0] ? mem_cgroup_uncharge_swap+0x20/0xa0 Mar 19 20:35:07 hn kernel: [8113e3a8] ? swap_entry_free+0x198/0x310 Mar 19 20:35:07 hn kernel: [a000523a] kvm_set_memory_region+0x2a/0x50 [kvm] Mar 19 20:35:07 hn kernel: [a000577f] kvm_vm_ioctl+0x51f/0x760 [kvm] Mar 19 20:35:07 hn kernel: [81170d30] do_vfs_ioctl+0x2e0/0x4e0 Mar 19 20:35:07 hn kernel: [8107666f] ? vtime_account_user+0x3f/0x60 Mar 19 20:35:07 hn kernel: [81170fb1] SyS_ioctl+0x81/0xa0 Mar 19 20:35:07 hn kernel: [81719ff2] system_call_fastpath+0x12/0x17 Is anyone working on this? thanks and best regards t. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 Bandan Das b...@makefile.in changed: What|Removed |Added CC||b...@makefile.in --- Comment #4 from Bandan Das b...@makefile.in --- Doe(In reply to Thomas Stein from comment #3) ... Is anyone working on this? thanks and best regards t. Does reverting the commit suggested in comment 2 work for you ? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
https://bugzilla.kernel.org/show_bug.cgi?id=82211 --- Comment #11 from Radim Krčmář rkrc...@redhat.com --- Should be fixed with KVM: x86: call irq notifiers with directed EOI, (http://www.spinics.net/lists/kernel/msg1949367.html) can you check if it is? Thanks. -- You are receiving this mail because: You are watching the assignee of the bug.-- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92871] nested kvm - Warning in L0 kernel when trying to launch L2 guest in L1 guest
https://bugzilla.kernel.org/show_bug.cgi?id=92871 Radim Krčmář rkrc...@redhat.com changed: What|Removed |Added CC||rkrc...@redhat.com --- Comment #1 from Radim Krčmář rkrc...@redhat.com --- Fixed with KVM: nVMX: mask unrestricted_guest if disabled on L0. (https://lkml.org/lkml/2015/3/17/478) -- You are receiving this mail because: You are watching the assignee of the bug.-- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53601] nVMX meta-bug
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Nadav Har'El n...@math.technion.ac.il changed: What|Removed |Added Status|NEW |RESOLVED Kernel Version||- Resolution|--- |DUPLICATE --- Comment #1 from Nadav Har'El n...@math.technion.ac.il --- *** This bug has been marked as a duplicate of bug 94971 *** -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Nadav Har'El n...@math.technion.ac.il changed: What|Removed |Added CC||n...@math.technion.ac.il --- Comment #2 from Nadav Har'El n...@math.technion.ac.il --- *** Bug 53601 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
https://bugzilla.kernel.org/show_bug.cgi?id=82211 Radim Krčmář rkrc...@redhat.com changed: What|Removed |Added CC||rkrc...@redhat.com --- Comment #10 from Radim Krčmář rkrc...@redhat.com --- I can reproduce with kernel-4.0.0-0.rc3.git2.1.fc23.x86_64 and attached Xen. qemu-kvm -kernel ./xen -initrd /boot/vmlinuz-[...] -cpu kvm64,+x2apic Xen doesn't use x2APIC (which is good), but x2APIC enables directed EOI for xAPIC, which doesn't work. All is good if we manually avoid it qemu-kvm [...] -append ioapic_ack=new KVM IOAPIC never gets EOI. I'll take a look where the problem is. -- You are receiving this mail because: You are watching the assignee of the bug.-- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] New: nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bug ID: 94971 Summary: nVMX meta bug Product: Virtualization Version: unspecified Kernel Version: NA Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: b...@makefile.in Regression: No Creating a new Nested Virtualization meta bug to track current Nested Virtualization issues. I can't edit the old meta bug (bug 53601) due to permission issues, Nadav suggested to close it. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54461] nVMX: Downgrading nested VMX features from user-space
https://bugzilla.kernel.org/show_bug.cgi?id=54461 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53711] nVMX: potential bug with IDT_VECTORING_INFO if !PIN_BASED_EXT_INTR_MASK
https://bugzilla.kernel.org/show_bug.cgi?id=53711 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54141] nVMX: Support TPR shadow
https://bugzilla.kernel.org/show_bug.cgi?id=54141 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53621] nVMX: MSR_IA32_FEATURE_CONTROL
https://bugzilla.kernel.org/show_bug.cgi?id=53621 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54471] nVMX: TRUE* MSRs unnecessary
https://bugzilla.kernel.org/show_bug.cgi?id=54471 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
https://bugzilla.kernel.org/show_bug.cgi?id=82211 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53631] nVMX: Support exit/entry MSR load/store
https://bugzilla.kernel.org/show_bug.cgi?id=53631 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53701] nVMX: Unchecked setting of cr4 for nested guest
https://bugzilla.kernel.org/show_bug.cgi?id=53701 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54521] nVMX: accurately emulate VMXON region
https://bugzilla.kernel.org/show_bug.cgi?id=54521 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94771] [Nested kvm on kvm] 32bit win7 guest as L2 guest sho blue screen
https://bugzilla.kernel.org/show_bug.cgi?id=94771 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 60782] [Nested] Windows XP Mode can not work
https://bugzilla.kernel.org/show_bug.cgi?id=60782 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53871] nVMX: Can malicious L2 kill L1?
https://bugzilla.kernel.org/show_bug.cgi?id=53871 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 43068] Operation restricted to levels L0-2 - kerneloops when booting L3
https://bugzilla.kernel.org/show_bug.cgi?id=43068 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 90381] error when loading kvm_intel module kvm_intel unuseable
https://bugzilla.kernel.org/show_bug.cgi?id=90381 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 45931] Nested Virt: VMX can't be initialized in L1 Xen (Xen on KVM)
https://bugzilla.kernel.org/show_bug.cgi?id=45931 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53761] nVMX: MSR bitmap merging
https://bugzilla.kernel.org/show_bug.cgi?id=53761 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53651] nVMX: L1 crashes with no-kvm-irqchip
https://bugzilla.kernel.org/show_bug.cgi?id=53651 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53611] nVMX: Add nested EPT
https://bugzilla.kernel.org/show_bug.cgi?id=53611 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53851] nVMX: Support live migration of whole L1 guest
https://bugzilla.kernel.org/show_bug.cgi?id=53851 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53641] nVMX: Windows as L2 guest doesn't work
https://bugzilla.kernel.org/show_bug.cgi?id=53641 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53861] nVMX: inaccuracy in emulation of entry failure
https://bugzilla.kernel.org/show_bug.cgi?id=53861 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53691] nVMX: Bug when L1 is swapped out
https://bugzilla.kernel.org/show_bug.cgi?id=53691 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 53681] nVMX: Rare crash on shadow-on-shadow case
https://bugzilla.kernel.org/show_bug.cgi?id=53681 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 54161] nVMX: nested vpid
https://bugzilla.kernel.org/show_bug.cgi?id=54161 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92871] nested kvm - Warning in L0 kernel when trying to launch L2 guest in L1 guest
https://bugzilla.kernel.org/show_bug.cgi?id=92871 Bandan Das b...@makefile.in changed: What|Removed |Added Blocks||94971 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94971] nVMX meta bug
https://bugzilla.kernel.org/show_bug.cgi?id=94971 Bandan Das b...@makefile.in changed: What|Removed |Added Depends on||43068, 53611, 53621, 53631, ||53641, 53651, 53681, 53691, ||53701, 53711, 53761, 53851, ||53861, 53871, 54141, 54161, ||54461, 54471, 45931, 54521, ||94771, 82211, 92871, 90381, ||60782 --- Comment #1 from Bandan Das b...@makefile.in --- Added Depends on bugs. Note that some of them might have been already fixed. I will go through them and either remove them here or add a comment, since only the reporter seem to have permissions to close bugs. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94771] [Nested kvm on kvm] 32bit win7 guest as L2 guest show blue screen
https://bugzilla.kernel.org/show_bug.cgi?id=94771 Zhou, Chao chao.z...@intel.com changed: What|Removed |Added Summary|[Nested kvm on kvm] 32bit |[Nested kvm on kvm] 32bit |win7 guest as L2 guest sho |win7 guest as L2 guest show |blue screen |blue screen -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 86161] On KVM, Windows 7 32bit guests sometimes run into blue screen(0x0000005c) during reboot
https://bugzilla.kernel.org/show_bug.cgi?id=86161 Timofey timo...@koolin.ru changed: What|Removed |Added CC||timo...@koolin.ru --- Comment #3 from Timofey timo...@koolin.ru --- I have the problem with guest Windows Server 2012 R2 (x64) uname -rvmo 3.10.0-123.13.1.el7.x86_64 #1 SMP Tue Dec 9 23:06:09 UTC 2014 x86_64 GNU/Linux (Centos 7.0) -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 86161] On KVM, Windows 7 32bit guests sometimes run into blue screen(0x0000005c) during reboot
https://bugzilla.kernel.org/show_bug.cgi?id=86161 --- Comment #4 from Timofey timo...@koolin.ru --- CPU: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94771] New: [Nested kvm on kvm] 32bit win7 guest as L2 guest sho blue screen
https://bugzilla.kernel.org/show_bug.cgi?id=94771 Bug ID: 94771 Summary: [Nested kvm on kvm] 32bit win7 guest as L2 guest sho blue screen Product: Virtualization Version: unspecified Kernel Version: 4.0.0-rc1 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: chao.z...@intel.com Regression: No Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32 Guest OS Type (Linux/Windows):Windows kvm.git Commit:4ff6f8e61eb7f96d3ca535c6d240f863ccd6fb7d qemu.kvm Commit:d598911b6f5e7bf7bafb63b8e1d074729e94aca7 Host Kernel Version: 4.0.0-rc1 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- create 32bit win7 guest as L2 guest, the guest will show blue screen. note: create 32bit win8 or 32bit win8.1 as L2 guest, the guest boots up fine. Reproduce steps: 1 create L1 guest: qemu-system-x86_64 -enable-kvm -m 8G -smp 4 -net nic,macaddr=00:12:31:34:51:31 -net tap,script=/etc/kvm/qemu-ifup nested-kvm.qcow -cpu host 2. create L2 guest qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net none win7-32.qcow Current result: 32bit win7 as L2 guest boots up fail Expected result: 32bit win7 as L2 guest boots up fine Basic root-causing log: -- -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 88671] Radeon driver fails to reset hardware properly after kvm guest reboot
https://bugzilla.kernel.org/show_bug.cgi?id=88671 --- Comment #6 from Tom Stellard tstel...@gmail.com --- I've been playing with this a little more and it seems to be working correctly, but radeon dynamic power management (dpm) always fails to initialize on the second guest boot. My questions are: 1. What methods are being used by kvm/qemu/libvirt to reset the GPU on guest shutdown? 2. Is the problem only cuased by the fact that GPU reset is not implemented correctly in the radeon driver of are there improvements that are needed in kvm/qemu/libvirt in order to get this working? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 88671] Radeon driver fails to reset hardware properly after kvm guest reboot
https://bugzilla.kernel.org/show_bug.cgi?id=88671 --- Comment #7 from Alex Williamson alex.william...@redhat.com --- (In reply to Tom Stellard from comment #6) I've been playing with this a little more and it seems to be working correctly, but radeon dynamic power management (dpm) always fails to initialize on the second guest boot. My questions are: 1. What methods are being used by kvm/qemu/libvirt to reset the GPU on guest shutdown? Secondary PCI bus reset from the parent bridge. 2. Is the problem only cuased by the fact that GPU reset is not implemented correctly in the radeon driver of are there improvements that are needed in kvm/qemu/libvirt in order to get this working? Without a device specific reset, we're doing to most thorough standard reset available to us. I've also tried to use some of the reset mechanisms implemented in the radeon FOSS driver but they offered no improvement over the bus reset. There seems to be some state retained in the device that is not cleared via bus reset. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 94011] New: Enable CONFIG_PARAVIRT_SPINLOCKS by default
https://bugzilla.kernel.org/show_bug.cgi?id=94011 Bug ID: 94011 Summary: Enable CONFIG_PARAVIRT_SPINLOCKS by default Product: Virtualization Version: unspecified Kernel Version: HEAD Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: enhancement Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: iba...@adinet.com.uy Regression: No The description says it should be enabled but it isn't enabled in the default configuration. So either alter the description to say If you are unsure how to answer this question, answer N. or add a default y. Make up your mind guys! :-P Have a great tea! :-) -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 Marcelo Tosatti mtosa...@redhat.com changed: What|Removed |Added CC||mtosa...@redhat.com --- Comment #2 from Marcelo Tosatti mtosa...@redhat.com --- (In reply to Ondřej Súkup from comment #1) I run about 7 nodes, an simulate build of openstack cloud in qemu-kvm env .. nodes randomly after reboot stop working, or hangs in few sec after reboot from journalctl: úno 13 18:10:22 argus kernel: qemu-system-x86: page allocation failure: order:4, mode:0x40d0 úno 13 18:10:23 argus kernel: CPU: 2 PID: 2731 Comm: qemu-system-x86 Not tainted 3.19.0-gentoo #2 úno 13 18:10:27 argus kernel: Hardware name: Dell Inc. OptiPlex 9010/0M9KCM, BIOS A19 08/18/2014 úno 13 18:10:27 argus kernel: 0004 a9baffad 9d5cdf0c úno 13 18:10:27 argus kernel: 40d0 9d0d5f1e 0040 úno 13 18:10:27 argus kernel: 9d807080 9d0d8dda 9d806180 a9baffad úno 13 18:10:27 argus kernel: Call Trace: úno 13 18:10:27 argus kernel: [9d5cdf0c] ? dump_stack+0x47/0x67 úno 13 18:10:27 argus kernel: [9d0d5f1e] ? warn_alloc_failed+0xee/0x150 úno 13 18:10:27 argus kernel: [9d0d8dda] ? __alloc_pages_direct_compact+0x14a/0x150 úno 13 18:10:27 argus kernel: [9d0d9556] ? __alloc_pages_nodemask+0x776/0xb80 úno 13 18:10:27 argus kernel: [9d0d9a3a] ? alloc_kmem_pages+0x3a/0x110 úno 13 18:10:27 argus kernel: [9d0ee4e3] ? kmalloc_order+0x13/0x50 úno 13 18:10:27 argus kernel: [9d0e954b] ? kmemdup+0x1b/0x40 úno 13 18:10:27 argus kernel: [c0aeb1fa] ? __kvm_set_memory_region+0x24a/0x9f0 [kvm] úno 13 18:10:27 argus kernel: [c0b154b0] ? kvm_set_ioapic+0x130/0x130 [kvm] úno 13 18:10:27 argus kernel: [c0aeb9c1] ? kvm_set_memory_region+0x21/0x40 [kvm] úno 13 18:10:27 argus kernel: [c0aebe1f] ? kvm_vm_ioctl+0x43f/0x750 [kvm] úno 13 18:10:27 argus kernel: [9d2ef4eb] ? blk_finish_plug+0xb/0x40 úno 13 18:10:27 argus kernel: [9d10ae75] ? SyS_madvise+0x3c5/0x800 úno 13 18:10:27 argus kernel: [9d07ca71] ? cpuacct_account_field+0x11/0x60 úno 13 18:10:27 argus kernel: [9d147748] ? do_vfs_ioctl+0x308/0x510 úno 13 18:10:27 argus kernel: [9d06ce3f] ? vtime_account_user+0x3f/0x60 úno 13 18:10:27 argus kernel: [9d151423] ? __fget+0x63/0xa0 úno 13 18:10:27 argus kernel: [9d147986] ? SyS_ioctl+0x36/0x80 úno 13 18:10:27 argus kernel: [9d5d453d] ? int_check_syscall_exit_work+0x34/0x3d úno 13 18:10:27 argus kernel: [9d5d4312] ? system_call_fastpath+0x12/0x17 úno 13 18:10:27 argus kernel: Mem-Info: úno 13 18:10:27 argus kernel: DMA per-cpu: úno 13 18:10:27 argus kernel: CPU0: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU1: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU2: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU3: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU4: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU5: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU6: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU7: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: DMA32 per-cpu: úno 13 18:10:27 argus kernel: CPU0: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU1: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU2: hi: 186, btch: 31 usd: 22 úno 13 18:10:27 argus kernel: CPU3: hi: 186, btch: 31 usd: 170 úno 13 18:10:27 argus kernel: CPU4: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU5: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU6: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU7: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: Normal per-cpu: úno 13 18:10:27 argus kernel: CPU0: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU1: hi: 186, btch: 31 usd: 30 úno 13 18:10:27 argus kernel: CPU2: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU3: hi: 186, btch: 31 usd: 161 úno 13 18:10:27 argus kernel: CPU4: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU5: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU6: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU7: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: active_anon:2109969 inactive_anon:930082 isolated_anon:0 active_file:318968 inactive_file:466719 isolated_file:0 unevictable:0 dirty:134084 writeback:3211
[Bug 25332] When a VM is rebooted, assigned devices do not get RESET ...
https://bugzilla.kernel.org/show_bug.cgi?id=25332 Alan a...@lxorguk.ukuu.org.uk changed: What|Removed |Added Status|NEW |RESOLVED CC||a...@lxorguk.ukuu.org.uk Kernel Version||- Resolution|--- |OBSOLETE -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] New: qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 Bug ID: 93251 Summary: qemu-kvm guests randomly hangs after reboot command in guest Product: Virtualization Version: unspecified Kernel Version: 3.19.0 Hardware: Intel OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: mimi...@gmail.com Regression: No -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
https://bugzilla.kernel.org/show_bug.cgi?id=93251 --- Comment #1 from Ondřej Súkup mimi...@gmail.com --- I run about 7 nodes, an simulate build of openstack cloud in qemu-kvm env .. nodes randomly after reboot stop working, or hangs in few sec after reboot from journalctl: úno 13 18:10:22 argus kernel: qemu-system-x86: page allocation failure: order:4, mode:0x40d0 úno 13 18:10:23 argus kernel: CPU: 2 PID: 2731 Comm: qemu-system-x86 Not tainted 3.19.0-gentoo #2 úno 13 18:10:27 argus kernel: Hardware name: Dell Inc. OptiPlex 9010/0M9KCM, BIOS A19 08/18/2014 úno 13 18:10:27 argus kernel: 0004 a9baffad 9d5cdf0c úno 13 18:10:27 argus kernel: 40d0 9d0d5f1e 0040 úno 13 18:10:27 argus kernel: 9d807080 9d0d8dda 9d806180 a9baffad úno 13 18:10:27 argus kernel: Call Trace: úno 13 18:10:27 argus kernel: [9d5cdf0c] ? dump_stack+0x47/0x67 úno 13 18:10:27 argus kernel: [9d0d5f1e] ? warn_alloc_failed+0xee/0x150 úno 13 18:10:27 argus kernel: [9d0d8dda] ? __alloc_pages_direct_compact+0x14a/0x150 úno 13 18:10:27 argus kernel: [9d0d9556] ? __alloc_pages_nodemask+0x776/0xb80 úno 13 18:10:27 argus kernel: [9d0d9a3a] ? alloc_kmem_pages+0x3a/0x110 úno 13 18:10:27 argus kernel: [9d0ee4e3] ? kmalloc_order+0x13/0x50 úno 13 18:10:27 argus kernel: [9d0e954b] ? kmemdup+0x1b/0x40 úno 13 18:10:27 argus kernel: [c0aeb1fa] ? __kvm_set_memory_region+0x24a/0x9f0 [kvm] úno 13 18:10:27 argus kernel: [c0b154b0] ? kvm_set_ioapic+0x130/0x130 [kvm] úno 13 18:10:27 argus kernel: [c0aeb9c1] ? kvm_set_memory_region+0x21/0x40 [kvm] úno 13 18:10:27 argus kernel: [c0aebe1f] ? kvm_vm_ioctl+0x43f/0x750 [kvm] úno 13 18:10:27 argus kernel: [9d2ef4eb] ? blk_finish_plug+0xb/0x40 úno 13 18:10:27 argus kernel: [9d10ae75] ? SyS_madvise+0x3c5/0x800 úno 13 18:10:27 argus kernel: [9d07ca71] ? cpuacct_account_field+0x11/0x60 úno 13 18:10:27 argus kernel: [9d147748] ? do_vfs_ioctl+0x308/0x510 úno 13 18:10:27 argus kernel: [9d06ce3f] ? vtime_account_user+0x3f/0x60 úno 13 18:10:27 argus kernel: [9d151423] ? __fget+0x63/0xa0 úno 13 18:10:27 argus kernel: [9d147986] ? SyS_ioctl+0x36/0x80 úno 13 18:10:27 argus kernel: [9d5d453d] ? int_check_syscall_exit_work+0x34/0x3d úno 13 18:10:27 argus kernel: [9d5d4312] ? system_call_fastpath+0x12/0x17 úno 13 18:10:27 argus kernel: Mem-Info: úno 13 18:10:27 argus kernel: DMA per-cpu: úno 13 18:10:27 argus kernel: CPU0: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU1: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU2: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU3: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU4: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU5: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU6: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: CPU7: hi:0, btch: 1 usd: 0 úno 13 18:10:27 argus kernel: DMA32 per-cpu: úno 13 18:10:27 argus kernel: CPU0: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU1: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU2: hi: 186, btch: 31 usd: 22 úno 13 18:10:27 argus kernel: CPU3: hi: 186, btch: 31 usd: 170 úno 13 18:10:27 argus kernel: CPU4: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU5: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU6: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU7: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: Normal per-cpu: úno 13 18:10:27 argus kernel: CPU0: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU1: hi: 186, btch: 31 usd: 30 úno 13 18:10:27 argus kernel: CPU2: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU3: hi: 186, btch: 31 usd: 161 úno 13 18:10:27 argus kernel: CPU4: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU5: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU6: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: CPU7: hi: 186, btch: 31 usd: 0 úno 13 18:10:27 argus kernel: active_anon:2109969 inactive_anon:930082 isolated_anon:0 active_file:318968 inactive_file:466719 isolated_file:0 unevictable:0 dirty:134084 writeback:3211 unstable:0 free:47211 slab_reclaimable:45577 slab_unreclaimable:74482 mapped:47028 shmem:382256 pagetables:23493 bounce:0 free_cma:43 úno 13 18:10:27 argus kernel: DMA free:15884kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #10 from Mark kernelbugzilla.org.mark...@dfgh.net --- well thanks very much guys, I'll cautiously say that a patched guest kernel seems to resolve it :-) the bug seemed to appear even when the host is untainted; serial log says [ 375.989736] divide error: [#1] SMP that's a Kubuntu partition that manages without the proprietary drivers while Fedora won't seem to give graphics properly with nouveau; not entirely satisfactory of course given that I've now had to modify a virtual machine that it was important to try to avoid modifying for testing purposes; although definitely better than crashing :-) do we keep the bug report open so that the host kvm handling bug gets fixed too / is this the right place to report that? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #8 from Mark kernelbugzilla.org.mark...@dfgh.net --- Created attachment 166461 -- https://bugzilla.kernel.org/attachment.cgi?id=166461action=edit dmesg -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #9 from Mark kernelbugzilla.org.mark...@dfgh.net --- I'll try both of your suggestions, thanks -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 Alan a...@lxorguk.ukuu.org.uk changed: What|Removed |Added Status|NEW |NEEDINFO CC||a...@lxorguk.ukuu.org.uk --- Comment #6 from Alan a...@lxorguk.ukuu.org.uk --- Can you reproduce it without the Nvidia blob loaded on the host ? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added CC||bonz...@gnu.org --- Comment #7 from Paolo Bonzini bonz...@gnu.org --- Your guest is probably missing commit c1118b3602c2329671ad5ec8bdf8e374323d6343. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92871] New: nested kvm - Warning in L0 kernel when trying to launch L2 guest in L1 guest
https://bugzilla.kernel.org/show_bug.cgi?id=92871 Bug ID: 92871 Summary: nested kvm - Warning in L0 kernel when trying to launch L2 guest in L1 guest Product: Virtualization Version: unspecified Kernel Version: 3.19.0-rc7 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: rik.th...@esat.kuleuven.be Regression: No Hi, I've enabled nested KVM on my L0 (host) kernel and have created a guest with the CPU model copied from the host. Inside this guest I've installed libvirt and am trying to create a KVM guest (L2 guest). As soon as virt-manager tries to create the domain, the L1 guest reboots and the following WARNING is logged by the L0 kernel: Feb 06 20:35:18 saturn kernel: [ cut here ] Feb 06 20:35:18 saturn kernel: WARNING: CPU: 0 PID: 2352 at arch/x86/kvm/vmx.c:9190 nested_vmx_vmexit+0x7fe/0x890 [kvm_intel]() Feb 06 20:35:18 saturn kernel: Modules linked in: vhost_net vhost macvtap macvlan tun xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 bridge stp llc bnep bluetooth binfmt_misc cpufreq_userspace cpufreq_powersave cpufreq_conservative cpufreq_stats nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables snd_hda_codec_hdmi cx88_blackbird cx2341x cx22702 cx88_dvb cx88_vp3054_i2c videobuf2_dvb dvb_core wm8775 tuner_simple tuner_types iTCO_wdt iTCO_vendor_support tda9887 tda8290 tuner snd_hda_codec_via snd_hda_codec_generic evdev snd_hda_intel cx8800 snd_hda_controller nouveau cx8802 snd_hda_codec videobuf2_dma_sg joydev cx88_alsa coretemp snd_hwdep Feb 06 20:35:18 saturn kernel: videobuf2_memops video mxm_wmi cx88xx wmi videobuf2_core tveeprom rc_core v4l2_common videodev media kvm_intel drm_kms_helper ttm drm snd_pcm arc4 kvm psmouse rt61pci eeprom_93cx6 rt2x00pci rt2x00mmio snd_timer rt2x00lib snd mac80211 cfg80211 i2c_algo_bit i2c_i801 soundcore serio_raw rfkill i7core_edac edac_core 8250_fintek xhci_pci xhci_hcd i2c_core lpc_ich mfd_core asus_atk0110 shpchp button acpi_cpufreq processor thermal_sys loop firewire_sbp2 fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 btrfs xor raid6_pq dm_mod raid1 raid0 md_mod sg sr_mod cdrom sd_mod hid_generic usbhid hid usb_storage crc32c_intel firewire_ohci ahci libahci firewire_core crc_itu_t libata scsi_mod ehci_pci ehci_hcd r8169 mii usbcore usb_common Feb 06 20:35:18 saturn kernel: CPU: 0 PID: 2352 Comm: qemu-system-x86 Not tainted 3.19.0-rc7 #1 Feb 06 20:35:18 saturn kernel: Hardware name: System manufacturer System Product Name/P7P55D-E, BIOS 150412/14/2010 Feb 06 20:35:18 saturn kernel: a06f19fa 815357b8 Feb 06 20:35:18 saturn kernel: 8106cde1 8801e4f53000 0014 Feb 06 20:35:18 saturn kernel: a06de3ce Feb 06 20:35:18 saturn kernel: Call Trace: Feb 06 20:35:18 saturn kernel: [815357b8] ? dump_stack+0x40/0x50 Feb 06 20:35:18 saturn kernel: [8106cde1] ? warn_slowpath_common+0x81/0xb0 Feb 06 20:35:18 saturn kernel: [a06de3ce] ? nested_vmx_vmexit+0x7fe/0x890 [kvm_intel] Feb 06 20:35:18 saturn kernel: [a05d370b] ? kvm_arch_vcpu_ioctl_run+0xd7b/0x1220 [kvm] Feb 06 20:35:18 saturn kernel: [a05cf0cc] ? kvm_arch_vcpu_load+0x4c/0x1f0 [kvm] Feb 06 20:35:18 saturn kernel: [a05bf982] ? kvm_vcpu_ioctl+0x322/0x5d0 [kvm] Feb 06 20:35:18 saturn kernel: [8109bdc6] ? set_next_entity+0x56/0x70 Feb 06 20:35:18 saturn kernel: [810128e0] ? __switch_to+0x440/0x5e0 Feb 06 20:35:18 saturn kernel: [811cf908] ? do_vfs_ioctl+0x2e8/0x4f0 Feb 06 20:35:18 saturn kernel: [8110161c] ? __audit_syscall_entry+0xbc/0x110 Feb 06 20:35:18 saturn kernel: [810228fb] ? syscall_trace_enter_phase1+0xfb/0x160 Feb 06 20:35:18 saturn kernel: [a05c71a4] ? kvm_on_user_return+0x44/0x80 [kvm] Feb 06 20:35:18 saturn kernel: [811cfb91] ? SyS_ioctl+0x81/0xa0 Feb 06 20:35:18 saturn kernel: [8153b4cf] ? int_signal+0x12/0x17 Feb 06 20:35:18 saturn kernel: [8153b22d] ? system_call_fastpath+0x16/0x1b Feb 06 20:35:18 saturn kernel: ---[ end trace e7e11898e469021e ]--- I first hit this bug on the Debian 3.16.7-ckt4-3 kernel, but it's the first kernel I tried so the bug might be older. This system has
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #4 from Mark kernelbugzilla.org.mark...@dfgh.net --- I should just add that that 'code' segment in the kvm dump is identical every time, I'd be happy to try to track what is causing it, providing someone could give me some pointers to debugging that kind of stuff in more detail Code=00 01 48 c7 c0 8a b0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 0f 01 c1 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3 89 f0 31 c9 f0 0f b0 0d fb 26 e6 00 40 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #5 from Mark kernelbugzilla.org.mark...@dfgh.net --- Created attachment 166021 -- https://bugzilla.kernel.org/attachment.cgi?id=166021action=edit result of guest lsmod; identical for mono-cpu / multi-cpu -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #1 from Mark kernelbugzilla.org.mark...@dfgh.net --- Created attachment 165181 -- https://bugzilla.kernel.org/attachment.cgi?id=165181action=edit serial log during bug; when smp 1 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] New: kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 Bug ID: 92291 Summary: kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well Product: Virtualization Version: unspecified Kernel Version: 3.18.3-201.fc21.x86_64 [host], 3.13.0-39-generic [ubuntu guest] Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: kernelbugzilla.org.mark...@dfgh.net Regression: No Created attachment 165171 -- https://bugzilla.kernel.org/attachment.cgi?id=165171action=edit kvm register dumps Overview Whenever I launch a kvm guest in qemu-system-x86_64 with -smp 1 [-cpu host -enable-kvm of course], the guest kernel crashes at some stage; I've seen the kernel crash before completing boot-up, giving the recognizable kernel crash trace, as well as during 'normal' operation when the guest simply 'freezes'. The host kernel gives me an oops as well, although abrt won't let me report it now as I've got Nvidia proprietary drivers 'tainting' the kernel The bug seems non-specific to guest OS, though mainly it's been *buntu guests, with various different kernels including lowlatency, I even think I've seen the bug with a Windows guest. I've tried building qemu from git sources, no particularly noticeable difference; Steps to reproduce == 1) Start linux guest on a multicore system [AMD FX8* series CPU?] with $ qemu-system-x86_64 -m 2G -cpu host -smp 4 -enable-kvm -hda [image_file] -vga vmware 2) wait until the guest kernel crashes; virtually every time in less than 10 minutes Actual results == guest kernel crashes, host kernel gives an oops too, presumably as a result of kvm passthrough Expected results guest virtual machine should work normally then keep working normally it would be good to try to pipe dmesg from the guest to the host serial connection, in case that would assist? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #3 from Mark kernelbugzilla.org.mark...@dfgh.net --- Created attachment 165201 -- https://bugzilla.kernel.org/attachment.cgi?id=165201action=edit host cpuinfo -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 92291] kvm/guest crashes when smp 1 with AMD FX8300; with host kernel oops from abrt as well
https://bugzilla.kernel.org/show_bug.cgi?id=92291 --- Comment #2 from Mark kernelbugzilla.org.mark...@dfgh.net --- Created attachment 165191 -- https://bugzilla.kernel.org/attachment.cgi?id=165191action=edit serial log when no smp -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 90381] error when loading kvm_intel module kvm_intel unuseable
https://bugzilla.kernel.org/show_bug.cgi?id=90381 Kashyap Chamarthy kashyap...@gmail.com changed: What|Removed |Added CC||kashyap...@gmail.com --- Comment #4 from Kashyap Chamarthy kashyap...@gmail.com --- Can't reproduce this with Kernel 3.18.1 (current upstream stable) -- tested nested virtualization with KVM. If you face issues with Debian specific Kernels, you might want to report it with Debian Kernel bug tracker. Since this is upstream tracker, you might have to reproduce this with 3.18 (or with 3.19-rc1 mainline). -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 90381] error when loading kvm_intel module kvm_intel unuseable
https://bugzilla.kernel.org/show_bug.cgi?id=90381 Bhasker C V bhas...@unixindia.com changed: What|Removed |Added Hardware|All |Intel --- Comment #5 from Bhasker C V bhas...@unixindia.com --- I am using 3.18.1 on my other DELL Q15R and this crash is not happening. This crash is particularly happening on the DELL D620 core2duo machines only. kvm (as per my comment above) does work fine but crashes _only_ when loaded as modprobe kvm_intel nested=1 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 90381] New: error when loading kvm_intel module
https://bugzilla.kernel.org/show_bug.cgi?id=90381 Bug ID: 90381 Summary: error when loading kvm_intel module Product: Virtualization Version: unspecified Kernel Version: 3.18.1 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_...@kernel-bugs.osdl.org Reporter: bhas...@unixindia.com Regression: No Created attachment 161951 -- https://bugzilla.kernel.org/attachment.cgi?id=161951action=edit kernel crash message Hi, Whenever I load the kvm_intel module (on my machine which does support vmx), the kernel crashes (not a catastropic crash but the module is no longer useable). kvm_intel is unuseable. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 90381] error when loading kvm_intel module
https://bugzilla.kernel.org/show_bug.cgi?id=90381 --- Comment #1 from Bhasker C V bhas...@unixindia.com --- The machine (also can be found in the crash attachment) is Dell D620 with processor features as below: processor: 1 vendor_id: GenuineIntel cpu family: 6 model: 15 model name: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz stepping: 2 microcode: 0x5c cpu MHz: 1000.000 cache size: 2048 KB physical id: 0 siblings: 2 core id: 1 cpu cores: 2 apicid: 1 initial apicid: 1 fpu: yes fpu_exception: yes cpuid level: 10 wp: yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow bugs: bogomips: 3328.70 clflush size: 64 cache_alignment: 64 address sizes: 36 bits physical, 48 bits virtual power management: -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
