Hi, This message would probably better fit on a user list, but as there isn't any AFAIK, so I post it here, if there is a better place for this I would be glad if someone could point that out.
I'm playing with actual versions of OVMF build straight from git, also tested with the one from kraxel.org's Jenkins CI builds (much thanks to the one who provides them!!) In comparison of a OVMF build from around November 2015 (I can look up the exact version if needed) I caught a few changes regarding the boot order and its settings. Is it by design that not all devices listed in the boot order section get probed (anymore)? E.g. it tries only EFI CD/ROM which is the first by default and then gives up printing an error and after an timeout I get the UEFI shell. If I open the UEFI settings and directly choose "EFI Misc Device" I get the working grub2 of my VM, but this was not needed in the earlier version, there it probed all devices until something "bootable" found and only if all were tried it did throw an error. Am I'm missing something here, or using it incorrect? Also this behaviour wouldn't be a slight nuisance if I could get the efivars store permanent, so that I could save the boot order. I'm using this command to launch OVMF (I stripped it a little down for readability, removed spice/vnc sockets and devices): > /usr/bin/kvm -id 7001 > -chardev > socket,id=qmp,path=/var/run/qemu-server/7001.qmp,server,nowait -mon > chardev=qmp,mode=control > -pidfile /var/run/qemu-server/7001.pid > -smbios type=1,uuid=a570abd4-c963-47da-a376-1eff898a1a70 > -global driver=cfi.pflash01,property=secure,value=on > -drive > if=pflash,format=raw,unit=0,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd > -drive > if=pflash,format=raw,unit=1,file=/var/lib/vz/images/7001/vm-7001-efi.raw > -name disposable-1 > -smp 4,sockets=1,cores=4,maxcpus=4 > -nodefaults > -boot menu=on,strict=on,reboot-timeout=1000 > -vga qxl > -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi > -m 6196 -k de -readconfig /usr/share/qemu-server/pve-q35.cfg > -chardev socket,path=/var/run/qemu-server/7001.qga,server,nowait,id=qga0 > -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 > -drive > file=/var/lib/vz/images/7001/vm-7001-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on > -device > virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 With this /var/lib/vz/images/7001/vm-7001-efi.raw never gets changed/written and any settings I make won't survive a reboot, or better the survive a reboot but no (graceful) poweroff - power on cycle. I checked the OVMF README from git and tried a few possibilities, e.g. at first I did not used "-global driver=cfi.pflash01,property=secure,value=on" or did not used the "unit=X" [X = (0,1)] in the pflash drives. I'm using Qemu 2.5 and checked also occasionally tested with 2.6 (rc1-3). I tried skimming through the commits but this repo is really active, that in combination that I'm not quite able to just understand all commits lead to nothing found out if/where there were changes made regarding the boot order/probing. For the persistence efivars problem I'm quite sure I miss something and the problem is me using it wrong... I'd be glad for any help regarding this! :-) best regards, - Thomas _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
