Your message dated Mon, 11 Aug 2014 22:11:14 +0200
with message-id <[email protected]>
and subject line Re: Bug#579801: [Pkg-libvirt-maintainers] Bug#579801: marked
as done (libvirt-bin errors about cpu topology)
has caused the Debian Bug report #579801,
regarding libvirt-bin errors about cpu topology
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
579801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579801
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
I have used older versions of libvirt on this machine earlier without problems
but am not sure which version must have introduced this problem
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-4-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libvirt-bin depends on:
ii adduser 3.112 add and remove users and groups
ii libavahi-client3 0.6.25-3 Avahi client library
ii libavahi-common3 0.6.25-3 Avahi common library
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcap-ng0 0.6.3-1 An alternate posix capabilities li
ii libdevmapper1.02.1 2:1.02.45-1 The Linux Kernel Device Mapper use
ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr
ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr
ii libparted0 2.2-5 The GNU Parted disk partitioning s
ii libpciaccess0 0.11.0-2 Generic PCI access library for X
ii libreadline6 6.1-1 GNU readline and history libraries
ii libsasl2-2 2.1.23.dfsg1-5 Cyrus SASL - authentication abstra
ii libudev0 151-3 libudev shared library
ii libuuid1 2.16.2-0 Universally Unique ID library
ii libvirt0 0.8.0-2 library for interfacing with diffe
ii libxenstore3.0 3.4.3~rc3-2 Xenstore communications library fo
ii libxml2 2.7.7.dfsg-2 GNOME XML library
ii logrotate 3.7.8-6 Log rotation utility
Versions of packages libvirt-bin recommends:
ii bridge-utils 1.4-5 Utilities for configuring the Linu
ii dnsmasq-base 2.52-1 A small caching DNS proxy and DHCP
ii iptables 1.4.6-2 administration tools for packet fi
ii netcat-openbsd 1.89-4 TCP/IP swiss army knife
ii qemu 0.12.3+dfsg-4 fast processor emulator
ii qemu-kvm 0.12.3+dfsg-4 Full virtualization on x86 hardwar
Versions of packages libvirt-bin suggests:
ii policykit-1 0.96-2 framework for managing administrat
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Sat, May 01, 2010 at 03:14:22PM +0530, Ritesh Raj Sarraf wrote:
> On Saturday 01 May 2010 14:42:20 Guido Günther wrote:
> > On Sat, May 01, 2010 at 08:45:07AM +0000, Debian Bug Tracking System wrote:
> > > Mistakenly, the kernel that had been running for the last couple of weeks
> > > was a -486 kernel on my Core Duo processor. That caused the problem.
> >
> > It's still a bug though. I reopened and lowered the severity.
> > -- Guido
>
> Yes, I agree. When run with the 486 image, the cpu was listed as Uniprocessor
> but did have the vmx extension listed.
We don't have that kernel in Debian anymore, so I'm closing this
report.
Cheers
-- Guido
--- End Message ---
