I'm going to mark this as Fix Released because I've been running Jaunty
throughout the cycle and have not hit this bug.
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
--
[hardy] libvirt loses ip for vnet0, which breaks dnsmasq
https://bugs.launchpad.net/bugs/198541
You receiv
Please note that the hal patch to show virtual network devices is in
Jaunty (coming from upstream).
--
[hardy] libvirt loses ip for vnet0, which breaks dnsmasq
https://bugs.launchpad.net/bugs/198541
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
--
[hardy] libvirt loses ip for vnet0, which breaks dnsmasq
https://bugs.launchpad.net/bugs/198541
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Latest hal fixed this issue. Adjusted milestone for post-hardy as this
will come up when the hal patched is reintroduced.
** Changed in: libvirt (Ubuntu)
Target: None => later
--
[hardy] libvirt loses ip for vnet0, which breaks dnsmasq
https://bugs.launchpad.net/bugs/198541
You received t
FYI, I uploaded a new hal into hardy which reverts the recent patch to
detect virtual network interfaces. So this is at least not a blocker for
hardy any more, but one day it will come back, so it eventually needs to
get fixed.
--
[hardy] libvirt loses ip for vnet0, which breaks dnsmasq
https://b
Well, I meant this line seems to be the problem:
Mar 4 18:05:36 foo avahi-daemon[7400]: Withdrawing address record for
192.168.122.1 on vnet0.
--
[hardy] libvirt loses ip for vnet0, which breaks dnsmasq
https://bugs.launchpad.net/bugs/198541
You received this bug notification because you are a m
