On Mar 31, 2008, at 3:09, Richard W.M. Jones wrote:
That's quite strange. Is this Xen? What does the XML look like?
I am trying to track down the problem. One thing I see is that if I
define/undefine
twice, returned UUID is the same. Does not it have some random
component in it (I see
some random stuff in uuid.c)?
Here is roughly what I am seeing right now:
D, [11:29:06#15021] DEBUG -- : xdefine_domain_xml(xml)
D, [11:29:06#15021] DEBUG -- : New domain defined with UUID
6911f001-6991-bc1c-e455-11f6f99e3951
D, [11:29:06#15021] DEBUG -- : undefine(6911f001-6991-bc1c-
e455-11f6f99e3951)
Then, the second attempt, within same process, second later:
D, [11:29:33#15021] DEBUG -- : define_domain_xml(xml)
D, [11:29:33#15021] DEBUG -- : New domain defined with UUID
6911f001-6991-bc1c-e455-11f6f99e3951
D, [11:29:34#15021] DEBUG -- : undefine(6911f001-6991-bc1c-
e455-11f6f99e3951)
E, [11:29:34#15021] ERROR -- : unknown error - libvir call
virDomainLookupByUUID failed (SystemCallError)
after the second attempt, because 'undefine' failed, I can see still
defined domain in virsh:
virsh # dominfo sample-domain
Id: -
Name: sample-domain
UUID: ccdbf043-cf3d-902b-f08f-1d6a0d571f13
OS Type: linux
State: shut off
CPU(s): 1
Max memory: 262144 kB
Used memory: 262144 kB
the UUID is different. So it looks like the "define_domain_xml"
returns wrong UUID second time.
I am continuing to debug this, any hints are appreciated.
Sincerely,
Vadim
--
"La perfection est atteinte non quand il ne reste rien a ajouter, mais
quand il ne reste rien a enlever." (Antoine de Saint-Exupery)