Hi Dave and all
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?
I first built it from source (0.7.6), but, when the package was released in rawvirt (repo
enabled in my system), I uninstalled my version ("make uninstall" in the
directory where I installed it from), then installed that of rawvirt...
When I started having these problems, I uninstalled / reinstalled again, but it didn't
change anything.
Well... you solved my problem anyway : to sort this out, I tried that again. Thus I
noticed that after having uninstalled everything (yum remove + make uninstall), the
"libvirtd" command still "worked" (with errors). I checked... and
there was a /sbin/libvirtd, left by I-don-t-know-which install! . It was one of those
last, undoubtly, since "libvirtd --version" actually returned 0.7.6... (And, of
course, in the default PATH, /sbin stands before /usr/bin/...)
I removed (=backuped just in case...) it, installed with yum, and it works at last!
Thanks for your help, you got me to the right path... And sorry for the inconvenient of a
"custom" install...
However, I don't explain why this libvirtd was left there... Were the paths changed
lately?
Frederic
----- "Dave Allan" <dallan(a)redhat.com> a écrit :
On 02/16/2010 03:04 PM, Frédéric Grelot wrote:
> Yep, here is what I get (see at the end) :
>
(snip)
>
> 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(a)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(a)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(a)redhat.com
>>>>>
https://www.redhat.com/mailman/listinfo/libvir-list
>>>
>>> --
>>> libvir-list mailing list
>>> libvir-list(a)redhat.com
>>>
https://www.redhat.com/mailman/listinfo/libvir-list
>
> --
> libvir-list mailing list
> libvir-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/libvir-list