> The only chance to see a domU in a state other than "b" is to use a
SMP system. :)
I have a smp and it shows blocked for me too
SMP doesn't guarantee that the guests are running when doing xm info. However,
being uni-processor GUARANTEES that Dom0 is the one running...
means that the guest is blocked, which is the state it is in when it's waiting
for I/O, timers or other domain(s) to let it run again. It's impossible to say
which one of those three (or more) possible causes are actually holding the
process up. If you don't actively do something in a domain, it will be blocked.
The best way to see SMP systems run is to put some infinite loop in a command
shell, or better yet run an infinite loop in a compiled language, such as
for(;;) ; /* doesn't end */
return 0; /* this is just here to make the
compiler happy */
forever.c -o forever
will make the domain use 100% of it's allocated CPU time (and any "spare"
cpu-time too, if there is any).
do this in Dom0, unless you want all DomU's to run very slow (and unless you
have Credit scheduler, in which case it MAY work OK).
Find out what India is talking about on - Yahoo!
Send FREE SMS to your friend's mobile from Yahoo!
Messenger Version 8. Get
Xen-users mailing list