[openstack-dev] [nova] how does UEFI booting of VM manage per-instance copies of OVMF_VARS.fd ?
Waines, Greg
Greg.Waines at windriver.com
Thu Sep 28 16:08:33 UTC 2017
Any info on this ?
I did launch a VM with UEFI booting and did not see any copy of OVMF_VARS.fd proactively copied into /etc/nova/instances/<UUID>/ .
Maybe Nova only does that on a change to OVMF_VARS.fd ???
( haven’t figured out how to do that )
anyways any info or pointers would be appreciated,
thanks,
Greg.
From: Greg Waines <Greg.Waines at windriver.com>
Reply-To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Date: Wednesday, September 27, 2017 at 9:09 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [nova] how does UEFI booting of VM manage per-instance copies of OVMF_VARS.fd ?
Hey there ... a question about UEFI booting of VMs.
i.e.
glance image-create --file cloud-2730. qcow --disk-format qcow2 --container-format bare --property “hw-firmware-type=uefi” --name clear-linux-image
in order to specify that you want to use UEFI (instead of BIOS) when booting VMs with this image
i.e. /usr/share/OVMF/OVMF_CODE.fd
/usr/share/OVMF/OVMF_VARS.fd
and I believe you can boot into the UEFI Shell, i.e. to change UEFI variables in NVRAM (OVMF_VARS.fd) by
booting VM with /usr/share/OVMF/UefiShell.iso in cd ...
e.g. to changes Secure Boot keys or something like that.
My QUESTION ...
· how does NOVA manage a unique instance of OVMF_VARS.fd for each instance ?
o i believe OVMF_VARS.fd is suppose to just be used as a template, and
is supposed to be copied to make a unique instance for each VM that UEFI boots
o how does NOVA manage this ?
§ e.g. is the unique instance of OVMF_VARS.fd created in
/etc/nova/instances/<UUID>/ ?
o ... and does this get migrated to another compute if VM is migrated ?
Greg.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170928/d1c1e640/attachment.html>
More information about the OpenStack-dev
mailing list