WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] domain reboots broken

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] domain reboots broken
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Thu, 16 Nov 2006 13:51:40 -0700
Delivery-date: Thu, 16 Nov 2006 12:53:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: OSLO R&D
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
   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.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel