Add a few words about UEFI user images
Change-Id: I37a686e6f48a422d38ac5921a188d894519b7530
This commit is contained in:
parent
2a7871d060
commit
4c4c7a869a
@ -23,6 +23,10 @@ the end user. There are two types of user images:
|
||||
The kernel/initramfs pair must not be used with whole disk images,
|
||||
otherwise they'll be mistaken for partition images.
|
||||
|
||||
Many distributions publish their own cloud images. These are usually whole disk
|
||||
images that are built for legacy boot mode (not UEFI), with Ubuntu being an
|
||||
exception (they publish images that work in both modes).
|
||||
|
||||
Building user images
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
@ -54,6 +58,12 @@ deployment and the actual OS which the user is going to run.
|
||||
|
||||
$ disk-image-create ubuntu vm dhcp-all-interfaces -o my-image
|
||||
|
||||
… with an EFI partition:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
$ disk-image-create ubuntu vm block-device-efi dhcp-all-interfaces -o my-image
|
||||
|
||||
The partition image command creates ``my-image.qcow2``,
|
||||
``my-image.vmlinuz`` and ``my-image.initrd`` files. The ``grub2`` element
|
||||
in the partition image creation command is only needed if local boot will
|
||||
|
Loading…
Reference in New Issue
Block a user