Displaying 2 results from an estimated 2 matches for "xm_list".
Did you mean:
vm_list
2006 Dec 13
1
Bug#402974: xen-utils-common: xen domain do not always shutdown
..."$1" | cut -c0-17`
+ name=`echo "$1" | cut -c0-40`
name=${name%% *}
- rest=`echo "$1" | cut -c18- `
+ rest=`echo "$1" | cut -c41- `
read id mem cpu vcpu state tm < <(echo "$rest")
}
@@ -204,15 +204,31 @@
fi
}
+xm_list()
+{
+ OK=0
+ while [ $OK -eq 0 ]; do
+ OUT=`xm list`
+ echo "$OUT" | grep -q "^Usage"
+ if [ $? -eq 1 ]; then
+ OK=1
+ else
+ sleep 1s
+ fi
+ done
+ echo "$OUT"
+ return 0
+}
+
all_zombies()
{...
2006 May 02
0
Mini-OS and Xend issue
...ot;list, destroy". Other commands like "vcpu-list" continue
to work. Once I restart xend, the problem goes away and does not show up
again. This happens only on fresh boots.
I did a little tracing on "xm list". (xm log is at the bottom)
xm list ends up calling
xm/main.py: xm_list()->getDomains()->server.xend.domains(1)
This ends up in
xend/XendDomain.py: xen_domains() -> xc.domain_getinfo()
This ends up in
lowlevel/xc/xc.c: pyxc_domain_getinfo()
Strange thing is that can see the last debug print in getDomains before
it called xen_domains() and the last print in xe...