From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Egger Subject: Re: Re: machine check report on HVM startup Date: Wed, 13 Aug 2008 14:40:58 +0200 Message-ID: <200808131440.58286.Christoph.Egger@amd.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: Keir Fraser List-Id: xen-devel@lists.xenproject.org On Wednesday 13 August 2008 14:36:21 Keir Fraser wrote: > On 13/8/08 13:27, "Keir Fraser" wrote: > >> This looks to me, there's a non-public event channel using the same > >> number as VIRQ_MCA which fires when launching memtest as HVM guest. > > > > I don't think this is the case. Sounds easy to repro this issue though. > > I'll give it a go. > > I can boot a memtest-3.4 ISO in an HVM guest on PAE hypervisor just fine. Does your Dom0 kernel registrate the machine check event handler ? If not, then it things go fine. If yes, then you should see the flood of=20 VIRQ_MCA events in the Dom0. Christoph =2D-=20 AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Gesch=E4ftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplement=E4r: AMD Saxony LLC (Sitz Wilmington, Delaware, USA) Gesch=E4ftsf=FChrer der AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy