On Wed, 2009-04-08 at 19:32 +0100, Daniel P. Berrange wrote:
libvirt TCK : Technology Compatibility Kit
Amazing :)
Even these 4 simple proof of concept scripts have highlighted
some horrible problems
- The QEMU driver 'define domain' method doesn't check for name
or UUID uniqueness correctly (well, at all)
- After starting an inactive domain, the remote driver does not
update the 'ID' field in the virDomainPtr
- After destroying a active domain, the remote driver does not
update the 'ID' field in the virDomainPtr
- When defining a persistent config for an already running domain
the Xen XM driver blows away the current 'ID' field for the
running domain, replacing it with -1.
I've seen this. I hope some fixes can be back-ported or are sufficiently
distinct that users can patch older libvirt releases.
Since I have non-HVM hardware and am using F8 for Xen, I often run into
a loss of state information about a domain in libvirt.
https://bugzilla.redhat.com/show_bug.cgi?id=453276
Restarting xend sometimes helps, but frequently winds up causing another
domain to show up as "unknown" in virsh and sometimes a domain will
crash.
Working around virsh with xm start sometimes results in a domain that
will pause right after grub finishes, and once unpaused it will crash
very shortly after finishing bootup.
The workaround for that for that seems to be
xm start -c domain
in another console
xm unpause domain
login to the domain and immediately
shutdown -r now
this reboot seems to reset something back to normal and allow the domain
to startup completely.
Boy, that was fun the first time it happened. :)