Re: [Users] virt-v2v windows 2003 migration issue
On Fri, Nov 15, 2013 at 07:25:16PM +0100, Jakub Bittner wrote:
Hello,
I've been trying to convert libvirtd managed kvm guest which runs
windows 2003 (with virtio driver installed), but it failed in the
end.
Command:
virt-v2v -i libvirt -ic qemu+ssh://user@node.example.com/system -o
rhev -os 10.50.98.15:/backup_nfs -of qcow2 -oa sparse -n ovirtmgmt
windows2003
Error reported
virt-v2v: No app in config matches os='windows' name='virtio'
distro='windows' major='5' minor='2' arch='i386'
FWIW this corresponds to Windows Server 2003 R2 as you said above. So
I guess that your /var/lib/virt-v2v/virt-v2v.db or /etc/virt-v2v.conf
doesn't contain an OS matching this.
However my copy of virt-v2v.db certainly *does* have it:
<app os='windows' major='5' minor='2' arch='x86_64'
name='virtio'>
<path>/usr/share/virtio-win/drivers/amd64/Win2003</path>
</app>
I can't remember how this is added. Maybe you need to install the
virtio-win drivers?
Iam running virt-v2v on Fedora 19. OVirt is 3.3.0 version..
You probably want to ask Matt Booth about this ...
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)