Comment 15 for bug 1446177

Weird. The initial scan should be able to open /sys/devices/system/node and then iterate over node0..7. Inside for example /sys/devices/system/node/node0/ there should be (the output unfortunately does not show as those are links) links for each cpu associated with that node. So in case of node0 there should be cpu0..7 pointing to ../../cpu/cpu0...7. Can you confirm those are there?
The only cases that would drop back to hard set the nodes to 1 seem to be:
- not being able to read /sys/devices/system/node
- failing to find /sys/devices/system/node/node<num>/cpu<num> entries
- failing to read from /sys/devices/system/node/node<num>/cpu<num>/topology/physical_package_id
  (sockets = max(physical_package_id)+1 -> should be 4 according to sysfs data)
- failing to allocate the socket bitmap which seems unlikely

And there is really nothing related to sysfs parsing in /var/log/libvirt/libvirt.log?