Re: [Users] virt-v2v windows 2003 migration issue

2013-11-20 Thread Jakub Bittner

Dne 20.11.2013 19:52, Richard W.M. Jones napsal(a):

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://u...@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:

   
 /usr/share/virtio-win/drivers/amd64/Win2003
   

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.


Hello,
thank you for reply. I added windows 2003 entry, copied files from 
virtio-win iso to directory, but it failed again. I give it up, because 
converting is way too slow and always fails in the end. I found, that 
best way to convert virtual machine is with clonezilla and nfs.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] virt-v2v windows 2003 migration issue

2013-11-20 Thread Richard W.M. Jones

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://u...@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:

  
/usr/share/virtio-win/drivers/amd64/Win2003
  

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#)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] virt-v2v windows 2003 migration issue

2013-11-15 Thread Jakub Bittner

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://u...@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'


Iam running virt-v2v on Fedora 19. OVirt is 3.3.0 version..
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users