Project Convirt/XenMan
README - v0.6

Known bugs/caveats

When using XenMan in Xen 3.0.3+/3.0.2 mixes environments, please ensure that XenMan is run on a 3.0.3+ node. XenMan running on a 3.0.2 node isn't forward compatible for managing Xen 3.0.3+ servers.
Occasionally, the memory/cpu usage percentages displayed in the Dashboard and elsewhere may spike momentarily to above 100%. This is due to a bug in the way Xen reports resource usage for VM's. Hopefully this will be fixed in the near future.
You might have to enter credentials for the same server multiple times when password based authentication scheme is used for managed server as opposed to key based authentication.
For example :
- When the server is expanded
- When terminal window is opened for selected VM
- When an operation requires remote file access and gnome-vfs is enabled in XenMan configuration.
Sometimes, the guest VM tab showing the virtual machine terminal fails to redraw properly. Clicking on the terminal and sending a Ctrl+l and/or some keystrokes often helps.
When the Virtual machine configuration file is changed, the directives may get saved in different order.
On some platforms the password field generates gtk/pango warnings and displays "?" characters. Ignore this, the password is read correctly by XenMan.
For XenMan to show vnc display correctly, vncunused in the vm config file should be set to 0.
The image store is no more governed by entries in xenman.conf. Users upgrading will have to use the new mechanism of defining and using images.
A property name in the xenman.conf has changed from "doms" to "vms", please make a note of this.

**NOTE**: For a full description of XenMan and its features, please consult the manual included in the XenMan documentation package.