virt-manager fails to create virtual network when ipv6 is disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt |
Confirmed
|
Undecided
|
Unassigned | ||
virt-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: virt-manager
virt-manager fails to create virtual networks (specifically the bridge device) when ipv6 is not present or disabled (in my case with ipv6.disable=1 on the kernel cmdline to work around some silly NFS bugs).
Steps to Reproduce:
1) Start virt-manager
2) Right click on 'localhost', select "details', go to the 'Virtual Networks' tab
3) Select the 'default' network, click on the 'Play/Run' button
Expected Behaviour:
virt manager should create the bridged interface as defined in the default configuration
Actual Behaviour:
An error dialog with the following message pops up and the interface is not created:
Error starting network: cannot disable /proc/sys/
Traceback (most recent call last):
File "/usr/share/
net.start()
File "/usr/share/
self.
File "/usr/lib/
if ret == -1: raise libvirtError ('virNetworkCre
libvirtError: cannot disable /proc/sys/
Because there is no virtual interface, virt-manager refuses to start any VMs.
matt@krypton:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
matt@krypton:~$ apt-cache policy virt-manager
virt-manager:
Installed: 0.8.4-7ubuntu1.1
Candidate: 0.8.4-7ubuntu1.1
Version table:
*** 0.8.4-7ubuntu1.1 0
500 http://
100 /var/lib/
0.8.4-7ubuntu1 0
500 http://
Thanks for reporting this bug and helping to make Ubuntu better.
This particular bug has been fixed in upstream libvirt, but is not yet fixed in natty. For lucid and maverick, the easiest fix is to use a debdiff like the below. For Natty, we should see about taking a more recent snapshot of libvirt.