|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] [BUG] xm create with an invalid kernel, get a generic domain
2.0.5 stable tools
I know this is unusual, but if you start a domain with an invalid kernel
(/bin/true,
or a mis-configured kernel, doesn't matter), xend errors out, but creates a
generically named domain and occupies the memory.
# xm info | grep free
free_memory : 861
# cat foo.conf
kernel = "/bin/true"
name = "badkerneltest"
# xm create -f foo.conf -c
Using config file "foo.conf".
Error: Error creating domain: (9, 'Bad file descriptor')
# xm info | grep free
free_memory : 765
# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 123 0 r---- 18173.9
Domain-64 64 96 3 --p-- 0.0
==> /var/log/xend.log <==
[2005-04-02 13:26:45 xend] ERROR (SrvBase:162) op=create: Error creating
domain: (0,
'Error')
Traceback (most recent call last):
File "/usr/lib/python/xen/xend/server/SrvBase.py", line 107, in _perform
val = op_method(op, req)
File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 71, in op_create
raise XendError("Error creating domain: " + str(ex))
XendError: Error creating domain: (0, 'Error')
It seems like xm/xend tries to continue allocating the domain, when it should
error
out completely.
-Chris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] [BUG] xm create with an invalid kernel, get a generic domain and RAM occupied,
Christopher S. Aker <=
|
|
|
|
|