On 02/16/2010 05:11 PM, Frédéric Grelot wrote:
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 i
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 un
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: deb
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.
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
> 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,
On 02/15/2010 02:30 PM, Frédéric Grelot wrote:
The udev driver is actually fully loaded, I even entered "udevadm
monitor" in a console, and it reacted as expected when I
plugged/unplugged an usb mouse... There is nothing about it in
dmesg/boot/message.log, nor libvirt.log (I set up libvirt daemon
The udev driver is actually fully loaded, I even entered "udevadm monitor" in a
console, and it reacted as expected when I plugged/unplugged an usb mouse...
There is nothing about it in dmesg/boot/message.log, nor libvirt.log (I set up
libvirt daemon to log at debug level in /var/log/libvirt/lib
> > # 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
I restarted the server, with no change.
I uninstalled
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 us
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, o
11 matches
Mail list logo
