OK I installed KVM but when I try to launch the Virtual Machines Manager nothing happens.
When I try to launch virt-manager from Konsole I get the following error
sudo virt-manager
Traceback (most recent call last):
File “/usr/share/virt-manager/virt-manager”, line 31, in <module>
from gi.repository import LibvirtGLib
ImportError: cannot import name LibvirtGLib
EDIT: I searched for and installed LibvritGLib manually and now it launches but displays another error:
Unable to connect to libvirt.
no connection driver available for qemu:///system
When I click details I get the following
Unable to connect to libvirt.
no connection driver available for qemu:///system
Libvirt URI is: qemu:///system
Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/connection.py”, line 864, in _do_open
self._backend.open(self._do_creds_password)
File “/usr/share/virt-manager/virtinst/connection.py”, line 161, in open
open_flags)
File “/usr/lib64/python2.7/site-packages/libvirt.py”, line 105, in openAuth
if ret is None:raise libvirtError(‘virConnectOpenAuth() failed’)
libvirtError: no connection driver available for qemu:///system
This installed qemu from the Virtualization repository.
Tried again. Same error. So I ran
Code:
sudo zypper dup
and replaced all virtualization libraries with the ones from the new
repo. This solved the problem successfully.
Now I have another problem. Xen promised me that at boot there will be
an option to boot into Xen but I see no such option. What did I do wrong
?
Hi
I don’t use Xen just kvm/virsh.
Have you looked in YaST at the virtualization tools?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.44-52.18-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
When I ran into what seems to likely be the same problem running vmware-tools-patches (the way to upgrade Tools) a couple months ago which involves re-compiling the kernel, my solution was to revert to gcc 4.6.
With this thread, I’m re-thinking whether gcc5.x is altogether “bad” with my recent experience updating Tools on LEAP. LEAP installs both gcc 4.6 and 5.x, and I <think> it’s successfully using gcc 5.x to update Tools(well, it worked up to M2. There is now a problem with Beta 1. Who knows, maybe with Beta 1 LEAP incorporated a TW method that breaks gcc 5.x). It might be interesting to see if Workstation 11 or 12 installs on LEAP without a problem, this might indicate it’s not gcc 5.x but how it’s implemented that is the problem.
In the meantime, I’ve submitted a feature request for TW to implement gcc as an “update-alternatives” to enable easy and quick switching.
Almost certainly because gcc 5.x hasn’t been pushed to 13.2 so you’re compiling with gcc 4.6.
As I noted, I’ve found the same in TW, if you compile with gcc 4.6 you should be successful.