Ian Campbell
2012-Jul-12 17:30 UTC
[Pkg-xen-devel] Bug#648670: xm was unable determine an actual domU state under some conditions
Hi Moonwalker, You might have some luck poking around under /var/lib/xend/*, or perhaps by removing and recreating the guest. Unfortunately the xend toolstack is not really maintained upstream (to be honest it is unmaintainable and no one has stepped up). Since you are using the "managed domains" functionality you might be interested in the xcp-xapi package which is in Wheezy today. Ian.
Seemingly Similar Threads
- Bug#648670: xm was unable determine an actual domU state under some conditions
- Processed: Retitle and reassign "xcp-xapi fails to start" to xen-utils-common as "xend shouldn't start if TOOLSTACK is not xm"
- Bug#682122: xcp-xapi: README.Debian has a few misleading commands
- Bug#721345: xcp-xapi: xl pci-attach is called by xapi in a PCI passthrough attempt. An error is raised due to the use of xapi and the PCI device cannot be attached to the VM.
- Bug#680528: xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot