On 07/18/2012 06:00 PM, Trey Dockendorf wrote:
I'm attempting to fine-tune the process of getting my
KVM/Libvirt
managed VMs over into my new oVirt infrastructure, and the virt-v2v
import is failing in the WUI with "Failed to read VM 'dh-imager01'
OVF, it may be corrupted". I've attached both engine and vdsm logs
that are a snapshot from when I ran the virt-v2v command until I saw
the failure under Events.
matt - any thoughts?
virt-v2v command used...
# virt-v2v -i libvirtxml -o rhev -os
dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml
dh-imager01_sys.qcow2: 100%
[===========================================================================================================================================================================================================]D
0h00m37s
virt-v2v: dh-imager01 configured with virtio drivers.
The xml has been modified numerous times based on past mailing list
comments to have VNC and Network information removed, but still the
same failure. I've attached the latest XML that was used in the log's
failure as dh-imager01.xml. I've also tried passing hte bridge device
(ovirtmgmt) in the above command with same failure results.
Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and
ovirt-engine-3.1 respectively.
Please let me know what other configuration information could be
helpful to debug / troubleshoot this.
Are there any other methods besides a virt-v2v migration that can
allow me to use my previous KVM VMs within oVirt?
Thanks
- Trey
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users