As per comment #10, I don't feel this bug is valid. Shutting down
libvirt should not shut down interfaces as VMs may still be running.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
There is no agreed upon fix to push upstream. Near as I can tell, the
consensus is in fact that libvirt is doing the right thing. That VMs
can continue running when you stop or restart libvirt-bin, and therefore
it would be wrong for libvirt to shut down its networking.
In which case I'd ask why
Has anyone pushed this upstream ?
--
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/345485
Title:
libvirt does not remove interfaces on stop
--
Ubuntu-server-bugs mailing list
Ubuntu
not sure if this should be a separate item or not, but as well as the
interface it doesn't restart dnsmasq.
For anyone else trying to do that I believe the steps needed are:
stop libvirt-bin
killall dnsmasq (assuming you don't have another)
ifconfig virbr0 down
brctl delbr virbr0
now, if
Unassigning myself, won't-fix for Lucid, as we don't yet have an agreed
upon approach, and this bug is not release critical.
** Changed in: libvirt (Ubuntu Lucid)
Assignee: Dustin Kirkland (kirkland) => (unassigned)
** Changed in: libvirt (Ubuntu Lucid)
Status: Confirmed => Won't Fix
Moving back to Confirmed as the original fix was reverted
** Changed in: libvirt (Ubuntu Lucid)
Status: Fix Released => Confirmed
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Serv
This bug was fixed in the package libvirt - 0.7.5-5ubuntu20
---
libvirt (0.7.5-5ubuntu20) lucid; urgency=low
* debian/libvirt-bin.upstart:
- remove unnecessary pid file existence test, LP: #510658
- revert virbr0 up/down hack added in 0.7.5-5ubuntu17, LP: #345485
-- Dustin
Uploaded a revert, in pending queue, should be approved after beta2
releases.
** Changed in: libvirt (Ubuntu Lucid)
Status: In Progress => Fix Committed
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are
** Changed in: libvirt (Ubuntu Lucid)
Status: Fix Released => In Progress
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
U
Loic, agreed. I'm going to revert this upload.
:-Dustin
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs maili
True, I'd forgotten that libvirt could be stopped and the VMs remain
running.
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubun
I don't think it's that obvious, it might have to preserve state across
restarts for instance. Depends whether some vms are running and using
the libvirt networks or not.
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification becau
If it created the interface on it's startup, it should remove the
interface on it's shutdown. Simple as that.
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
I don't think this is correct the correct place to fix the bug; the name
"virbr0" shouldn't be hardcoded in the upstart script and the command-
line "ifconfig virbr0 start" is bogus anyway. For instance, I
personally disable the virbr0 interface, but I could easily imagine
people renaming it or ha
This bug was fixed in the package libvirt - 0.7.5-5ubuntu17
---
libvirt (0.7.5-5ubuntu17) lucid; urgency=low
* debian/libvirt-bin.upstart: bring virbr0 up/down on upstart start/stop
of libvirt, LP: #345485
-- Dustin KirklandThu, 01 Apr 2010 23:08:33 -0500
** Changed in: li
** Also affects: libvirt (Ubuntu Lucid)
Importance: Low
Status: Confirmed
** Changed in: libvirt (Ubuntu Lucid)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu Lucid)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Changed in: libvirt (Ubuntu Lucid)
Still present in up to date Lucid beta
$ ifconfig -a | grep vir
virbr0Link encap:Ethernet HWaddr 5a:85:91:8b:65:30
$ sudo service libvirt-bin stop
libvirt-bin stop/waiting
$ ifconfig -a | grep vir
virbr0Link encap:Ethernet HWaddr 5a:85:91:8b:65:30
** Changed in: libvirt (Ubuntu)
Jamin-
Can you reproduce this in Lucid?
I think this should be cleaned up by libvirt's upstart script.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Incomplete
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received this bug notification b
I was still able to reproduce this problem on Karmic.
Regards
chuck
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
libvirt does not remove interfaces on stop
https://bugs.launchpad.net/bugs/345485
You received th
19 matches
Mail list logo
