https://bugzilla.novell.com/show_bug.cgi?id=662083
https://bugzilla.novell.com/show_bug.cgi?id=662083#c4
Jan Beulich
- 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?
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 ?
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.
- 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 ?
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. -- 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.