From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Subject: Re: domain reboots broken (and suspend too) Date: Thu, 16 Nov 2006 16:50:15 -0500 Message-ID: <455CDD17.8040900@tycho.ncsc.mil> References: <1163710300.5529.35.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1163710300.5529.35.camel@lappy> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alex Williamson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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