Hi Marcus,
On Mon, Dec 12, 2011 at 09:05:30PM +0100, Marcus Osdoba wrote:
> Am 30.11.2011 20:49, schrieb Guido Günther:
> >>Traceback (most recent call last):
> >> File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick
> >> conn.tick()
> >> File "/usr/share/virt-manager/virtManager/connection.py", line 1410, in
> >> tick
> >> self.hostinfo = self.vmm.getInfo()
> >> File "/usr/lib/python2.6/dist-packages/libvirt.py", line 2824, in getInfo
> >> if ret is None: raise libvirtError ('virNodeGetInfo() failed',
> >> conn=self)
> >>libvirtError: An error occurred, but the cause is unknown
> >Please check why libvirt is failing here. Using "virsh nodeinfo" and
> >running libvirt in debug mode should provide some useful output.
> Hi, sorry for the late answer.
> Please find attached my protocol of libvirtd with log_level=1.
>
> When running:
>
> root@debian:/home/test# virsh nodeinfo
> error: failed to get node information
> error: An error occurred, but the cause is unknown
>
> the output attached was created.
>
> One need to know, that I tried to use the 486 variant (which is the
> only option for non-PAE systems beyond squeeze).
You mean you're running the 486 kernel flavour? If so I'll try to
reproduce this once I have more than GPRS to download the kernel.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
