Bug 1314307

Summary:	the mac setting is too early when macvtap virtual machine does live migrating
Product:	[Community] Virtualization Tools	Reporter:	Michael Liu <ztehypervisor>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	crobinso, dyuan, laine, mzhan, ztehypervisor
Target Milestone:	---	Flags:	ztehypervisor: needinfo-
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-03 09:34:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michael Liu 2016-03-03 11:47:51 UTC

Description of problem:
start the virtual machine vm 1 with macvtap net device, on another host there is one same virtual machine vm2, and vm2 can ping packets to vm1. When vm1 live migrates to the host which has the virtual machine vm2, the time of ping interuption is too long.

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

How reproducible:


Steps to Reproduce:
1. Start the virtual machine vm 1 with macvtap net device
2. On another host, start one same virtual machine vm2
3. Vm2 can ping packets to vm1
4. Vm1 does live migration to the host which has the virtual machine vm2

Actual results:
the time of ping interuption is too long

Expected results:


Additional info:

Comment 1 Cole Robinson 2016-04-10 22:11:46 UTC

What distro are you using? What guest OS?
What does 'too long' mean specifically? How long does the migration itself take?

Comment 2 Michael Liu 2016-04-26 22:56:07 UTC

(In reply to Cole Robinson from comment #1)
> What distro are you using? What guest OS?
> What does 'too long' mean specifically? How long does the migration itself
> take?

Thanks for your reply.
The host OS is centos7.0, the same to the guest. Libvirt version is 1.2.21.
The time of ping interuption is too long, this 'too long' takes about 200 seconds.
About the migration time, I will check again and reply to you.

Comment 3 Cole Robinson 2016-04-27 16:11:26 UTC

Where does libvirt 1.2.21 come from? The official centos versions are different AFAICT. If you can try a newer libvirt version that would help (this bug tracker tends to only track latest libvirt versions)

Comment 4 Laine Stump 2016-04-27 20:28:35 UTC

As far as I can tell, CentOS 7.0 has libvirt 1.1.1.

This sounds eerily similar to a bug that was fixed in libvirt 1.2.12 - Bug 1081461. Those patches were also backported to the RHEL libvirt version 1.2.8-11 which was in RHEL/CentOS 7.1.

Is there a chance you're misreading your version number?

Comment 5 Michael Liu 2020-01-03 09:34:54 UTC

EOL