time xm li --state=running Name ID Mem VCPUs State Time(s) Domain-0 0 2048 8 r----- 63348.0 compute1 24 4096 8 -b---- 7916.9 hati 10 2048 2 -b---- 11995.5 ipcop_test 28 512 1 -b---- 727.2 titan 1 2048 2 -b---- 9005.4 trac 14 512 1 -b---- 2715.5 real 46m19.120s user 0m0.142s sys 0m0.220s Could someone at least offer an possible explanation? It is a b133 xvm running on Xeon(Harpertown). Florian
Uhm still have incredible latency for xm commands in dom0, strange is that the second server (completely the same) not has this problem. Ideas? Please! Florian Am 02.03.2010 13:31, schrieb Florian Manschwetus:> time xm li --state=running > Name ID Mem VCPUs State > Time(s) > Domain-0 0 2048 8 r----- > 63348.0 > compute1 24 4096 8 -b---- > 7916.9 > hati 10 2048 2 -b---- > 11995.5 > ipcop_test 28 512 1 -b---- > 727.2 > titan 1 2048 2 -b---- > 9005.4 > trac 14 512 1 -b---- > 2715.5 > > real 46m19.120s > user 0m0.142s > sys 0m0.220s > > Could someone at least offer an possible explanation? It is a b133 xvm > running on Xeon(Harpertown). > > Florian > > > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
On 3/11/10 9:23 AM, Florian Manschwetus wrote:> Uhm still have incredible latency for xm commands in dom0, strange is > that the second server (completely the same) not has this problem. > > Ideas? Please! >What do the log files say? - have you increased the logging levels? Otherwise, try truss... K.