Libvirt 0.8.6-1

hal is missing as dependency for libvirt
:: Starting libvirtd [BUSY]
/usr/sbin/libvirtd: error while loading shared libraries: libhal.so.1: cannot open shared object file: No such file or directory
[FAIL]

thestinger wrote:https://bugs.archlinux.org/
already reported

Similar Messages

  • Virt-manager - Unable to connect to libvirt

    Unable to connect to libvirt:
    Failed to connect socket to '/var/run/libvirt/libvirt-sock': Verbindungsaufbau abgelehnt
    Verify that:
    - The 'libvirtd' daemon has been started
    kvm, kvm-intel and libvirtd are started.
    did i forget anything?
    Last edited by ffflrn (2012-05-14 17:12:31)

    Same happening here. Problem appeared here after
    [2012-05-14 14:24] upgraded libvirt (0.9.11-2 -> 0.9.12-1)
    Can you confirm?
    EDIT:
    https://bbs.archlinux.org/viewtopic.php … 4#p1101984
    Last edited by toad (2012-05-15 07:49:28)

  • [SOLVED] Unable to launch KVM/libvirt VMs

    I performed a system update yesterday, and I am now unable to start any guests via libvirt/KVM.  Here's what journalctl reports when I try to start a machine that is in a saved state:
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (vnet0): carrier is OFF
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (vnet0): new Tun device (driver: 'unknown' ifindex: 56)
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (vnet0): exported as /org/freedesktop/NetworkManager/Devices/55
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (virbr0): bridge port vnet0 was attached
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (vnet0): enslaved to virbr0
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <error> [1432759965.789279] [devices/nm-device.c:2086] nm_device_generate_connection(): (virbr0): Generated connection does not verify: bridge.forward-delay: value '1' is out of range <2-30>
    May 27 15:52:45 IPsoftLappy kernel: device vnet0 entered promiscuous mode
    May 27 15:52:45 IPsoftLappy kernel: virbr0: port 2(vnet0) entered listening state
    May 27 15:52:45 IPsoftLappy kernel: virbr0: port 2(vnet0) entered listening state
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (vnet0): link connected
    May 27 15:52:45 IPsoftLappy dbus[324]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'
    May 27 15:52:45 IPsoftLappy systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
    May 27 15:52:45 IPsoftLappy systemd[1]: Starting Virtual Machine and Container Registration Service...
    May 27 15:52:45 IPsoftLappy dbus[324]: [system] Successfully activated service 'org.freedesktop.machine1'
    May 27 15:52:45 IPsoftLappy systemd[1]: Started Virtual Machine and Container Registration Service.
    May 27 15:52:45 IPsoftLappy systemd-machined[21492]: New machine qemu-mwkigit.
    May 27 15:52:45 IPsoftLappy systemd[1]: Started Virtual Machine qemu-mwkigit.
    May 27 15:52:45 IPsoftLappy systemd[1]: Starting Virtual Machine qemu-mwkigit.
    May 27 15:52:45 IPsoftLappy kernel: virbr0: port 2(vnet0) entered disabled state
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (virbr0): bridge port vnet0 was detached
    May 27 15:52:45 IPsoftLappy NetworkManager[320]: <info> (vnet0): released from master virbr0
    May 27 15:52:45 IPsoftLappy kernel: device vnet0 left promiscuous mode
    May 27 15:52:45 IPsoftLappy kernel: virbr0: port 2(vnet0) entered disabled state
    May 27 15:52:45 IPsoftLappy systemd-machined[21492]: Machine qemu-mwkigit terminated.
    May 27 15:52:46 IPsoftLappy libvirtd[591]: failed to connect to monitor socket: No such process
    May 27 15:52:46 IPsoftLappy libvirtd[591]: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
    failed to initialize KVM: Permission denied
    May 27 15:52:46 IPsoftLappy libvirtd[591]: Unable to restore from managed state /var/lib/libvirt/qemu/save/mwkigit.save. Maybe the file is corrupted?
    And if I try to start a guest that is powered down:
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (vnet0): carrier is OFF
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (vnet0): new Tun device (driver: 'unknown' ifindex: 57)
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (vnet0): exported as /org/freedesktop/NetworkManager/Devices/56
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (virbr0): bridge port vnet0 was attached
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (vnet0): enslaved to virbr0
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <error> [1432760645.546056] [devices/nm-device.c:2086] nm_device_generate_connection(): (virbr0): Generated connection does not verify: bridge.forward-delay: value '1' is out of range <2-30>
    May 27 16:04:05 IPsoftLappy kernel: device vnet0 entered promiscuous mode
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (vnet0): link connected
    May 27 16:04:05 IPsoftLappy kernel: virbr0: port 2(vnet0) entered listening state
    May 27 16:04:05 IPsoftLappy kernel: virbr0: port 2(vnet0) entered listening state
    May 27 16:04:05 IPsoftLappy dbus[324]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'
    May 27 16:04:05 IPsoftLappy systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
    May 27 16:04:05 IPsoftLappy systemd[1]: Starting Virtual Machine and Container Registration Service...
    May 27 16:04:05 IPsoftLappy dbus[324]: [system] Successfully activated service 'org.freedesktop.machine1'
    May 27 16:04:05 IPsoftLappy systemd[1]: Started Virtual Machine and Container Registration Service.
    May 27 16:04:05 IPsoftLappy systemd-machined[22516]: New machine qemu-Windows7.
    May 27 16:04:05 IPsoftLappy systemd[1]: Started Virtual Machine qemu-Windows7.
    May 27 16:04:05 IPsoftLappy systemd[1]: Starting Virtual Machine qemu-Windows7.
    May 27 16:04:05 IPsoftLappy kernel: virbr0: port 2(vnet0) entered disabled state
    May 27 16:04:05 IPsoftLappy kernel: device vnet0 left promiscuous mode
    May 27 16:04:05 IPsoftLappy kernel: virbr0: port 2(vnet0) entered disabled state
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (virbr0): bridge port vnet0 was detached
    May 27 16:04:05 IPsoftLappy NetworkManager[320]: <info> (vnet0): released from master virbr0
    May 27 16:04:05 IPsoftLappy systemd-machined[22516]: Machine qemu-Windows7 terminated.
    May 27 16:04:05 IPsoftLappy libvirtd[591]: failed to connect to monitor socket: No such process
    May 27 16:04:05 IPsoftLappy libvirtd[591]: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
    failed to initialize KVM: Permission denied
    I am in the following groups:
    $ groups
    root wheel video users libvirt kvm
    $
    my polkit has the group libvirt in it:
    # cat /etc/polkit-1/rules.d/50-org.libvirt.unix.manage.rules
    polkit.addRule(function(action, subject) {
    if ((action.id == "org.libvirt.unix.manage" || action.id == "org.libvirt.unix.monitor") &&
    subject.isInGroup("libvirt")) {
    return polkit.Result.YES;
    and some package version info:
    $ pacman -Q | grep -iP "virt|qemu"
    libvirt 1.2.15-1
    libvirt-glib 0.2.0-1
    libvirt-python 1.2.15-1
    qemu 2.3.0-2
    virt-install 1.2.0-2
    virt-manager 1.2.0-2
    $
    I'm sure I'm missing something, but I just can't place it.
    Last edited by slackcub (2015-06-01 17:47:10)

    So, just cause I was curious, I tried starting a vm as root, and got the same error:
    [rules.d]# virsh -c qemu:///system start mwkigit
    error: Failed to start domain mwkigit
    error: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
    failed to initialize KVM: Permission denied
    [rules.d]#
    So this is obviously an issue with how the interaction with the KVM module works. How exactly does that happen that no one can access the module?
    Last edited by slackcub (2015-06-01 14:13:13)

  • Libvirt-lxc No valid cgroup for machine // systemd-nspawn

    I am getting mad at trying to set up correctly a arch linux container on my guest with libvirt (LXC left me with a broken set up too).
    Here are some basic info:
    - custom kernel with user space set
    - host up-to-date
    - guest mounted on my root fs /dahlia  <---- Is it Ok or shall I mount to /machine/dahlia?
    - virsh uri is set by default to virsh -c lxc
    - systemd cgconfig.service is disabled
    - controllers are automatically mounted in /sys/fs/cgroup
    # virsh dumpxml dahlia
    <name>dahlia</name>
    <uuid>a34b58db-894f-4f4a-81f0-b13d2d5d7732</uuid>
    <memory unit='KiB'>409600</memory>
    <currentMemory unit='KiB'>409600</currentMemory>
    <vcpu placement='static'>1</vcpu>
    <resource>
    <partition>/dahlia</partition>
    </resource>
    <os>
    <type arch='x86_64'>exe</type>
    <init>/bin/init</init>
    </os>
    <idmap>
    <uid start='0' target='1000' count='10'/>
    <gid start='0' target='1000' count='10'/>
    </idmap>
    <clock offset='utc'/>
    <on_poweroff>destroy</on_poweroff>
    <on_reboot>restart</on_reboot>
    <on_crash>destroy</on_crash>
    <devices>
    <emulator>/usr/lib/libvirt/libvirt_lxc</emulator>
    <filesystem type='mount' accessmode='passthrough'>
    <source dir='/'/>
    <target dir='/'/>
    </filesystem>
    <interface type='network'>
    <mac address='52:54:00:89:8f:1a'/>
    <source network='default'/>
    </interface>
    <console type='pty'>
    <target type='lxc' port='0'/>
    </console>
    </devices>
    <seclabel type='none'/>
    </domain>
    gabx@hortensia ➤➤ ~ # virsh list --all
    Id Name State
    - dahlia shut off
    $ ls /etc/systemd/system
    machine-dahlia.slice
    $ ls -al /sys/fs/cgroup/systemd
    drwxr-xr-x 2 root root 0 Feb 17 10:28 machine.slice/
    drwxr-xr-x 44 root root 0 Feb 17 10:42 system.slice/
    drwxr-xr-x 3 root root 0 Feb 17 10:27 user.slice/
    gabx@hortensia ➤➤ ~ % ls -al /sys/fs/cgroup/systemd/machine.slice
    total 0
    drwxr-xr-x 2 root root 0 Feb 17 10:28 ./
    drwxr-xr-x 6 root root 0 Feb 17 10:27 ../
    -rw-r--r-- 1 root root 0 Feb 17 10:28 cgroup.clone_children
    --w--w--w- 1 root root 0 Feb 17 10:28 cgroup.event_control
    -rw-r--r-- 1 root root 0 Feb 17 10:28 cgroup.procs
    -rw-r--r-- 1 root root 0 Feb 17 10:28 notify_on_release
    -rw-r--r-- 1 root root 0 Feb 17 10:28 tasks
    There is no subdir machine-dahlia.slice in /sys/fs/cgroup/systemd/machine.slice. Is it OK ? I would say there need one.
    I can start the container this way :
    gabx@hortensia ➤➤ ~ # systemd-nspawn -bD /dahlia
    BUT not this way :
    gabx@hortensia ➤➤ ~ # virsh start dahlia
    error: Failed to start domain dahlia
    error: internal error: No valid cgroup for machine dahlia
    I can't figure out where does this cgroup issue comes from.
    Thank you for help
    Last edited by gabx (2014-02-17 11:09:13)

    If it can help, here is part of the output of systemd-cgls:
    ├─user.slice
    │ └─user-1000.slice
    │ ├─session-3.scope
    │ │ ├─1121 login -- gabx
    │ │ ├─1123 -zsh
    │ │ ├─1160 sudo systemd-nspawn -bD /dahlia
    │ │ └─1161 systemd-nspawn -bD /dahlia
    │ └─session-1.scope
    │ ├─ 473 login -- gabx
    ├─session-3.scope
    │ │ ├─1121 login -- gabx
    │ │ ├─1123 -zsh
    │ │ ├─1160 sudo systemd-nspawn -bD /dahlia
    │ │ └─1161 systemd-nspawn -bD /dahlia
    │ └─session-1.scope
    │ ├─ 473 login -- gabx
    └─system.slice
    ├─1 /sbin/init splash
    ├─machine-dahlia.scope
    │ ├─user.slice
    │ │ └─user-0.slice
    │ │ ├─session-3.scope
    │ │ │ ├─1198 login -- root
    │ │ │ └─1204 -bash
    In this case, I started systemd-nspawn on tty3 when sudoing, outside any X session
    What surprises me is I was waiting for the container be registered in /sys/fs/cgroup/systemd/machine.slice (no dahlia.slice inside) and not in the user-1000.slice/session-3.scope dir:
    gabx@hortensia ➤➤ ~ % ls -al /sys/fs/cgroup/systemd/user.slice/user-1000.slice
    total 0
    drwxr-xr-x 4 root root 0 Feb 17 11:50 ./
    drwxr-xr-x 3 root root 0 Feb 17 11:49 ../
    drwxr-xr-x 2 root root 0 Feb 17 11:50 session-1.scope/
    drwxr-xr-x 2 root root 0 Feb 17 11:51 session-3.scope/
    -rw-r--r-- 1 root root 0 Feb 17 11:50 cgroup.clone_children
    --w--w--w- 1 root root 0 Feb 17 11:50 cgroup.event_control
    -rw-r--r-- 1 root root 0 Feb 17 11:50 cgroup.procs
    -rw-r--r-- 1 root root 0 Feb 17 11:50 notify_on_release
    -rw-r--r-- 1 root root 0 Feb 17 11:50 task

  • Libvirt networking [solved]

    I installed libvirt from AUR and I don't seem to be having any luck getting networking going with it.  I thought I would see if any one has any ideas.
    Whenever I start libvirtd, I get the following error:
    # libvirtd
    libvir: QEMU error : internal error failed to add iptables rule to allow DHCP requests from 'virbr0' : Invalid argument
    Failed to autostart network 'default': internal error failed to add iptables rule to allow DHCP requests from 'virbr0' : Invalid argument
    $ brctl show
    bridge name bridge id STP enabled interfaces
    I tried adding the virbr0 bridge and I get the following:
    # brctl addbr virbr0
    # brctl stp virbr0 on
    # brctl show
    bridge name bridge id STP enabled interfaces
    virbr0 8000.000000000000 yes
    # libvirtd
    libvir: QEMU error : internal error cannot create bridge 'virbr0' : File exists
    Failed to autostart network 'default': internal error cannot create bridge 'virbr0' : File exists
    So I'm guessing that virbr0 should be automatically set-up by libvirt.  Does anyone have any idea what I need to do to get libvirt setting-up networks for me?
    Last edited by emphire (2008-06-30 04:59:04)

    I figured it out.  I was missing the iptables package and the network is coming up now.

  • OVS 3.2.1: Installing libvirt and/or virt tools (e.g., virt-install)

    Has anybody here successfully installed libvirt and/or virt-install on Oracle VM Server 3.2.1?
    I've attempted to install libvirt & virtinstall from source...
    [root@xen3 virtinst-0.600.3]# cd /usr/local/src/virtinst-0.600.3
    [root@xen3 virtinst-0.600.3]# python setup.py install
    running install
    running build
    Version              : 0.600.3
    RHEL6 defaults       : False
    Formatting ru.po to build/mo/ru/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting gu.po to build/mo/gu/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting nl.po to build/mo/nl/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting pt_BR.po to build/mo/pt_BR/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting zh_CN.po to build/mo/zh_CN/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting sr.po to build/mo/sr/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting zh_TW.po to build/mo/zh_TW/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting [email protected] to build/mo/sr@latin/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting it.po to build/mo/it/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting fr.po to build/mo/fr/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting es.po to build/mo/es/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting uk.po to build/mo/uk/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting da.po to build/mo/da/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting ja.po to build/mo/ja/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    Formatting pl.po to build/mo/pl/LC_MESSAGES/virtinst.mo
    sh: msgfmt: command not found
    running build_py
    running build_scripts
    running install_lib
    running install_scripts
    changing mode of /usr/bin/virt-clone to 755
    changing mode of /usr/bin/virt-image to 755
    changing mode of /usr/bin/virt-convert to 755
    changing mode of /usr/bin/virt-install to 755
    running install_data
    error: can't copy 'build/mo/ru/LC_MESSAGES/virtinst.mo': doesn't exist or not a regular file
    [root@xen3 libvirt-1.0.2]# cd /usr/local/src/libvirt-1.0.2
    [root@xen3 libvirt-1.0.2]# ./configure
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... no
    checking how to create a ustar tar archive... gnutar
    checking whether to enable maintainer-specific portions of Makefiles... yes
    checking whether make supports nested variables... no
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking for gcc... no
    checking for cc... no
    checking for cl.exe... no
    configure: error: in `/usr/local/src/libvirt-1.0.2':
    configure: error: no acceptable C compiler found in $PATH
    See `config.log' for more details...but been confounded by the lack of gcc in the public-yum repo .
    [root@xen3 libvirt-1.0.2]# yum search gcc
    ======================= Matched: gcc =======================
    libgcc.x86_64 : GCC version 4.1 shared support library
    libstdc++.x86_64 : GNU Standard C++ Library
    libtermcap.x86_64 : A basic system library for accessing the termcap database.
    python-zope-interface.x86_64 : Zope interfaces packageIdeas? Suggestions?

    Suggestions…? Well yes… simply forget about that! Oracle treats OVM server as an appliance - or least they'd like to and sell us the hardware as well. Since they can't do that, they decided to "craft" the system to their likings and omit lots of things one might consider either necessary or nice to have.
    Oralce did intentionally leave out all the gcc stuff and a lot of the other tools as well, to make sure mortals don't mess around with the system. If you want to use OVM then you will have to live with that or risk breaking any part of OVM and rendering your installation unsupported by Oracle.
    Besides, I don't actually see, why one would need to install libvirt/virt-install on a OVM server?

  • Libvirt cgroup issues [SOLVED]

    I installed a fresh Arch a few days ago and I'm getting strange errors when trying to start some VMs.  Here's the error for one of the VMs:
    Error starting domain: Unable to create cgroup for debian6-test: No such file or directory
    Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in tmpcb
    callback(*args, **kwargs)
    File "/usr/share/virt-manager/virtManager/domain.py", line 1090, in startup
    self._backend.create()
    File "/usr/lib/python2.7/site-packages/libvirt.py", line 678, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
    libvirtError: Unable to create cgroup for debian6-test: No such file or directory
    cgroups are working:
    # fgrep cgroup /proc/mounts
    tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
    cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
    cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
    cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
    cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
    cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    And the libvirt node exists:
    # ls -l /sys/fs/cgroup/libvirt/
    total 0
    drwxr-xr-x 2 root root 40 Oct 3 12:14 qemu
    These VMs were previously defined and working on another Arch install on another hard drive, as recently as 2 weeks ago.  Maybe libvirt is broken...?
    Edit: I fixed this by reinstalling libvirt.  I'm not sure what was wrong with my libvirt before, because it was persisting across reboots.  Anyways, it's fixed now.
    Edit 2: Actually, it seems that this still comes back from time to time, even when one VM is already running.  To fix it I have to restart libvirtd (ie, systemctl restart libvirtd).
    Last edited by stickyboy (2012-10-16 06:51:40)

    I installed a fresh Arch a few days ago and I'm getting strange errors when trying to start some VMs.  Here's the error for one of the VMs:
    Error starting domain: Unable to create cgroup for debian6-test: No such file or directory
    Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in tmpcb
    callback(*args, **kwargs)
    File "/usr/share/virt-manager/virtManager/domain.py", line 1090, in startup
    self._backend.create()
    File "/usr/lib/python2.7/site-packages/libvirt.py", line 678, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
    libvirtError: Unable to create cgroup for debian6-test: No such file or directory
    cgroups are working:
    # fgrep cgroup /proc/mounts
    tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
    cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
    cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
    cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
    cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
    cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.lua 0 0
    And the libvirt node exists:
    # ls -l /sys/fs/cgroup/libvirt/
    total 0
    drwxr-xr-x 2 root root 40 Oct 3 12:14 qemu
    These VMs were previously defined and working on another Arch install on another hard drive, as recently as 2 weeks ago.  Maybe libvirt is broken...?
    Edit: I fixed this by reinstalling libvirt.  I'm not sure what was wrong with my libvirt before, because it was persisting across reboots.  Anyways, it's fixed now.
    Edit 2: Actually, it seems that this still comes back from time to time, even when one VM is already running.  To fix it I have to restart libvirtd (ie, systemctl restart libvirtd).
    Last edited by stickyboy (2012-10-16 06:51:40)

  • Libvirt permissions differ on upgrade

    (12/16) upgrading libvirt [--------------------------------] 100%
    warning: /etc/libvirt/qemu/networks/default.xml installed as /etc/libvirt/qemu/networks/default.xml.pacnew
    warning: directory permissions differ on /var/lib/libvirt/qemu/
    filesystem: 755 package: 770
    >>> You may need to run 'rm -rf ~/.libvirt'
    Does pacman just never update permissions automatically?  Anyway I just manually changed it with the following command.  Hope that was the right call.
    $ sudo chmod 770 /var/lib/libvirt/qemu/

    Directory permissions are never changed automatically. A directory could be part of two different packages, with each package specifying different permissions. To make the job easier pacman only warns about changed directory permissions. File permissions are another matter, they will be modified.
    You did the right thing with changing the permissions if the 755 wasn't set by you manually.

  • [SOLVED] Unable to net-start "default" network in libvirt (KVM)

    Hi. I've used this tutorial  and have net-define'ed a network from this xml, but when i try to net-start it, i get the following error:
    virsh # net-start default
    error: Failed to start network default
    error: internal error Network is already in use by interface virbr0
    At first i though that some other network has already been defined and auto-started, so i've checked net-list
    virsh # net-list --all
    Name State Autostart
    default inactive no
    Here is the output from $ ip a show dev virbr0
    4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
    link/ether ce:1e:b4:54:83:83 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
    I became curious, and found out that dnsmasq was running
    $ ps -ef | ack dnsm | ack -v ack
    nobody 12333 1 0 13:04 ? 00:00:00 dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override
    With that i thought that everything works just fine, and i should try to configure a virtual machine to use the default network.
    EDIT:
    Looks like $ virsh edit fedora and /etc/libvirt/qemu/fedora.xml contain different things. I am pretty confused.
    /etc/libvirt/qemu/fedora.xml
    virsh edit fedora
    virsh # list --all
    Id Name State
    - fedora shut off
    virsh # start fedora
    error: Failed to start domain fedora
    error: internal error Network 'default' is not active.
    How can it be started and not started at the same time?
    Last edited by blin (2011-12-18 14:51:49)

    Well, it turns out, i shoulde have run virsh as root, that way everuthing works fine.

  • [solved] Libvirt "No accelerator found!" but aqemu and qemu-kvm works.

    After the latest update to libvirt I have been getting a weird error message when I try to run or install a new VM on multiple machines.
    Unable to complete install: 'internal error process exited while connecting to monitor: char device redirected to /dev/pts/1
    Could not access KVM kernel module: Permission denied
    failed to initialize KVM: Permission denied
    No accelerator found!
    Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 1943, in do_install
    guest.start_install(False, meter=meter)
    File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1249, in start_install
    noboot)
    File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1317, in _create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
    File "/usr/lib/python2.7/site-packages/libvirt.py", line 2722, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
    I have hardware virtulization enabled in the BIOS on my machines, as well as the the required kernel modules loaded:
    > lscpu
    Architecture: x86_64
    CPU op-mode(s): 32-bit, 64-bit
    Byte Order: Little Endian
    CPU(s): 2
    On-line CPU(s) list: 0,1
    Thread(s) per core: 1
    Core(s) per socket: 2
    Socket(s): 1
    NUMA node(s): 1
    Vendor ID: AuthenticAMD
    CPU family: 16
    Model: 6
    Stepping: 3
    CPU MHz: 800.000
    BogoMIPS: 4989.39
    Virtualization: AMD-V
    L1d cache: 64K
    L1i cache: 64K
    L2 cache: 1024K
    NUMA node0 CPU(s): 0,1
    > grep -E "(vmx|svm)" /proc/cpuinfo
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save
    > lsmod | ack 'kvm*'
    kvm_amd 52055 0
    kvm 384721 1 kvm_amd
    I am able to create and run VMs using qemu-kvm directly and with using aqemu-git without any issues.  I am not sure if the direct cause is with Libvirt or if I am using qemu-kvm-spice from AUR (has not caused an issue before).
    Last edited by vendion (2013-02-16 20:15:15)

    I had the same problem, however the fix did not work for me.
    Tried replacing kvm user and group with qemu (since it exists), same problem.
    Reverted and created a kvm user (which did not exist and qemu-kvm package did not create), then the problem changes to
    error: Unable to read from monitor: Connection reset by peer
    I do not know if it is relevant but when run as root I get:
    # qemu-kvm
    Could not initialize SDL(No available video device) - exiting
    However as the user of the current login a qemu-kvm starts with no problems.
    maybe it indicates a systemd/polkit qxl/SDL driver problem or cgroups problem?
    my libvirtd.conf I had set the permissions to polkit but commenting it out to get the defaults changes nothing.
    a stab in the dark would predict that since systemd/polkit only allows programmes to run on the login session/seat, it is preventing the kvm/qemu user to run a programme since that user has not logged in?
    so I changed the user and group in qemu.conf again but this time to root then the following error :
    connecting to monitor: chardev: opening backend "pty" failed
    changing it to the current session/seat login username and group:
    success
    On the other hand maybe it is as result of a messed up passwd or groups file causing polkit not to work correctly?
    UPDATE: the problem also goes away when I remove a SDL display and then use the trusty old(archaic) VNC. so as I said, my guess is the qxl framebuffer and/or SDL is not being granted permission to use the display by polkit or PAM or systemd or whatever is supposed to be granting it permission.  it can probably be fixed with a rule....
    Last edited by hawkinstw (2013-03-13 23:16:18)

  • [solved]libvirt /dev/net/tun error

    I had set up virtualization several weeks ago using libvirt and virt-manager on my system, but when I tried to use it the other day the clients won't launch.  I get this error:
    Feb 4 22:39:51 it-alanmlap libvirtd[29964]: Unable to open /dev/net/tun, is tun module loaded?: No such device
    /dev/net/tun exists, and has permissions 666.
    I tried the procedure outlined here:
    http://wiki.libvirt.org/page/Guest_won% … terface%29
    But it did not have any effect on the problem.
    My VM's are just using NAT networking, but the error persists no matter what I set the networking to.
    I'm stumped, any suggestions?
    Last edited by lykwydchykyn (2014-02-07 17:38:32)

    lykwydchykyn wrote:
    brain0 wrote:When you update the kernel, you need to reboot. You updated the kernel without rebooting.
    Well, maybe; that's one of the first things I checked, but it looked like I was running the latest kernel.
    How exactly did you check? Were
    pacman -Q linux
    and
    uname -r
    the same?

  • [SOLVED]Libvirt: Need to ssh x10 Times Before Connecting to VM

    I have a libvirt + qemu/kvm setup that I can remote into with ssh. The initial ssh connection to the server is fine. However, when I want to view the VM, it prompts me for my ssh passphrase literally 10 times. The funny thing is, it actually works after that...
    Any thoughts on the cause? I'm not sure what config files would be relevant here.
    All the ssh connections!
    Last edited by Hspasta (2014-08-13 20:59:38)

    Awesome wm and virt-manager here.
    Adding something like this to .xinit works for virt-manager but it'll ask for ssh passphrase right after startx command.
    ~/.xinitrc
    keychain ~/.ssh/id_ecdsa
    [ -f ~/.keychain/$HOSTNAME-sh ] && . ~/.keychain/$HOSTNAME-sh 2>/dev/null
    [ -f ~/.keychain/$HOSTNAME-sh-gpg ] && . ~/.keychain/$HOSTNAME-sh-gpg 2>/dev/null
    exec awesome

  • Libvirt: Unable to define LVM storage pool

    Hello,
    I'm trying to define an LVM storage pool for my virtual machines using KVM/libvirt. The configuration looks like this:
    <pool type="logical">
    <name>vol0</name>
    <source>
    <device path="/dev/md0"/>
    </source>
    <target>
    <path>/dev/vol0</path>
    </target>
    </pool>
    The problem is, that this LVM group is already active (other vms running using volumes inside this group) and 'virsh pool-start vol0' wants me to disable it. Is there any way to start the pool without "deactivate" the volume group?
    virsh pool-start vol0
    error: internal error '/sbin/vgchange -an vol0' exited with non-zero status 5 and signal 0: Can't deactivate volume group "vol0" with 14 open logical volume(s)
    Further, I'm a bit curious that libvirt might recreate the volume group and therefore deletes all the content during the building process.
    Would appreciate any advice
    Regards,
    Jonas

    maahes wrote:
    did so now, only now I'm getting a slightly different error: could not find udevd no such file or directory. I checked both grub.cfg's and my mkinitcpio.conf and there's no listing for udevd ....which I've never heard of, so I assumed it was a typo?
    For clarification: udev is in the mkinitcpio.
    I'm not sure whether I yet have a good intuition for how you have your machine set up, but I suspect you need to include a cryptdevice flag to the kernel in your grub config. The file isn't found because the kernel doesn't know your root directory needs decrypting first.
    My setup is an LVM over LUKS over LVM sandwich. To boot into my system, the grub.cfg contains the line:
    linux /vmlinuz-linux root=/dev/mapper/cryptvg-root cryptdevice=/dev/mapper/vg-crypt:root rootfstype=ext4 pcie_aspm=force acpi_osi=Linux acpi_backlight=vendor i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 ro
    Now, most of those flags don't have anything to do with your problem, but note the cryptdevice. It tells the kernel it's dealing with an encrypted filesystem sitting in a logical volume called crypt on a volume group called vg. The bit after the colon tells the kernel to associate this encrypted filesystem with /dev/mapper/root.
    As for how to fix your system, I'm afraid I still feel a bit fuzzy about how your LVM and encrypted layers relate to each other, whether you have LVM over LUKS, or LUKS over LVM, or something else. Was there a particular how-to that you followed?

  • Vagrant + vagrant-libvirt plugin

    Hi,
    I'm having some issues with installing the vagrant-libvirt plugin.
    I've installed vagrant from AUR with yaourt and try to install the plugin with
    $ vagrant plugin install vagrant-libvirt
    The following error shows up:
    Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
    /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/installer.rb:562:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)
    /opt/vagrant/embedded/bin/ruby extconf.rb
    checking for virNetworkPtr in libvirt/libvirt.h... *** extconf.rb failed ***
    Could not create Makefile due to some reason, probably lack of
    necessary libraries and/or headers. Check the mkmf.log file for more
    details. You may need configuration options.
    Provided configuration options:
    --with-opt-dir
    --with-opt-include
    --without-opt-include=${opt-dir}/include
    --with-opt-lib
    --without-opt-lib=${opt-dir}/lib
    --with-make-prog
    --without-make-prog
    --srcdir=.
    --curdir
    --ruby=/opt/vagrant/embedded/bin/ruby
    --with-libvirt-include
    --without-libvirt-include
    --with-libvirt-lib
    --without-libvirt-lib
    --with-libvirt-config
    --without-libvirt-config
    --with-pkg-config
    --without-pkg-config
    /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:381:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
    You have to install development tools first.
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:491:in `block in try_compile'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:443:in `with_werror'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:491:in `try_compile'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:1022:in `try_type'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:1050:in `block in have_type'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:790:in `block in checking_for'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:284:in `block (2 levels) in postpone'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:254:in `open'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:284:in `block in postpone'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:254:in `open'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:280:in `postpone'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:789:in `checking_for'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/mkmf.rb:1049:in `have_type'
    from extconf.rb:10:in `block in have_libvirt_types'
    from extconf.rb:10:in `each'
    from extconf.rb:10:in `have_libvirt_types'
    from extconf.rb:211:in `<main>'
    Gem files will remain installed in /home/twouters/.vagrant.d/gems/gems/ruby-libvirt-0.4.0 for inspection.
    Results logged to /home/twouters/.vagrant.d/gems/gems/ruby-libvirt-0.4.0/ext/libvirt/gem_make.out
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/installer.rb:540:in `block in build_extensions'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/installer.rb:515:in `each'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/installer.rb:515:in `build_extensions'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/installer.rb:180:in `install'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/dependency_installer.rb:297:in `block in install'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `each'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `each_with_index'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `install'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/action/install_gem.rb:38:in `block in call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/gem_helper.rb:42:in `block in with_environment'
    from /opt/vagrant/embedded/lib/ruby/1.9.1/rubygems/user_interaction.rb:40:in `use_ui'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/gem_helper.rb:41:in `with_environment'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/action/install_gem.rb:28:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/action/bundler_check.rb:20:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/command/base.rb:17:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/command/install.rb:44:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/command/root.rb:47:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/cli.rb:46:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:467:in `cli'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/bin/vagrant:84:in `<top (required)>'
    from /opt/vagrant/bin/../embedded/gems/bin/vagrant:23:in `load'
    from /opt/vagrant/bin/../embedded/gems/bin/vagrant:23:in `<main>'
    I've had a look at the log file ~/.vagrant.d/gems/gems/ruby-libvirt-0.4.0/ext/libvirt/mkmf.log which contained a great pointer to the issue:
    package configuration for libvirt
    cflags:
    ldflags:
    libs: -lvirt -ldl
    "gcc -o conftest -I/opt/vagrant/embedded/include/ruby-1.9.1/x86_64-linux -I/opt/vagrant/embedded/include/ruby-1.9.1/ruby/backward -I/opt/vagrant/embedded/include/ruby-1.9.1 -I. -I/tmp/vagrant-temp/embedded/include -I/tmp/vagrant-temp/embedded/include -L/tmp/vagrant-temp/embedded/lib -fPIC conftest.c -L. -L/opt/vagrant/embedded/lib -Wl,-R/opt/vagrant/embedded/lib -L/tmp/vagrant-temp/embedded/lib -Wl,-R/tmp/vagrant-temp/embedded/lib -L. -I/tmp/vagrant-temp/embedded/include -L/tmp/vagrant-temp/embedded/lib -rdynamic -Wl,-export-dynamic -lvirt -ldl '-Wl,-rpath,/../lib' -Wl,-R -Wl,/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib -lruby -lpthread -lrt -ldl -lcrypt -lm -lc"
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_global_init@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_multi_cleanup@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_easy_init@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_easy_setopt@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_multi_remove_handle@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_slist_free_all@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_share_init@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_multi_init@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_easy_cleanup@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_easy_perform@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_share_cleanup@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_easy_strerror@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_easy_getinfo@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_slist_append@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_share_setopt@CURL_OPENSSL_4'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libvirt.so: undefined reference to `curl_multi_add_handle@CURL_OPENSSL_4'
    collect2: error: ld returned 1 exit status
    checked program was:
    /* begin */
    1: #include "ruby.h"
    2:
    3: int main() {return 0;}
    /* end */
    Libvirt has been installed on my system and is built against the system curl libraries, but vagrant is trying to use the embedded curl libraries in /opt/vagrant/embedded/lib/
    I have "confirmed" this behaviour by removing the curl libs from /opt/vagrant/embedded/lib/ and /opt/vagrant/embedded/lib/pkgconfig/.
    After removing the libs and pkgconfig file the installation of vagrant-libvirt succeeds.
    $ vagrant plugin install vagrant-libvirt
    Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
    Installed the plugin 'vagrant-libvirt (0.0.5)'!
    I know this isn't the right way to do this, so I wanted to ask if anyone knows how this should be fixed / worked around in a correct fashion.

    I had the same problem with vagrant-kvm.
    And deleting libcurl was a temporary workaround for me too.
    Here are the files which have to be removed (for copy'n'paste):
    $ mv /opt/vagrant/embedded/lib/libcurl.so{,.backup}
    $ mv /opt/vagrant/embedded/lib/libcurl.so.4{,.backup}
    $ mv /opt/vagrant/embedded/lib/libcurl.so.4.3.0{,.backup}
    $ mv /opt/vagrant/embedded/lib/pkgconfig/libcurl.pc{,backup}
    This problem could be solved by creating custom ruby-libvirt gem for vagrant, which links against the system libcurl (by using LIBRARY_PATH).

  • Libvirt via virt-manager virtual network start failed

    virt-manager v1.2.1
    libvirtd v1.2.16
    I tested firewall: iptables && ip6tables work well while.
    when I start a virtual network named 'default' (created by libvirt), it occur that:
    "Error starting network 'default': internal error: Failed to initialize a valid firewall backend".
    thanks for any reply
    Last edited by shenhd (2015-06-17 03:56:45)

    rob356 wrote:
    I had the same problem, but with vagrant and the libvirt provider. I fixed it temporarily by re-building libvirt with a patch that removes the code that throws that error. It looks like in an attempt to fix this bug they went overboard checking if a valid firewall backend was loaded. I commented out that section and everything seems to work fine. Obviously this is not a permanent fix, but I don't know enough about libvirt's codebase to fix it properly. Anyways here is the patch:
    --- libvirt-1.2.16.orig/src/util/virfirewall.c 2015-05-23 08:56:12.000000000 -0400
    +++ libvirt-1.2.16.new/src/util/virfirewall.c 2015-06-18 10:01:51.954157612 -0400
    @@ -932,14 +932,14 @@
    virMutexLock(&ruleLock);
    - if (currentBackend == VIR_FIREWALL_BACKEND_AUTOMATIC) {
    +// if (currentBackend == VIR_FIREWALL_BACKEND_AUTOMATIC) {
    /* a specific backend should have been set when the firewall
    * object was created. If not, it means none was found.
    - virReportError(VIR_ERR_INTERNAL_ERROR, "%s",
    - _("Failed to initialize a valid firewall backend"));
    - goto cleanup;
    +// virReportError(VIR_ERR_INTERNAL_ERROR, "%s",
    +// _("Failed to initialize a valid firewall backend"));
    +// goto cleanup;
    +// }
    if (!firewall || firewall->err == ENOMEM) {
    virReportOOMError();
    goto cleanup;
    thx! however, @Basic-Master 's solution is better.

Maybe you are looking for

  • Adobe Creative Cloud won't install

    Hey guys, I recently tried to install Adobe Creative Cloud but during the installation process it will suddenly quit on me. I tried it again, downloaded the installer again, rebooted my computer, but still can't get it to work. I do have other Adobe

  • File adapter mapping -  parser: no data allowed here

    Hello, something really nice: Scenario picks up a file to move it renamed with timestamp to another destination via FTP protocoll. File picked up: ok But in pipeline: Message in trace: <Trace level="1" type="T">RuntimeException during appliction Java

  • ORA-00928(Missing Select Keyword)

    Hi All. This procedure searches for a given keyword in all the tables of a schema. BEGIN EXECUTE IMMEDIATE 'DROP TABLE Results CASCADE CONSTRAINTS'; EXCEPTION WHEN OTHERS THEN NULL; END; CREATE GLOBAL TEMPORARY TABLE Results      ColumnName nvarchar2

  • Opmn does not start all processs when server ( windows 2003 is rebooted ).

    There is a startup script which starts every process when run from cmd. But when the server is rebooted it does not start Portal, WebCache. The startup Script : @ECHO OFF REM --------------------------------------------- REM 10gAS Rel 2 Midtier start

  • Correlating message id between async messages

    Hi guys... I have several JMS->Xi->AbapProxy AbapProxy->Xi->JMS scenarios, almost like request-reply, the difference is that all calls are async. My environment is a Xi3.0 and a SAP ISOIL 4.72 with SAP WebAS 6.2, with the abap proxies processed in SA