Re: domain reboots broken (and suspend too)

[Chris <hap10@tycho.ncsc.mil>]

Alex Williamson wrote:
>    I noticed this problem on Xen/ia64, but I see the same behavior on
> Xen/x86_64 cset:12468:fc25a6eadccd (maybe x86_32 as well?).  Rebooting a
> paravirt domain doesn't work.  The xend.log looks pretty normal and ends
> with "Adding domain #", but xm-list doesn't show the new domain running.
> Furthermore, there would appear to be a memory leak as if the new domain
> (that doesn't show up in xm list) is actually there.  Even more strange,
> I can do an xm destroy on the domain number that should have been
> created on the reboot, but isn't listed in xm list, and get the memory
> back.  This is pretty simple to reproduce, just create a paravirt domain
> that restarts on reboot (the default) and try it.  Thanks,

I see the behavior too.

See my post yesterday: "Problems Noticed after Xend-API Patchset."  The
short version is that both reboot and suspend are broken.

Hopefully Ewan and/or Alastair will confirm and put these issues in
their queue.

-Chris