[Pkg-libvirt-maintainers] Bug#579801: Bug#579801: libvirt-bin errors about cpu topology

Guido Günther agx at sigxcpu.org
Sat May 1 09:02:45 UTC 2010


On Sat, May 01, 2010 at 10:58:03AM +0200, Guido Günther wrote:
> Hi Ritesh,
> On Sat, May 01, 2010 at 02:13:49AM +0530, Ritesh Raj Sarraf wrote:
> > Package: libvirt-bin
> > Version: 0.8.0-2
> > Severity: important
> > 
> > When I try to use virt-manager to connect to my locally running libvirtd instance,
> > I get the following error and the connection is never established.
> > 
> > May  1 02:04:54 learner libvirtd: 02:04:54.719: error : parse_socket:126 : cannot open /sys/devices/system/cpu/cpu0/topology/physical_package_id: No such file or directory
> > May  1 02:04:54 learner libvirtd: 02:04:54.720: warning : qemudCapsInit:1068 : Failed to get host CPU
> > May  1 02:04:54 learner libvirtd: 02:04:54.983: error : parse_socket:126 : cannot open /sys/devices/system/cpu/cpu0/topology/physical_package_id: No such file or directory
> > May  1 02:04:55 learner libvirtd: 02:04:55.467: error : parse_socket:126 : cannot open /sys/devices/system/cpu/cpu0/topology/physical_package_id: No such file or directory
> Please see 
> 	http://wiki.debian.org/libvirt#Bugreports.2BAC8-Debugging
> on howto generate debugging information. Can you try to verify if this
> is really the reason for your issues? I do wonder why you're lacking
> these files /sys.
The important part is virt-manager here. It seems libvirt is behaving
sanely but I assume getNodeInfo fails for virt-manager and so it hangs
but it shouldn't. Can you check that?
Cheers,
 -- Guido





More information about the Pkg-libvirt-maintainers mailing list