Bug 1639597 - RFE: allow tunnelled live migration over unix socket libvirt destination connection
Summary: RFE: allow tunnelled live migration over unix socket libvirt destination conn...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: libvirt
Version: 8.1
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: 8.1
Assignee: Virtualization Maintenance
QA Contact: Fangge Jin
URL:
Whiteboard:
Depends On: 1638889
Blocks: 1758964
TreeView+ depends on / blocked
 
Reported: 2018-10-16 07:38 UTC by Jaroslav Suchanek
Modified: 2020-02-25 13:55 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1638889
Environment:
Last Closed: 2020-02-25 13:55:30 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Suchanek 2018-10-16 07:38:24 UTC
+++ This bug was initially created as a clone of Bug #1638889 +++

Description of problem:

Libvirt prevents performing a live migration when the destination libvirt connection is a unix socket. 

In KubeVirt, we need the ability to tunnel a live migration through a unix socket to another network namespace which then connects to the destination libvirt.  From the libvirtd perspective in the source environment, it looks like we're attempting to migrate the domain to the same host since the destination connection is a local unix socket. 


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


How reproducible:
100%

Steps to Reproduce:
1. On the source node, create a socat connection that forwards all connections on a unix socket to a remote libvirtd instance.

Example.
socat unix-listen:local-destination-socket,reuseaddr,fork tcp:192.168.66.102:22222


2. Attempt to perform a live migration with the local unix socket 'local-destination-socket' as the destination. 

Example:
virsh migrate --copy-storage-all --tunnelled --p2p --live --xml domain.xml my-vm qemu+unix:///system?socket=local-destination-socket

Actual results:

error "Attempt to migrate guest to the same host"

Expected results:

successful migration

Comment 2 Peter Krempa 2020-02-25 13:55:30 UTC
In general I don't think we want to promote tunelled migration any more. There are many qemu features which now require separate connection. Please reopen this if you still think it's necessary with appropriate justification.


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