summary refs log tree commit diff stats
path: root/gitlab/issues/target_i386/host_missing/accel_KVM/2003.toml
blob: fb83b09a93150cb40bbb4bc83b233b26ba7f17b3 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
id = 2003
title = "Windows guest boot happens blue screen and crash by using \"-cpu Skylake-Server,+la57,phys-bits=52\""
state = "closed"
created_at = "2023-11-24T06:21:30.759Z"
closed_at = "2023-12-04T08:02:44.354Z"
labels = ["accel: KVM", "target: i386"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/2003"
host-os = "CentOS Stream 9, Linux"
host-arch = "x86"
qemu-version = "QEMU emulator version 8.1.91 (v8.2.0-rc1), commit id: 8fa379170c2a12476021f5f50d6cf3f672e79e7b"
guest-os = "Windows 10 Pro, Version 1607, 64-bit"
guest-arch = "x86"
description = """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."""
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 = """Suspected to be a QEMU regression issue, the first bad commit id: 14f5a7bae4cb5ca45a03e16b5bb0c5d766fd51b7.

Latest successful version commit id: cea3ea670fe265421131aad90c36fbb87bc4d206"""