summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/hypervisor/934
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/hypervisor/934
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloademulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/hypervisor/934')
-rw-r--r--results/classifier/gemma3:12b/hypervisor/93446
1 files changed, 46 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/934 b/results/classifier/gemma3:12b/hypervisor/934
new file mode 100644
index 00000000..92b98d36
--- /dev/null
+++ b/results/classifier/gemma3:12b/hypervisor/934
@@ -0,0 +1,46 @@
+
+VM execution fails for tianocore edk2 ovmf uefi based image on windows whpx
+Description of problem:
+Cannot do a UEFI tianocore boot of image with linux installation.
+
+I think the BIOS/UEFI/firmware when run inside a virtual-machine should be oblivious to the type of hypervisor, just probe and enable the emulated hardware. Maybe WHPX is not enabling pflash devices properly. 
+
+My goal is to create a 40Gb fedora linux image with a on-image UEFI boot sequence that I can 
+1. native boot using ventoy (works)
+2. boot using kvm/qemu in linux (works)
+3. boot using whpx/qemu in windows (no success yet)
+
+My original sequence of steps to reproduce was.
+1. Under Linux, in qemu-vm, create a bootable linux image by installing from the fedora livecd installer
+2. Confirm qemu-VM/fedora installation/UEFI boot works fine under Linux/kvm/qemu. One can see tianocore logo booting up.
+3. reboot to windows
+4. attempt to boot with analogous windows qemu command. confirm boot failure and error message
+5. remove ```-accel whpx``` and rerun, confirm boot succeeds with tianocore image, albeit un-accelarated
+
+It turns out the image creation is not required.
+
+The below works under linux
+```
+XDG_RUNTIME_DIR=/run/user/1000 qemu-system-x86_64 -cpu qemu64 -m 4096 -machine "type=q35" -accel "kvm" -smp "sockets=1,cores=8,threads=1" -boot d -drive "index=0,if=pflash,format=raw,readonly=on,file=/usr/share/edk2/ovmf/OVMF_CODE.fd" -drive "index=1,if=pflash,format=raw,file=/vol/15KJ_Images/vstorage/OVMF_VARS.fd" -drive "index=2,format=raw,file=/vol/15KJ_Images/transcend/m02_lnx.raw.img.vtoy"  -device "virtio-vga-gl" -display "gtk,gl=on" -rtc "base=utc" -net "user" -device "virtio-net,netdev=vmnic" -netdev "user,id=vmnic,net=192.168.20.0/24,dns=192.168.20.3,dhcpstart=192.168.20.15" -qmp tcp:0:5955,server,nowait
+```
+The below does not work under windows
+```
+qemu-system-x86_64 -cpu qemu64 -m 4096 -machine "type=q35,kernel-irqchip=off" -accel whpx -smp "sockets=1,cores=8,threads=1" -boot d -drive "index=0,if=pflash,format=raw,readonly=on,file=C:/vol/scoop_01/scoopg/apps/qemu/current/share/edk2-x86_64-code.fd" -drive "index=1,if=pflash,format=raw,file=E:/vstorage/OVMF_VARS.fd" -drive "index=2,if=virtio,media=disk,format=raw,file=H:\m01_lnx.raw.img" -drive "index=3,if=virtio,media=disk,format=raw,file=H:\gkpics01.raw.img"  -drive "index=4,if=virtio,media=disk,format=vhdx,file=E:\test\sgdata.vhdx" -display gtk -vga virtio -rtc base=utc -netdev user,id=vmnic1,net=192.168.20.0/24,dns=192.168.20.3,dhcpstart=192.168.20.15 -device virtio-net,netdev=vmnic1  -qmp "tcp:127.0.0.1:5955,server,nowait"
+:
+Windows Hypervisor Platform accelerator is operational
+qemu-system-x86_64: WHPX: Failed to emulate MMIO access with EmulatorReturnStatus: 2
+qemu-system-x86_64: WHPX: Failed to exec a virtual processor
+```
+
+The image does boot if one removes the hardware hypervisor argument ```-accel whpx```
+Steps to reproduce:
+The full qemu command with disk images is not required. Just the accel whpx and the pflash devices are sufficient.
+1. Confirm that the VM does not execute with the command
+```
+qemu-system-x86_64 -cpu qemu64 -m 4096 -machine "type=q35,kernel-irqchip=off" -accel whpx -boot c -drive "index=0,if=pflash,format=raw,readonly=on,file=C:/vol/scoop_01/scoopg/apps/qemu/current/share/edk2-x86_64-code.fd"
+```
+2. Confirm that the VM does execute and tianocore logo shoes up when ```-accel whpx ``` is removed.
+Additional information:
+- In the planned changes of Fedora 37, going forward, fedora installer will no longer support installing fresh to machines with legacy BIOS and will necessarily require UEFI boot. This means that there is urgency in allowing this mode of booting. 
+  - https://fedoraproject.org/wiki/Releases/37/ChangeSet
+  - https://fedoraproject.org/wiki/Changes/DeprecateLegacyBIOS