aboutsummaryrefslogtreecommitdiffstats
path: root/tools/flask/libflask
diff options
context:
space:
mode:
authorkfraser@localhost.localdomain <kfraser@localhost.localdomain>2007-08-28 16:11:05 +0100
committerkfraser@localhost.localdomain <kfraser@localhost.localdomain>2007-08-28 16:11:05 +0100
commit40f18cbcf0740bde81f6e9ed7f6ac82677d5e057 (patch)
treec58bc19294eb2faade1e06eed1f523e5014773e6 /tools/flask/libflask
parentde01426fdf7361ea196626901998408b76a33735 (diff)
downloadxen-40f18cbcf0740bde81f6e9ed7f6ac82677d5e057.tar.gz
xen-40f18cbcf0740bde81f6e9ed7f6ac82677d5e057.tar.bz2
xen-40f18cbcf0740bde81f6e9ed7f6ac82677d5e057.zip
xm: Fix error message for xm create command.
When I tested xm create command, I saw the following error message. I expected an error message "Error: (12, 'Cannot allocate memory')" because I intentionally caused a memory shortage on the test. But the error message was different from my expectation. # xm create /xen/HVMdomain.1 Using config file "/xen/HVMdomain.1". Error: an integer is required I looked at xend.log to examine the cause why the error message was shown. (Could you see the attached xend.log?) xend had the error message "Error: (12, 'Cannot allocate memory')" first. But xend changed the error message to "Error: an integer is required" halfway. I'm not sure about the cause why an exception occurred in logging processing. But when I applied an attached patch, I confirmed that the error message that I expected was shown. The patch does not call xc.domain_destroy_hook() if self.domid is None. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Diffstat (limited to 'tools/flask/libflask')
0 files changed, 0 insertions, 0 deletions