Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hypervisor:base:xen [2014/04/02 02:37] admin [Configure Networking] |
hypervisor:base:xen [2014/04/03 02:07] (current) admin Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Xen ====== | ====== Xen ====== | ||
| + | <WRAP center round important 60%> | ||
| + | In case you want to install the full XCP-XAPI toolstack, don't go any further and read the [[xcp-xapi|XCP-XAPI]] section. | ||
| + | </WRAP> | ||
| + | |||
| [[https://wiki.debian.org/Xen]] | [[https://wiki.debian.org/Xen]] | ||
| Line 29: | Line 33: | ||
| Please refer to the [[:hypervisor:base:network|Network configuration]] section. | Please refer to the [[:hypervisor:base:network|Network configuration]] section. | ||
| + | ===== Reliable Setup ===== | ||
| - | ===== Configure Domain 0 Memory ===== | + | To avoid random, unexplained performance issues and failures in a XEN virtualization environment the following configuration items should always be checked; Correspondingly, before troubleshooting ANY XEN Host or VM issue verify the XEN Host configuration as follows: |
| + | |||
| + | * "Lock down" the amount of memory assigned to dom0. | ||
| + | * Set the amount of memory Dom0 is given at boot time | ||
| + | * Disable ballooning | ||
| + | * Do not restrict dom0 to a single VCPU | ||
| + | * Only use Logical Volume Manager (LVM) on Dom0 or DomU, but not both | ||
| + | |||
| + | More (for SUSE): [[http://www.novell.com/support/kb/doc.php?id=3559698]] | ||
| + | ==== Configure Dom0 Memory ==== | ||
| On a system which is dedicated to running Xen guests it is better to instead give dom0 some static amount of RAM and to disable ballooning, here 1024MB. | On a system which is dedicated to running Xen guests it is better to instead give dom0 some static amount of RAM and to disable ballooning, here 1024MB. | ||
| Line 63: | Line 77: | ||
| At this point you should **reboot** so that these changes take effect. | At this point you should **reboot** so that these changes take effect. | ||
| + | === Ensure that Xen is running === | ||
| + | <code> | ||
| + | > cat /proc/xen/capabilities | ||
| + | </code> | ||
| + | Should display “control_d” | ||
| ===== Configure guest behaviour on host reboot ===== | ===== Configure guest behaviour on host reboot ===== | ||