[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] Cannot enumerate physical devices with libvirt 0.7.6



On 02/16/2010 03:04 PM, Frédéric Grelot wrote:
Yep, here is what I get (see at the end) :

14:06:22.071: debug : do_open:1110 : name "qemu:///system" to URI components:
   scheme qemu
   opaque (null)
   authority (null)
   server (null)
   user (null)
   port 0
   path /system

14:06:22.071: debug : do_open:1120 : trying driver 0 (Test) ...
14:06:22.071: debug : do_open:1126 : driver 0 Test returned DECLINED
14:06:22.071: debug : do_open:1120 : trying driver 1 (OPENVZ) ...
14:06:22.071: debug : do_open:1126 : driver 1 OPENVZ returned DECLINED
14:06:22.071: debug : do_open:1120 : trying driver 2 (VBOX) ...
14:06:22.071: debug : do_open:1126 : driver 2 VBOX returned DECLINED
14:06:22.071: debug : do_open:1120 : trying driver 3 (remote) ...
14:06:22.071: debug : do_open:1126 : driver 3 remote returned DECLINED
14:06:22.071: debug : do_open:1120 : trying driver 4 (QEMU) ...
14:06:22.071: debug : do_open:1126 : driver 4 QEMU returned SUCCESS
14:06:22.071: debug : do_open:1146 : network driver 0 Test returned DECLINED
14:06:22.071: debug : do_open:1146 : network driver 1 VBOX returned DECLINED
14:06:22.071: debug : do_open:1146 : network driver 2 remote returned DECLINED
14:06:22.071: debug : do_open:1146 : network driver 3 Network returned SUCCESS
14:06:22.071: debug : do_open:1165 : interface driver 0 Test returned DECLINED
14:06:22.071: debug : do_open:1165 : interface driver 1 remote returned DECLINED
14:06:22.072: debug : do_open:1185 : storage driver 0 Test returned DECLINED
14:06:22.072: debug : do_open:1185 : storage driver 1 VBOX returned DECLINED
14:06:22.072: debug : do_open:1185 : storage driver 2 remote returned DECLINED
14:06:22.072: debug : do_open:1185 : storage driver 3 storage returned SUCCESS
14:06:22.072: debug : do_open:1205 : node driver 0 Test returned DECLINED
14:06:22.072: debug : do_open:1205 : node driver 1 remote returned DECLINED
14:06:22.072: debug : do_open:1232 : secret driver 0 Test returned DECLINED
14:06:22.072: debug : do_open:1232 : secret driver 1 remote returned DECLINED
14:06:22.072: debug : do_open:1232 : secret driver 2 secret returned SUCCESS
14:06:22.072: debug : virConnectClose:1381 : conn=0x1eaf0b0


I think the times when I get those lines matches with my "virsh nodedev-list" requests (or something like this : virt-manager tries to create a vm, add hardware...).

Does this help?

That's odd, you only have two entries in the node driver array, and I have four on my test system, which I just installed. How did you install the box, install F12, then what? Just to rule this out, did you rebuild the RPM?

Frederic.


----- "Dave Allan"<dallan redhat com>  a écrit :

On 02/16/2010 03:00 AM, Frédéric Grelot wrote:
Daniel was referring to the libvirt udev driver--the libvirt code
that

interacts with udev--not to udev itself, which is what you're
testing

with udevadm.

Ok, sorry... At least I ensured that udev itself is on...

   In any of your logs when you have libvirt debug logging
turned on, do you see the message:

Registering udev node device backend

Nope, I checked in /var/log/* and libvirt.log in debug mode (which,
after 1 1/2 day of "debug" activity enabled, is already 2Gb!)
There is no mention of udev. I think it means that the udev driver
is not loaded in libvirt? How could enable it then? (or produce some
message telling me why it is not) ?


These messages are the result of not being able to find the
device,
which is consistent with the other things you're seeing.  These
are
all symptoms of the node device code not running.

OK, I'll wait for your suggestions...

Do you see messages like:


14:35:01.849: debug : do_open:1205 : node driver 0 Test returned
DECLINED
14:35:01.849: debug : do_open:1205 : node driver 1 ESX returned
DECLINED
14:35:01.849: debug : do_open:1205 : node driver 2 remote returned
DECLINED
14:35:01.849: debug : do_open:1205 : node driver 3 udevDeviceMonitor
returned SUCCESS

in your debug log?


Frederic.



Have you any other Idea?
Frederic.


----- "Daniel P. Berrange"<berrange redhat com>    a écrit :

On Fri, Feb 12, 2010 at 08:05:21PM +0100, Fr?d?ric Grelot wrote:
Hi all,

I often update my F12 box with the rawvirt repository, which
just
installed libvirt 0.7.6. Since that, I cannot enumerate physical
devices (and thus get a beautiful error when I start one of my
vms
that should use a USB device).

I don't think I changed anything else on that box, and, of
course, I
already restarted the libvirt daemon.
I haven't restarted the server itself, because it is currently
used,
but I could do it if necessary...

I make good use of the qemu hypervisor, and I'm looking forward
to
solve this issue!

Frederic.

# libvirtd --version libvirtd (libvirt) 0.7.6

# virsh --version 0.7.6

# virsh nodedev-list error :Failed to count node devices error
:this function is not supported by the hypervisor:
virNodeNumOfDevices

It would appear that the udev driver failed to start - there are
probably messages in syslog about the problem


Regards, Daniel -- |: Red Hat, Engineering, London   -o-
http://people.redhat.com/berrange/ :| |: http://libvirt.org  -o-
http://virt-manager.org  -o- http://ovirt.org :| |:
http://autobuild.org       -o- http://search.cpan.org/~danberr/
:|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742
7D3B 9505 :|

-- libvir-list mailing list libvir-list redhat com
https://www.redhat.com/mailman/listinfo/libvir-list

--
libvir-list mailing list
libvir-list redhat com
https://www.redhat.com/mailman/listinfo/libvir-list

--
libvir-list mailing list
libvir-list redhat com
https://www.redhat.com/mailman/listinfo/libvir-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]