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/
Home Products Support Community News


Re: [Xen-devel] [PATCH 00/11] [v2] misc changes for kexec in pv-on-hvm g

To: Olaf Hering <olaf@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 00/11] [v2] misc changes for kexec in pv-on-hvm guests
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Thu, 28 Jul 2011 14:43:43 +0100
Delivery-date: Thu, 28 Jul 2011 06:44:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=+MeC9wXYYsmRo115Bw6J7t2E50gMNlPRCd4oHlxnnaA=; b=cDJ7ATxiAdN1hBFnjuzouKyxOKKc8bCDYhiJKh8xdhvrFgs88EsJL8DOPtR23UWdNx IhieeJllEPVvIklSKiHqi/jDTrqsR1oWvi+n9IfODbFwwOf6ZZnUOdiHxyMRUFoB1CaP tYkNFWqxavoaLznBzAMFzpxlXiOHTT74HuXvM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110728132300.248098023@xxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxNLF2I39/zcg9QGEC70gd2UqEHig==
Thread-topic: [Xen-devel] [PATCH 00/11] [v2] misc changes for kexec in pv-on-hvm guests
User-agent: Microsoft-Entourage/
On 28/07/2011 14:23, "Olaf Hering" <olaf@xxxxxxxxx> 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).

 -- Keir

Xen-devel mailing list