Thanks for your reply.
Here is my experimental setting. I start a domu, run "xm list --long", the uuid shown to me was (uuid 6cc8ab86-4ad4-7820-3326-53d666ff96aa). Then, I shut down this domu, and start the same domu again. I got a different uuid:
(uuid 0c9ee2d6-4a9f-c0bf-989f-148bec284e15). You can see these two uuids are different.
I am using the latest xen-unstable.
Any further thought? If the persistent identifier does exists, do we have a programmable solution to get the persistent identifier (not command line, because it dump too much information and need additional work to filter the useless information)?
Thanks,
lily
On 12/28/06, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
On Wed, Dec 27, 2006 at 11:09:43PM -0500, Lily Huang wrote:
> Hi,
>
> As we know, a domainU's domid may change after system reboots. Does Xen
> provide a persistent identifier for each domU? I tried UUID, but UUID also
> changes across reboots. Any idea on this? If Xen does provide such a
> mechanism to persistently identify a domain U? What is it?
Which UUID do you mean? The one that xm list --long shows you as the
UUID for the domain certainly shouldn't change across reboots (it
doesn't for me).
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel