openstack/openstack-manuals
Code Issues Proposed changes

change to section_compute-configure-xen

Browse Source 
changed: Other functionalities such as host aggregates, do not work.
changed bug

Change-Id: If67a1a7fe54c60bd2a614a0faeda17f1cca29a7d
This commit is contained in:
shilla-saebi 2014-06-03 00:20:42 -04:00 committed by Christian Berendt
parent a1f8f50c25
commit a7cf4358fd
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/config-reference/compute/section_compute-configure-xen.xml
View File

@ -24,7 +24,7 @@ xenapi_connection_password = your_password</programlisting>
The <literal>xenapi_connection_url</literal> is generally the management
network IP address of the XenServer. Though it is possible to use the
internal network IP Address (169.250.0.1) to contact XenAPI, this does not
allow live migration between hosts, and other functionalities like host aggregates
allow live migration between hosts. Other functionalities such as host aggregates,
do not work.
</para></note>
<para>It is possible to manage Xen using libvirt, though this is not well-tested or supported. To
@ -38,7 +38,7 @@ virt_type = xen</programlisting></para>
<title>Agent</title>
<para>
If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started.
Generally a large timeout is required for Windows instances, bug you may want to tweak <literal>agent_version_timeout</literal>
Generally a large timeout is required for Windows instances, but you may want to tweak <literal>agent_version_timeout</literal>.
</para></section>
<section xml:id="xen-firewall">
<title>Firewall</title>