openstack
/
security-doc
Code Issues Proposed changes

Sentence rewording CH. 41 - Hardening the Virtualization Layers 

Implemented corrections offered in bug report from N Dillon.

Closes-Bug: #1342438

Change-Id: Iedc68c98f46b5d816e8f3f561a7e9c12b1ea1473
Co-Authored-By: Nathaniel Dillon <nathaniel.dillon@hp.com>
This commit is contained in:
Shellee Arnold 2014-09-01 18:01:43 -07:00 committed by Andreas Jaeger
parent 8bc596ab99
commit 575249b08f
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
security-guide/section_hardening-the-virtualization-layers.xml
View File

@ -123,13 +123,14 @@
<section xml:id="hardening-the-virtualization-layers-idp490976">
<title>Minimizing the QEMU code base</title>
<para>
One classic security principle is to remove any unused
components from your system. QEMU provides support for many
different virtual hardware devices. However, only a small
number of devices are needed for a given instance. Most
instances will use the virtio devices. However, some legacy
instances will need access to specific hardware, which can
be specified using glance metadata:</para>
The first recommendation is to minimize the QEMU code base
by removing unused components from the system. QEMU provides
support for many different virtual hardware devices, however
only a small number of devices are needed for a given
instance. The most common hardware devices are the virtio
devices. Some legacy instances will need access to specific
hardware, which can be specified using glance metadata:
</para>
<screen><prompt>$</prompt> <userinput>glance image-update \
--property hw_disk_bus=ide \
--property hw_cdrom_bus=ide \