It looks like in the VM configuration file that Proxmox uses, you can use an
line to pass specific arguments to qemu/kvm. Without tinkering, I pulled the following out of what Proxmox used to launch the VM (under which it hangs as described above)
Code: Select all
/usr/bin/kvm -id 105 \
-name openvms01,debug-threads=on \
-no-shutdown \
-chardev socket,id=qmp,path=/var/run/qemu-server/105.qmp,server=on,wait=off \
-mon chardev=qmp,mode=control \
-chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 \
-mon chardev=qmp-event,mode=control \
-pidfile /var/run/qemu-server/105.pid \
-daemonize \
-smbios type=1,uuid=f023d86e-3fd2-4f1a-b1d1-d1fd08d0c4b8 \
-drive if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd \
-drive if=pflash,unit=1,id=drive-efidisk0,format=qcow2,file=/mnt/pve/nas1/images/105/vm-105-disk-0.qcow2 \
-smp 2,sockets=1,cores=2,maxcpus=2 \
-nodefaults \
-boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg \
-vnc unix:/var/run/qemu-server/105.vnc,password=on \
-cpu host,+kvm_pv_eoi,+kvm_pv_unhalt \
-m 8192 \
-readconfig /usr/share/qemu-server/pve-q35-4.0.cfg \
-device vmgenid,guid=44c8893c-2db9-4b56-89c4-a23027a4661d \
-device usb-tablet,id=tablet,bus=ehci.0,port=1 \
-chardev socket,id=serial0,path=/var/run/qemu-server/105.serial0,server=on,wait=off \
-device isa-serial,chardev=serial0 \
-device VGA,id=vga,bus=pcie.0,addr=0x1 \
-iscsi initiator-name=iqn.1993-08.org.debian:01:38cfe8efc7 \
-drive file=/mnt/pve/nas1/template/iso/X86E921OE.ISO,if=none,id=drive-ide2,media=cdrom,aio=io_uring \
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101 -device ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7 \
-drive file=/mnt/pve/nas1/images/105/vm-105-disk-1.qcow2,if=none,id=drive-sata0,format=qcow2,cache=none,aio=io_uring,detect-zeroes=on \
-device ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100 \
-drive file=/mnt/pve/nas1/images/105/vm-105-disk-2.qcow2,if=none,id=drive-sata1,format=qcow2,cache=none,aio=io_uring,detect-zeroes=on \
-device ide-hd,bus=ahci0.1,drive=drive-sata1,id=sata1 \
-netdev type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown \
-device e1000,mac=1E:53:8F:01:A0:AC,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102 \
-machine type=q35+pve0
If you know of any specific options that must or must not be present, or if you have specific qemu command lines that work, I can tinker here to get Proxmox to launch it that way from its UI. I know the args config line is used frequently when trying to boot "Hackintosh" VMs since there has to be stuff injected into SMBIOS to successfully fake Apple hardware.
Added in 3 hours 40 seconds:
I guess if someone can post a
(so that the output doesn't get right-truncated) and snip out the process where you're SUCCESSFULLY running E9.2-1 on qemu/kvm, that'd help. So far I haven't found the right combination of parameters to allow it to run.
Added in 3 hours 54 minutes 16 seconds:
Well, here's a thought...I'll just install Rocky Linux as a VM on Proxmox, then use qemu/kvm as a nested hypervisor there (I already have nested virtualization enabled in the Proxmox kernel) to install. It's not ideal, and I'll pay a small performance penalty for it, but it gets me past the problem until I can find out the actual problem on Proxmox itself.