Problems with iPXE pxe-virtio.rom and https

[Alwin]

What does qm showcmd 114 --pretty show?

 

[phenomax]

 

[Alwin]

The romfile has been added and either when network boot starts or you run it through the boot menu (ESC), it will boot from the custom iPXE. I tested it on PVE 5.4 and 6.0 and it worked both times.

 

[phenomax]

Does the iPXE boot screen show https as a feature?

 

[Alwin]

Does the iPXE boot screen show https as a feature?

Yes.

 

[phenomax]

Ok. So I investigated some more:
When I don't set qm set 114 -machine pc-i440fx-3.0.pxe, the romfile is not specified on the VM's device config:

Spoiler: VMConfig

# qm showcmd 114 --pretty
/usr/bin/kvm \
  -id 114 \
  -name test \
  -chardev 'socket,id=qmp,path=/var/run/qemu-server/114.qmp,server,nowait' \
  -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/114.pid \
  -daemonize \
  -smbios 'type=1,uuid=a991fea5-3820-4b7d-96dc-6a10fd6da099' \
  -smp '1,sockets=1,cores=1,maxcpus=1' \
  -nodefaults \
  -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' \
  -vnc unix:/var/run/qemu-server/114.vnc,x509,password \
  -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce \
  -m 512 \
  -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' \
  -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' \
  -device 'vmgenid,guid=fb496ddb-d9e7-485f-84cf-43341e7dbe9c' \
  -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' \
  -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' \
  -device 'VGA,id=vga,bus=pci.0,addr=0x2' \
  -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' \
  -iscsi 'initiator-name=iqn.1993-08.org.debian:01:2996a3575a32' \
  -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' \
  -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' \
  -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' \
  -drive 'file=/var/lib/vz/images/114/vm-114-disk-0.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=native,detect-zeroes=on' \
  -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=300' \
  -netdev 'type=tap,id=net0,ifname=tap114i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \
  -device 'virtio-net-pci,mac=A6:B2:3E:FF:DB:6A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=100' \
  -machine 'type=pc'

Which leads to the old iPXE boot (without the HTTPS support from the custom rom)

However when setting the machine to the v3 i440fx, network boot does not show up in the boot menu:

Spoiler: VMConfig with machine entry

# qm showcmd 114 --pretty
/usr/bin/kvm \
  -id 114 \
  -name test \
  -chardev 'socket,id=qmp,path=/var/run/qemu-server/114.qmp,server,nowait' \
  -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/114.pid \
  -daemonize \
  -smbios 'type=1,uuid=a991fea5-3820-4b7d-96dc-6a10fd6da099' \
  -smp '1,sockets=1,cores=1,maxcpus=1' \
  -nodefaults \
  -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' \
  -vnc unix:/var/run/qemu-server/114.vnc,x509,password \
  -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce \
  -m 512 \
  -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' \
  -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' \
  -device 'vmgenid,guid=fb496ddb-d9e7-485f-84cf-43341e7dbe9c' \
  -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' \
  -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' \
  -device 'VGA,id=vga,bus=pci.0,addr=0x2' \
  -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' \
  -iscsi 'initiator-name=iqn.1993-08.org.debian:01:2996a3575a32' \
  -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' \
  -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' \
  -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' \
  -drive 'file=/var/lib/vz/images/114/vm-114-disk-0.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=native,detect-zeroes=on' \
  -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=300' \
  -netdev 'type=tap,id=net0,ifname=tap114i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \
  -device 'virtio-net-pci,mac=A6:B2:3E:FF:DB:6A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=100,romfile=pxe-virtio.rom' \
  -machine 'type=pc-i440fx-3.0'

Can you tell me, why the network does not show up as boot option then?

 

[Alwin]

Please upgrade to the latest 5.4 packages, I conducted my tests on an updated system.

 

[phenomax]

I am on the latest 5.4 release.

 

[Alwin]

Hm... then I don't know, below my vm config on PVE 5.4-13.

bootdisk: scsi0
cores: 1
ide2: none,media=cdrom
machine: pc-i440fx-3.0.pxe
memory: 512
net0: virtio=BA:6F:12:78:0A:76,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local:101/vm-101-disk-0.raw,size=1G
scsihw: virtio-scsi-pci
smbios1: uuid=ce6f9d72-5da5-470d-975e-6b01997bc020
sockets: 1
vmgenid: b0259f69-d7dc-49b6-8718-f12db3c71efb

 

[phenomax]

Sorry to bother you again: Could you please walk me through the exact steps you took in order to create and boot your vm? I have upgraded to Proxmox V6

 

[Alwin]

Sorry to bother you again: Could you please walk me through the exact steps you took in order to create and boot your vm?

Default settings on the wizard, with a 1GB disk and the updated romfile in place. Is the build log giving any hints?