[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] Reusing dumpxml output
- From: Stefan de Konink <skinkie xs4all nl>
- To: "Daniel P. Berrange" <berrange redhat com>
- Cc: libvir-list redhat com
- Subject: Re: [libvirt] Reusing dumpxml output
- Date: Thu, 14 Aug 2008 11:15:36 +0200 (CEST)
On Thu, 14 Aug 2008, Daniel P. Berrange wrote:
> On Thu, Aug 14, 2008 at 01:04:56AM +0200, Stefan de Konink wrote:
> > I would like to reuse configurations that have been edited using the
> > libvirt api. For example by attaching interfaces.
> >
> > Now the output that dumpxml generates, is very 'specific' to an active
> > configuration. I am not able to use a stored configuration from an active
> > domain to redefine it after it has been undefined. Is there a trick to do
> > so? Or should one really strip all 'live' attributes first?
>
> The XML is supposed to be idempotent - the XML you get from 'dumpxml'
> should be able to be fed back into 'create' resulting in exactly the
> same VM config.
>
> Previously there were a few places where you had to tweak the XML,
> eg to remove the auto-allocated VNC port, or remove the VIF target
> device name. In current CVS those issues are all fixed, so you should
> not have to change anything in the XML. So any further problems in
> this area are definitely bugs.
>
> There is also the option to request the 'inactive' XML dump for a running
> domain which removes any auto-allocated params. This is just a convenience
> though, and not required for re-creating the VM later.
Do you see the <bootloader /> bug? Or am I using a buggy git version?
I'll try the inactive parameter, that should be better in general.
Stefan
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]