RE: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

I saw general exception in Xen:

VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 240kB freed
translate_domain_pte: bad mpa=0000010000000014 (>
0000000010004000),vadr=e000010
000000014,pteval=0010010000000661,itir=0000000000000760
(XEN) translate_domain_pte: bad mpa=000000007c1c8618 (>
0000000010004000),vadr=3
fffff0000000618,pteval=000000007c1c8561,itir=0000000000000038
(XEN) lookup_domain_mpa: bad mpa 000000007c1c8618 (> 0000000010004000
(XEN) translate_domain_pte: bad mpa=0000f84dc0003f30 (>
0000000010004000),vadr=2
000000000023f30,pteval=f000f84dc00016a3,itir=0000000000005138
(XEN) lookup_domain_mpa: bad mpa 0000f84dc0003f30 (> 0000000010004000
(XEN) ia64_fault: General Exception: IA-64 Reserved Register/Field fault
(data a
ccess): reflecting

Maybe due to our environment difference like disk image, still
investigate...

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian,
>Kevin
>Sent: Thursday, September 01, 2005 10:40 AM
>To: John Byrne
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] Community effort neededtocatch
>upwithxen-unstable
>
>>From: John Byrne [mailto:john.l.byrne@xxxxxx]
>>>
>>> You can "make XEN_NO_IOEMU=y". So this change is not required.
>>
>>Yeah, but I have to remember to do it.
>
>VTI unmodified domain will required device model, and use __ia64__ here
>actually affect the former. Later when we bring qemu back to compile,
>there's then no need for this option. So please just take a bit extra
>effort to assign the option in cmdline, or you can simply modify it
>locally but not send out as a patch. ;-)
>
>>
>>Here are my patches. I spoke too soon about being done. I think the
>>console driver has a problem in it. My system rebooted when I got to
>the
>>console login. I'm only online for about 1/2 hour more. Let me know if
>>you have the same problem or find a fix.
>>
>>John
>>
>
>I'm trying now...
>
>Thanks,
>Kevin
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel