userxm - a user-level interface to the Xen xm commands
userxm {create|destroy|list|console} [slice number]
By default, any user in Dom0 can issue any commands to xm, and control any DomU slice. This is bad if you want to allow different people to administer their own slices on the Xen box. After applying the right patch, one can set up Xen to only allow a superuser to issue xm commands (other than xm list, which cannot cause any harm). userxm is a wrapper script which is setuid root, and checks who the user is, and which slice(s) they own.
number - this is the slice number that you want to control. If left blank, it is assumed to be 1.
create, c - create (start) the slice. This is equivalent to xm create
destroy, d - destroy (stop) the slice. Note, this does not gracefully shut the slice down. This is equivalent to xm destroy
list, l - list all running domains. This is equivalent to xm list. If this command is given, any slice
number is ignored.
console, cons - connect to the console of your domain. This is equivalent to xm console.
To start up your first (or only) slice:
userxm create
or
userxm c
To start your fifth slice:
userxm c 5
To kill your first slice:
userxm destroy
or
userxm d
To kill your third slice:
userxm d 3
To list all running slices:
userxm list
or
userxm l
To connect to the console of your second slice:
userxm console 2
or
userxm cons 2
guest.lst The guest list. This is a space-delimited file matching users (and their slice numbers) with names of DomU's.
userxm returns a zero exit status if the command executed successfully, non-zero if there was an error
Written by Patrick Kaeding (pkaeding at ccs dot neu dot edu) for Crew (http://crew.ccs.neu.edu); based heavily on uml utilities written by Russell Neches and Andrew Medico.
newdisk(8), guest.lst(5)