Unable to boot from CDROM with OVMF BIOS since 4.3

[FuriousGeorge]

Not sure what happened, but creating a VM and changing it to OVMF bios now renders it unable to boot from the CD ROM. If I change it back to SeaBIOS it will boot the CD ROM again.

After I create the VM I add an EFI disk. At first boot I dump out to the shell. If I go into the BIOS and manually select the CD ROM device to boot from, the screen seems to quickly refresh, and nothing else happens.

There is no output indicating an error with the CDROM device.

I've tried a 64-bit Win7 and 8.1 so far, with the same result.

 

[tom]

works here.

make sure you have latest Proxmox VE version.
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.3

if you still have issues, please post:

> pveversion -v

and your VM config:

> qm config VMID

 

[FuriousGeorge]

pveversion -v
proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve)
pve-manager: 4.3-10 (running version: 4.3-10/7230e60f)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.21-1-pve: 4.4.21-71
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-47
qemu-server: 4.0-94
pve-firmware: 1.1-10
libpve-common-perl: 4.0-80
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-68
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.3-14
pve-qemu-kvm: 2.7.0-6
pve-container: 1.0-81
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

# qm config 999
bios: ovmf
boot: dcn
bootdisk: virtio0
cores: 12
efidisk0: local-zfs:vm-999-disk-1,size=128K
ide2: local:iso/Win7SP1U64.iso,media=cdrom
memory: 2048
name: test
net0: virtio=6A:47:20:0B:9F:DB,bridge=vmbr0
numa: 1
ostype: win8
scsihw: virtio-scsi-pci
smbios1: uuid=b7dbdb97-af12-424a-83b0-a36532ab0e2e
sockets: 1
virtio0: fastpool:vm-999-disk-1,cache=unsafe,size=240G

/usr/bin/kvm -id 999 \
-chardev 'socket,id=qmp,path=/var/run/qemu-server/999.qmp,server,nowait' \
-mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/999.pid \
-daemonize \
-smbios \'type=1,uuid=b7dbdb97-af12-424a-83b0-a36532ab0e2e' \
-drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/kvm/OVMF_CODE-pure-efi.fd' \
-drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/zvol/rpool/data/vm-999-disk-1' \
-name test -smp '12,sockets=1,cores=12,maxcpus=12' \
-nodefaults \
-boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' \
-vga std \
-vnc unix:/var/run/qemu-server/999.vnc,x509,password \
-no-hpet \
-cpu 'kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' \
-m 2048 \
-object 'memory-backend-ram,id=ram-node0,size=2048M' -numa 'node,nodeid=0,cpus=0-11,memdev=ram-node0' \
-k en-us -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 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' \
-device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:209b855ce18e' \
-drive 'file=/var/lib/vz/template/iso/Win7SP1U64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' \
-device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100' \
-drive 'file=/dev/zvol/fastpool/vm-999-disk-1,if=none,id=drive-virtio0,cache=unsafe,format=raw,aio=threads,detect-zeroes=on' \
-device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=200' \
-netdev 'type=tap,id=net0,ifname=tap999i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \
-device 'virtio-net-pci,mac=6A:47:20:0B:9F:DB,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' \
-rtc 'driftfix=slew,base=localtime' \
-global 'kvm-pit.lost_tick_policy=discard'

I added a CDROM to an existing VM, and I got the same result. I no longer have any 4.2 PMs to test with at hand, but I'm sure the existing VM was created from a CD-ROM with 4.2. That said, I don't see any obvious change in the invocation of kvm.

I also tested it on another 4.3-latest server, with the same result. Maybe a bug? I'm going to try to install the OS using SeaBios and then switch to OVMF, which I don't imagine will be that difficult.

 

[FuriousGeorge]

I can't imagine what I might be doing wrong. I just installed using SeaBios, switched to EFI, and was surprised to see the CD boot. However, the disk now would not.

I reinstalled the OS, and everything works again.

I'm going to try and repeat the process, and update this thread. I didn't want anyone to waste their time until then.

 

[FuriousGeorge]

I was not able to get the Windows 8.1 VM working with OVMF. I'm not sure what I did differently before. Maybe more importantly, I realize now the problem is not isolated to cd rom disks. VMs in this state are also unable to boot virtual hard disks. Switching to SeaBios solves the problem every time.

Here is the working Windows 10 vm's vmid.conf.

# qm config 112
balloon: 6144
bios: ovmf
bootdisk: virtio0
cores: 12
efidisk0: local-zfs:vm-112-disk-2,size=128K
memory: 8192
name: TEST1
net0: virtio=9E:09:38:D5:41:F6,bridge=vmbr0
numa: 1
ostype: win8
scsihw: virtio-scsi-pci
smbios1: uuid=9df38ec5-009e-4249-ab2e-fe250104b3de
sockets: 1
virtio0: local-zfs:vm-112-disk-1,cache=writeback,size=240G

... and here is the non-bootable Windows 7 VM's:

qm config 106
balloon: 6144
bios: ovmf
boot: cdn
bootdisk: virtio0
cores: 12
efidisk0: local-zfs:vm-106-disk-2,size=128K
memory: 8192
name: TEST2
net0: virtio=8A:69:E6:62:13:78,bridge=vmbr0
numa: 1
ostype: win8
scsihw: virtio-scsi-pci
smbios1: uuid=6faa9cd8-2e34-40c9-ad0c-019b71bc3215
sockets: 1
virtio0: local-zfs:vm-106-disk-1,cache=writeback,size=240G

I have no idea what the issue might be.