On Thursday 09 April 2009, Joseph Apuzzo wrote:
> Trying to get virt-manager to manage Ubuntu's new JeOS server
> images, which now do install and run quite nicely under KVM ( aka
> install the server image iso but hit F4 at the main screen and pick
> virtual image, to get JeOS ). So I have two servers installed but
> how does one get networking, working?
>
> I know you need to do a "sudo adduser $USER kvm" to get KVM working
> for a user, but how to get the networking, working? Every time I
> try and activate a network or add a network bridge I get the error:
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/host.py", line 262, in
> start_network
> net.start()
> File "/usr/share/virt-manager/virtManager/network.py", line 71,
> in start self.net.create()
> File "/usr/lib/python2.6/dist-packages/libvirt.py", line 612, in
> create if ret == -1: raise libvirtError ('virNetworkCreate()
> failed', net=self) libvirtError: cannot create bridge 'virbr1':
> Operation not permitted
>
> Which seems like a permission issue, but what permission does my
> user need? I've been googleing it but since virt-manager is a
> Fedora product there are no Ubuntu hits.
>
> Any ideas are appricated
Unfortunately I'm not at all familiar with KVM so I can't help there.
However you said ANY ideas are appreciated, so I'll discuss one
alternative that could be used for this.
I've been using VirtualBox. Under VirtualBox version 1.x.x networking
was kind of a pain in the butt because it required setting up a
tun/tap, a bridge, and then a virtual interface. If for some reason
you must use VirtualBox version 1 I can explain how to set that up.
However now with Virtualbox version 2.x.x all of that pain is gone and
networking works mostly as you'd expect. An exception is that Linux
2.6.29 has some internal changes such that the kernel driver for
vboxdrv needs to have "VBOX_USE_INSERT_PAGE = 1" uncommented in the
makefile -- but is is only if you compile your own kernel...
If you decide to try VirtualBox for this, install 'virtualbox-ose',
'virtualbox-ose-modules-<kernel_version_for_your_kernel>', and load
the modules 'vboxdrv' and 'vboxnetflt'. (You'll want to add both of
those to /etc/modules later.) Then run the "Virtualbox OSE" GUI.
It's fairly straightforward from there.
Knowing you I think you'd like it, because it's all GUI-based. ;-)
-- Chris
--
Chris Knadle
[email protected]
_______________________________________________
Mid-Hudson Valley Linux Users Group http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
Upcoming Meetings (6pm - 8pm) MHVLS Auditorium
Mar 7 - Web Hack-a-thon - SUNY Newpaltz
Apr 1 - EC2 and Cloud Computer
May 6 - TBD
