Bug#657120: libvirt-bin: Should bring down virtual networks upon stop when no VM still there

January 24th, 2012 - 04:40 am ET by Olivier Berger | Report spam
Package: libvirt-bin
Version: 0.9.8-2
Severity: normal

Hi.

When one issues /etc/init.d/libvirt-bin stop, and no VMs are still running, it should bring down the virtual networks.

AFAICT, virbr0 is still there, though.

See https://bugs.launchpad.net/ubuntu/+...bug/345485 for some details on this issue on Ubuntu side.

AFAIU, the conclusion in that LP bug was that nothing should be down WRT networks when VMs are running.

But I think that one could expect that libvirt actually *knows* if VMs are still running, and may then be able to do things if no VM it started are still running.

Is there something that can be done to have libvirt not mess too much with the host when it is no longer needed ?

Thanks in advance.

Best regards,

Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (300, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libvirt-bin depends on:
ii adduser 3.113
ii gettext-base 0.18.1.1-5
ii libavahi-client3 0.6.30-6
ii libavahi-common3 0.6.30-6
ii libblkid1 2.20.1-1.2
ii libc6 2.13-24
ii libcap-ng0 0.6.6-1
ii libdevmapper1.02.1 2:1.02.67-2
ii libgcrypt11 1.5.0-3
ii libgnutls26 2.12.16-1
ii libnl1 1.1-7
ii libnuma1 2.0.8~rc2-1
ii libparted0debian1 2.3-8
ii libpcap0.8 1.2.1-1
ii libpciaccess0 0.12.902-1
ii libreadline6 6.2-8
ii libsasl2-2 2.1.25.dfsg1-3
ii libudev0 175-3
ii libvirt0 0.9.8-2
ii libxenstore3.0 4.1.2-2
ii libxml2 2.7.8.dfsg-5.1
ii libyajl1 1.0.12-2
ii logrotate 3.8.1-1

Versions of packages libvirt-bin recommends:
ii bridge-utils 1.5-2
ii dmidecode 2.11-4
ii dnsmasq-base 2.59-4
ii ebtables 2.0.9.2-2
ii gawk 1:3.1.8+dfsg-0.1
ii iproute 20120105-1
ii iptables 1.4.12.2-1
ii libxml2-utils 2.7.8.dfsg-5.1
ii netcat-openbsd 1.89-4
ii parted 2.3-8
ii qemu 1.0+dfsg-2
ii qemu-kvm 1.0+dfsg-3

Versions of packages libvirt-bin suggests:
pn policykit-1 0.104-1
pn radvd <none>

/etc/default/libvirt-bin changed [not included]
/etc/libvirt/qemu/networks/default.xml [Errno 13] Permission non accordée: u'/etc/libvirt/qemu/networks/default.xml'




To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 5 repliesReplies Make a reply

Replies

#1 Guido Günther
January 24th, 2012 - 05:10 am ET | Report spam
tags 657120 +wontfix
thanks

On Tue, Jan 24, 2012 at 10:30:49AM +0100, Olivier Berger wrote:
Package: libvirt-bin
Version: 0.9.8-2
Severity: normal

Hi.

When one issues /etc/init.d/libvirt-bin stop, and no VMs are still running, it should bring down the virtual networks.

AFAICT, virbr0 is still there, though.

See https://bugs.launchpad.net/ubuntu/+...bug/345485 for some details on this issue on Ubuntu side.

AFAIU, the conclusion in that LP bug was that nothing should be down WRT networks when VMs are running.

But I think that one could expect that libvirt actually *knows* if VMs are still running, and may then be able to do things if no VM it started are still running.

Is there something that can be done to have libvirt not mess too much with the host when it is no longer needed ?


Libvirt doesn't bring down vms when it stops nor storage pools nor
networks. Why should it? It should infact preserve it's state across
restarts.
Cheers,



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics