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 1203367 - Fail to Migrate with Bridged network, eth + macvtap ,with different interface name on two hosts
Summary: Fail to Migrate with Bridged network, eth + macvtap ,with different interface...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Laine Stump
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1186142
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-18 17:01 UTC by Jan Kurik
Modified: 2019-05-20 11:37 UTC (History)
20 users (show)

Fixed In Version: libvirt-0.10.2-46.el6_6.4
Doc Type: Bug Fix
Doc Text:
The interface configuration of any libvirt domain which was of type='network' and referenced an "unmanaged" libvirt network had incorrect XML data for the interface transmitted during a migration, containing the "status" of the interface instead of the name of the network to use ("configuration"). As a consequence, the migration destination tried to set up the domain network interface using the status information from the source of the migration, and the migration thus failed. With this update, libvirt sends the configuration data for each device during migration rather than the status data, and the migration of a domain using interfaces of type='network' now succeeds.
Clone Of: 1186142
Environment:
Last Closed: 2015-04-01 06:15:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1185501 0 urgent CLOSED Sometimes cannot start/migrate vm with macvtap interface 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2015:0769 0 normal SHIPPED_LIVE libvirt bug fix update 2015-04-01 10:15:05 UTC

Internal Links: 1185501

Description Jan Kurik 2015-03-18 17:01:00 UTC 
This bug has been copied from bug #1186142 and has been proposed
to be backported to 6.6 z-stream (EUS).
Comment 8 Hu Jianwei 2015-03-26 04:40:38 UTC 
Verified as below:

[root@intel-i5-8-1 ~]# rpm -q libvirt qemu-kvm kernel
libvirt-0.10.2-46.el6_6.4.x86_64
qemu-kvm-0.12.1.2-2.445.el6.x86_64
kernel-2.6.32-504.el6.x86_64

On source host:
[root@intel-i5-8-1 ~]# virsh net-dumpxml vepa-net
<network connections='1'>
  <name>vepa-net</name>
  <uuid>237071e3-e3bc-3af6-4d23-c45b57815304</uuid>
  <forward dev='hjw' mode='vepa'>
    <interface dev='hjw' connections='1'/>
  </forward>
</network>

[root@intel-i5-8-1 ~]# virsh dumpxml mig | grep "/interface" -B6
    <interface type='direct'>
      <mac address='52:54:00:92:15:bf'/>
      <source dev='hjw' mode='vepa'/>
      <target dev='macvtap0'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
[root@intel-i5-8-1 ~]# virsh dumpxml mig --inactive| grep "/interface" -B6
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x2'/>
    </controller>
    <interface type='network'>
      <mac address='52:54:00:92:15:bf'/>
      <source network='vepa-net'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

[root@intel-i5-8-1 ~]# virsh migrate --live mig qemu+ssh://10.66.85.230/system --verbose
root.85.230's password: 
Migration: [100 %]

On destination host:
[root@amd-2427-32-2 ~]# virsh net-dumpxml vepa-net
<network connections='1'>
  <name>vepa-net</name>
  <uuid>bf754e24-0d2a-7777-362e-3b8f7cf043bc</uuid>
  <forward dev='eth0' mode='vepa'>
    <interface dev='eth0' connections='1'/>
  </forward>
</network>

[root@amd-2427-32-2 ~]# virsh dumpxml mig | grep "/interface" -B6
    <interface type='direct'>
      <mac address='52:54:00:92:15:bf'/>
      <source dev='eth0' mode='vepa'/>
      <target dev='macvtap0'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

Libvirt can report a more clear message when interface already has a passthru mode macvtap device. 
11: macvtap0@hjw: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether 52:54:00:92:15:bf brd ff:ff:ff:ff:ff:ff
    macvtap  mode passthru
[root@intel-i5-8-1 ~]# virsh start mig
error: Failed to start domain mig
error: error creating macvtap interface macvtap1@hjw (52:54:00:92:15:BF): Invalid argument

We can get expected results, changed to Verified.
Comment 11 errata-xmlrpc 2015-04-01 06:15:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0769.html
Note You need to log in before you can comment on or make changes to this bug.