|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] domu state: broken
> I have yet been able to have a correctly working domu state working
> without being in a broken state. I can do everything regarding networks
> and have check all the appropriate logs but I still can not debug or
> find out what could be causing the broken state. Are there proper
> places one can look?
>
> # xm list
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 6560 2 r-----
> 317.6 node1 10 750 1
> -b---- 4.4
That looks normal to me. The "b" stands for "blocked" i.e. it's probably
waiting for IO from disk or network. On a uniprocessor system you'll never
actually a domain other than dom0 in the "r" (running) state - since in order
to run xm list, dom0 has to be in the act of running. On a multiprocessor
system, a domain which is doing lots of IO, or not using the CPU much, or
sharing with other domains is also going to spend quite a lot of time not in
the "r" state.
Does the CPU time usage displayed by xm list go up? If you use xm console,
can you connect to the domain? I suspect the domain has started OK, but
possibly its not displaying the console correctly or something. It looks
like it's running tho...
Cheers,
Mark
--
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|