From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [Xen-devel] [PATCH] xen PVonHVM: require at least Xen 3.4 as dom0 Date: Tue, 30 Oct 2012 19:28:59 +0100 Message-ID: <20121030182859.GA8775@aepfle.de> References: <1351613105-24408-1-git-send-email-olaf@aepfle.de> <20121030181732.GZ8912@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20121030181732.GZ8912@reaktio.net> Sender: linux-kernel-owner@vger.kernel.org To: Pasi =?utf-8?B?S8Okcmtrw6RpbmVu?= Cc: Jeremy Fitzhardinge , Konrad Rzeszutek Wilk , xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org List-Id: xen-devel@lists.xenproject.org On Tue, Oct 30, Pasi K=C3=A4rkk=C3=A4inen wrote: > On Tue, Oct 30, 2012 at 05:05:05PM +0100, Olaf Hering wrote: > > The XenPVHVM extensions have not been tested much on very old > > hypervisors. At least Xen 3.4 gets some testing with the pvops kern= el. > >=20 > > Require at least Xen 3.4 for the PVonHVM extensions. If an older > > hypervisor is detected the extensions will be disabled and the gues= t > > will only see emulated hardware. > >=20 > > Signed-off-by: Olaf Hering > > >=20 > IIRC upstream Linux PVonHVM drivers do work OK today on RHEL5 Xen,=20 > which advertises itself as Xen 3.1.2-based.. If thats the case, and a combination thats supposed to work, the patch can be dropped if the hvmloader does really leave room at =46E700000-FE800000. Olaf