← Back to team overview

registry team mailing list archive

[Bug 579892] Re: libvirt should not use the MAC address assigned to tap devices/vnet interfaces by the TAP/TUN driver

 

This debdiff adds the patch which fixes this bug.

** Patch added: "debdiff of patch against current lucid libvirt"
   https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/579892/+attachment/1730070/+files/mac.debdiff

** Changed in: libvirt (Ubuntu)
       Status: Fix Committed => Fix Released

** Description changed:

  On Ubuntu 10.04 I have problems using libvirt with a bridge because the
  TUN devices get random mac addresses and thus, change the bridge device
  mac address, which takes the lower mac addres of all devices attached to
  the bridge. The main and most critical problem is that, sometimes, we
  lose network connectivity for several seconds (usually 10-20 seconds) on
  the libvirt host and all its guests when a guest is powered off.
  
  Searching for similar problems I found my problem described at
  https://bugzilla.redhat.com/show_bug.cgi?id=571991
+ 
+ Impact: Random loss of network connectivity on guest power on/off.
+ 
+ Fix: This bug was fixed upstream and in maverick, using the same patch
+      (modulo porting0 which is added by the debdiff attached here.  It
+      forces libvirt to ensure that the bridge mac address is lower than
+      that of any of its devices.
+ 
+ Patch: debdiff is attached
+ 
+ Instructions: Power bridged guests on/off in libvirt, while continuously
+       checking network connectivity to existing guests.
+ 
+ Regression: The patch itself should definately be safe, since it is
+       ported from the fix in the redhat bug.

-- 
 libvirt should not use the MAC address assigned to tap devices/vnet interfaces by the TAP/TUN driver
https://bugs.launchpad.net/bugs/579892
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fedora.



References