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:
Install vdsm on virt-v2v host,then run virt-v2v to convert a guest,it will fail.
Version-Release number of selected component (if applicable):
virt-v2v-0.8.2-1.el6.x86_64
libvirt-0.9.4-0rc2.el6.x86_64
libguestfs-1.7.17-19.el6.x86_64
vdsm-4.9-86.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.Install vdsm on virt-v2v host,#yum install vdsm
2.Run virt-v2v:
#virt-v2v -ic qemu+ssh:///10.66.72.122/system -os home kvm-rhel5.7-i386
Actual results:
virt-v2v fail with message:
virt-v2v -ic qemu+ssh:///10.66.72.122/system -os home kvm-rhel5.7-i386
virt-v2v: Failed to connect to qemu:///system: libvirt error code: 45, message: authentication failed: Failed to step SASL negotiation: -7 (SASL(-7): invalid parameter supplied: Unexpectedly missing a prompt result)
Expected results:
virt-v2v will pop up authentication to libvirt and then virt-v2v convert successfully.
Additional info:
Add "#" to auth_unix_rw="sasl" in file /etc/libvirt/libvirtd.conf ,virt-v2v can convert successfully.
This is not a bug IMHO, your libvirt is configured using sasl as authentication method for unix socket. however, you don't tell this to virt-v2v, virt-v2v has an option to specify the target libvirt uri format.
(In reply to comment #2)
> This is not a bug IMHO, your libvirt is configured using sasl as authentication
> method for unix socket. however, you don't tell this to virt-v2v, virt-v2v has
> an option to specify the target libvirt uri format.
Hi Osier
When installing vdsm,it will add:
auth_unix_rw="sasl" # by vdsm
to /etc/libvirt/libvirtd.config,we didn't configure it alone.So virt-v2v need to provide authentication to libvirt as default.
Comment 7RHEL Program Management
2012-12-14 07:07:02 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 9Richard W.M. Jones
2014-11-18 11:20:18 UTC