Does anyone know if there is an issue with using the virt-v2v tool to output vm's to a RAID10 volume?

I ask because I got an error when attempting to do so once conversion was completed (converting from VMWare to KVM)...

and googling the error got me this...

from here: https://bugzilla.redhat.com/show_bug.cgi?id=749828

anyone esle come across this?

I'm guessing you're referring to writing to a backing store which is hosted on a RAID10 volume? If so, that's not problem the BZ is referring to. The BZ is specifically referring to guests which use MD devices internally. The underlying storage of the backing store doesn't affect qemu. It's actually already been fixed, too. I missed it when we were doing the latest libguestfs build, though, so it wasn't automatically updated. I just did it manually.

The issue you're having here is that libguestfs inspection isn't finding an operating system. There are numerous potential reasons for that. The quickest way to debug that is to run inspection on its own against the source VM. To help, I'm going to need a bit more information, though. Specifically:

* The versions of virt-v2v and libguestfs you're using
* The full virt-v2v command line you ran
* The operating system running in the guest

Incidentally, the best forum for virt-v2v discussions is the libguestfs mailing list (libguestfs@redhat.com).

Matt

Hi Matt, thanks for reply, the info is....

yum --version virt-v2v
3.2.29

yum --version libguestfs
3.2.29

Full virt line ran:
virt-v2v -ic esx://SOURCE_IP?no_verify=1 -o rhev -os DESTINATION_IP:/home/exports --network rhevm MyVM

MyVM running Win2003 SP2

/home/export is on a RAID10 volume. I've since had to go back to VMware for production reasons, but if anything occurs to you about the above setup it would be good to know as I intend to try again as soon as possible.

The command you're looking for is: 'rpm -q virt-v2v libguestfs'. The above is just printing out the version of yum

Yeah, /home/export on a RAID10 volume is fine. Is the host system RHEL? If it is, you additionally need to install a package called libguestfs-winsupport in order to support converting Windows guests. You'll find it in a separate channel on RHN called RHEL V2VWIN. If the host system is Fedora, the windows support is built in to the main libguestfs package. If it's CentOS, it's presumably kicking around somewhere. I'm not personally familiar with it, though.

I'd try that before anything else. It's a pretty common issue.

Thanks Matthew

rpm -q virt-v2v libguestfs
virt-v2v-0.8.3-5.el6.x86_64
libguestfs-1.7.17-26.el6.x86_64

The host is actually the hypervisor RHEV 3 beta by the way.

The RHEV 3 hypervisor is a spin of RHEL 6, so you'll definitely need to dig out libguestfs-winsupport from somewhere. I'm almost 100% sure that's your problem.