Bug 681386

Summary: Can't connect to remote host, storage pool invalid
Product: [Fedora] Fedora Reporter: Victor Sira <vsira>
Component: virt-v2vAssignee: Matthew Booth <mbooth>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: crobinso, mbooth, virt-maint, zbrown
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-06 17:53:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Victor Sira 2011-03-02 00:20:11 UTC 
Description of problem:

We're attempting to connect to a remote host with the XEN hypervisor and attempting a v2v connection. The XEN host or hosts are running Red Hat Cluster Suite and have the guests running on shared storage. Starting, Stopping and Migration is controlled with the Red Hat Cluster Suite tools.

When we attempt the command:

virt-v2v -ic xen+ssh://xqist-t220-b5 -network DEST_NET -o rhev -osd some-nfs-server:/my-path/my-export-domain myhost
root@xqist-t220-b5's password:

virt-v2v: Failed to retrieve storage volume /xen02/qistadssd85/drive1.img:libvirt error code: 47, message: invalid storage volume pointer in no storage vol with matching path 

It appears that libvirt is not recognizing the underlying XEN environment and not able to locate the VM or the storage pools that the guests are using.

Version-Release number of selected component (if applicable):


How reproducible:

All the time.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

virt-v2v: Failed to retrieve storage volume /xen02/qistadssd85/drive1.img:libvirt error code: 47, message: invalid storage volume pointer in no storage vol with matching path 

Expected results:

The guest is migrated to the RHEV export domain.

Additional info:

If we copy the disk image and the dumpxml file of the corresponding guest to a third machine and perform the export using -i libvirtxml, the operation works as expected.
Comment 1 Matthew Booth 2011-03-02 10:02:49 UTC 
I suspect you're hitting a known current limitation in libvirt. virt-v2v relies on libvirt for volume information, but libvirt will only return information for volumes which are in a defined pool. I suspect that there is no pool on the remote server which contains /xen02/qistadssd85/drive1.img. The workaround is to define one.

The easiest way to do this is with virt-manager. Run:

virt-manager -c xen+ssh://xqist-t220-b5

Highlight the xen connection and go to Edit->Connection Details->Storage. Create a new directory storage pool called whatever you like. Ensure that the target path is /xen02/qistadssd85.

This won't create, delete, or modify in any way the contents of this directory. It'll just cause it to manage what's already there.
Comment 2 Cole Robinson 2012-06-06 17:53:21 UTC 
Needinfo unresponded for a while (and F14 is end of life), so closing.