diff --git a/doc/common/section_glance_cli_manage_images.xml b/doc/common/section_glance_cli_manage_images.xml
index a9d35aa76e..63ca942195 100644
--- a/doc/common/section_glance_cli_manage_images.xml
+++ b/doc/common/section_glance_cli_manage_images.xml
@@ -9,11 +9,10 @@
who can upload and manage images. The operator might restrict
image upload and management to only cloud administrators or
operators.
- You can upload images through the glance client or the Image
- Service API. You can also use the nova client to list images,
- set and delete image metadata, delete images, and take a
- snapshot of a running instance to create an image. After you
- upload an image, you cannot change it.
+ You can upload images through the glance client or the Image Service API. You can also use
+ the nova client to list images, set, and delete image metadata, delete images, and take a
+ snapshot of a running instance to create an image. After you upload an image, you cannot
+ change it.For details about image creation, see the Virtual Machine Image
@@ -257,19 +256,76 @@
- To annotate an image with a property that
- describes the required VIF model:
- $glance image-update \
- --property hw_vif_model=e1000 f16-x86_64-openstack-sda
- If you specify a VIF model that is not
- supported, the instance fails to launch. See .
+ To annotate an image with a property that describes the disk_bus, cdrom_bus,
+ and vif_model:
+ #glance image-update \
+ --property hw_disk_bus=scsi \
+ --property hw_cdrom_bus=ide \
+ --property hw_vif_model=e1000 \
+ f16-x86_64-openstack-sda
+ Currently libvirt will determine the disk/cdrom/vif device models based on the
+ configured hypervisor type (libvirt_type in
+ /etc/nova/nova.conf). For the sake of optimal
+ performance, it will default to using virtio for both disk and VIF (NIC) models.
+ The downside of this approach is that it is not possible to run operating
+ systems that lack virtio drivers, for example, BSD, Solaris, old Linux, and old
+ Windows.
+ If you specify a disk or CD-ROM bus model that is not supported, see . If you specify a VIF model that is not supported,
+ the instance fails to launch. See .The valid model values depend on the
libvirt_type setting, as shown in
- the following table:
+ the following tables:
+