diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/hypervisor/266 | 2 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/hypervisor/2665 | 12 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/hypervisor/2669 | 19 |
3 files changed, 33 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/266 b/results/classifier/gemma3:12b/hypervisor/266 new file mode 100644 index 000000000..96c43e11a --- /dev/null +++ b/results/classifier/gemma3:12b/hypervisor/266 @@ -0,0 +1,2 @@ + +'mtfsf' instruction can clear FI incorrectly diff --git a/results/classifier/gemma3:12b/hypervisor/2665 b/results/classifier/gemma3:12b/hypervisor/2665 new file mode 100644 index 000000000..e1525e1bf --- /dev/null +++ b/results/classifier/gemma3:12b/hypervisor/2665 @@ -0,0 +1,12 @@ + +target/arm: cannot boot when CPU supports SME +Description of problem: +On macOS 15.2 beta, Apple's Hypervisor.framework exposes the SME feat flag to QEMU. As a result, in `arm_cpu_sme_finalize`, `cpu_isar_feature(aa64_sme, cpu)` returns true and the program will always exit with the following: + +``` +qemu-aarch64-softmmu: cannot disable sme4224 +All SME vector lengths are disabled. +With SME enabled, at least one vector length must be enabled. +``` + +This is because `vq_supported` and `vq_init` are both 0 as they are not initialized anywhere. It seems that in the original commit e74c097638d38b46d9c68f11565432034afc0ad0 the only place `cpu->sme_vq.supported` is initialized is with `aarch64_max_initfn` when KVM and HVF are not used as the backend. diff --git a/results/classifier/gemma3:12b/hypervisor/2669 b/results/classifier/gemma3:12b/hypervisor/2669 new file mode 100644 index 000000000..1957c7477 --- /dev/null +++ b/results/classifier/gemma3:12b/hypervisor/2669 @@ -0,0 +1,19 @@ + +CPU Hotplug (Host Model) Causes the Windows VM to BSOD +Description of problem: +The QEMU runs on a host with the Intel(R) Xeon(R) CPU E3-1230 v6 CPU which supports Software Guard Extension (SGX). I start a VM with Windows Server 2019 inside and with `-cpu host,...`. When I attempts to hotplug additional CPU (when the VM is running), the OS issues a bug check 0x3e (`MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED`). The problem is that the newly hotplugged CPU is not evaluated as "equivalent enough" compared to the already present CPUs. I did some more digging and reverse engineering and it looks like the CPU being hotplugged has SGX turned off. This seems to be fixed when the VM reboots. + +I tried to disable SGX through `-cpu host,-sgx` which helps (the VM successfully accepts the hotplugged CPU), however, `+sgx` does not help (seems to have no effect on the CPU being hotplugged). + +My goal is to be able to hotplug CPUs even when the host CPU supports SGX. + +I tested with QEMU 8.0.0, 9.1.0, 9.1.1 and 9.1.50 (current master) but with no luck. +Steps to reproduce: +1. Create a simple Windows VM, +2. start the VM, +3. use `qpm-shell` to hotplug a CPU (https://www.qemu.org/docs/master/system/cpu-hotplug.html). + +I can provide you the VM as well but its image (QCOW2) has around 10G in size. + +Best regards +Martin Dráb |