As this has a workaround (in comment #11), making this low priority, I'm
marking this wontfix for lucid.
** Changed in: libvirt (Ubuntu Lucid)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: libvirt (Ubuntu Lucid)
Status: New = In Progress
** Changed in: libvirt (Ubuntu Lucid)
Importance: Undecided = Low
** Changed in: libvirt (Ubuntu Lucid)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a
@Marcelo,
regarding comment #11: it sure sounds like a good workaround. Have you
been using it, and can you verify that it works for you?
** 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
(If answer to comment #14 is 'no', then I will reprioritize this bug to
medium)
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
Marked verification-done per Alex's confirmation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/579892
Title:
libvirt should not use the MAC address assigned to tap devices/vnet
@Serge,
Yes, I've using that suggestion (pre-up ) in the
/etc/network/interfaces file of the KVM Host, and the interface freeze
problem disappeared since I added that line, a month ago.
I'd recommend to use it and check if it works for you too.
Regards,
Marcelo
--
You received this bug
Quoting Marcelo Fernandez (marcelo.fidel.fernan...@gmail.com):
@Serge, where is located that PPA with Lucid's libvirt package fixed, so
I can test it too?
Do you know when this it's going to be SRU'd? It's been a lot of time
since Lucid (LTS) is out and this bug is *very* annoying. :-/
Hi
@Serge, where is located that PPA with Lucid's libvirt package fixed, so
I can test it too?
Do you know when this it's going to be SRU'd? It's been a lot of time
since Lucid (LTS) is out and this bug is *very* annoying. :-/
Thanks
--
You received this bug notification because you are a member
I have another question,
Putting pre-up ifconfig eth0 hw ether 00:00:00:00:00:01 in the
interfaces config file, like Carlos did, is a workaround to the bug?
Just to clarify :-)
Regards
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: libvirt (Ubuntu Lucid)
Importance: Undecided
Status: New
--
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
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
Sven and Sven,
sorry - a fix for this had been backported to lucid and tested, but
now I see that the bug it had been targeted to ended up being
invalidated, so that fix never ended up being SRU'd into lucid.
I'm doing that now.
--
libvirt should not use the MAC address assigned to tap
(Before doing the final steps in SRU process, I want to upload this fix to a PPA
and test it one more time)
--
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
(Tested upgrade on lucid partition on my laptop)
--
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 Ubuntu
Server Team, which is subscribed
If anyone has experienced this problem on Hardy, please chime in here. I had
a patch at
https://launchpad.net/~serge-hallyn/+archive/libvirt-fix-macaddr?field.series_filter=hardy
which can be forward-ported if need be, but I've not heard anyone mention
having this
bug on Hardy, so don't want to
Second that. This bug is very annoying..
--
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 Ubuntu
Server Team, which is subscribed to
Hi,
may i ask where the fix is? Its still in lucid and kills connectivity.
Regards,
Sven
--
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
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
--
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 Ubuntu
Server Team, which
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Committed
--
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 Ubuntu
Server
This is my network configuration:
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off
pre-up ifconfig eth0 hw ether 00:00:00:00:00:01
The macaddress change is the workaround I'm using right now
Could you post the libvirt xml configuration of your guests and network?
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
libvirt should not use the MAC address assigned to tap devices/vnet interfaces
by the
21 matches
Mail list logo
