We are moving our equipment to the datacenter tomorrow, so won't have
much more input until after then. But all of the links etc are all
where they are expected to be. Not sure if the libvirt user can read
those, but I'm sure it can since my standard user can.
Running a 'find . -name physical_package_id -exec cat {} \;' from
/sys/devices/system shows 0's and 1's. So according to your formula
there, we would definitely be seeing a "2" for my sockets. Shows only
1. According to the other data, that 1 is not from the "max" value, it
is simply just putting 1 as a static number.
I am not sure what socket bitmap is, or anything else about it. :-) Or
I might have something to comment on this.
Also, one thing to keep in mind, all of this has been fixed since Ubuntu
15.04. So something in the pipe between all previous versions and then
has allowed this to start working. This is possibly kernel related or
even in another package that libvirt depends on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446177
Title:
Nodeinfo returns wrong NUMA topology / bad virtualization performance
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1446177/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
