Comment 20 for bug 1274376

On 4 February 2014 09:46, Dimitri John Ledkov <email address hidden> wrote:
> On 30 January 2014 22:57, Jamie Strandboge <email address hidden> 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.

Bah, checked my old scripts and manual, the
--boot=loader=path/to/ovmf.fd is correct syntax.

> 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.