On Mon, Feb 09, 2009 at 01:37:14PM +0000, Richard W.M. Jones wrote: > Below is what /proc/cpuinfo looks like on an Ultrasparc T1 running > Linux. > > I haven't looked into it in detail yet, but the report from Dennis > Gilmore is that this breaks every libvirt command. Presumably we are > parsing /proc/cpuinfo at libvirt startup ... It shouldn't break libvirt startup AFAICT. We use this info for the virNodeInfo command obviously, but also when starting a new guest for purpose of CPU pinning. The latter is probably better off with us using numactl or a sysconf() macro determine max # of pCPUs available, since we don't need the full socket,core, thread topology in that context. > (Initially reported by Dennis Gilmore) Don't suppose Dennis has a patch to add support for this ? He mentioned he was going to work on one when this came up on IRC a week or so back. FWIW, we'll need to add logic to src/nodeinfo.c to make the /proc/cpuinfo fields it looks for be architecture dependant since this stuff varies across basically every architecture. I expect ia64, ppc, s390, etc are all just as broken in this regard. 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@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list