On Mon, Feb 09, 2009 at 01:48:58PM +0000, Daniel P. Berrange wrote: > 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. No. I'm waiting to get some more details, and I also now have access to his Sparc machine so I can test this myself. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my OCaml programming blog: http://camltastic.blogspot.com/ Fedora now supports 68 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list