[Pkg-xen-devel] Bug#418245: xen-utils-common: race condition in "xm
list" when destroying domains.
Russell Coker
russell at coker.com.au
Sun Apr 8 13:06:54 UTC 2007
Package: xen-utils-common
Version: 3.0.3-0-2
Severity: normal
After running "halt" in a couple of domains I ran "xm list" repeatedly to see
when the halt command was complete.
Below is some of the output. The "Device 0 not connected" should not occur.
yoyoxen:~# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 484 1 r----- 163.4
ha1 1 64 1 -b---- 138.3
ha1-unstable 2 64 1 -b---- 130.5
ha2-unstable 4 64 1 -b---- 134.9
yoyoxen:~# xm list
Error: Device 0 not connected
Usage: xm list [options] [Domain, ...]
List information about all/some domains.
-l, --long Output all VM details in SXP
--label Include security labels
yoyoxen:~# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 484 1 r----- 168.7
ha1-unstable 2 64 1 ------ 130.5
ha2-unstable 4 64 1 -b---- 135.0
yoyoxen:~#
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-xen-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Versions of packages xen-utils-common depends on:
ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip
ii udev 0.105-4 /dev/ and hotplug management daemo
xen-utils-common recommends no packages.
-- no debconf information
More information about the Pkg-xen-devel
mailing list