On 30 January 2014 22:57, Jamie Strandboge <ja...@ubuntu.com> wrote: > apport information > > ** Tags added: apport-collected saucy > > ** Description changed: > > On up to date 14.04, if I create a vm with: > virt-install --connect=qemu:///system --name=sb-saucy-amd64 --arch=x86_64 > --ram=768 \ > --disk=path=<path > to>/sb-saucy-amd64.qcow2,size=8,format=qcow2,bus=ide,sparse=True \ > --virt-type=kvm --accelerate --hvm --cdrom=<path > to>/saucy-desktop-amd64.iso \ > --os-type=linux --os-variant=generic26 --graphics=vnc > --network=network=default,model=virtio \ > --video=cirrus --noreboot --boot=loader=OVMF.fd >
I believe --boot=loader=OVMF.fd is not correct option. A valid one is --boot-loader=OVMF.fd. Nonetheless, that wouldn't be ideal way to execute OVMF.fd. It's better to make a copy of OVMF.fd and provision the copy to qemu as a -pflash copy-of-OVMF.fd in Read-Write mode, cause then one can store all variables & secureboot keys which survive a reboot. Does virt-install support provisioning "-pflash" devices? -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274376 Title: 14.04 ovmf causes oops when running update-grub under kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1274376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
