From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH 00/11] [v2] misc changes for kexec in pv-on-hvm guests Date: Mon, 1 Aug 2011 15:00:50 +0200 Message-ID: <20110801130050.GC9956@aepfle.de> References: <20110728132300.248098023@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jul 28, Keir Fraser wrote: > On 28/07/2011 14:23, "Olaf Hering" wrote: > > > 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? > > Rip the moving parts from tools/misc/xen-detect.c. It does rely on hooking > SIGILL if you want to safely probe for being a PV guest (uses a > paravirtualised CPUID instruction that is normally an illegal instruction). Thanks, I will work on a better kexec-tools patch to distinguish dom0 from a PVonHVM guest. Olaf