mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-03-06 08:53:39 +00:00
Updated notes about HVM devices / boot details
This commit is contained in:
parent
e1ec9651a2
commit
86a22bd660
@ -1,3 +1,9 @@
|
|||||||
|
Mon Aug 14 10:55:02 EDT 2006 Daniel Berrange <berrange@redhat.com>
|
||||||
|
|
||||||
|
* docs/libvir.html, docs/format.html: Updated description of
|
||||||
|
HVM boot device, and disk device configuration to match up
|
||||||
|
new new behaviour from previous changes
|
||||||
|
|
||||||
Fri Aug 11 09:37:02 EDT 2006 Daniel Berrange <berrange@redhat.com>
|
Fri Aug 11 09:37:02 EDT 2006 Daniel Berrange <berrange@redhat.com>
|
||||||
|
|
||||||
* src/libvirt.c: Avoid duplicated attempts to shutdown or
|
* src/libvirt.c: Avoid duplicated attempts to shutdown or
|
||||||
|
@ -99,7 +99,7 @@ systems:</p><pre><domain type='xen' id='3'>
|
|||||||
<os>
|
<os>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><type>hvm</type></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><type>hvm</type></span>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><loader>/usr/lib/xen/boot/hvmloader</loader></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><loader>/usr/lib/xen/boot/hvmloader</loader></span>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><boot dev='hda'/></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><boot dev='da'/></span>
|
||||||
</os>
|
</os>
|
||||||
<memory>524288</memory>
|
<memory>524288</memory>
|
||||||
<vcpu>1</vcpu>
|
<vcpu>1</vcpu>
|
||||||
@ -115,22 +115,50 @@ systems:</p><pre><domain type='xen' id='3'>
|
|||||||
</interface>
|
</interface>
|
||||||
<disk type='file'>
|
<disk type='file'>
|
||||||
<source file='/root/fv0'/>
|
<source file='/root/fv0'/>
|
||||||
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='ioemu:hda'</span>/>
|
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='hda'</span>/>
|
||||||
|
</disk>
|
||||||
|
<disk type='file' <span style="color: #0000E5; background-color: #FFFFFF">device='cdrom'</span>>
|
||||||
|
<source file='/root/fc5-x86_64-boot.iso'/>
|
||||||
|
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='hdc'</span>/>
|
||||||
|
<readonly/>
|
||||||
|
</disk>
|
||||||
|
<disk type='file' <span style="color: #0000E5; background-color: #FFFFFF">device='floppy'</span>>
|
||||||
|
<source file='/root/fd.img'/>
|
||||||
|
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='fda'</span>/>
|
||||||
</disk>
|
</disk>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><graphics type='vnc' port='5904'/></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><graphics type='vnc' port='5904'/></span>
|
||||||
</devices>
|
</devices>
|
||||||
</domain></pre><p>There is a few things to notice specifically for HVM domains:</p><ul><li>the <os> block description is very different, first it indicates
|
</domain></pre><p>There is a few things to notice specifically for HVM domains:</p><ul><li>the <code><os></code> block description is very different, first it indicates
|
||||||
that the type is 'hvm' for hardware virtualization, then instead of a
|
that the type is 'hvm' for hardware virtualization, then instead of a
|
||||||
kernel, boot and command line arguments, it points to an os boot loader
|
kernel, boot and command line arguments, it points to an os boot loader
|
||||||
which will extract the boot informations from the boot device specified
|
which will extract the boot informations from the boot device specified
|
||||||
in a separate boot element</li>
|
in a separate boot element. The <code>dev</code> attribute on the <code>boot</code>
|
||||||
<li>the <devices> section includes an emulator entry pointing to an
|
tag can be one of:
|
||||||
|
<ul><li><code>fd</code> - boot from first floppy device</li>
|
||||||
|
<li><code>hd</code> - boot from first harddisk device</li>
|
||||||
|
<li><code>cdrom</code> - boot from first cdrom device</li>
|
||||||
|
</ul></li>
|
||||||
|
<li>the <code><devices></code> section includes an emulator entry pointing to an
|
||||||
additional program in charge of emulating the devices</li>
|
additional program in charge of emulating the devices</li>
|
||||||
<li>the disk entry indicates in the dev target section that the emulation
|
<li>the disk entry indicates in the dev target section that the emulation
|
||||||
for the drive is the first IDE disk device hda</li>
|
for the drive is the first IDE disk device hda. The list of device names
|
||||||
<li>the <devices> section also include at least one entry for the
|
supported is dependant on the Hypervisor, but for Xen it can be any IDE
|
||||||
|
device <code>hda</code>-<code>hdd</code>, or a floppy device <code>fda</code>,
|
||||||
|
<code>fdb</code>. The <code><disk></code> element also supports a 'device'
|
||||||
|
attribute to indicate what kinda of hardware to emulate. The following values are
|
||||||
|
supported:
|
||||||
|
<ul><li><code>floppy</code> - a floppy disk controller</li>
|
||||||
|
<li><code>disk</code> - a generic hard drive (the default it omitted)</li>
|
||||||
|
<li><code>cdrom</code> - a CDROM device</li>
|
||||||
|
</ul>
|
||||||
|
For Xen 3.0.2 and earlier a CDROM device can only be emulated on the
|
||||||
|
<code>hdc</code> channel, while for 3.0.3 and later, it can be emulated on
|
||||||
|
any IDE channel.</li>
|
||||||
|
<li>the <code><devices></code> section also include at least one entry for the
|
||||||
graphic device used to render the os. Currently there is just 2 types
|
graphic device used to render the os. Currently there is just 2 types
|
||||||
possible 'vnc' or 'sdl'</li>
|
possible 'vnc' or 'sdl'. If the type is 'vnc', then an additional <code>port</code>
|
||||||
|
attribute will be present indicating the TCP port on which the VNC server is
|
||||||
|
accepting client connections.</li>
|
||||||
</ul><p>It is likely that the HVM description gets additional optional elements
|
</ul><p>It is likely that the HVM description gets additional optional elements
|
||||||
and attributes as the support for fully virtualized domain expands,
|
and attributes as the support for fully virtualized domain expands,
|
||||||
especially for the variety of devices emulated and the graphic support
|
especially for the variety of devices emulated and the graphic support
|
||||||
|
@ -423,7 +423,7 @@ systems:</p>
|
|||||||
<os>
|
<os>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><type>hvm</type></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><type>hvm</type></span>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><loader>/usr/lib/xen/boot/hvmloader</loader></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><loader>/usr/lib/xen/boot/hvmloader</loader></span>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><boot dev='hda'/></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><boot dev='hd'/></span>
|
||||||
</os>
|
</os>
|
||||||
<memory>524288</memory>
|
<memory>524288</memory>
|
||||||
<vcpu>1</vcpu>
|
<vcpu>1</vcpu>
|
||||||
@ -439,7 +439,16 @@ systems:</p>
|
|||||||
</interface>
|
</interface>
|
||||||
<disk type='file'>
|
<disk type='file'>
|
||||||
<source file='/root/fv0'/>
|
<source file='/root/fv0'/>
|
||||||
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='ioemu:hda'</span>/>
|
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='hda'</span>/>
|
||||||
|
</disk>
|
||||||
|
<disk type='file' <span style="color: #0000E5; background-color: #FFFFFF">device='cdrom'</span>>
|
||||||
|
<source file='/root/fc5-x86_64-boot.iso'/>
|
||||||
|
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='hdc'</span>/>
|
||||||
|
<readonly/>
|
||||||
|
</disk>
|
||||||
|
<disk type='file' <span style="color: #0000E5; background-color: #FFFFFF">device='floppy'</span>>
|
||||||
|
<source file='/root/fd.img'/>
|
||||||
|
<target <span style="color: #0000E5; background-color: #FFFFFF">dev='fda'</span>/>
|
||||||
</disk>
|
</disk>
|
||||||
<span style="color: #0000E5; background-color: #FFFFFF"><graphics type='vnc' port='5904'/></span>
|
<span style="color: #0000E5; background-color: #FFFFFF"><graphics type='vnc' port='5904'/></span>
|
||||||
</devices>
|
</devices>
|
||||||
@ -447,18 +456,40 @@ systems:</p>
|
|||||||
|
|
||||||
<p>There is a few things to notice specifically for HVM domains:</p>
|
<p>There is a few things to notice specifically for HVM domains:</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li>the <os> block description is very different, first it indicates
|
<li>the <code><os></code> block description is very different, first it indicates
|
||||||
that the type is 'hvm' for hardware virtualization, then instead of a
|
that the type is 'hvm' for hardware virtualization, then instead of a
|
||||||
kernel, boot and command line arguments, it points to an os boot loader
|
kernel, boot and command line arguments, it points to an os boot loader
|
||||||
which will extract the boot informations from the boot device specified
|
which will extract the boot informations from the boot device specified
|
||||||
in a separate boot element</li>
|
in a separate boot element. The <code>dev</code> attribute on the <code>boot</code>
|
||||||
<li>the <devices> section includes an emulator entry pointing to an
|
tag can be one of:
|
||||||
|
<ul>
|
||||||
|
<li><code>fd</code> - boot from first floppy device</li>
|
||||||
|
<li><code>hd</code> - boot from first harddisk device</li>
|
||||||
|
<li><code>cdrom</code> - boot from first cdrom device</li>
|
||||||
|
</ul>
|
||||||
|
</li>
|
||||||
|
<li>the <code><devices></code> section includes an emulator entry pointing to an
|
||||||
additional program in charge of emulating the devices</li>
|
additional program in charge of emulating the devices</li>
|
||||||
<li>the disk entry indicates in the dev target section that the emulation
|
<li>the disk entry indicates in the dev target section that the emulation
|
||||||
for the drive is the first IDE disk device hda</li>
|
for the drive is the first IDE disk device hda. The list of device names
|
||||||
<li>the <devices> section also include at least one entry for the
|
supported is dependant on the Hypervisor, but for Xen it can be any IDE
|
||||||
|
device <code>hda</code>-<code>hdd</code>, or a floppy device <code>fda</code>,
|
||||||
|
<code>fdb</code>. The <code><disk></code> element also supports a 'device'
|
||||||
|
attribute to indicate what kinda of hardware to emulate. The following values are
|
||||||
|
supported:
|
||||||
|
<ul>
|
||||||
|
<li><code>floppy</code> - a floppy disk controller</li>
|
||||||
|
<li><code>disk</code> - a generic hard drive (the default it omitted)</li>
|
||||||
|
<li><code>cdrom</code> - a CDROM device</li>
|
||||||
|
</ul>
|
||||||
|
For Xen 3.0.2 and earlier a CDROM device can only be emulated on the
|
||||||
|
<code>hdc</code> channel, while for 3.0.3 and later, it can be emulated on
|
||||||
|
any IDE channel.</li>
|
||||||
|
<li>the <code><devices></code> section also include at least one entry for the
|
||||||
graphic device used to render the os. Currently there is just 2 types
|
graphic device used to render the os. Currently there is just 2 types
|
||||||
possible 'vnc' or 'sdl'</li>
|
possible 'vnc' or 'sdl'. If the type is 'vnc', then an additional <code>port</code>
|
||||||
|
attribute will be present indicating the TCP port on which the VNC server is
|
||||||
|
accepting client connections.</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<p>It is likely that the HVM description gets additional optional elements
|
<p>It is likely that the HVM description gets additional optional elements
|
||||||
|
Loading…
x
Reference in New Issue
Block a user