On Wednesday 13 August 2008 14:48:04 Keir Fraser wrote:
> On 13/8/08 13:40, "Christoph Egger" <Christoph.Egger@xxxxxxx> 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
> > VIRQ_MCA events in the Dom0.
>
> How do I make it do that?
Assuming you use Linux as Dom0, apply the attached patch to your local tree.
With it, you should see a flood of "xen_mca: HW reported correctable error(s)"
Dom0 kernel messages.
Note, the patch is not intended to go upstream. There will be something better
in the future.
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
linux_xenmca.diff
Description: Text Data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|