Bug#648670: xm was unable determine an actual domU state under some conditions

2012-07-12 Thread Ian Campbell
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

Bug#648670: xm was unable determine an actual domU state under some conditions

2011-11-13 Thread Moonwalker
Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: xm start caused Domain is already running error,