I tried to start a domain that I knew would fail, as the vbd it would
use was already in use.
However, Xend entered a state that made xm unusable and I had to restart
it:
# xm create -c hal2.xm 
Using config file "./hal2.xm".
/usr/lib/xen/bin/xenconsole: invalid option -- 1
Invalid number of arguments
Try `/usr/lib/xen/bin/xenconsole --help' for more information.
# xm list
Internal error: Device 769 (vbd) could not be connected.
Device /dev/bit/xentmp is mounted in a guest domain,
and so cannot be mounted now..
Internal error: (3, 'No such process').
# xm list
Internal error: (3, 'No such process').
The conversation that is causing the problem:
---> to server
<?xml version='1.0'?>
<methodCall>
<methodName>VM_metrics.get_all_records</methodName>
<params>
<param>
<value><string>314e378d-1895-3682-d254-66e6134f0950</string></value>
</param>
</params>
</methodCall>
<--- from server
<?xml version='1.0'?>
<methodResponse>
<params>
<param>
<value><struct>
<member>
<name>Status</name>
<value><string>Failure</string></value>
</member>
<member>
<name>ErrorDescription</name>
<value><array><data>
<value><string>INTERNAL_ERROR</string></value>
<value><string>(3, 'No such process')</string></value>
</data></array></value>
</member>
</struct></value>
</param>
</params>
</methodResponse>
-- 
lfr
0/0

Attachment: pgph7b7eifzVG.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel