name = "test"
uuid = "287fe83e-8d9a-c935-6026-c9ea85b60e87"
maxmem = 7168
memory = 7168
vcpus = 7
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 0
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib/xen/bin/stubdom-dm"
vfb = [ "type=vnc,vncunused=1" ]
disk = [ "phy:/dev/sys/lv0,hda,w", "phy:/dev/sys/lv1,hdb,w", "phy:/dev/sys/lv2,h
dc,w" ]
vif = [ "mac=00:50:56:0f:dd:02,bridge=eth0,script=vif-bridge" ]
parallel = "none"
serial = "none"




Thanks it worked.
 
-M




> Date: Sat, 20 Mar 2010 11:19:05 +0100
> Subject: Re: [libvirt-users] virsh domxml-to-native xen-xm request
> From: matthias.bolte@googlemail.com

> 2010/3/20 Mike Viau <viaum@sheridanc.on.ca>:
> > Hello,
> >
> > I was looking at http://libvirt.org/drvxen.html
> >
> > And realized that "virsh domxml-to-native" may be used to convert the
> > libvirt xml formatted domU configuration to native.
> >
> > The configuration is for stubdom-dm Xen guests.
> >
> > Syntax appears to be virsh domxml-to-native xen-xm new_vm1.xml >
> > /etc/xen/new_vm1 but I get an error.
> >
> > error: invalid argument in unsupported config type xen-xm
> >
> >
> > Can someone please post their output of the command: virsh domxml-to-native
> > xen-xm new_vm1.xml
> >
>
> Do you just run this command?
>
> virsh domxml-to-native xen-xm new_vm1.xml > /etc/xen/new_vm1
>
> If you don't specify an explicit connection URI, or have
> VIRSH_DEFAULT_CONNECT_URI set to to some Xen connection URI, then
> libvirt will try to autodetect your hypervisor and might find QEMU. In
> that case I can reproduce the reported error.
>
> To make it work you need to specify a proper connection URI, for example
>
> virsh -c xen:/// domxml-to-native xen-xm new_vm1.xml > /etc/xen/new_vm1
>
> or whatever URI you need for your setup.
>
> Matthias

---

Take your contacts everywhere. Try Messenger for mobile