https://bugzilla.novell.com/show_bug.cgi?id=662083 https://bugzilla.novell.com/show_bug.cgi?id=662083#c5 --- Comment #5 from Samuel Kvasnica <samuel.kvasnica@ims.co.at> 2011-01-11 13:32:00 UTC --- (In reply to comment #4)
(In reply to comment #3)
- 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
Which you consider right or wrong? wrong, it is the +1.0 offset case
...why are there actually 2 CPUs shown ?
Because vCPU-s can't be removed altogether, they can only be marked unused (or really, paused). If the resources tied to this worry you, dom0_max_vcpus= is your friend. ok
- 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
just looked at that box again, it did not climb up, seems to be happening only on xend start
to happen if xend is started automatically during the boot process => race condition ?
Does it perhaps matter whether the CPU being removed happens to be under load? If so, the question then would (again) be whether the same applies to native.
I will test this, cpu load is very probably involved. -- 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.