Results 1 to 6 of 6

Thread: Virtual Machine Manager comlains about libvirtd

  1. #1

    Default Virtual Machine Manager comlains about libvirtd

    It complains that it can't connect to localhost because probably libvirtd is not running. Well it is running, so please share your wisdom with me.
    Here is error message:
    Code:
    Unable to open connection to hypervisor URI 'qemu:///system':
    unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: Permission denied
    Traceback (most recent call last):
      File "/usr/share/virt-manager/virtManager/connection.py", line 971, in _try_open
        None], flags)
      File "/usr/lib64/python2.6/site-packages/libvirt.py", line 111, in openAuth
        if ret is None:raise libvirtError('virConnectOpenAuth() failed')
    libvirtError: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: Permission denied
    I see there "permission" mentioned, do i have to rum Virtual Machine Manager as root? and how do i do that?

  2. #2

    Default Re: Virtual Machine Manager comlains about libvirtd

    ok... i fired up VMM from yast (as root obviously) and connection was established. But when i tried t make new machine i got following error:
    Code:
    A hypervisor is not running.  For kvm, load the kvm kernel modules.  If you want to run xen, reboot and load the xen kernel
    Code:
    Details 
    
    Traceback (most recent call last):
      File "/usr/share/virt-manager/virtManager/engine.py", line 661, in show_create
        create = vmmCreate(virtman=True,key=0)
      File "/usr/lib/python2.6/site-packages/vminstall/gtk/interface.py", line 117, in __init__
        raise HypervisorError(HypervisorError.E_NO_HYPERVISOR)
    HypervisorError: A hypervisor is not running.  For kvm, load the kvm kernel modules.  If you want to run xen, reboot and load the xen kernel.

  3. #3
    Join Date
    Nov 2008
    Location
    GTA, Ontario, Canada
    Posts
    15

    Default Re: Virtual Machine Manager comlains about libvirtd

    Well, I have different problems with VirtualBox but love it :-) Anyways, for some reason I have to run it as root, otherwise it doesn't start. Try to launch it from console: :/> su

    #VirtualBox

    And make sure you spelled it right -- it is case sensitive :-)
    cheers

  4. #4
    Join Date
    Jul 2010
    Location
    Adelaide, Australia
    Posts
    963

    Default Re: Virtual Machine Manager comlains about libvirtd

    Hi, if you are on Xen make sure you are running the xen kernel. You can see this by typing:

    # uname -a

    In the terminal and it should show xen in there. Also make sure that xend is started. If you are on kvm make sure that the kvm module is loaded:

    For intel:
    # modprobe kvm_intel

    For amd:
    # modprobe kvm_amd

    Thanks
    Desktop: Gigabyte GA-Z270-HD3 - Core i7 7700K - openSUSE Leap 42.2 KDE
    Laptop: HP EliteBook 8770W - Core i7 3940XM - openSUSE Leap 42.2 KDE

  5. #5
    Join Date
    Jul 2010
    Location
    Adelaide, Australia
    Posts
    963

    Default Re: Virtual Machine Manager comlains about libvirtd

    Quote Originally Posted by tomekania View Post
    Well, I have different problems with VirtualBox but love it :-) Anyways, for some reason I have to run it as root, otherwise it doesn't start. Try to launch it from console: :/> su

    #VirtualBox

    And make sure you spelled it right -- it is case sensitive :-)
    cheers
    Are you part of the vboxusers group? I had to join this group with:

    # usermod -G vboxusers your_username_here

    To be able to use VirtualBox as normal user
    Desktop: Gigabyte GA-Z270-HD3 - Core i7 7700K - openSUSE Leap 42.2 KDE
    Laptop: HP EliteBook 8770W - Core i7 3940XM - openSUSE Leap 42.2 KDE

  6. #6

    Lightbulb Re: Virtual Machine Manager comlains about libvirtd

    As the error message says, the problem is that libvirtd daemon is not started. To start it, Open YAST | System | System Services (runlevel) and mark libvirtd as enable services.

    This solved the problem on my pc.


    Taken from KVM Virtualization on openSUSE 11.3 | Spirit of Change

    Day after a day I feel opensuse is less user friendly and not suitable for novices. May be Novel removed these complexities in SLED and keep them in the OpenSuse so that users think too much to buy their SLED? Please discuss this with me since I began to think seriously to return to Kubuntu. I loved the stability and maturity of OpenSuse but I'm not ready to spend this much time and efforts solving problems like this. Ubuntu/Kubuntu guys supersede Novel in this area.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •