[Users] v2v error

suporte at logicworks.pt suporte at logicworks.pt
Tue May 7 16:51:03 UTC 2013


Hi, 

I did that but it fails, maybe the KVM disk has to be the same size or bigger? 

Regards 
Jose 

----- Original Message -----

From: "Michael Wagenknecht" <Wagenknecht at FuH-E.de> 
To: users at ovirt.org 
Sent: Terça-feira, 7 de Maio de 2013 12:47:52 
Subject: Re: [Users] v2v error 

Hi, 
the folder images/<imgId> contains the virtual disks. Every disk in a separate folder. 
You can ignore the .meta file in the images folder. 
The other one is the image file. You can check it with the command: 
qemu-img info f89d8ca3-f65c-45a0-8f2e-df2f05014d0b 

The folder master/vms/<vmId> contains a description file of the vm in the .ovf format. 
When your VM uses more than one virtual disks, there you can find the imgId of the disks. 

Regards, Michael 


Am 07.05.2013 13:24, schrieb suporte at logicworks.pt : 


Hi Michael, 

Thanks. One question, Myexported VM has the name Fedora, how can I identify it on the system? 
In the export domain i have 
drwxr-xr-x. 2 vdsm kvm 4096 Apr 12 17:07 dom_md 
drwxr-xr-x. 3 vdsm kvm 4096 May 7 10:57 images 
drwxr-xr-x. 4 vdsm kvm 4096 Apr 12 17:08 master 

and in 
/mnt/398da79f-53e1-43dd-8836-e58edd4de975/images/2a95635c-3e1b-45a6-be8c-fa66317b6475 
I have 
-rw-rw----. 1 vdsm kvm 1073741824 May 7 10:59 f89d8ca3-f65c-45a0-8f2e-df2f05014d0b 
-rw-r--r--. 1 vdsm kvm 269 May 7 10:57 f89d8ca3-f65c-45a0-8f2e-df2f05014d0b.meta 

which one is the exported VM? 

----- Original Message -----

From: "Michael Wagenknecht" <Wagenknecht at FuH-E.de> 
To: users at ovirt.org 
Sent: Terça-feira, 7 de Maio de 2013 7:33:49 
Subject: Re: [Users] v2v error 

Hi, 
I had the same problem some weeks ago. After many hours of try an error I went another way. 
I made a new VM on the ovirt engine with the same parameter than the kvm VM. Especially the "Allocation Policy" of the virtual disk is important (Preallocated for raw images and Thin Provision for qcow images). Then I export the VM. Then I copy the image from the KVM server to the ovirt export folder and override the empty one. Please check the permissions. Now you can import the VM. 
I go this way with a lot of linux and windows VMs. 

Regards, Michael 


Am 07.05.2013 01:52, schrieb suporte at logicworks.pt : 
<blockquote>


This is what I get if run LIBGUESTFS_DEBUG=1 virt-v2v -i libvirt -ic qemu+ssh://root@IP-Address/system -o rhev -os nfs.domain.local:/ovirt/export -of qcow2 -oa sparse -n ovirtmgmt VM_Name 



Fedora14.qcow2: 100% [===============================================]D 0h59m31s 
libguestfs: create: flags = 0, handle = 0x2d8fdd0 
libguestfs: launch: attach-method=libvirt 
libguestfs: launch: tmpdir=/tmp/libguestfs4jk5Wh 
libguestfs: launch: umask=0022 
libguestfs: launch: euid=36 
libguestfs: libvirt version = 10002 (0.10.2) 
libguestfs: [00000ms] connect to libvirt 
libguestfs: opening libvirt handle: URI = NULL, auth = virConnectAuthPtrDefault, flags = 0 
libguestfs: successfully opened libvirt handle: conn = 0x2d7b690 
libguestfs: [00164ms] get libvirt capabilities 
libguestfs: [05465ms] parsing capabilities XML 
libguestfs: [05467ms] build appliance 
libguestfs: command: run: febootstrap-supermin-helper 
libguestfs: command: run: \ --verbose 
libguestfs: command: run: \ -u 36 
libguestfs: command: run: \ -g 36 
libguestfs: command: run: \ -f checksum 
libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d 
libguestfs: command: run: \ x86_64 
supermin helper [00002ms] whitelist = (not specified), host_cpu = x86_64, kernel = (null), initrd = (null), appliance = (null) 
supermin helper [00002ms] inputs[0] = /usr/lib64/guestfs/supermin.d 
checking modpath /lib/modules/3.8.6-203.fc18.x86_64 is a directory 
picked vmlinuz-3.8.6-203.fc18.x86_64 because modpath /lib/modules/3.8.6-203.fc18.x86_64 exists 
checking modpath /lib/modules/3.8.11-200.fc18.x86_64 is a directory 
picked vmlinuz-3.8.11-200.fc18.x86_64 because modpath /lib/modules/3.8.11-200.fc18.x86_64 exists 
checking modpath /lib/modules/3.8.8-202.fc18.x86_64 is a directory 
picked vmlinuz-3.8.8-202.fc18.x86_64 because modpath /lib/modules/3.8.8-202.fc18.x86_64 exists 
supermin helper [00002ms] finished creating kernel 
supermin helper [00003ms] visiting /usr/lib64/guestfs/supermin.d 
supermin helper [00003ms] visiting /usr/lib64/guestfs/supermin.d/base.img 
supermin helper [00010ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img 
supermin helper [00052ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles 
supermin helper [00748ms] visiting /usr/lib64/guestfs/supermin.d/init.img 
supermin helper [00762ms] visiting /usr/lib64/guestfs/supermin.d/udev-rules.img 
supermin helper [00770ms] adding kernel modules 
supermin helper [00898ms] finished creating appliance 
libguestfs: checksum of existing appliance: 7705d920c064a722def20ac25b6fb162ceec1019efac541dacfea976a5540326 
libguestfs: [06509ms] begin building supermin appliance 
libguestfs: [06509ms] run supermin-helper 
libguestfs: command: run: febootstrap-supermin-helper 
libguestfs: command: run: \ --verbose 
libguestfs: command: run: \ -u 36 
libguestfs: command: run: \ -g 36 
libguestfs: command: run: \ --copy-kernel 
libguestfs: command: run: \ -f ext2 
libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d 
libguestfs: command: run: \ x86_64 
libguestfs: command: run: \ /var/tmp/guestfs.uYx5Jb/kernel 
libguestfs: command: run: \ /var/tmp/guestfs.uYx5Jb/initrd 
libguestfs: command: run: \ /var/tmp/guestfs.uYx5Jb/root 
supermin helper [00001ms] whitelist = (not specified), host_cpu = x86_64, kernel = /var/tmp/guestfs.uYx5Jb/kernel, initrd = /var/tmp/guestfs.uYx5Jb/initrd, appliance = /var/tmp/guestfs.uYx5Jb/root 
supermin helper [00001ms] inputs[0] = /usr/lib64/guestfs/supermin.d 
checking modpath /lib/modules/3.8.6-203.fc18.x86_64 is a directory 
picked vmlinuz-3.8.6-203.fc18.x86_64 because modpath /lib/modules/3.8.6-203.fc18.x86_64 exists 
checking modpath /lib/modules/3.8.11-200.fc18.x86_64 is a directory 
picked vmlinuz-3.8.11-200.fc18.x86_64 because modpath /lib/modules/3.8.11-200.fc18.x86_64 exists 
checking modpath /lib/modules/3.8.8-202.fc18.x86_64 is a directory 
picked vmlinuz-3.8.8-202.fc18.x86_64 because modpath /lib/modules/3.8.8-202.fc18.x86_64 exists 
supermin helper [00110ms] finished creating kernel 
supermin helper [02561ms] finished mke2fs 
supermin helper [02563ms] visiting /usr/lib64/guestfs/supermin.d 
supermin helper [02563ms] visiting /usr/lib64/guestfs/supermin.d/base.img 
supermin helper [11451ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img 
supermin helper [11522ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles 
supermin helper [38004ms] visiting /usr/lib64/guestfs/supermin.d/init.img 
supermin helper [38010ms] visiting /usr/lib64/guestfs/supermin.d/udev-rules.img 
supermin helper [38016ms] adding kernel modules 
supermin helper [62584ms] closing ext2 filesystem 
supermin helper [62585ms] finished creating appliance 
libguestfs: [69110ms] finished building supermin appliance 
libguestfs: command: run: rm 
libguestfs: command: run: \ -rf /var/tmp/guestfs.uYx5Jb 
libguestfs: command: run: qemu-img 
libguestfs: command: run: \ create 
libguestfs: command: run: \ -f qcow2 
libguestfs: command: run: \ -b /var/tmp/.guestfs-36/root.14358 
libguestfs: command: run: \ -o backing_fmt=raw 
libguestfs: command: run: \ /tmp/libguestfs4jk5Wh/snapshot1 
Formatting '/tmp/libguestfs4jk5Wh/snapshot1', fmt=qcow2 size=4294967296 backing_file='/var/tmp/.guestfs-36/root.14358' backing_fmt='raw' encryption=off cluster_size=65536 lazy_refcounts=off 
libguestfs: command: run: qemu-img 
libguestfs: command: run: \ create 
libguestfs: command: run: \ -f qcow2 
libguestfs: command: run: \ -b /tmp/etlVovb09U 
libguestfs: command: run: \ -o backing_fmt=raw 
libguestfs: command: run: \ /tmp/libguestfs4jk5Wh/snapshot2 
Formatting '/tmp/libguestfs4jk5Wh/snapshot2', fmt=qcow2 size=446464 backing_file='/tmp/etlVovb09U' backing_fmt='raw' encryption=off cluster_size=65536 lazy_refcounts=off 
libguestfs: [69351ms] create libvirt XML 
virt-v2v: Failed to launch guestfs appliance. Try running again with LIBGUESTFS_DEBUG=1 for more information 
libguestfs: closing guestfs handle 0x2d8fdd0 (state 0) 
libguestfs: command: run: rm 
libguestfs: command: run: \ -rf /tmp/libguestfs4jk5Wh 





----- Original Message -----

De: suporte at logicworks.pt 
Para: Users at ovirt.org 
Enviadas: Segunda-feira, 6 Maio, 2013 23:45:36 
Assunto: [Users] v2v error 




I'm trying to export a VM from KVM. It's a Fedora14 machine. 

I run: virt-v2v -i libvirt -ic qemu+ssh://root@IP-Address/system -o rhev -os nfs.domain.local:/ovirt/export -of qcow2 -oa sparse -n ovirtmgmt VM_Name 



It starts to buid the umage but in the end I have an error message: 

virt-v2v: Failed to launch guestfs appliance. Try running again with LIBGUESTFS_DEBUG=1 for more information 



Something wrong with the guestfs? 



Jose 



-- 


Jose Ferradeira 
http://www.logicworks.pt 


_______________________________________________ 
Users mailing list 
Users at ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 




_______________________________________________
Users mailing list Users at ovirt.org http://lists.ovirt.org/mailman/listinfo/users 


-- 
Mit freundlichen Grüßen

Michael Wagenknecht
FuH Entwicklungsgesellschaft mbH
Geschäftsführer Carola Fornoff
HRB Freiburg 701203, UID DE255007372
Hauptstr. 4, D-79224 Umkirch
Tel +49 7665 93288-0, Fax -150 
_______________________________________________ 
Users mailing list 
Users at ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 


</blockquote>

-- 
Mit freundlichen Grüßen

Michael Wagenknecht
FuH Entwicklungsgesellschaft mbH
Geschäftsführer Carola Fornoff
HRB Freiburg 701203, UID DE255007372
Hauptstr. 4, D-79224 Umkirch
Tel +49 7665 93288-0, Fax -150 
_______________________________________________ 
Users mailing list 
Users at ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130507/87e34ddc/attachment-0001.html>


More information about the Users mailing list