From d0c85e36e4de67af628d54e9ab577cc3fad7796a Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Thu, 3 Jul 2025 07:27:52 +0000 Subject: add deepseek and gemma results --- results/classifier/gemma3:12b/hypervisor/1456819 | 101 +++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 results/classifier/gemma3:12b/hypervisor/1456819 (limited to 'results/classifier/gemma3:12b/hypervisor/1456819') diff --git a/results/classifier/gemma3:12b/hypervisor/1456819 b/results/classifier/gemma3:12b/hypervisor/1456819 new file mode 100644 index 000000000..c0e472cdb --- /dev/null +++ b/results/classifier/gemma3:12b/hypervisor/1456819 @@ -0,0 +1,101 @@ + +OVMF, Hyper-V, virtio, Win7 incompatibility + +Host kernel: v4.1-rc4 +QEMU: qemu.git tag v2.3.0 +OVMF: edk2.git-ovmf-x64-0-20150518.b1004.g54ae9c0.noarch +libvirt: 1.2.13.1-1.fc21.x86_64 +Guest: en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso + +If I attempt to use the above software versions to start a VM install, I hit one of two problems: + +(a) If I use a virtio NIC, the VM aborts with an error similar to: + +qemu-system-x86_64: Guest moved used index from 22 to 0 + +(b) If I use an emulated (e1000) NIC, the VM switches to a black screen when I should have the dancing windows boot animation logo + +Both of these are resolved by switching off ALL Hyper-V enlightenments as shown in the below XML. Enabling any one of them results in the above behavior. + +This problem is only seen with OVMF, removing the loader and nvram directives below allows all Hyper-V enlightenments to be enabled, with or without a virtio NIC. + + + win7-ovmf-demo + a42b96e9-e95d-42c6-9f4a-0236f3d38d95 + 4194304 + 4194304 + 2 + + hvm + /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd + /var/lib/libvirt/qemu/nvram/win7-ovmf-demo_VARS.fd + + + + + + + + + + + + + + + + + + destroy + restart + restart + + + + + + /usr/local/bin/qemu-system-x86_64 + + + + + + +
+ + +
+ + + +
+ + + +
+ + + +
+ + + +
+ + + + + +
+ + + + + +