[et-mgmt-tools] [PATCH 05 of 11] Allow output in libvirt.rng format

[David Lutterkort]

On Tue, 2008-07-08 at 13:25 +0100, Daniel P. Berrange wrote:
> On Mon, Jul 07, 2008 at 03:51:35PM -0700, john.levon at sun.com wrote:
> > # HG changeset patch
> > # User john.levon at sun.com
> > # Date 1215470429 25200
> > # Node ID 4528daf7a40728f906e1843b8368198ce9d438c5
> > # Parent  6042ba3dce6a57dbe7ee547ae65be93dbef1b0a2
> > Allow output in libvirt.rng format
> > 
> > Add "virt-instance" formatter.
> > 
> > Signed-off-by: John Levon <john.levon at sun.com>
> 
> This is overlapping quite alot with what virt-image does when it
> converts 'image' format XML  into the libvirt XML, and its never
> going to give satisfactory results because virt-image is operating

I assume you mean 'virt-instance' - for virt-image I was very careful to
only use information from capabilities XML, and avoid hardcoded data in
the code because it would be too much of a maintenance burden.

> standalone without any libvirt connection. This means it is unable
> to get any hypervisor specific capabilities data to determine what
> the required OS / boot type options are.

The right approach then seems to use virt-convert to convert to
image.xml and use virt-image to fill in the  deployment specific bits,
even if the user thinks they are just converting a VM from one format to
another.

David