Skip to contentSkip to conversation

New: [Nested VM] Failed to boot L2 Windows guest on L1 Windows guest

Bug 218257 [email protected] 2 participants 4 messages Dec 12, 2023 – Apr 15, 2024 KVM

lore
Share & tools
lore
#0 lore raw

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

            Bug ID: 218257
           Summary: [Nested VM] Failed to boot L2 Windows guest on L1
                    Windows guest
           Product: Virtualization
           Version: unspecified
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: kvm
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: Yes
           Bisected a1c288f87de7aff94e87724127eabb6cdb38b120
         commit-id:

Created attachment 305591
--> https://bugzilla.kernel.org/attachment.cgi?id=305591&action=edit
Captured failed screen on L2 guest

Environment:
------------
CPU Architecture: x86_64
Host OS: CentOS Stream 9
Guest OS L1: Windows 10 Pro (10.0.18362 N/A Build 18362), x64-based PC Guest OS L2: Windows 10 Enterprises (10.0.10240 N/A Build 10240), x64-based PC kvm.git next branch commit id: e9e60c82fe391d04db55a91c733df4a017c28b2f qemu-kvm commit id:
Host Kernel Version: 6.7.0-rc1
Hardware: Sapphire Rapids

Bug detailed description:
--------------------------
To verify two nested Windows guests scenarios, we used Windows image to create L1 guest, then failed to boot L2 Windows guest on L1 guest. The error screen is captured in attachment.

Note: this is suspected to be a KVM Kernel bug by bisect the different commits:

kvm next                                 + qemu-kvm   = result
a1c288f87de7aff94e87724127eabb6cdb38b120 + d451e32c   = bad
e1a6d5cf10dd93fc27d8c85cd7b3e41f08a816e6 + d451e32c   = good

Reproduce steps:
----------------
1.create L1 guests:
qemu-system-x86_64 -accel kvm -cpu host -smp 8 -drive file=L1_VMWARE_L2_WIN10.img,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -m 8192 -monitor pty -daemonize -vnc :7 -device virtio-net-pci,netdev=nic0,mac=00:05:66:34:98:e6 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on
2. create L2 guests:
Using VMware Workstation to boot Win10 guest.

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

Expected result:
----------------
L2 guest (Windows 10 guest) boot up successfully.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#1 lore raw
Quoted 17 lines · On Tue, Dec 12, 2023, [email protected] wrote:

Environment:
------------
CPU Architecture: x86_64
Host OS: CentOS Stream 9
Guest OS L1: Windows 10 Pro (10.0.18362 N/A Build 18362), x64-based PC Guest OS L2: Windows 10 Enterprises (10.0.10240 N/A Build 10240), x64-based PC kvm.git next branch commit id: e9e60c82fe391d04db55a91c733df4a017c28b2f qemu-kvm commit id:
Host Kernel Version: 6.7.0-rc1
Hardware: Sapphire Rapids

Bug detailed description:
--------------------------
To verify two nested Windows guests scenarios, we used Windows image to create L1 guest, then failed to boot L2 Windows guest on L1 guest. The error screen is captured in attachment.

Quoted 4 lines

Note: this is suspected to be a KVM Kernel bug by bisect the different commits:

kvm next                                 + qemu-kvm   = result
a1c288f87de7aff94e87724127eabb6cdb38b120 + d451e32c   = bad
e1a6d5cf10dd93fc27d8c85cd7b3e41f08a816e6 + d451e32c   = good

Assuming git bisect didn't point at exactly the merge commit, can you please bisect to the exact commit, instead of the merge commit? I.e.

git bisect start
git bisect bad a1c288f87de7aff94e87724127eabb6cdb38b120 git bisect good e1a6d5cf10dd93fc27d8c85cd7b3e41f08a816e6

and go from there.

Hopefully it isn't the merge commit that's being blamed, as that will be far more painful to figure out.

#2 lore raw

[Bug 218257] [Nested VM] Failed to boot L2 Windows guest on L1 Windows guest

In reply to [email protected]

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

--- Comment #1 from Sean Christopherson ([email protected]) ---

Quoted 20 lines · On Tue, Dec 12, 2023, [email protected] wrote:

Environment:
------------
CPU Architecture: x86_64
Host OS: CentOS Stream 9
Guest OS L1: Windows 10 Pro (10.0.18362 N/A Build 18362), x64-based PC Guest OS L2: Windows 10 Enterprises (10.0.10240 N/A Build 10240), x64-based PC
kvm.git next branch commit id: e9e60c82fe391d04db55a91c733df4a017c28b2f qemu-kvm commit id:
Host Kernel Version: 6.7.0-rc1
Hardware: Sapphire Rapids

Bug detailed description:
--------------------------
To verify two nested Windows guests scenarios, we used Windows image to create
L1 guest, then failed to boot L2 Windows guest on L1 guest. The error screen is
captured in attachment.

Quoted 5 lines

Note: this is suspected to be a KVM Kernel bug by bisect the different commits:

kvm next                                 + qemu-kvm   = result
a1c288f87de7aff94e87724127eabb6cdb38b120 + d451e32c   = bad
e1a6d5cf10dd93fc27d8c85cd7b3e41f08a816e6 + d451e32c   = good

Assuming git bisect didn't point at exactly the merge commit, can you please bisect to the exact commit, instead of the merge commit? I.e.

git bisect start
git bisect bad a1c288f87de7aff94e87724127eabb6cdb38b120 git bisect good e1a6d5cf10dd93fc27d8c85cd7b3e41f08a816e6

and go from there.

Hopefully it isn't the merge commit that's being blamed, as that will be far more
painful to figure out.

Signature · 4 lines
You may reply to this email to add a comment.

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

[Bug 218257] [Nested VM] Failed to boot L2 Windows guest on L1 Windows guest

In reply to [email protected]

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

Ma Xiangfei ([email protected]) changed:

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

--- Comment #2 from Ma Xiangfei ([email protected]) --- This issue cannot reproduce in the latest kernel. KVM commit/branch: 9bc60f73
Qemu commit/branch: 927284d6
Host Kernel: 6.9.0-rc1
Host OS: CentOS 9

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.