Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Convert to libvirt failed by using unprivileged user, the user defined pool could not be recognized by virt-v2v.
Version-Release number of selected component (if applicable):
virt-v2v-0.6.2-4.el6.x86_64
libguestfs-1.7.17-17.el6.x86_64
libvirt-0.8.7-18.el6.x86_64
virt-manager-0.8.6-4.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. create a normal user (user1) on RHEL6.1 with libvirt installed
2. login as user1 and define a new pool (dir_pool_user1):
[user1@dhcp-8-218 ~]$ cat /tmp/dir_pool_user.xml
<pool type="dir">
<name>dir_pool_user1</name>
<target>
<path>/tmp/dir_pool_user1</path>
</target>
</pool>
[user1@dhcp-8-218 Desktop]$ virsh pool-list
Name State Autostart
-----------------------------------------
default active yes
dir_pool_user1 active no
3. Convert a remote VM to local libvirt pool by user1:
[user1@dhcp-8-218 Desktop]$ virt-v2v -ic xen+ssh://root.72.123 -op dir_pool_user1 xen-hvm-rhel5.7-x86_64
virt-v2v: Output pool dir_pool_user1 is not a valid storage pool
Actual results:
As step 3.
Expected results:
Below two result should be both OK:
Solution 1: The local pool defined by the unprivileged user can be recognized, and converting successfully
Solution 2: Document that virt-v2v converting can only be used by root user, no matter the target is libvirt or RHEV
Additional info:
Below sentence can be found in virt-v2v man page:
N.B. When exporting to RHEV, virt-v2v must run as root.
This is cause by the same underlying problem as bug 671094, namely that when running as non-root, the default libvirt target is still qemu:///system rather than qemu:///session.
*** This bug has been marked as a duplicate of bug 671094 ***