[CentOS] Virtual Machine Manager error
incoming-centos at rjl.com
Thu Jan 19 18:25:59 UTC 2012
On 01/18/2012 03:15 PM, Ljubomir Ljubojevic wrote:
> On 01/18/2012 11:27 AM, Darrin Wilkinson wrote:
>> I am getting the exact same error on a CentOS 6.2 X86_64 machine that I have
>> just setup.
>> Removed and re-installed ALL the *virt* and *qemu* packages ( re-installed from
>> the distro CD ).
>> The machine is a DELL Optiplex 755 with an Intel x86_64 processor.
>> I found there was a similar bug on Fedora a while ago and it was fixed here:
>> Not sure if the two are related but it seems likely given the descriptions...
> My CentOS 6.2 x86_64 KVM system works as expected.
> By I have not updated libvirt, libvirt-client and libvirt-python! :
> [root at kancelarija ~]# yum list libvirt libvirt-client libvirt-python
> Loaded plugins: downloadonly, fastestmirror, priorities, refresh-packagekit
> Loading mirror speeds from cached hostfile
> 1312 packages excluded due to repository priority protections
> Installed Packages
> libvirt.x86_64 0.9.4-23.el6_2.1 @plc-updates
> libvirt-client.x86_64 0.9.4-23.el6_2.1 @plc-updates
> libvirt-python.x86_64 0.9.4-23.el6_2.1 @plc-updates
> Available Packages
> libvirt.x86_64 0.9.4-23.el6_2.4 plc-updates
> libvirt-client.i686 0.9.4-23.el6_2.4 plc-updates
> libvirt-client.x86_64 0.9.4-23.el6_2.4 plc-updates
> libvirt-python.x86_64 0.9.4-23.el6_2.4 plc-updates
> Try downgrading those 3 packages.
The error that you are reporting is simply telling you that the libvirtd
daemon is not running. You can confirm this with
ps auxw | grep libvirtd
root 3329 0.0 0.0 600440 8420 ? Sl 10:22 0:00
If it is not running then attempt to start it with:
service libvirtd start
To have it start at system startup run
chkconfig libvirtd on
I have one system where, for some reason 'service libvirtd start' fails,
works. I have not had a chance to determine why yet. Also, if libvirtd
fails to start, check your log files /var/log/messages /var/log/boot.log
/var/log/audit/audit.log for errors. You could also try temporarily
disabling selinux enforcement with "setenforce 0". Use 'setenforce 1'
to renable it.
More information about the CentOS