Starting about 2 weeks ago Xend has started to fall over a lot doing what
should be normal actions, so much so that our xm-test suite more or less
fails all the tests as it keeps apparently knocking over xend on relatively
simple operations like create, and list.
What is most bizarre now is this "no such process" error generated by Xend.
Here is a segment of our xm-test results that shows this:
...
[dom0] Running `xm create /dev/null ramdisk=/root/xm-test/ramdisk/initrd.img
kernel=/boot/vmlinuz-2.6.12-xenU root=/dev/ram0 name=default memory=64'
Using config file "/dev/null".
Traceback (most recent call last):
File "/usr/sbin/xm", line 10, in ?
main.main(sys.argv)
File "/root/xen-unstable/dist/install/usr/lib/python/xen/xm/main.py", line
724, in main
handle_xend_error(argv[1], args[0], ex)
File "/root/xen-unstable/dist/install/usr/lib/python/xen/xm/main.py", line
162, in handle_xend_error
raise ex
xen.xend.XendProtocol.XendError: (3, 'No such process')
Unable to create domain
...
Any thoughts on why this is might be the case?
-Sean
--
__________________________________________________________________
Sean Dague Mid-Hudson Valley
sean at dague dot net Linux Users Group
http://dague.net http://mhvlug.org
There is no silver bullet. Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________
pgp4BZRNqq6Na.pgp
Description: PGP signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home