Bug 1638882 - RFE: option to allow live migration between hosts with the same hostname
Summary: RFE: option to allow live migration between hosts with the same hostname
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1639596
TreeView+ depends on / blocked
 
Reported: 2018-10-12 17:22 UTC by David Vossel
Modified: 2020-04-17 13:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1639596 (view as bug list)
Environment:
Last Closed: 2020-04-17 13:41:39 UTC


Attachments (Terms of Use)

Description David Vossel 2018-10-12 17:22:24 UTC
Description of problem:

In KubeVirt we have a somewhat unique use case where we need to migration between two libvirt environments that have the same hostname. There's a check in libvirt that prevents this from being possible.

"Attempt to migrate guest to the same host"

Normally that makes complete sense. However for our use case, we are migrating a VM between two containerized environments scheduled by kubernetes that exist on different hosts. We need both the source and target containerized environments (pods) to look identical in order to operate within kubernetes in a predictable way. This makes libvirt think we're attempting a live migration to the same node when in fact we are not. 


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


How reproducible:

100%

Steps to Reproduce:
1. attempt to perform a live migration between two nodes with the same hostname.




Additional info:

Comment 3 Daniel Berrangé 2020-04-17 13:41:39 UTC
This was fixed in

commit 6799b72d927015db4ce4cab879f072abc91a41ae
Author: Michal Prívozník <mprivozn@redhat.com>
Date:   Tue Feb 25 15:53:12 2020 +0100

    qemu: Don't compare local and remote hostnames on migration


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