https://bugzilla.novell.com/show_bug.cgi?id=662083 https://bugzilla.novell.com/show_bug.cgi?id=662083#c3 --- Comment #3 from Samuel Kvasnica <samuel.kvasnica@ims.co.at> 2011-01-10 21:36:49 UTC --- Uhm, this is going to be complicated. I don't see any straight mathematical relationship of this offset to the number of cpus, at least there must be other parameter involved. It began with 2.6.34 kernel, well actually already 2.6.33 if you look into my old good Bug #584554. I get following offsets: PentiumD 2-core: dom0-cpus=1: 1.0 Xeon X3450 4-cores + HT: dom0-cpus=2: 5.0 Xeon E5530 4-cores + HT (1 socket only): dom0-cpus=2, 2.0 or 3.0 ..so I wouldn't dare to fit a 5-th degree polynomial over 3 points... I just rebooted the pentiumD system several times. Results so far: - native kernel, playing with /sys/devices/system/cpu/cpu1/online => correct load average - dom0_max_vcpus=1 => correct load average - I've observed this happening immediately after starting 'rcxend start' by hand, in that state I see: top - 22:15:37 up 42 min, 3 users, load average: 0.97, 0.67, 0.40 Tasks: 172 total, 1 running, 171 sleeping, 0 stopped, 0 zombie Cpu0 : 0.1%us, 0.4%sy, 0.2%ni, 99.1%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st xm vcpu-list 0 Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 0 r-- 346.7 any cpu Domain-0 0 1 - --p 20.7 any cpu ..why are there actually 2 CPUs shown ? and if I invoke 'xm vcpu-set 0 2' now, load average gets correct. Switching vcpu-set to 1/2 several times => still everything correct. - however (!), I've observed cases (about 30%) when this did not happen at all during manual xend start, I have the pentiumD system in such state at the moment and will wait if it climbs up over night. I would say it is very likely to happen if xend is started automatically during the boot process => race condition ? Other specialities: there is openais and drbd running on all these systems. And there are no DomUs running while testing this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.