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:
In virt-v2v manual,there is description of -ic parameter as:
-ic URI
Specifies the connection to use when using the libvirt input method. If omitted, this defaults to
qemu:///system when virt-v2v runs as root, or qemu:///session when virt-v2v runs as a regular user
When use virt-v2v as regular user,the -ic parameter descripted in virt-v2v manual doesn't match the actual behaviour
Version-Release number of selected component (if applicable):
virt-v2v-0.8.3-5.el6.x86_64
libguestfs-1.7.17-26.el6.x86_64
libvirt-0.9.4-20.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.Make sure there are two pools created by non-root user,and there is a guest in one pool.
[tzheng@tzheng-linux ~]$ virsh pool-list
Name State Autostart
-----------------------------------------
test-pool active no
tzheng-pool active no
[tzheng@tzheng-linux ~]$ virsh list --all
Id Name State
----------------------------------
- esx4.0-rhel5.6-x86_64 shut off
2.Use virt-v2v to convert the guest to another pool as non-root user.
[tzheng@tzheng-linux ~]$ virt-v2v -os test-pool -on test esx4.0-rhel5.6-x86_64
virt-v2v: Failed to connect to qemu:///system: libvirt error code: 45, message: authentication failed: authentication failed
When I add "-ic qemu:///session" to the command,it will convert successfully.
[tzheng@tzheng-linux ~]$ virt-v2v -ic qemu:///session -os test-pool -on test esx4.0-rhel5.6-x86_64
ESX4.0-rhel5u6-64b_ESX4.0-rhel5u6-64b: 100% [=====================================================================]D 0h03m04s
virt-v2v: test configured with virtio drivers.
Actual results:
If omit the -ic parameter,the error message showed as:Failed to connect to qemu:///system.
Expected results:
Since in virt-v2v manual,if omit the -ic parameter as regular user,it defaults to qemu:///session,so the error message showed should be:Failed to connect to qemu:///session
Additional info:
As communicated with Matthew,the priority and severity of the bug is low,it can be fixed in 6.3.
Comment 2RHEL Program Management
2012-05-03 04:38:22 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
So the solution is to update man page:
-ic URI
Specifies the connection to use when using the libvirt input method. If omitted, this defaults to
qemu:///system
Or to fix it in the source code?
Comment 4Richard W.M. Jones
2014-11-18 11:26:04 UTC