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.
Bug 624062 - Tunnelled migration doesn't work in RHEL 6.0 without increasing security risk
Summary: Tunnelled migration doesn't work in RHEL 6.0 without increasing security risk
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Chris Lalancette
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-13 14:43 UTC by Justin Clift
Modified: 2015-07-13 04:34 UTC (History)
8 users (show)

Fixed In Version: libvirt-0.8.1-25.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 630625 (view as bug list)
Environment:
Last Closed: 2010-11-10 21:05:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Justin Clift 2010-08-13 14:43:08 UTC
Description of problem:

Due a bug in the location of a socket file with libvirt, tunnelled migration to move a virtual machine from one host server to another doesn't work in RHEL 6.0.

There *is* a workaround, of changing the process ownership of QEMU from the default qemu:qemu:, to root:root, however this introduces potential security risk.

Chris Lalancette has created (very simple) working patches upstream, which allow tunnelled migration to work properly out of the box.  (No change to root:root ownership needed)


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

libvirt 0.8.1-24 and earlier


How reproducible:

Every time.


Steps to Reproduce:
1. Using a standard installation of RHEL 6.0 running libvirt, attempt to migrate a virtual machine from one host server to another:

  # virsh migrate --live vm1 qemu+ssh://host2/system --p2p --tunnelled --desturi tcp:host2

Migration will fail every time.

  
Actual results:

Migration fails.


Expected results:

The guest virtual machine will migrate to the new host server without incident.


Additional info:

Comment 2 Daniel Veillard 2010-08-15 16:44:33 UTC
libvirt-0.8.1-25.el6 has been built in RHEL-6-candidate with the fixes,

Daniel

Comment 3 Justin Clift 2010-08-17 16:28:01 UTC
Tested tunnelled migration in libvirt-0.8.1-25.el6 with qemu:qemu owned QEMU.  It worked fine for me.

Comment 6 releng-rhel@redhat.com 2010-11-10 21:05:40 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.