From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 00/11] [v2] misc changes for kexec in pv-on-hvm guests Date: Fri, 29 Jul 2011 13:35:37 -0400 Message-ID: <20110729173537.GB7745@dumpdata.com> References: <20110728132300.248098023@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110728132300.248098023@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Olaf Hering Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jul 28, 2011 at 03:23:00PM +0200, Olaf Hering wrote: > > > The following series implement kexec in a pv-on-hvm guest. > I send it here once more for further review before bothering lkml. Ah, OK. Ignore my comment about attaching the other maintainers to the patch then. > > With this series doing kexec in a loop is now possible. > > > A fixed kexec-tools-2.0.2 package is required: > http://lists.infradead.org/pipermail/kexec/2011-May/005026.html > However, as I just found out, xenfs unconditionally adds /proc/xen/capabilities > even for hvm guest. > > So: how is a hvm guest supposed to be detected in 3.0? A real "HVM" or PVonHVM? What about following the syntax of 'xen-detect' which does an cpuid instruction. > > Olaf > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel