[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xentop missing domain state marker

> full details (versions, configuration etc) to the list. It'd also be
> interesting to know what "xl list" says about those domains.

host                   : earth
release                : 3.5.0-48-generic
version                : #72~precise1-Ubuntu SMP Tue Mar 11 20:09:08 UTC
machine                : x86_64
nr_cpus                : 8
max_cpu_id             : 15
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2806
hw_caps                :
virt_caps              : hvm
total_memory           : 24567
free_memory            : 4212
sharing_freed_memory   : 0
sharing_used_memory    : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 2
xen_extra              : .2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : placeholder dom0_mem=6500M dom0_max_vcpus=2
cc_compiler            : gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
cc_compile_by          : root
cc_compile_domain      : 
cc_compile_date        : Sat Apr 27 19:19:06 EEST 2013
xend_config_format     : 4

dom0 has:
GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6500M dom0_max_vcpus=2

Each guest has been configured to run with a 1VCPU.

The problem comes when I load all guests, meaning Im putting some load
on each guest domain, to simulate some conditions that I will be able to
measure using xenrec from dom0. During my tests I was able to notice
this strange thing coming from xentop.

I will repeat the tests and post back xl list during the test. Most
likely same thing will pop-up.

> I suspect the answer is that there are states between running and
> blocked which are not seen outside of the hypervisor, are these states
> transient or constant for a given domain?

Can we somehow get a valid 'NA' if none of the expected values: 
 blocked (b), dying (d), shutdown (s) crashed (c), paused (p), running
(r) are found ? 

Stefan Parvu <sparvu@xxxxxxxxxxxxxxxxxxxxxx>

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.