aboutsummaryrefslogtreecommitdiffstats
path: root/tools/blktap/drivers/block-sync.c
diff options
context:
space:
mode:
authorKeir Fraser <keir.fraser@citrix.com>2008-07-11 12:47:50 +0100
committerKeir Fraser <keir.fraser@citrix.com>2008-07-11 12:47:50 +0100
commitb7e17149f3579bf5e99d51e1f9f6524631bfd2ee (patch)
tree95c30da6b8288bc7a0406050b5140ae33f30c9e4 /tools/blktap/drivers/block-sync.c
parent7acbaf60a917f48fb551b21086d9c6ef34705de6 (diff)
downloadxen-b7e17149f3579bf5e99d51e1f9f6524631bfd2ee.tar.gz
xen-b7e17149f3579bf5e99d51e1f9f6524631bfd2ee.tar.bz2
xen-b7e17149f3579bf5e99d51e1f9f6524631bfd2ee.zip
xend: Ignore errors from dying domains in RPC server
When a domain is in the process of shutting down there is a small window when the domain is known to XenD, but it will be unable to form an SXPR for it due it being in the middle of device hot-unplug. This causes the 'xm list' command to totally fail with an error like # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] The 'xm list' command calls into the 'domains' method of XMLRPCServer.py in XenD. This method just iterates over the list of domains, fetching the sxpr for each in turn, but with no exception handling. So if a single domain fails to generate an sxpr, no data is returned even for other domains which are still functional. This patch simply makes XenD ignore and skip over domains which throw an exception, logging the problematic domain. NB, this problem only hits 'xm list' if it is configured to use the legay XMLRPC server instead of XenAPI. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'tools/blktap/drivers/block-sync.c')
0 files changed, 0 insertions, 0 deletions