[libvirt] How does libvirt 0.6.3 load kvm driver

[Jason Wong]

Daniel P. Berrange wrote:
> On Tue, Jun 30, 2009 at 06:38:35PM +0800, Jason Wong wrote:
>   
>> Daniel P. Berrange wrote:
>>     
>>> On Tue, Jun 30, 2009 at 01:59:36PM +0800, Jason Wong wrote:
>>>  
>>>       
>> Let me clarify, the KVM qemu driver, in my understanding is the part 
>> that responsible for the communication between  KVM hypervisor and 
>> libvirt (I think it is in the source code qemu_driver.c).
>> For KVM kernel module, I have manually use "modprobe kvm" command into 
>> kernel.
>>
>> Perhaps  I  should use the term "qemu driver" instead of "kvm driver".
>>     
>
> Ah, so you mean the libvirt QEMU driver isn't working. The best first
> step to diagnosing those problems is to stop the libvirtd daemon,
> and run it manually with debugging enabled
>
>   LIBVIRT_DEBUG=1 /usr/sbin/libvirtd
>
> with any luck there will be some failure reported explaining why the
> QEMU driver didn't activate.
>
> Daniel
>   
Dear Daniel,

I have enable the libvirt debug mode by setting LIBVIRT_DEBUG=1 and here 
is the debug message:

======================================= debug message 
=========================================
17:41:11.219: debug : virInitialize:290 : register drivers
17:41:11.219: debug : virRegisterDriver:667 : registering Test as driver 0
17:41:11.219: debug : virRegisterNetworkDriver:567 : registering Test as 
network driver 0
17:41:11.219: debug : virRegisterStorageDriver:598 : registering Test as 
storage driver 0
17:41:11.219: debug : virRegisterDeviceMonitor:629 : registering Test as 
device driver 0
17:41:11.219: debug : virRegisterDriver:667 : registering Xen as driver 1
17:41:11.219: debug : vboxRegister:68 : VBoxCGlueInit failed: 0.0.0, 
errorval=-1
17:41:11.219: debug : virRegisterDriver:667 : registering VBOX as driver 2
17:41:11.219: debug : virConnectOpen:1050 : name=qemu:///system
17:41:11.219: debug : do_open:920 : name "qemu:///system" to URI 
components:
 scheme qemu
 opaque (null)
 authority (null)
 server (null)
 user (null)
 port 0
 path /system

17:41:11.219: debug : do_open:930 : trying driver 0 (Test) ...
17:41:11.219: debug : do_open:936 : driver 0 Test returned DECLINED
17:41:11.219: debug : do_open:930 : trying driver 1 (Xen) ...
17:41:11.219: debug : do_open:936 : driver 1 Xen returned DECLINED
17:41:11.219: debug : do_open:930 : trying driver 2 (VBOX) ...
17:41:11.219: debug : do_open:936 : driver 2 VBOX returned DECLINED
libvir: error : could not connect to qemu:///system
17:41:11.219: debug : virUnrefConnect:210 : unref connection 0x60dd00 1
17:41:11.219: debug : virReleaseConnect:171 : release connection 0x60dd00
libvirt error: could not connect to qemu:///system (code=5)
error: failed to connect to hypervisor
================================end of debug message 
=========================================

 From the debug message, it seems that libvirt does not load qemu drivr 
but it load Xen and VBOX driver........
However, the fact is that I have load KVM kernel module into kernel by 
using "modprobe kvm" and "modprobe kvm_intel"
And the result of "lsmod|grep kvm" shows:

================================= result of lsmod 
==============================================
[root at node2 ~]# lsmod | grep kvm
kvm_intel              46664  0
kvm                   166224  1 kvm_intel
[root at node2 ~]#
================================= end of result of lsmod 
=========================================

-- 
Jason Wong

System engineer

Cluster Technology Limited

Email: hcwong at clustertech.com

Direct Line: (852) 2655-6129

Tel: (852) 2655-6100

Fax: (852) 2994-2101

Website: www.clustertech.com
------------------------------

**************************************************************************
The information and attachment contained in this e-mail originating from
Cluster Technology Limited is confidential and intended solely for
the specified addressees. If you have received this email in error,
please do not read, copy, distribute, disclose or use any information of
this email in any way and please immediately notify the sender and delete
this email. Thank you for your cooperation.
**************************************************************************