2. To see the current xen configuration for your oes11 DomU:
xm list -l oes11
(That’s a lower case ELL after the “-”)
3. To save the current xen configuration for your oes11 DomU:
xm list -l oes11 >oes11.py
the current xen configuration will be save to file oes11.py, in your current directory
4. Now, if you no longer want xend to manage your oes11 Domu:
xm delete oes11
Note: this doesn’t delete the DomU or the virtual filestore. It just removes the definition from the XenStore.
5. To verify that Xen no longer knows about your oes11 DomU:
That will list all the DomU’s managed by xend. oes11 is no longer listed.
6. Even though the DomU is no longer managed by xend, you can still “run” it using the original configuration:
xm create /etc/xen/oes11
7. You can also import the configuration back into the XenStore using the file created in step 3:
xm new -F oes11.py
8. Step 7 just imports the configuration. It doesn’t start the DomU. To start the DomU:
xm start oes11
There are a few more important points to consider:
- The XenStore contains the current configuration including changes made with “Virtual Machine Manager”.
- The file you use with xm create is static. It contains the initial configuration without any subsequent changes. For this reason it is often obsolete.
- You are limited to making relatively simple changes to your DomU using “Virtual Machine Manager”.
This is the preferred method for changing your Xen configuration:
A. Shutdown the DomU using the appropriate OS specific method or from the Dom0:
xm shutdown <DomU>
B. Verify the DomU is no longer running:
C. Save the current xen configuration for your DomU in a file:
xm list -l <DomU> > DomU.py
D. Save a copy of the file (just in case!).
E. Make any changes to the configuration using your favorite text editor and save the changes. <Modified Configuration>
F. Delete the current configuration from the XenStore
xm delete <DomU>
G. Import the modified configuration back into the XenStore using the file created in step E:
xm new -F <Modified Configuration>
H. Start the DomU
xm start <DomU>
An added benefit of following this procedure is you retain a backup copy of your DomU configuration should anything happen to the XenStore.