From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: domain reboots broken Date: Thu, 16 Nov 2006 13:51:40 -0700 Message-ID: <1163710300.5529.35.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org 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, Alex -- Alex Williamson HP Open Source & Linux Org.