Libguestfs - Nov 2014 - Re: virt-v2v: Died at /usr/bin/virt-p2v-server line 411

Le 19/11/2014 13:03, Richard W.M. Jones a écrit :
> On Wed, Nov 19, 2014 at 12:58:11PM +0100, Nicolas Ecarnot wrote:
>> But it is now failing with an error message telling it can not
>> connect to the local socket /var/run/libvirt/libvirt-sock.
>
> This is basically a libvirt bug that you have to solve separately.
> I'm guessing that basic commands such as `virsh nodeinfo' also
fail.
>
> I don't know what the reason for that will be, but you can ask the
> libvirt users list to help you fix it.
>
>>> To avoid libvirt problems, do:
>>>
>>>     export LIBGUESTFS_BACKEND=direct
>>
>> But in this use case, I don't know where to set this variable?
>
> I believe it will work if you put this into root's .bash_profile or
> .bashrc (ie. /root/.bash_profile).
PROGRESS !

I added the setting above into the root profile, and now, things are 
beginning to move.

The first server I have to convert is a production server, so I can not 
easily halt it to run many test conversion.
So these days I'm trying to convert a VM (and I don't know if this is 
possible though I don't see why it wouldn't be).

When trying to p2v an Oracle Linux 7.0 VM, it ran very verbosely then 
failed saying it was not a kind of OS it knows how to convert.
When trying to p2v a old windows XP VM, it ran the same long way then 
failed telling that no root device was found in this operating system image.

As I read in detail the very long log, I saw different things failing, 
and amongst them, the issue telling that the 36:36 permissions on the 
NFS export share will prevent the import into RHEV. I don't know if it 
is an issue at this point. Anyway, I don't see any image coming into 
this nfs subtree at present.

Asap, I will try to run a P2V on the windows 2003 server source - the 
one I'm struggling for for weeks, and let you know.

Stay tuned.

PS : Thank you Richard for your support.

-- 
Nicolas Ecarnot

On Wed, Nov 19, 2014 at 02:41:49PM +0100, Nicolas Ecarnot
wrote:
> When trying to p2v an Oracle Linux 7.0 VM, it ran very verbosely
> then failed saying it was not a kind of OS it knows how to convert.
We could probably support OEL with a bit of effort, but it's not
supported now.  The virt-v2v manual (which you should read, as well as
the virt-p2v manual) provides a list of all OSes which are supported.
> When trying to p2v a old windows XP VM, it ran the same long way
> then failed telling that no root device was found in this operating
> system image.
Windows XP should work.  If it doesn't work you have to enable
debugging (this is now enabled by default in all new virt-p2v
versions), and then provide the full debug logs.  See the instructions
for where these are located on the conversion server.
> As I read in detail the very long log, I saw different things
> failing, and amongst them, the issue telling that the 36:36
> permissions on the NFS export share will prevent the import into
> RHEV. I don't know if it is an issue at this point. Anyway, I don't
> see any image coming into this nfs subtree at present.
When using '-o rhev', permissions should be set correctly for you
automatically.  Instead of summarising and interpreting what the debug
logs say (which is not useful), provide the debug logs.

However if it doesn't succeed in the conversion, then it's not going
to appear in RHEV.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v

Le 19/11/2014 15:03, Richard W.M. Jones a écrit :
> On Wed, Nov 19, 2014 at 02:41:49PM +0100, Nicolas Ecarnot wrote:
>> When trying to p2v an Oracle Linux 7.0 VM, it ran very verbosely
>> then failed saying it was not a kind of OS it knows how to convert.
>
> We could probably support OEL with a bit of effort, but it's not
> supported now.  The virt-v2v manual (which you should read, as well as
> the virt-p2v manual) provides a list of all OSes which are supported.
Richard,

Don't worry, I can ensure you that I'm reading and reading and reading 
again.
BTW, these docs are very well done. This is comfortable.

Concerning OL7, this is not a serious issue, this was just a test.
>> When trying to p2v a old windows XP VM, it ran the same long way
>> then failed telling that no root device was found in this operating
>> system image.
>
> Windows XP should work.  If it doesn't work you have to enable
> debugging (this is now enabled by default in all new virt-p2v
> versions), and then provide the full debug logs.  See the instructions
> for where these are located on the conversion server.
In the mean time, I googled around and found that though I copied the 
right virtio-win hierarchy into the conversion server, I also had to 
install the missing libguestfs-winsupport.
Another run of p2v of the previous windows XP succeed!
I did not try to import it into RHEV, but I can see it appearing in the 
export domain list. So I guess the hardest part is done.
>> As I read in detail the very long log, I saw different things
>> failing, and amongst them, the issue telling that the 36:36
>> permissions on the NFS export share will prevent the import into
>> RHEV. I don't know if it is an issue at this point. Anyway, I
don't
>> see any image coming into this nfs subtree at present.
>
> When using '-o rhev', permissions should be set correctly for you
> automatically.  Instead of summarising and interpreting what the debug
> logs say (which is not useful), provide the debug logs.
I knew you would say that, but I'm still searching for a way to 
copy-paste from a Dell iDrac environnment...

Well, now, I had the opportunity to run the real P2V on the 2003 server, 
and it is failing.
But it appears that the partition seems more complex than what I'm used 
to see ("two system (dell?) or windows system partitions").
I choose the third one, that is the one containing the system (C:) and 
marked as bootable.

It is failing very quickly, with the following error :
--------------------
Creating an overlay to protect the source blahblah
qemu-img create -q -f qcow2 -b 'nbd:localhost:55756' -o 
'compat=1.1,backing_fmt=raw' /var/tmp/v2vblahblah.qcow2
nbd.c:nbd_receive_negociate():L501: read failed
qemu-img: /var/tmp/v2vvovblahbla.qcow2: could not open 
'nbd:localhost:55756': could not open image: invalid argument: invalid 
argument

then other blahblahblah before closing.

I'll try another run by selecting every partition.



-- 
Nicolas Ecarnot