Xen project Mailing List

Hi Kyle,

Thanks so much for your time and advice, I must say it's been far much helpful and I appreciate it.

I have upgraded to the most recent version of libvirt for AMD64 architecture which is 0.9.2-7

(http://packages.debian.org/squeeze-backports/amd64/libvirt0/download) and this is the result:

root@neutrino:~# virsh version

Compiled against library: libvir 0.9.2

Using library: libvir 0.9.2

Using API: Xen 3.0.1

Running hypervisor: Xen 4.1.0

root@neutrino:~#

The UNIX socket interface is enabled: (xend-unix-server yes). No clue about the Xen API line yet.

Here is a new phenomenon though:

root@neutrino:~# virsh -c xen:/// domxml-from-native xen-xm winxp.cfg > config.xml

error: An error occurred, but the cause is unknown

root@neutrino:~#

As you've perfectly described I can actually start the domain using: #xm create winxp.cfg. And again, the control is managed by

xm and # virsh list --all doesn't show anything. Virsh cannot create the domain since it is not in an XML format nor can it start it

because it is not a libvirt managed domain.

There are no last entries either in /var/log/messages or /var/log/libvirt/libvirtd.log. Virsh and virt-manager are working fine and can

indeed connect to the hypervisor.

And just one last question: remus (for HA), is independent of all the libvirt management and workarounds? I mean, can I use both things

at the same time?, because I see virsh / virt-manager can in fact migrate domains, but it is just live-migration and not intended for HA.

Thank you once again!

Tony.

_______________________________________________________________________________________

> From: kyl191@xxxxxxxxxx
> Date: Thu, 1 Dec 2011 11:34:06 +0800
> Subject: Re: [Xen-users] How to make a P2V domU be recognized by Xend
> To: dftonywhite@xxxxxxxxxxx
> CC: xen-users@xxxxxxxxxxxxxxxxxxx
>
> Hi Tony,
> Those errors look like something's wrong with libvirt -
> http://wiki.libvirt.org/page/FAQ#error:_Unknown_Failure mentions that
> the "Unknown failure" messages are a result of bad error reporting in
> libvirt, but says more details should be available in dmesg and
> /var/log/messages.log
>
> Those libvirt versions are quite old though - I'm guessing Debian 6 is
> the stable release? http://packages.debian.org/stable/libvirt-bin says
> the version is still 0.8.3-5+squeeze2, when the latest release is
> 0.9.7 (http://libvirt.org/sources/)
>
> Any chance of using a backport?
> http://packages.debian.org/squeeze-backports/libvirt-bin is 0.9.6, so
> that might work better. I'm just wondering about the Xen API line -
> 4.0 to 4.1 made a number of changes, so I don't know what 3.0.1 to
> 4.1.0 would be like, and I'm thinking that might be the source of the
> errors.
>
> That said - your config file is a standard Xen config file, so it's
> strange that it'd be in /var/lib/xend/domains. You can get around
> virsh to at least see if it starts - Put the config (or a copy) in
> /etc/xen, and try xm create -c /etc/xen/filename. That should at least
> get Xen starting the domU, but not managing it yet.
>
> - Kyle
>
> On Thu, Dec 1, 2011 at 5:40 AM, Antonio Colin <dftonywhite@xxxxxxxxxxx> wrote:
> > Hi Kyle,
> >
> > Sorry for late reply but I was trying this, finally I got this error:
> >
> > root@neutrino:~# virsh -c xen:/// domxml-from-native xen-xm winxp.cfg
> > error: Unknown failure
> > root@neutrino:~# virsh domxml-from-native xen-xm winxp.cfg > config.xml &&
> > virsh define config.xml
> > error: Unknown failure
> > root@neutrino:~#
> >
> > My config file is Python format and it's here: http://pastebin.com/yc9qBSSJ
> > And the libvirt and hypervisor versions I am using are these:
> >
> > root@neutrino:~# virsh version
> > Compiled against library: libvir 0.8.3
> > Using library: libvir 0.8.3
> > Using API: Xen 3.0.1
> > Running hypervisor: Xen 4.1.0
> > root@neutrino:~#
> >
> > Thank you,
> > Tony.
> > ________________________________
> > Date: Sun, 27 Nov 2011 10:14:42 +0800
> > From: kyl191@xxxxxxxxxx
> > To: dftonywhite@xxxxxxxxxxx
> > CC: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-users] How to make a P2V domU be recognized by Xend
> >
> >
> > Hi,
> > What config file format do you have? A xml file, the native xen config file
> > (just a check of python code) or the config.sxp format?
> >
> > You'll need to get xend to recognise the config file first, and to do that
> > you'll need to import it. virsh has a number of tools to help with that - if
> > you have a python config, you can do a
> >
> > virsh domxml-from-native config.file > config.xml && virsh define config.xml
> >
> > If you have the config.sxp format, I'm afraid I've got no clue how to help
> > you - From what I understand it's a copy of the stuff in xenstore, so I'm
> > not sure if you can simply create a folder with the domU's uuid and move the
> > config file there and expect it to work. You could try creating a native xen
> > config file from the examples in /etc/xen, and just specify the disk image
> > to use, then just do a xm start config.file
> >
> > Hope that helped..
> >
> > - Kyle
> >
> > On 26/11/2011 3:12 PM, Antonio Colin wrote:
> >
> > Hi Guys,
> >
> > I have Debian 6 + Xen 4.1.1 and created a DomU with virt-manager after
> > creation:
> >
> > laptopvm:~# xm list
> > Name                                        ID   Mem VCPUs      State
> > Time(s)
> > Domain-0                                   0    1024     1
> > r-----    729.1
> > centos-4                                        512
> > 1                         0.0
> > laptopvm:~#
> >
> > Its config file is in:
> > /var/lib/xend/domains/c0e57693-78a5-0a0b-89b6-93034535ab5a/config.sxp
> >
> > Then I did a P2V of another OS and I have the *.img file and the config file
> > but I
> > can't get Xen recognize it as another domU.
> >
> > How can I make Xen/Xend do that as well as generate the UUIDs for the domU's
> > devices in its config.sxp file ?
> > Any useful commands?
> >
> > Regards,
> > Tony.
> >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >