Skip to contentSkip to conversation

New: [nested virt] L2 Windows guest can't boot up ('-cpu host' to start L1)

Bug 58921 [email protected] 1 participant 5 messages May 29, 2013 – Nov 13, 2013 KVM

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=58921

Summary: [nested virt] L2 Windows guest can't boot up ('-cpu
host' to start L1)
Product: Virtualization
Version: unspecified
Kernel Version: 3.10.0-rc1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: [email protected]
ReportedBy: [email protected]
Regression: Yes

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows): Windows
kvm.git next branch Commit:db6ae6158186a17
qemu-kvm Commit:b5803aa3583e82e513
Host Kernel Version:3.9.0-rc3
Hardware:SandyBridge-EP

Bug detailed description:
--------------------------
In 'kvm on kvm' nested virtualization environment,if I start L1 with '-cpu host', a Windows (e.g. Win7) guest can't boot up as L2 guest.

note:
1. when creating a linux guest as L2 guest, L2 guest boot up fine
2. if starting L1 with '-cpu qemu64,+vmx', L2 Windows can boot up.
3. this should be a kvm kernel bug:

kvm next + qemu-kvm   =  result
db6ae615 + b5803aa3   = bad
188424ba + b5803aa3   = good

Reproduce steps:
----------------
1.create L1 guests:
qemu-system-x86_64 --enable-kvm -m 10240 -smp 8 -net nic,macaddr=00:12:45:67:2B:1C -net tap,script=/etc/kvm/qemu-ifup nested-kvm-rhel6u4.qcow -cpu host
2. create L2 guests:
qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none win7.img

Current result:
----------------
L2 guest (win7 guest) failed to boot up.

Expected result:
----------------
L2 guest (win7 guest) boot up fine

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
#1 lore raw

[Bug 58921] [nested virt] L2 Windows guest can't boot up ('-cpu host' to start L1)

https://bugzilla.kernel.org/show_bug.cgi?id=58921

Nadav Har'El <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Nadav Har'El <[email protected]> 2013-06-03 10:48:19 --- This is a dup of bug 53641

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
#2 lore raw

[Bug 58921] [nested virt] L2 Windows guest can't boot up ('-cpu host' to start L1)

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=58921

Zhou, Chao <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from Zhou, Chao <[email protected]> --- this commit fixed the bug:
commit cd2633c59b6f511effb53e10fa2c1e20b1cec1e7

Author: Jan Kiszka <[email protected]>
Date:   Wed Oct 23 17:42:15 2013 +0100

nVMX: Fix pick-up of uninjected NMIs

__vmx_complete_interrupts stored uninjected NMIs in arch.nmi_injected, not arch.nmi_pending. So we actually need to check the former field in vmcs12_save_pending_event. This fixes the eventinj unit test when run in nested KVM.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
#3 lore raw

[Bug 58921] [nested virt] L2 Windows guest can't boot up ('-cpu host' to start L1)

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=58921

Alan <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]
         Resolution|---                         |CODE_FIX
Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.