Bug 969054
Summary: | Cannot use migration network on a source host with multiple NICs | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Assaf Muller <amuller> | |
Component: | vdsm | Assignee: | Assaf Muller <amuller> | |
Status: | CLOSED NOTABUG | QA Contact: | ||
Severity: | low | Docs Contact: | ||
Priority: | low | |||
Version: | 3.3.0 | CC: | abaron, bazulay, danken, hateya, iheim, jkt, lpeer, sgrinber | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | network | |||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 971394 (view as bug list) | Environment: | ||
Last Closed: | 2013-07-14 14:49:28 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 971394 | |||
Bug Blocks: |
Description
Assaf Muller
2013-05-30 14:47:45 UTC
Proposed Solution: We need the ability to specify the source address when setting up the migration socket. Currently QEMU and Libvirt don't support this feature. The cleanest implementation for this issue requires some work on upstream qemu and libvirt, as qemu does expose the ability to set the source address of migration traffic (from qmp-commands.hx): migrate ------- Migrate to URI. Arguments: - "blk": block migration, full disk copy (json-bool, optional) - "inc": incremental disk copy (json-bool, optional) - "uri": Destination URI (json-string) Another alternative would be to set a special destination routing before migration starts. I believe that this alternative would prove fragile, and that it should not be taken before we see a proven need for cross-subnet migration. Closed: The recommended configuration is to perform migrations between hosts on layer 2. Migration between hosts that are on different subnets doesn't perform so well. Therefor, it is assumed that the migration network is present on all hosts in the cluster. This makes this bug not a bug. Even if both hosts have multiple NICs, since it is assumed that they're on the same subnet, then both hosts have the migration network and are connected via layer 2. The source host will get the destination IP address of the destination host from the engine, and the source IP will be chosen automatically to be the local interface that's in the migration network. |