View source for Managing Xen Hardware based Virtual Machines (HVM)

[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Virtualization tools]] > [[Xen]] > [[Managing Xen Hardware based Virtual Machines (HVM)]]

'''A more updated lab is hosted at http://www.sbarjatiya.com/website/courses/2010/monsoon/system_and_resource_virtualization/labs/04-managing_xen_hvm_guests.pdf '''

==Domain creation or management==


===Create a new domain===

To create a new domain or virtual machine we can use command
<pre>
xm create <hvm_configuration_file> -c
</pre>
Here, -c is to attach console as soon as the domain is created.



===Delete/Destroy running domain===
To delete/destroy running domain (This is like force-off on VM) we can use:
<pre>
xm destroy {<domain_id>|<domain_name>}
</pre>
Here: 
*'<tt>domain_id</tt>' is the domain ID listed against domain in '<tt>xm list</tt>' command output and
*'<tt>domain_name</tt>' is the name of domain that we specify with '<tt>name</tt>' parameter in domain configuration file

This is like removing power from VM without giving it time to shutdown gradually. File systems, databases, network connections may be in inconsistent state and hence destroying a domain may lead to data loss. Unlike '<tt>shutdown</tt>' and '<tt>reboot</tt>' options discussed later this option is guaranteed to force off a domain and guest OS configuration cant prevent domain from getting powered off.



===Pause a domain===

To pause a domain so that it is no longer considered by Xen Hypervisor for scheduling we can use:
<pre>
xm pause {<domain_id>|<domain_name>}
</pre>

Note that paused domain will continue using RAM resoures. All files used for virtualization on host OS will still remain open. Only domain is not scheduled by hypervisor. If we pause domain for long time then the network connections (like TCP) may time-out and hence when we unpause the state of network connections may change. If network connections are with other VM and they are also paused then timeout should not occur. 



===Unpause a domain===

To unpause a paused domain so that it is again considered by Xen Hypervisor for scheduling, we can use:
<pre>
xm unpause {<domain_id>|<domain_name>}
</pre>



===Reboot a domain===

We can use command
<pre>
xm reboot [options] {<domain_id>|<domain_name>}
</pre>
to reboot a running domain. Two options are available while using reboot command
#'<tt>-w</tt>' - This option can be used to indicate to '<tt>xm</tt>' that we want to wait till the reboot completes. This prevents command from returning just after indicating to Xen hypervisor that mentioned domain should be rebooted. This can be useful in scripting or programming when we want following commands to be executed only after reboot is finished. 
#:Note that by reboot finished we just mean that VM has rebooted. It does not means that OS has booted again. OS may take considerable more time to boot after VM has rebooted.
#'<tt>-a</tt>' - This option can be used to reboot all running domains. In this case we do not need to specify any '<tt>domain_id</tt>' or '<tt>domain_name</tt>' as parameter.

''Note this will work only if OS is configured to reboot, if reboot button is pressed on keyboard/PC. One can configure OS to give prompt whenever reboot / poweroff / suspend etc. buttons are pressed. In those cases the OS and hence domain may not reboot but provide option to user and wait for him/her to choose what should be done.''



===Shutdown a domain===
We can use command
<pre>
xm shutdown [options] {<domain_id>|<domain_name>}
</pre>
to shutdown a running domain. Options for shutdown are same as options for reboot ('<tt>-a</tt>' and '<tt>-w</tt>') and have similar effect. Here also it is necessary for guest OS to be configured to shutdown when shutdown button on keyboard/Cabinet is pressed. If guest OS is configured to prompt to user before some action is taken then shutdown is not guaranteed.



===Saving a domain===

We can save running domain in a state file. This effectively means that domain would be paused and its RAM contents will be stored in state file. This is somewhat like hibernating the guest OS but no support for hibernate is required from Guest OS. Also normally in hibernate the machine uses its own hard-disk for storing RAM contents. In this case the host OS would store RAM contents of guest OS. When we save a domain RAM resources and other host resources used by domain on host OS are freed and hence we can use the same RAM for other purposes like creating / restoring other domains.

To save a running domain in a state file we can use:
<pre>
xm save {<domain_id>|<domain_name>} <state_file>
</pre>

Note that:
*When we use save command on domain it gets renamed to '<tt>migrating-&lt;old_name&gt;</tt>' and remains in running state for a while. After that it goes to s (shutdown state) and eventually gets removed from list of domains.
*Sufficient space must be available on partition where we are trying to save the image so that entire RAM contents and little extra information can be saved.



===Restoring a domain===

We can restore a domain from state file using:
<pre>
xm restore <state_file>
</pre>

Note that:
*During restore we only specify state file and not the initial configuration with which domain was created. Hence apart from RAM contents state file also stores information about configuration of domain.
*Like pause here also network connections may time out if we are restoring domain after long time.
*When we try to restore a domain it will initially remain in blocked and paused states. Later it moves to blocked or running state.
*State file is not deleted / altered during restore and hence we can restore using same state file as many time as we want. This can help in cloning VMs. If we use this method to create clones then IP conflict will occur and same MAC address on both machines would cause problem. Such issues would need to be resolved.
*Care must be taken to ensure that sufficient RAM is free on host OS before trying to restore a guest from state file to avoid Guest from crashing. 



===Connecting to virtual console of running Xen domain===

If we want to connect to virtual console of Xen domain during creation then we can use option '<tt>-c</tt>' while creating domain. If later we want to connect to virtual console then we can use:
<pre>
xm console {<domain_id>|<domain_name>}
</pre>
Note that to come out of console to get prompt back we have to use telnet escape sequence (Ctrl + ']'). Ctrl+C is transparently passed to the console and hence wont help in coming out of console.






==Domain information==

===List running domain===

To list currently running Xen domains we can use command:
<pre>
xm list
</pre>
The above command also lists state of each running domain. The possible values for state and their meanings are:
{| border="1" cellspacing="5" cellpadding="5"
|-
| '''State''' || Meaning 
|-
|    r        || Running 
|-
|    b        || Blocked - Means either waiting for I/O or is sleeping as nothing left to do
|-
|    p        || Paused - Domain is paused and hence will continue using RAM resoures. All files will still remain open. Only domain is not scheduled by hypervisor. Note that if we pause domain for long time then the network connections (like TCP) may time-out and hence when we unpause the state of network connections may change. If network connections are with other VM and they are also paused then timeout should not occur. 
|-
|    s        || Shutdown - The guest is requested to Shutdown or reboot or suspended. The process is being carried out.
|-
|    c        || Crashed - The domain has crashed. Usually this state can only occur if the domain has been configured not to restart on crash.
|-
|    d        || Dying - The domain is in process of dying but has not completely shutdown or crashed 
|-
|}



===Finding domain ID for particular domain name===

In case we want to find domain ID for given domain name then we can either look for the ID against name in '<tt>xm list</tt>' output or we can use:
<pre>
xm domid <domain_name>
</pre>
to get domain ID for given domain name. This can be very useful if we are writing programs that will manipulate domain and we want our program to be able to find domain ID based on domain name.



===Finding domain name for particular domain ID===

In case we want to find domain name for given domain ID then we can either look for the name against ID in '<tt>xm list</tt>' output or we can use:
<pre>
xm domname <domain_id>
</pre>
to get domain name for given domain ID.



===Finding all parameters used for running domain===

To find all parameters being used by running domain we can use:
<pre>
xm list --long
</pre>
This will even display attached block devices, network interfaces, values for parameters like '<tt>usb</tt>' etc. 

Note that:
*We can also look at configuration file for finding the same information. But there is not guarantee that configuration file has not been altered after domain is created. Also we can attach/detach devices from running domain which may not be listed in configuration file. Hence, this method of finding configuration of running domains is more accurate.
*Command '<tt>xenstore-ls</tt>' provides us with evem more detailed information then '<tt>xm list --long</tt>'


===Xen message buffer===

We can see xen message buffer using:
<pre>
xm dmesg
</pre>

If we want to clear the xen message buffer then we can use
<pre>
xm dmesg -c
</pre>

Xen message buffer contains messages generated during Xen boot and also other important warnings / errors that Xen generates during running and hence is very nice tool to help with troubleshooting



===Xen information===

To print information about current Xen installation including basic information about current host OS, we can use:
<pre>
xm info
</pre>



==Monitoring xen resources==

If we want to see usage of various Xen resources like CPU, Block devices, network devices, which domains are running, etc. information in top like view then we can use command
<pre>
xentop
</pre>
In xentop we can use:
*'d' - To change the delay time after which information is refreshed
*'n' - To include information about network devices / interfaces in output.
*'b' - To include information about block devices in output
*'v' - To see information about Virtual CPUs in output
*'s' - To change sort order for displayed values.





==Tips==

*Most '<tt>xm</tt>' commands work in background. Hence, if we get prompt back after running a command it does not mean that old command has completed. We should ensure using '<tt>xm list</tt>' command whether previous command(s) are finished or not.
*Most of this information is also available at xm man page which can be viewed using '<tt>man xm</tt>' command



[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Virtualization tools]] > [[Xen]] > [[Managing Xen Hardware based Virtual Machines (HVM)]]