[one-users] Failed to acquire pid file '/var/run/libvirtd.pid': Resource temporarily unavailable - error when run /usr/sbin/libvirtd start

Hector Sanjuan lists at convivencial.org
Wed Oct 31 00:15:13 PDT 2012


Hi,

I don't have problems starting libvirtd while VMs machines are running.  
However, last time I tried to launch a kvm machine  when a VirtualBox one  
was running it failed. With a kvm machine running and trying to start a  
VirtualBox one I got nice kernel backtraces in my screen and hard freezes.  
So no, doesnt seem such a good idea to run VBox and kvm in the same box.

Hector

On Wed, 31 Oct 2012 05:48:38 +0100, Qiubo Su (David Su)  
<qiubosu at gmail.com> wrote:

> dear opennebula community,
>
> recently in one single PC (with ubuntu 12.04 64 bits server as OS), i  
> installed/configured a Cloud system with OpenNebula >3.6.0. The  
> Hypervisor is KVM. But when run /usr/sbin/libvirtd start, got below  
> error:
>
> 2012-10-31 04:30:47.283+0000: 20014: info : libvirt version: 0.9.8
> 2012-10-31 04:30:47.283+0000: 20014: error : virPidFileAcquirePath:345 :  
> Failed to acquire pid file '/var/run/>libvirtd.pid': Resource  
> temporarily unavailable
>
> it looks like the the libvirt daemon doesn't work. it is much  
> appreciated if anyone can help with this.
>
> moreover, a long time before setted up the Cloud system, in the same PC  
> i have Oracle VirtualBox installed and several VM >OS instances created  
> under VirtualBox. the operation of these VM instances are fine.
> the user:group of Oracle VirtualBox and its VM instances is different  
> from that for the Cloud system (includes openebula, >kvm, libvirt etc)
>
> is it ok to have two VM hosts installed in the same PC, as described  
> above? could this cause the above error when run /usr/>sbin/libvirtd  
> start.
>
> thanks for your hep.
>
> thanks,
> david su



-- 
Hector Sanjuan
@hecsanjuan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20121031/17de4402/attachment-0002.htm>


More information about the Users mailing list