nafallo@pony:/etc/libvirt/qemu/networks$ ls -l *
-rw-r--r-- 1 root root 151 2009-01-20 22:52 bklabs.xml
lrwxrwxrwx 1 root root 10 2010-11-19 20:06 default.xml - bklabs.xml
-rw-r--r-- 1 root root 231 2011-03-15 22:23 default.xml.dpkg-new
-rw-r--r-- 1 root root 153 2008-09-15 22:39 lchost.xml
Sure enough.
--
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/746497
Title:
libvirt installs firewall rules on package upgrades
--
Ubuntu-server-bugs mailing list
Looking at http://libvirt.org/formatnetwork.html#examplesRoute, I
suspect this is viewed as a feature, since, if you did have some
existing firewall rules, this would punch the needed holes through that
to let the VMs work as expected. Agreed it wouldn't hurt to make that
more configurable.
Thanks again for opening this bug.
After talking to upstream (specifically thanks to laine on #virt :), the
firewall rules are a feature of the libvirt networks. To do what you
want, you should create the bridge yourself (i.e. using
/etc/network/interfaces), and then specify that the vm's attach
nafallo@pony:/etc/libvirt/qemu/networks$ ls -l *
-rw-r--r-- 1 root root 151 2009-01-20 22:52 bklabs.xml
lrwxrwxrwx 1 root root 10 2010-11-19 20:06 default.xml - bklabs.xml
-rw-r--r-- 1 root root 231 2011-03-15 22:23 default.xml.dpkg-new
-rw-r--r-- 1 root root 153 2008-09-15 22:39 lchost.xml
Sure enough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746497
Title:
libvirt installs firewall rules on package upgrades
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Looking at http://libvirt.org/formatnetwork.html#examplesRoute, I
suspect this is viewed as a feature, since, if you did have some
existing firewall rules, this would punch the needed holes through that
to let the VMs work as expected. Agreed it wouldn't hurt to make that
more configurable.
Thanks again for opening this bug.
After talking to upstream (specifically thanks to laine on #virt :), the
firewall rules are a feature of the libvirt networks. To do what you
want, you should create the bridge yourself (i.e. using
/etc/network/interfaces), and then specify that the vm's attach
Not to confuse the matter, but here is my network template for the
network (the other parts of how things work is in my quagga config):
nafallo@pony:~$ cat /etc/libvirt/qemu/networks/bklabs.xml
network
namebklabs/name
bridge name=bklabs/
forward mode=route/
ip address=91.194.67.9
I should have mentioned this is Ubuntu 10.04 LTS, fully up-to-date. I
had the same problem on 8.04 LTS and 8.10, and haven't tried any other
versions.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Not to confuse the matter, but here is my network template for the
network (the other parts of how things work is in my quagga config):
nafallo@pony:~$ cat /etc/libvirt/qemu/networks/bklabs.xml
network
namebklabs/name
bridge name=bklabs/
forward mode=route/
ip address=91.194.67.9
I should have mentioned this is Ubuntu 10.04 LTS, fully up-to-date. I
had the same problem on 8.04 LTS and 8.10, and haven't tried any other
versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for reporting this bug. I'm not quite sure why this is
happening. Do you have any other networks defined? Are the files in
/var/lib/libvirt/network/ the same as thos in
/etc/libvirt/qemu/network?
Does the same thing happen if you do /etc/init.d/libvirt-bin restart?
And if you reboot?
13 matches
Mail list logo
