[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] [PATCH] Power Hypervisor Support for libvirt - minimum set of features
- From: "Daniel P. Berrange" <berrange redhat com>
- To: Eduardo Otubo <otubo linux vnet ibm com>
- Cc: Libvirt <libvir-list redhat com>
- Subject: Re: [libvirt] [PATCH] Power Hypervisor Support for libvirt - minimum set of features
- Date: Wed, 1 Jul 2009 10:55:19 +0100
On Mon, Jun 29, 2009 at 04:11:20PM -0300, Eduardo Otubo wrote:
> Hello Daniel,
>
> > I might be missing something, but this database doesn't appear to be
> > persistent at all - it just lives for the duration of the virConnectPtr
> > object's lifetime. So if you create two connections you'd get two
> > different UUIDs for the same VM.
>
> Yes, that's right. I thought I could make it work kinda stable before
> make it persistent.
>
> And here I have a little question: The way I thought I could make it
> persistent is just to implement the virDomainDefineXML function. This
> way, I would make init__uid_db() check if there is some xml file
> defined, if not just create a new UUID for that lpar.
>
> But, in this case, virsh/libvirtd could be run from anywhere, so the xml
> file would be in other machine and so on. Then I thought I could create
> the XML in HMC's machine, then I would have a little more control of the
> UUIDs. What do you think?
I think you'd be better with the latter idea if possible - its fairly
important to have stable UUID's no matter where you connect from
Daniel
--
|: Red Hat, Engineering, London -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 :|
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]