As discussed throughout this book, the
xm command is the core Xen command for interacting with the hypervisor, controlling resource allocation and availability, creating and terminating Xen domainU guests, and so on.
xm command is essentially a command suite that actually performs many different functions. To perform any of these subcommands, you type xm subcommand and supply the options that are necessary for that particular subcommand.
You can display a list of the most commonly used
xm subcommands by typing the
xm command with no arguments. To see a complete list of all available subcommands, type xm help.
This appendix describes all of the available
xm subcommands, what they do, the options that each subcommand requires in order to perform a specific task, and any optional arguments that you can supply when executing any of these subcommands.
Security labels support the Xen/sHype access control framework, which was discussed in "Xen Access Control and Security Policies" in Chapter 9. When security policies and access controls are enabled in the hypervisor, you cannot start a domain that is not labeled with the name of the security policy that it will use. You must label both the domain (in its configuration file) and the filesystem and swap resources that it uses. Domain labels are added to a domain's configuration file, and resource labels are stored in the file