On Mon, Mar 10, 2008 at 11:37:19AM +0000, Richard W.M. Jones wrote:
On Sat, Mar 08, 2008 at 09:47:43AM +0100, Toth Istvan wrote:
I've looked into the virsh code, and it seems that it was written with only only old-style xen in mind, and xen 3.1's managed domains break the logic.
I don't understand this statement. The current 'cmdStart' code checks if the domain ID is -1 (ie. a managed domain, but inactive), and that seems correct.
This sounds very much like a bug in XenD to be be honest. If libvirt has got an ID of -1 then the domain is definitely dead - libvirt talks directly to the hypervisor. So if XenD meanwhile things its not dead, then its a XenD bug. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|