diff options
Diffstat (limited to 'results/classifier/deepseek-2/output/hypervisor/2003')
| -rw-r--r-- | results/classifier/deepseek-2/output/hypervisor/2003 | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/output/hypervisor/2003 b/results/classifier/deepseek-2/output/hypervisor/2003 new file mode 100644 index 00000000..ad233818 --- /dev/null +++ b/results/classifier/deepseek-2/output/hypervisor/2003 @@ -0,0 +1,16 @@ + +Windows guest boot happens blue screen and crash by using "-cpu Skylake-Server,+la57,phys-bits=52" +Description of problem: +We are verifying 5-level paging enabling on Windows guest. After creating Windows guest, the system boot caused blue screen and no screen interface response. + +Same QEMU parameter without **+la57,phys-bits=52** (i.e., `./qemu-system-x86_64 -accel kvm -smp 4 -m 4096 -machine q35 -drive file=Winvm5l_host5l_ept5_1698034398,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -cpu Skylake-Server -monitor pty -daemonize -vnc :40541 -device virtio-net-pci,netdev=nic0,mac=00:5b:0b:59:0d:26 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on`), the same Windows image can be booted successfully. Initially suspected this new QEMU release does not support 5-level paging related features. +Steps to reproduce: +1. Create guest by using the command + +``` +./qemu-system-x86_64 -accel kvm -smp 4 -m 4096 -machine q35 -drive file=Winvm5l_host5l_ept5_1698034398,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -cpu Skylake-Server,+la57,phys-bits=52 -monitor pty -daemonize -vnc :40541 -device virtio-net-pci,netdev=nic0,mac=00:5b:0b:59:0d:26 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on +``` +Additional information: +Suspected to be a QEMU regression issue, the first bad commit id: 14f5a7bae4cb5ca45a03e16b5bb0c5d766fd51b7. + +Latest successful version commit id: cea3ea670fe265421131aad90c36fbb87bc4d206 |