* Kernel panic with tboot E820_UNUSABLE region
@ 2013-05-14 11:06 Aurelien Chartier
2013-05-14 13:40 ` Konrad Rzeszutek Wilk
2013-05-14 13:53 ` David Vrabel
0 siblings, 2 replies; 14+ messages in thread
From: Aurelien Chartier @ 2013-05-14 11:06 UTC (permalink / raw)
To: xen-devel; +Cc: Ross Philipson, konrad.wilk
Hi everybody,
We noticed a crash in Linux dom0 early boot sequence when running over
tboot and Xen. The issue seemed related with a E820 region that tboot is
setting as E820_UNUSABLE. We posted to tboot-devel to understand better
what could be the cause of the kernel panic. This thread can be read
here :
http://sourceforge.net/mailarchive/forum.php?thread_name=51852B26.7070406%40citrix.com&forum_name=tboot-devel
Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
and found what could be the cause of the kernel panic. I am not familiar
with that part of Xen, so feel free to correct me.
The Xen memory setup code called during early boot is trying to release
chunks of memory in xen_set_identity_and_release for non-RAM regions
(including E820_UNUSABLE). The xen_set_identity_and_release_chunk
function is calling HYPERVISOR_update_va_mapping, which will fail in our
case. As tboot marked that region as being unusable, Xen did not map
those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
Xen code) is returning an error. As the return value of the hypercall
is not checked in Linux code, xen_set_identity_and_release_chunk
function is carrying on and tries to release the E820_UNUSABLE chunk.
This is apparently messing up some Xen internal memory structures,
resulting in a kernel crash when Linux is initializing its memory mapping.
A possible fix I have tried is to check the return value of
HYPERVISOR_update_va_mapping and if encountering an error, exit from
xen_set_identity_and_release_chunk. This is fixing the kernel panic, but
I am not sure about other implications by that change.
Any ideas about this issue ?
Thanks in advance,
Aurelien
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 11:06 Kernel panic with tboot E820_UNUSABLE region Aurelien Chartier
@ 2013-05-14 13:40 ` Konrad Rzeszutek Wilk
2013-05-14 14:11 ` Jan Beulich
2013-05-14 14:12 ` Aurelien Chartier
2013-05-14 13:53 ` David Vrabel
1 sibling, 2 replies; 14+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-14 13:40 UTC (permalink / raw)
To: Aurelien Chartier; +Cc: xen-devel, Ross Philipson
On Tue, May 14, 2013 at 12:06:16PM +0100, Aurelien Chartier wrote:
> Hi everybody,
>
> We noticed a crash in Linux dom0 early boot sequence when running over
> tboot and Xen. The issue seemed related with a E820 region that tboot is
> setting as E820_UNUSABLE. We posted to tboot-devel to understand better
> what could be the cause of the kernel panic. This thread can be read
> here :
> http://sourceforge.net/mailarchive/forum.php?thread_name=51852B26.7070406%40citrix.com&forum_name=tboot-devel
>
> Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
> and found what could be the cause of the kernel panic. I am not familiar
> with that part of Xen, so feel free to correct me.
>
> The Xen memory setup code called during early boot is trying to release
> chunks of memory in xen_set_identity_and_release for non-RAM regions
> (including E820_UNUSABLE). The xen_set_identity_and_release_chunk
> function is calling HYPERVISOR_update_va_mapping, which will fail in our
> case. As tboot marked that region as being unusable, Xen did not map
> those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
> Xen code) is returning an error. As the return value of the hypercall
> is not checked in Linux code, xen_set_identity_and_release_chunk
> function is carrying on and tries to release the E820_UNUSABLE chunk.
> This is apparently messing up some Xen internal memory structures,
> resulting in a kernel crash when Linux is initializing its memory mapping.
>
> A possible fix I have tried is to check the return value of
> HYPERVISOR_update_va_mapping and if encountering an error, exit from
> xen_set_identity_and_release_chunk. This is fixing the kernel panic, but
> I am not sure about other implications by that change.
The implications are explained in the git commit that added that:
83d51ab47
xen/setup: update VA mapping when releasing memory during setup
In xen_memory_setup(), if a page that is being released has a VA
mapping this must also be updated. Otherwise, the page will be not
released completely -- it will still be referenced in Xen and won't be
freed util the mapping is removed and this prevents it from being
reallocated at a different PFN.
This was already being done for the ISA memory region in
xen_ident_map_ISA() but on many systems this was omitting a few pages
as many systems marked a few pages below the ISA memory region as
reserved in the e820 map.
This fixes errors such as:
(XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 2097153 > 2097152
(XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 17)
So I think it would be OK to continue with the rest of the function, so something
like this:
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 94eac5c..f07ca54 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -219,9 +219,10 @@ static void __init xen_set_identity_and_release_chunk(
* to be updated to be 1:1.
*/
for (pfn = start_pfn; pfn <= max_pfn_mapped && pfn < end_pfn; pfn++)
- (void)HYPERVISOR_update_va_mapping(
+ if (HYPERVISOR_update_va_mapping(
(unsigned long)__va(pfn << PAGE_SHIFT),
- mfn_pte(pfn, PAGE_KERNEL_IO), 0);
+ mfn_pte(pfn, PAGE_KERNEL_IO), 0))
+ break;
if (start_pfn < nr_pages)
*released += xen_release_chunk(
But that looks like a hack as the issue seems to be with the hypervisor?
>
> Any ideas about this issue ?
Fix the bug in the hypervisor?
>
> Thanks in advance,
> Aurelien
^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 11:06 Kernel panic with tboot E820_UNUSABLE region Aurelien Chartier
2013-05-14 13:40 ` Konrad Rzeszutek Wilk
@ 2013-05-14 13:53 ` David Vrabel
2013-05-14 14:33 ` Aurelien Chartier
1 sibling, 1 reply; 14+ messages in thread
From: David Vrabel @ 2013-05-14 13:53 UTC (permalink / raw)
To: Aurelien Chartier; +Cc: xen-devel, Ross Philipson, konrad.wilk
On 14/05/13 12:06, Aurelien Chartier wrote:
> Hi everybody,
>
> We noticed a crash in Linux dom0 early boot sequence when running over
> tboot and Xen. The issue seemed related with a E820 region that tboot is
> setting as E820_UNUSABLE. We posted to tboot-devel to understand better
> what could be the cause of the kernel panic. This thread can be read
> here :
> http://sourceforge.net/mailarchive/forum.php?thread_name=51852B26.7070406%40citrix.com&forum_name=tboot-devel
>
> Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
> and found what could be the cause of the kernel panic. I am not familiar
> with that part of Xen, so feel free to correct me.
>
> The Xen memory setup code called during early boot is trying to release
> chunks of memory in xen_set_identity_and_release for non-RAM regions
> (including E820_UNUSABLE). The xen_set_identity_and_release_chunk
> function is calling HYPERVISOR_update_va_mapping, which will fail in our
> case. As tboot marked that region as being unusable, Xen did not map
> those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
> Xen code) is returning an error. As the return value of the hypercall
> is not checked in Linux code, xen_set_identity_and_release_chunk
> function is carrying on and tries to release the E820_UNUSABLE chunk.
> This is apparently messing up some Xen internal memory structures,
> resulting in a kernel crash when Linux is initializing its memory mapping.
That does not sound quite right to me. xen_set_identity_and_release()
is releasing RAM pfns that overlap with holes in the machine memory map
and get_page_from_l1e() should always succeed. The fact that they're
overlapping with something marked as UNUSABLE shouldn't matter since its
no different from any other of the holes.
Is tboot causing Xen to do something weird like leaving holes in dom0's
initial memory allocation?
I would also check what max_pfn_mapped is. Perhaps it's miscalculated
and were trying to update mappings that don't exit?
David
>
> A possible fix I have tried is to check the return value of
> HYPERVISOR_update_va_mapping and if encountering an error, exit from
> xen_set_identity_and_release_chunk. This is fixing the kernel panic, but
> I am not sure about other implications by that change.
>
> Any ideas about this issue ?
>
> Thanks in advance,
> Aurelien
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 13:40 ` Konrad Rzeszutek Wilk
@ 2013-05-14 14:11 ` Jan Beulich
2013-05-14 14:12 ` Aurelien Chartier
1 sibling, 0 replies; 14+ messages in thread
From: Jan Beulich @ 2013-05-14 14:11 UTC (permalink / raw)
To: Aurelien Chartier, Konrad Rzeszutek Wilk; +Cc: xen-devel, Ross Philipson
>>> On 14.05.13 at 15:40, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Tue, May 14, 2013 at 12:06:16PM +0100, Aurelien Chartier wrote:
>> Hi everybody,
>>
>> We noticed a crash in Linux dom0 early boot sequence when running over
>> tboot and Xen. The issue seemed related with a E820 region that tboot is
>> setting as E820_UNUSABLE. We posted to tboot-devel to understand better
>> what could be the cause of the kernel panic. This thread can be read
>> here :
>>
> http://sourceforge.net/mailarchive/forum.php?thread_name=51852B26.7070406%40c
> itrix.com&forum_name=tboot-devel
>>
>> Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
>> and found what could be the cause of the kernel panic. I am not familiar
>> with that part of Xen, so feel free to correct me.
>>
>> The Xen memory setup code called during early boot is trying to release
>> chunks of memory in xen_set_identity_and_release for non-RAM regions
>> (including E820_UNUSABLE). The xen_set_identity_and_release_chunk
>> function is calling HYPERVISOR_update_va_mapping, which will fail in our
>> case. As tboot marked that region as being unusable, Xen did not map
>> those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
>> Xen code) is returning an error. As the return value of the hypercall
>> is not checked in Linux code, xen_set_identity_and_release_chunk
>> function is carrying on and tries to release the E820_UNUSABLE chunk.
>> This is apparently messing up some Xen internal memory structures,
>> resulting in a kernel crash when Linux is initializing its memory mapping.
>>
>> A possible fix I have tried is to check the return value of
>> HYPERVISOR_update_va_mapping and if encountering an error, exit from
>> xen_set_identity_and_release_chunk. This is fixing the kernel panic, but
>> I am not sure about other implications by that change.
>
> The implications are explained in the git commit that added that:
>
> 83d51ab47
>
> xen/setup: update VA mapping when releasing memory during setup
>
> In xen_memory_setup(), if a page that is being released has a VA
> mapping this must also be updated. Otherwise, the page will be not
> released completely -- it will still be referenced in Xen and won't be
> freed util the mapping is removed and this prevents it from being
> reallocated at a different PFN.
>
> This was already being done for the ISA memory region in
> xen_ident_map_ISA() but on many systems this was omitting a few pages
> as many systems marked a few pages below the ISA memory region as
> reserved in the e820 map.
>
> This fixes errors such as:
>
> (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 2097153 > 2097152
> (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0
> (0 of 17)
>
> So I think it would be OK to continue with the rest of the function, so
> something
> like this:
>
> diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
> index 94eac5c..f07ca54 100644
> --- a/arch/x86/xen/setup.c
> +++ b/arch/x86/xen/setup.c
> @@ -219,9 +219,10 @@ static void __init xen_set_identity_and_release_chunk(
> * to be updated to be 1:1.
> */
> for (pfn = start_pfn; pfn <= max_pfn_mapped && pfn < end_pfn; pfn++)
> - (void)HYPERVISOR_update_va_mapping(
> + if (HYPERVISOR_update_va_mapping(
> (unsigned long)__va(pfn << PAGE_SHIFT),
> - mfn_pte(pfn, PAGE_KERNEL_IO), 0);
> + mfn_pte(pfn, PAGE_KERNEL_IO), 0))
> + break;
>
> if (start_pfn < nr_pages)
> *released += xen_release_chunk(
>
> But that looks like a hack as the issue seems to be with the hypervisor?
>>
>> Any ideas about this issue ?
>
> Fix the bug in the hypervisor?
Without having seen an actual log, this is mostly guessing. My
guessing here is that the kernel is touching an E820_UNUSABLE
page, which the hypervisor rightly rejects (E820_UNUSABLE is
different from there not being any mention of a page in the E820
table - in that case, the page would be assumed to possibly be
an MMIO one, and Xen would generally allow Dom0 to map it).
Jan
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 13:40 ` Konrad Rzeszutek Wilk
2013-05-14 14:11 ` Jan Beulich
@ 2013-05-14 14:12 ` Aurelien Chartier
1 sibling, 0 replies; 14+ messages in thread
From: Aurelien Chartier @ 2013-05-14 14:12 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Ross Philipson
On 14/05/13 14:40, Konrad Rzeszutek Wilk wrote:
> On Tue, May 14, 2013 at 12:06:16PM +0100, Aurelien Chartier wrote:
>> Hi everybody,
>>
>> We noticed a crash in Linux dom0 early boot sequence when running over
>> tboot and Xen. The issue seemed related with a E820 region that tboot is
>> setting as E820_UNUSABLE. We posted to tboot-devel to understand better
>> what could be the cause of the kernel panic. This thread can be read
>> here :
>> http://sourceforge.net/mailarchive/forum.php?thread_name=51852B26.7070406%40citrix.com&forum_name=tboot-devel
>>
>> Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
>> and found what could be the cause of the kernel panic. I am not familiar
>> with that part of Xen, so feel free to correct me.
>>
>> The Xen memory setup code called during early boot is trying to release
>> chunks of memory in xen_set_identity_and_release for non-RAM regions
>> (including E820_UNUSABLE). The xen_set_identity_and_release_chunk
>> function is calling HYPERVISOR_update_va_mapping, which will fail in our
>> case. As tboot marked that region as being unusable, Xen did not map
>> those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
>> Xen code) is returning an error. As the return value of the hypercall
>> is not checked in Linux code, xen_set_identity_and_release_chunk
>> function is carrying on and tries to release the E820_UNUSABLE chunk.
>> This is apparently messing up some Xen internal memory structures,
>> resulting in a kernel crash when Linux is initializing its memory mapping.
>>
>> A possible fix I have tried is to check the return value of
>> HYPERVISOR_update_va_mapping and if encountering an error, exit from
>> xen_set_identity_and_release_chunk. This is fixing the kernel panic, but
>> I am not sure about other implications by that change.
> The implications are explained in the git commit that added that:
>
> 83d51ab47
>
> xen/setup: update VA mapping when releasing memory during setup
>
> In xen_memory_setup(), if a page that is being released has a VA
> mapping this must also be updated. Otherwise, the page will be not
> released completely -- it will still be referenced in Xen and won't be
> freed util the mapping is removed and this prevents it from being
> reallocated at a different PFN.
>
> This was already being done for the ISA memory region in
> xen_ident_map_ISA() but on many systems this was omitting a few pages
> as many systems marked a few pages below the ISA memory region as
> reserved in the e820 map.
>
> This fixes errors such as:
>
> (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 2097153 > 2097152
> (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 17)
>
> So I think it would be OK to continue with the rest of the function, so something
> like this:
>
> diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
> index 94eac5c..f07ca54 100644
> --- a/arch/x86/xen/setup.c
> +++ b/arch/x86/xen/setup.c
> @@ -219,9 +219,10 @@ static void __init xen_set_identity_and_release_chunk(
> * to be updated to be 1:1.
> */
> for (pfn = start_pfn; pfn <= max_pfn_mapped && pfn < end_pfn; pfn++)
> - (void)HYPERVISOR_update_va_mapping(
> + if (HYPERVISOR_update_va_mapping(
> (unsigned long)__va(pfn << PAGE_SHIFT),
> - mfn_pte(pfn, PAGE_KERNEL_IO), 0);
> + mfn_pte(pfn, PAGE_KERNEL_IO), 0))
> + break;
>
> if (start_pfn < nr_pages)
> *released += xen_release_chunk(
>
> But that looks like a hack as the issue seems to be with the hypervisor?
The issue is triggered by the call to xen_release_chunk, not the
update_va_mapping hypercall. So, I was using a return rather than a break.
This is probably a hack, I just mentioned it to stress the fact that the
kernel crash was caused by the call to xen_release_chunk (and the
decrease_reservation hypercall to Xen I assume).
>> Any ideas about this issue ?
> Fix the bug in the hypervisor?
>
I was wondering how much xen_release_chunk was relying on the fact that
the previous hypercalls have succeeded. If I understood it correctly,
this is not the case, so there may be a way to make the rest of the code
more robust.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 13:53 ` David Vrabel
@ 2013-05-14 14:33 ` Aurelien Chartier
2013-05-14 14:46 ` Jan Beulich
0 siblings, 1 reply; 14+ messages in thread
From: Aurelien Chartier @ 2013-05-14 14:33 UTC (permalink / raw)
To: David Vrabel; +Cc: xen-devel, Ross Philipson, konrad.wilk
On 14/05/13 14:53, David Vrabel wrote:
> On 14/05/13 12:06, Aurelien Chartier wrote:
>> Hi everybody,
>>
>> We noticed a crash in Linux dom0 early boot sequence when running over
>> tboot and Xen. The issue seemed related with a E820 region that tboot is
>> setting as E820_UNUSABLE. We posted to tboot-devel to understand better
>> what could be the cause of the kernel panic. This thread can be read
>> here :
>> http://sourceforge.net/mailarchive/forum.php?thread_name=51852B26.7070406%40citrix.com&forum_name=tboot-devel
>>
>> Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
>> and found what could be the cause of the kernel panic. I am not familiar
>> with that part of Xen, so feel free to correct me.
>>
>> The Xen memory setup code called during early boot is trying to release
>> chunks of memory in xen_set_identity_and_release for non-RAM regions
>> (including E820_UNUSABLE). The xen_set_identity_and_release_chunk
>> function is calling HYPERVISOR_update_va_mapping, which will fail in our
>> case. As tboot marked that region as being unusable, Xen did not map
>> those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
>> Xen code) is returning an error. As the return value of the hypercall
>> is not checked in Linux code, xen_set_identity_and_release_chunk
>> function is carrying on and tries to release the E820_UNUSABLE chunk.
>> This is apparently messing up some Xen internal memory structures,
>> resulting in a kernel crash when Linux is initializing its memory mapping.
> That does not sound quite right to me. xen_set_identity_and_release()
> is releasing RAM pfns that overlap with holes in the machine memory map
> and get_page_from_l1e() should always succeed. The fact that they're
> overlapping with something marked as UNUSABLE shouldn't matter since its
> no different from any other of the holes.
get_page_from_l1e() is failing as the call to
page_get_owner_and_reference() is returning NULL. This was caused by
page->count_info being equal to 0, which means the page has not been
allocated, according to the comment in that function. I assume this page
has not been allocated because it is located in a region marked as
E820_UNUSABLE by tboot.
>
> Is tboot causing Xen to do something weird like leaving holes in dom0's
> initial memory allocation?
Yes, there are pfns linked to pages that are not allocated.
The E820 map seen by Xen is :
(XEN) Multiboot-e820 RAM map:
(XEN) 0000000000000000 - 0000000000060000 (usable)
(XEN) 0000000000060000 - 0000000000068000 (reserved)
(XEN) 0000000000068000 - 0000000000091800 (usable)
(XEN) 0000000000091800 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000000800000 (usable)
(XEN) 0000000000800000 - 0000000000975000 (unusable)
(XEN) 0000000000975000 - 0000000020000000 (usable)
(XEN) 0000000020000000 - 0000000020200000 (reserved)
(XEN) 0000000020200000 - 0000000040004000 (usable)
(XEN) 0000000040004000 - 0000000040005000 (reserved)
(XEN) 0000000040005000 - 0000000060000000 (usable)
(XEN) 0000000060000000 - 0000000060200000 (reserved)
(XEN) 0000000060200000 - 00000000c5e00000 (usable)
(XEN) 00000000c5e00000 - 00000000c86f8000 (reserved)
(XEN) 00000000c86f8000 - 00000000c8800000 (ACPI NVS)
(XEN) 00000000c8800000 - 00000000ca3c5000 (reserved)
(XEN) 00000000ca3c5000 - 00000000ca408000 (ACPI NVS)
(XEN) 00000000ca408000 - 00000000cac00000 (reserved)
(XEN) 00000000caf00000 - 00000000cb000000 (reserved)
(XEN) 00000000cb800000 - 00000000cfa00000 (reserved)
(XEN) 00000000f8000000 - 00000000fc000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed00000 - 00000000fed04000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed30000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000012e600000 (usable)
The region 0000000000975000 - 0000000020000000 has been set to unusable
by tboot.
Calls to update_va_mapping show the following error messages (with mfn
going from 800 to 974):
(XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from L1
entry 000
0000000800463 for l1e_owner=0, pg_owner=0
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 14:33 ` Aurelien Chartier
@ 2013-05-14 14:46 ` Jan Beulich
2013-05-14 15:14 ` Aurelien Chartier
2013-05-14 16:49 ` David Vrabel
0 siblings, 2 replies; 14+ messages in thread
From: Jan Beulich @ 2013-05-14 14:46 UTC (permalink / raw)
To: Aurelien Chartier, David Vrabel; +Cc: xen-devel, Ross Philipson, konrad.wilk
>>> On 14.05.13 at 16:33, Aurelien Chartier <aurelien.chartier@citrix.com> wrote:
With
> (XEN) 0000000000100000 - 0000000000800000 (usable)
> (XEN) 0000000000800000 - 0000000000975000 (unusable)
> (XEN) 0000000000975000 - 0000000020000000 (usable)
>...
> The region 0000000000975000 - 0000000020000000 has been set to unusable
> by tboot.
... you certainly mean the range 800000-975000.
> Calls to update_va_mapping show the following error messages (with mfn
> going from 800 to 974):
>
> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from L1
> entry 0000000000800463 for l1e_owner=0, pg_owner=0
Yes, the kernel has no business mapping that region, and the
hypervisor rightly refuses the attempt.
Jan
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 14:46 ` Jan Beulich
@ 2013-05-14 15:14 ` Aurelien Chartier
2013-05-14 16:49 ` David Vrabel
1 sibling, 0 replies; 14+ messages in thread
From: Aurelien Chartier @ 2013-05-14 15:14 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel, David Vrabel, Ross Philipson, konrad.wilk
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On 14/05/13 15:46, Jan Beulich wrote:
>>>> On 14.05.13 at 16:33, Aurelien Chartier <aurelien.chartier@citrix.com> wrote:
> With
>
>> (XEN) 0000000000100000 - 0000000000800000 (usable)
>> (XEN) 0000000000800000 - 0000000000975000 (unusable)
>> (XEN) 0000000000975000 - 0000000020000000 (usable)
>> ...
>> The region 0000000000975000 - 0000000020000000 has been set to unusable
>> by tboot.
> ... you certainly mean the range 800000-975000.
Oops, wrong copy/paste. You got that right.
>
>> Calls to update_va_mapping show the following error messages (with mfn
>> going from 800 to 974):
>>
>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from L1
>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
> Yes, the kernel has no business mapping that region, and the
> hypervisor rightly refuses the attempt.
I attached a log of the kernel panic with Xen 4.1.3 and Linux 3.8.10.
Thanks,
Aurelien
[-- Attachment #2: tboot-xen-e820-kernel-panic --]
[-- Type: text/plain, Size: 95832 bytes --]
TBOOT: ******************* TBOOT *******************
TBOOT: 2012-01-15 23:30 +0800 1.7.0
TBOOT: *********************************************
TBOOT: command line: min_ram=0x2000000 ehci_handoff=true loglvl=all serial=11520
0/921600,8n1,magic logging=serial,memory bypass_inv_err=1
TBOOT: ehci: Found pci device 0000:1a.0, bar0:f7e38000 addr:68
TBOOT: ehci: handoff
TBOOT: ehci: Found pci device 0000:1d.0, bar0:f7e37000 addr:68
TBOOT: ehci: handoff
TBOOT: BSP is cpu 0
TBOOT: original e820 map:
TBOOT: 0000000000000000 - 0000000000091800 (1)
TBOOT: 0000000000091800 - 00000000000a0000 (2)
TBOOT: 00000000000e0000 - 0000000000100000 (2)
TBOOT: 0000000000100000 - 0000000020000000 (1)
TBOOT: 0000000020000000 - 0000000020200000 (2)
TBOOT: 0000000020200000 - 0000000040004000 (1)
TBOOT: 0000000040004000 - 0000000040005000 (2)
TBOOT: 0000000040005000 - 00000000c5f0a000 (1)
TBOOT: 00000000c5f0a000 - 00000000c6000000 (2)
TBOOT: 00000000c6000000 - 00000000c6753000 (1)
TBOOT: 00000000c6753000 - 00000000c6800000 (2)
TBOOT: 00000000c6800000 - 00000000c6fb2000 (1)
TBOOT: 00000000c6fb2000 - 00000000c7000000 (2)
TBOOT: 00000000c7000000 - 00000000c86f8000 (1)
TBOOT: 00000000c86f8000 - 00000000c8800000 (4)
TBOOT: 00000000c8800000 - 00000000c99f5000 (1)
TBOOT: 00000000c99f5000 - 00000000ca3c5000 (2)
TBOOT: 00000000ca3c5000 - 00000000ca408000 (4)
TBOOT: 00000000ca408000 - 00000000ca6cf000 (1)
TBOOT: 00000000ca6cf000 - 00000000cabf0000 (2)
TBOOT: 00000000cabf0000 - 00000000cac00000 (1)
TBOOT: 00000000cb800000 - 00000000cfa00000 (2)
TBOOT: 00000000f8000000 - 00000000fc000000 (2)
TBOOT: 00000000fec00000 - 00000000fec01000 (2)
TBOOT: 00000000fed00000 - 00000000fed04000 (2)
TBOOT: 00000000fed1c000 - 00000000fed20000 (2)
TBOOT: 00000000fee00000 - 00000000fee01000 (2)
TBOOT: 00000000ff000000 - 0000000100000000 (2)
TBOOT: 0000000100000000 - 000000012e600000 (1)
TBOOT: TPM is ready
TBOOT: TPM nv_locked: TRUE
TBOOT: TPM timeout values: A: 10, B: 10, C: 10, D: 10
TBOOT: Wrong timeout A, fallback to 750
TBOOT: Wrong timeout B, fallback to 2000
TBOOT: Wrong timeout C, fallback to 750
TBOOT: Wrong timeout D, fallback to 750
TBOOT: reading Verified Launch Policy from TPM NV...
TBOOT: TPM: get capability, return value = 00000002
TBOOT: TPM: fail to get public data of 0x20000001 in TPM NV
TBOOT: :reading failed
TBOOT: reading Launch Control Policy from TPM NV...
TBOOT: TPM: get capability, return value = 00000002
TBOOT: TPM: fail to get public data of 0x40000001 in TPM NV
TBOOT: :reading failed
TBOOT: failed to read policy from TPM NV, using default
TBOOT: policy:
TBOOT: version: 2
TBOOT: policy_type: TB_POLTYPE_WARN_ON_FAILURE
TBOOT: hash_alg: TB_HALG_SHA1
TBOOT: policy_control: 00000001 (EXTEND_PCR17)
TBOOT: num_entries: 2
TBOOT: policy entry[0]:
TBOOT: mod_num: 0
TBOOT: pcr: none
TBOOT: hash_type: TB_HTYPE_ANY
TBOOT: num_hashes: 0
TBOOT: policy entry[1]:
TBOOT: mod_num: any
TBOOT: pcr: 19
TBOOT: hash_type: TB_HTYPE_ANY
TBOOT: num_hashes: 0
TBOOT: no policy in TPM NV.
TBOOT: IA32_FEATURE_CONTROL_MSR: 0000ff07
TBOOT: CPU is SMX-capable
TBOOT: CPU is VMX-capable
TBOOT: SMX is enabled
TBOOT: LT.ESTS: 0x0
TBOOT: LT.E2STS: 0x0
TBOOT: TXT chipset and all needed capabilities present
TBOOT: TPM: read nv index 20000002 offset 00000000, return value = 00000002
TBOOT: Error: read TPM error: 0x2.
TBOOT: TXT.ERRORCODE: 0x0
TBOOT: TXT.HEAP.BASE: 0xcaf20000
TBOOT: TXT.HEAP.SIZE: 0xe0000 (917504)
TBOOT: bios_data (@0xcaf20008, 0x56):
TBOOT: version: 4
TBOOT: bios_sinit_size: 0x0 (0)
TBOOT: lcp_pd_base: 0x0
TBOOT: lcp_pd_size: 0x0 (0)
TBOOT: num_logical_procs: 8
TBOOT: flags: 0x00000000
TBOOT: ext_data_elts[]:
TBOOT: BIOS_SPEC_VER:
TBOOT: major: 0x2
TBOOT: minor: 0x1
TBOOT: rev: 0x0
TBOOT: ACM:
TBOOT: num_acms: 1
TBOOT: acm_addrs[0]: 0xffe5f000
TBOOT: CR0 and EFLAGS OK
TBOOT: supports preserving machine check errors
TBOOT: CPU is ready for SENTER
TBOOT: last boot has no error.
TBOOT: checking if module is an SINIT for this platform...
TBOOT: ACM size is too small: acmod_size=2577, acm_hdr->size*4=20
TBOOT: checking if module is an SINIT for this platform...
TBOOT: chipset production fused: 1
TBOOT: chipset ids: vendor: 0x8086, device: 0xb001, revision: 0x1
TBOOT: processor family/model/stepping: 0x306a8
TBOOT: platform id: 0x10000000000000
TBOOT: 1 ACM chipset id entries:
TBOOT: vendor: 0x8086, device: 0xc000, flags: 0x1, revision: 0x3f, extende
d: 0x0
TBOOT: chipset id mismatch
TBOOT: checking if module is an SINIT for this platform...
TBOOT: 1 ACM chipset id entries:
TBOOT: vendor: 0x8086, device: 0xc000, flags: 0x1, revision: 0x7, extended
: 0x0
TBOOT: chipset id mismatch
TBOOT: checking if module is an SINIT for this platform...
TBOOT: 1 ACM chipset id entries:
TBOOT: vendor: 0x8086, device: 0xb001, flags: 0x1, revision: 0x1, extended
: 0x0
TBOOT: 2 ACM processor id entries:
TBOOT: fms: 0x206a0, fms_mask: 0xfff3ff0, platform_id: 0x10000000000000, p
latform_mask: 0x1c000000000000
TBOOT: fms: 0x206a0, fms_mask: 0xfff3ff0, platform_id: 0x4000000000000, pl
atform_mask: 0x1c000000000000
TBOOT: processor mismatch
TBOOT: checking if module is an SINIT for this platform...
TBOOT: 1 ACM chipset id entries:
TBOOT: vendor: 0x8086, device: 0xb001, flags: 0x1, revision: 0x1, extended
: 0x0
TBOOT: 4 ACM processor id entries:
TBOOT: fms: 0x206a0, fms_mask: 0xfff3ff0, platform_id: 0x10000000000000, p
latform_mask: 0x1c000000000000
TBOOT: fms: 0x206a0, fms_mask: 0xfff3ff0, platform_id: 0x4000000000000, pl
atform_mask: 0x1c000000000000
TBOOT: fms: 0x306a0, fms_mask: 0xfff3ff0, platform_id: 0x10000000000000, p
latform_mask: 0x1c000000000000
TBOOT: SINIT matches platform
TBOOT: TXT.SINIT.BASE: 0xcaf00000
TBOOT: TXT.SINIT.SIZE: 0x20000 (131072)
TBOOT: copied SINIT (size=cb40) to 0xcaf00000
TBOOT: AC mod base alignment OK
TBOOT: AC mod size OK
TBOOT: AC module header dump for SINIT:
TBOOT: type: 0x2 (ACM_TYPE_CHIPSET)
TBOOT: subtype: 0x0
TBOOT: length: 0xa1 (161)
TBOOT: version: 0
TBOOT: chipset_id: 0xb001
TBOOT: flags: 0x0
TBOOT: pre_production: 0
TBOOT: debug_signed: 0
TBOOT: vendor: 0x8086
TBOOT: date: 0x20120203
TBOOT: size*4: 0xcb40 (52032)
TBOOT: code_control: 0x0
TBOOT: entry point: 0x00000008:000063bd
TBOOT: scratch_size: 0x8f (143)
TBOOT: info_table:
TBOOT: uuid: {0x7fc03aaa, 0x46a7, 0x18db, 0xac2e,
{0x69, 0x8f, 0x8d, 0x41, 0x7f, 0x5a}}
TBOOT: ACM_UUID_V3
TBOOT: chipset_acm_type: 0x1 (SINIT)
TBOOT: version: 4
TBOOT: length: 0x2c (44)
TBOOT: chipset_id_list: 0x4ec
TBOOT: os_sinit_data_ver: 0x6
TBOOT: min_mle_hdr_ver: 0x00020000
TBOOT: capabilities: 0x0000002e
TBOOT: rlp_wake_getsec: 0
TBOOT: rlp_wake_monitor: 1
TBOOT: ecx_pgtbl: 1
TBOOT: pcr_map_no_legacy: 0
TBOOT: pcr_map_da: 1
TBOOT: acm_ver: 59
TBOOT: chipset list:
TBOOT: count: 1
TBOOT: entry 0:
TBOOT: flags: 0x1
TBOOT: vendor_id: 0x8086
TBOOT: device_id: 0xb001
TBOOT: revision_id: 0x1
TBOOT: extended_id: 0x0
TBOOT: processor list:
TBOOT: count: 4
TBOOT: entry 0:
TBOOT: fms: 0x206a0
TBOOT: fms_mask: 0xfff3ff0
TBOOT: platform_id: 0x10000000000000
TBOOT: platform_mask: 0x1c000000000000
TBOOT: entry 1:
TBOOT: fms: 0x206a0
TBOOT: fms_mask: 0xfff3ff0
TBOOT: platform_id: 0x4000000000000
TBOOT: platform_mask: 0x1c000000000000
TBOOT: entry 2:
TBOOT: fms: 0x306a0
TBOOT: fms_mask: 0xfff3ff0
TBOOT: platform_id: 0x10000000000000
TBOOT: platform_mask: 0x1c000000000000
TBOOT: entry 3:
TBOOT: fms: 0x306a0
TBOOT: fms_mask: 0xfff3ff0
TBOOT: platform_id: 0x4000000000000
TBOOT: platform_mask: 0x1c000000000000
TBOOT: file addresses:
TBOOT: &_start=0x804000
TBOOT: &_end=0x974f90
TBOOT: &_mle_start=0x804000
TBOOT: &_mle_end=0x829000
TBOOT: &_post_launch_entry=0x804010
TBOOT: &_txt_wakeup=0x8041e0
TBOOT: &g_mle_hdr=0x81b740
TBOOT: MLE header:
TBOOT: uuid={0x9082ac5a, 0x476f, 0x74a7, 0x5c0f,
{0x55, 0xa2, 0xcb, 0x51, 0xb6, 0x42}}
TBOOT: length=34
TBOOT: version=00020001
TBOOT: entry_point=00000010
TBOOT: first_valid_page=00000000
TBOOT: mle_start_off=4000
TBOOT: mle_end_off=29000
TBOOT: capabilities: 0x00000027
TBOOT: rlp_wake_getsec: 1
TBOOT: rlp_wake_monitor: 1
TBOOT: ecx_pgtbl: 1
TBOOT: pcr_map_no_legacy: 0
TBOOT: pcr_map_da: 1
TBOOT: MLE start=804000, end=829000, size=25000
TBOOT: ptab_size=3000, ptab_base=0x801000
TBOOT: TXT.HEAP.BASE: 0xcaf20000
TBOOT: TXT.HEAP.SIZE: 0xe0000 (917504)
TBOOT: bios_data (@0xcaf20008, 0x56):
TBOOT: version: 4
TBOOT: bios_sinit_size: 0x0 (0)
TBOOT: lcp_pd_base: 0x0
TBOOT: lcp_pd_size: 0x0 (0)
TBOOT: num_logical_procs: 8
TBOOT: flags: 0x00000000
TBOOT: ext_data_elts[]:
TBOOT: BIOS_SPEC_VER:
TBOOT: major: 0x2
TBOOT: minor: 0x1
TBOOT: rev: 0x0
TBOOT: ACM:
TBOOT: num_acms: 1
TBOOT: acm_addrs[0]: 0xffe5f000
TBOOT: highest min_ram (0x2000000) region found: base=0x60200000, size=0x65d0a00
0
TBOOT: discarding RAM above reserved regions: 0xc6000000 - 0xc6753000
TBOOT: discarding RAM above reserved regions: 0xc6800000 - 0xc6fb2000
TBOOT: discarding RAM above reserved regions: 0xc7000000 - 0xc86f8000
TBOOT: discarding RAM above reserved regions: 0xc8800000 - 0xc99f5000
TBOOT: discarding RAM above reserved regions: 0xca408000 - 0xca6cf000
TBOOT: discarding RAM above reserved regions: 0xcabf0000 - 0xcac00000
TBOOT: min_lo_ram: 0x0, max_lo_ram: 0xc5f0a000
TBOOT: min_hi_ram: 0x100000000, max_hi_ram: 0x12e600000
TBOOT: no LCP module found
TBOOT: os_sinit_data (@0xcaf3117e, 0x7c):
TBOOT: version: 6
TBOOT: mle_ptab: 0x801000
TBOOT: mle_size: 0x25000 (151552)
TBOOT: mle_hdr_base: 0x17740
TBOOT: vtd_pmr_lo_base: 0x0
TBOOT: vtd_pmr_lo_size: 0xc5e00000
TBOOT: vtd_pmr_hi_base: 0x100000000
TBOOT: vtd_pmr_hi_size: 0x2e600000
TBOOT: lcp_po_base: 0x0
TBOOT: lcp_po_size: 0x0 (0)
TBOOT: capabilities: 0x00000002
TBOOT: rlp_wake_getsec: 0
TBOOT: rlp_wake_monitor: 1
TBOOT: ecx_pgtbl: 0
TBOOT: pcr_map_no_legacy: 0
TBOOT: pcr_map_da: 0
TBOOT: efi_rsdt_ptr: 0x0
TBOOT: ext_data_elts[]:
TBOOT: EVENT_LOG_POINTER:
TBOOT: size: 16
TBOOT: elog_addr: 0xcaf30176
TBOOT: Event Log Container:
TBOOT: Signature: TXT Event Container
TBOOT: ContainerVer: 1.0
TBOOT: PCREventVer: 1.0
TBOOT: Size: 4096
TBOOT: EventsOffset: [48,48)
TBOOT: setting MTRRs for acmod: base=0xcaf00000, size=0xcb40, num_pages=13
TBOOT: executing GETSEC[SENTER]...
TBOOT: ******************* TBOOT *******************
TBOOT: 2012-01-15 23:30 +0800 1.7.0
TBOOT: *********************************************
TBOOT: command line: min_ram=0x2000000 ehci_handoff=true loglvl=all serial=11520
0/921600,8n1,magic logging=serial,memory bypass_inv_err=1
TBOOT: ehci: Found pci device 0000:1a.0, bar0:f7e38000 addr:68
TBOOT: ehci: handoff
TBOOT: ehci: Found pci device 0000:1d.0, bar0:f7e37000 addr:68
TBOOT: ehci: handoff
TBOOT: BSP is cpu 0
TBOOT: original e820 map:
TBOOT: 0000000000000000 - 0000000000091800 (1)
TBOOT: 0000000000091800 - 00000000000a0000 (2)
TBOOT: 00000000000e0000 - 0000000000100000 (2)
TBOOT: 0000000000100000 - 0000000020000000 (1)
TBOOT: 0000000020000000 - 0000000020200000 (2)
TBOOT: 0000000020200000 - 0000000040004000 (1)
TBOOT: 0000000040004000 - 0000000040005000 (2)
TBOOT: 0000000040005000 - 00000000c5f0a000 (1)
TBOOT: 00000000c5f0a000 - 00000000c6000000 (2)
TBOOT: 00000000c6000000 - 00000000c6753000 (1)
TBOOT: 00000000c6753000 - 00000000c6800000 (2)
TBOOT: 00000000c6800000 - 00000000c6fb2000 (1)
TBOOT: 00000000c6fb2000 - 00000000c7000000 (2)
TBOOT: 00000000c7000000 - 00000000c86f8000 (1)
TBOOT: 00000000c86f8000 - 00000000c8800000 (4)
TBOOT: 00000000c8800000 - 00000000c99f5000 (1)
TBOOT: 00000000c99f5000 - 00000000ca3c5000 (2)
TBOOT: 00000000ca3c5000 - 00000000ca408000 (4)
TBOOT: 00000000ca408000 - 00000000ca6cf000 (1)
TBOOT: 00000000ca6cf000 - 00000000cabf0000 (2)
TBOOT: 00000000cabf0000 - 00000000cac00000 (1)
TBOOT: 00000000cb800000 - 00000000cfa00000 (2)
TBOOT: 00000000f8000000 - 00000000fc000000 (2)
TBOOT: 00000000fec00000 - 00000000fec01000 (2)
TBOOT: 00000000fed00000 - 00000000fed04000 (2)
TBOOT: 00000000fed1c000 - 00000000fed20000 (2)
TBOOT: 00000000fee00000 - 00000000fee01000 (2)
TBOOT: 00000000ff000000 - 0000000100000000 (2)
TBOOT: 0000000100000000 - 000000012e600000 (1)
TBOOT: TPM is ready
TBOOT: TPM nv_locked: TRUE
TBOOT: TPM timeout values: A: 10, B: 10, C: 10, D: 10
TBOOT: Wrong timeout A, fallback to 750
TBOOT: Wrong timeout B, fallback to 2000
TBOOT: Wrong timeout C, fallback to 750
TBOOT: Wrong timeout D, fallback to 750
TBOOT: reading Verified Launch Policy from TPM NV...
TBOOT: TPM: get capability, return value = 00000002
TBOOT: TPM: fail to get public data of 0x20000001 in TPM NV
TBOOT: :reading failed
TBOOT: reading Launch Control Policy from TPM NV...
TBOOT: TPM: get capability, return value = 00000002
TBOOT: TPM: fail to get public data of 0x40000001 in TPM NV
TBOOT: :reading failed
TBOOT: failed to read policy from TPM NV, using default
TBOOT: policy:
TBOOT: version: 2
TBOOT: policy_type: TB_POLTYPE_WARN_ON_FAILURE
TBOOT: hash_alg: TB_HALG_SHA1
TBOOT: policy_control: 00000001 (EXTEND_PCR17)
TBOOT: num_entries: 2
TBOOT: policy entry[0]:
TBOOT: mod_num: 0
TBOOT: pcr: none
TBOOT: hash_type: TB_HTYPE_ANY
TBOOT: num_hashes: 0
TBOOT: policy entry[1]:
TBOOT: mod_num: any
TBOOT: pcr: 19
TBOOT: hash_type: TB_HTYPE_ANY
TBOOT: num_hashes: 0
TBOOT: no policy in TPM NV.
TBOOT: IA32_FEATURE_CONTROL_MSR: 0000ff07
TBOOT: CPU is SMX-capable
TBOOT: CPU is VMX-capable
TBOOT: SMX is enabled
TBOOT: LT.ESTS: 0x0
TBOOT: LT.E2STS: 0x0
TBOOT: TXT chipset and all needed capabilities present
TBOOT: TPM: read nv index 20000002 offset 00000000, return value = 00000002
TBOOT: Error: read TPM error: 0x2.
TBOOT: TXT.ERRORCODE: 0xc0000001
TBOOT: AC module error :
TBOOT: acm_type: 0x1
TBOOT: progress: 0x00
TBOOT: error: 0x0
TBOOT: TXT.HEAP.BASE: 0xcaf20000
TBOOT: TXT.HEAP.SIZE: 0xe0000 (917504)
TBOOT: bios_data (@0xcaf20008, 0x56):
TBOOT: version: 4
TBOOT: bios_sinit_size: 0x0 (0)
TBOOT: lcp_pd_base: 0x0
TBOOT: lcp_pd_size: 0x0 (0)
TBOOT: num_logical_procs: 8
TBOOT: flags: 0x00000000
TBOOT: ext_data_elts[]:
TBOOT: BIOS_SPEC_VER:
TBOOT: major: 0x2
TBOOT: minor: 0x1
TBOOT: rev: 0x0
TBOOT: ACM:
TBOOT: num_acms: 1
TBOOT: acm_addrs[0]: 0xffe5f000
TBOOT: measured launch succeeded
TBOOT: TXT.HEAP.BASE: 0xcaf20000
TBOOT: TXT.HEAP.SIZE: 0xe0000 (917504)
TBOOT: bios_data (@0xcaf20008, 0x56):
TBOOT: version: 4
TBOOT: bios_sinit_size: 0x0 (0)
TBOOT: lcp_pd_base: 0x0
TBOOT: lcp_pd_size: 0x0 (0)
TBOOT: num_logical_procs: 8
TBOOT: flags: 0x00000000
TBOOT: ext_data_elts[]:
TBOOT: BIOS_SPEC_VER:
TBOOT: major: 0x2
TBOOT: minor: 0x1
TBOOT: rev: 0x0
TBOOT: ACM:
TBOOT: num_acms: 1
TBOOT: acm_addrs[0]: 0xffe5f000
TBOOT: os_mle_data (@0xcaf2005e, 0x11120):
TBOOT: version: 3
TBOOT: mbi: 0x974f90
TBOOT: os_sinit_data (@0xcaf3117e, 0x7c):
TBOOT: version: 6
TBOOT: mle_ptab: 0x801000
TBOOT: mle_size: 0x25000 (151552)
TBOOT: mle_hdr_base: 0x17740
TBOOT: vtd_pmr_lo_base: 0x0
TBOOT: vtd_pmr_lo_size: 0xc5e00000
TBOOT: vtd_pmr_hi_base: 0x100000000
TBOOT: vtd_pmr_hi_size: 0x2e600000
TBOOT: lcp_po_base: 0x0
TBOOT: lcp_po_size: 0x0 (0)
TBOOT: capabilities: 0x00000002
TBOOT: rlp_wake_getsec: 0
TBOOT: rlp_wake_monitor: 1
TBOOT: ecx_pgtbl: 0
TBOOT: pcr_map_no_legacy: 0
TBOOT: pcr_map_da: 0
TBOOT: efi_rsdt_ptr: 0x0
TBOOT: ext_data_elts[]:
TBOOT: EVENT_LOG_POINTER:
TBOOT: size: 16
TBOOT: elog_addr: 0xcaf30176
TBOOT: Event Log Container:
TBOOT: Signature: TXT Event Container
TBOOT: ContainerVer: 1.0
TBOOT: PCREventVer: 1.0
TBOOT: Size: 4096
TBOOT: EventsOffset: [48,296)
TBOOT: Event:
TBOOT: PCRIndex: 17
TBOOT: Type: 0x402
TBOOT: Digest: 8d 3d d5 c8 e7 95 df ac 5d bf a9 85 93 10
b2 bc ea 36 d3 47
TBOOT: Data: 36 bytes
30 ed 7b c9 e1 f3 2a 7e 48 9f bd 15 d8 51 85 f4
ff d8 88 34 a3 10 4d 19 33 43 91 78 3d 55 eb bf
00 00 00 00
TBOOT: Event:
TBOOT: PCRIndex: 255
TBOOT: Type: 0x401
TBOOT: Digest: 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
TBOOT: Data: 4 bytes
00 00 00 00
TBOOT: Event:
TBOOT: PCRIndex: 17
TBOOT: Type: 0x403
TBOOT: Digest: a9 33 34 c9 d5 c6 78 5b 29 bf bb c6 5d a9
4e fd 78 0c e3 a8
TBOOT: Data: 80 bytes
ff ff ff ff 08 11 11 20 01 b0 00 00 00 01 ff ff
ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
TBOOT: Event:
TBOOT: PCRIndex: 18
TBOOT: Type: 0x404
TBOOT: Digest: 23 37 e1 55 ad e5 56 de 86 59 ba 94 2d 29
89 ae 44 c7 54 6d
TBOOT: Data: 0 bytes
TBOOT: sinit_mle_data (@0xcaf311fa, 0x27e):
TBOOT: version: 8
TBOOT: bios_acm_id:
ff ff ff ff 08 11 11 20 01 b0 00 00 00 01 ff ff ff ff ff ff
TBOOT: edx_senter_flags: 0x00000000
TBOOT: mseg_valid: 0x0
TBOOT: sinit_hash:
8d 3d d5 c8 e7 95 df ac 5d bf a9 85 93 10 b2 bc ea 36 d3 47
TBOOT: mle_hash:
23 37 e1 55 ad e5 56 de 86 59 ba 94 2d 29 89 ae 44 c7 54 6d
TBOOT: stm_hash:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
TBOOT: lcp_policy_hash:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
TBOOT: lcp_policy_control: 0x00000000
TBOOT: rlp_wakeup_addr: 0xcaf019c0
TBOOT: num_mdrs: 6
TBOOT: mdrs_off: 0x1ee
TBOOT: num_vtd_dmars: 184
TBOOT: vtd_dmars_off: 0x136
TBOOT: sinit_mdrs:
TBOOT: 0000000000000000 - 00000000000a0000 (GOOD)
TBOOT: 0000000000100000 - 0000000001000000 (GOOD)
TBOOT: 0000000001000000 - 00000000caf00000 (GOOD)
TBOOT: 0000000100000000 - 000000012e600000 (GOOD)
TBOOT: 00000000cb000000 - 00000000cb800000 (SMRAM NON-OVERLAY)
TBOOT: 00000000f8000000 - 00000000fc000000 (PCIE EXTENDED CONFIG)
TBOOT: proc_scrtm_status: 0x00000000
TBOOT: CPU supports 36 phys address bits
TBOOT: RSDP (v2, DELL â‚(âÿÆ$) @ 0x0f0490
TBOOT: acpi_table_ioapic @ 0xc6ffb854, .address = 0xfec00000
TBOOT: acpi_table_mcfg @ 0xc6ffb900, .base_address = 0xf8000000
TBOOT: mtrr_def_type: e = 1, fe = 1, type = 0
TBOOT: mtrrs:
TBOOT: base mask type v
TBOOT: 0000000000000 0000000f00000 06 01
TBOOT: 0000000100000 0000000fe0000 06 01
TBOOT: 0000000120000 0000000ff0000 06 01
TBOOT: 00000000e0000 0000000fe0000 00 01
TBOOT: 00000000d0000 0000000ff0000 00 01
TBOOT: 00000000cc000 0000000ffc000 00 01
TBOOT: 00000000cb800 0000000fff800 00 01
TBOOT: 000000012f000 0000000fff000 00 01
TBOOT: 000000012e800 0000000fff800 00 01
TBOOT: 000000012e600 0000000fffe00 00 01
TBOOT: highest min_ram (0x2000000) region found: base=0x60200000, size=0x65d0a00
0
TBOOT: discarding RAM above reserved regions: 0xc6000000 - 0xc6753000
TBOOT: discarding RAM above reserved regions: 0xc6800000 - 0xc6fb2000
TBOOT: discarding RAM above reserved regions: 0xc7000000 - 0xc86f8000
TBOOT: discarding RAM above reserved regions: 0xc8800000 - 0xc99f5000
TBOOT: discarding RAM above reserved regions: 0xca408000 - 0xca6cf000
TBOOT: discarding RAM above reserved regions: 0xcabf0000 - 0xcac00000
TBOOT: reserving 0xc5e00000 - 0xc5f0a000, which was truncated for VT-d
TBOOT: min_lo_ram: 0x0, max_lo_ram: 0xc5f0a000
TBOOT: min_hi_ram: 0x100000000, max_hi_ram: 0x12e600000
TBOOT: MSR for SMM monitor control on BSP is 0x0.
TBOOT: verifying ILP is opt-out or has the same MSEG header with TXT.MSEG.BASE
opt-out
TBOOT: : succeeded.
TBOOT: enabling SMIs on BSP
TBOOT: mle_join.entry_point = 8041e0
TBOOT: mle_join.seg_sel = 8
TBOOT: mle_join.gdt_base = 805000
TBOOT: mle_join.gdt_limit = 3f
TBOOT: joining RLPs to MLE with MONITOR wakeup
TBOOT: rlp_wakeup_addr = 0xcaf019c0
TBOOT: cpu 3 waking up from TXT sleep
TBOOT: waiting for all APs (7) to enter wait-for-sipi...
TBOOT: MSR for SMM monitor control on cpu 3 is 0x0
TBOOT: verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 3
: succeeded.
TBOOT: enabling SMIs on cpu 3
TBOOT: .VMXON done for cpu 3
TBOOT:
TBOOT: cpu 2 waking up from TXT sleep
TBOOT: launching mini-guest for cpu 3
TBOOT: MSR for SMM monitor control on cpu 2 is 0x0
TBOOT: verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 2
: succeeded.
TBOOT: enabling SMIs on cpu 2
TBOOT: VMXON done for cpu 2
TBOOT: launching mini-guest for cpu 2
TBOOT: cpu 6 waking up from TXT sleep
TBOOT: MSR for SMM monitor control on cpu 6 is 0x0
TBOOT: verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 6
: succeeded.
TBOOT: enabling SMIs on cpu 6
TBOOT: VMXON done for cpu 6
TBOOT: launching mini-guest for cpu 6
TBOOT: cpu 7 waking up from TXT sleep
TBOOT: MSR for SMM monitor control on cpu 7 is 0x0
TBOOT: verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 7
: succeeded.
TBOOT: enabling SMIs on cpu 7
TBOOT: VMXON done for cpu 7
TBOOT: launching mini-guest for cpu 7
TBOOT: cpu 4 waking up from TXT sleep
TBOOT: MSR for SMM monitor control on cpu 4 is 0x0
TBOOT: verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 4
: succeeded.
TBOOT: enabling SMIs on cpu 4
TBOOT: VMXON done for cpu 4
TBOOT: launching mini-guest for cpu 4
TBOOT: cpu 5 waking up from TXT sleep
TBOOT: MSR for SMM monitor control on cpu 5 is 0x0
TBOOT: verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 5
: succeeded.
TBOOT: enabling SMIs on cpu 5
TBOOT: VMXON done for cpu 5
TBOOT: .launching mini-guest for cpu 5
TBOOT: cpu 1 waking up from TXT sleep
TBOOT: MSR for SMM monitor control on cpu 1 is 0x0
TBOOT: .verifying ILP's MSR_IA32_SMM_MONITOR_CTL with cpu 1
. : succeeded.
TBOOT: enabling SMIs on cpu 1
TBOOT: .VMXON done for cpu 1
TBOOT: .launching mini-guest for cpu 1
TBOOT: .
TBOOT: all APs in wait-for-sipi
TBOOT: saved IA32_MISC_ENABLE = 0x00850089
TBOOT: set TXT.CMD.SECRETS flag
TBOOT: opened TPM locality 1
TBOOT: DMAR table @ 0xc6ffd278 saved.
TBOOT: no LCP module found
TBOOT: check for module location adjustments.
TBOOT: (range from 00000000c6801000 to 00000000c69bbaf4 is in E820_RESERVED)
TBOOT: adjust module 0 of mbi (c6801000 - c69bbaf3) in e820 table
module moved from c6801000 to 977000
TBOOT: (range from 00000000c8801000 to 00000000c8bbfd00 is in E820_RESERVED)
TBOOT: adjust module 1 of mbi (c8801000 - c8bbfcff) in e820 table
module moved from c8801000 to b32000
TBOOT: (range from 00000000c7001000 to 00000000c7e3ec00 is in E820_RESERVED)
TBOOT: adjust module 2 of mbi (c7001000 - c7e3ebff) in e820 table
module moved from c7001000 to ef1000
TBOOT: (range from 00000000c600a000 to 00000000c600c577 is in E820_RESERVED)
TBOOT: adjust module 3 of mbi (c600a000 - c600c576) in e820 table
module moved from c600a000 to 1d2f000
TBOOT: verifying module 0 of mbi (977000 - b31af3) in e820 table
(range from 0000000000977000 to 0000000000b31af4 is in E820_RAM)
TBOOT: : succeeded.
TBOOT: verifying module 1 of mbi (b32000 - ef0cff) in e820 table
(range from 0000000000b32000 to 0000000000ef0d00 is in E820_RAM)
TBOOT: : succeeded.
TBOOT: verifying module 2 of mbi (ef1000 - 1d2ebff) in e820 table
(range from 0000000000ef1000 to 0000000001d2ec00 is in E820_RAM)
TBOOT: : succeeded.
TBOOT: verifying module 3 of mbi (1d2f000 - 1d31576) in e820 table
(range from 0000000001d2f000 to 0000000001d31577 is in E820_RAM)
TBOOT: : succeeded.
TBOOT: protecting TXT heap (caf20000 - caffffff) in e820 table
TBOOT: protecting SINIT (caf00000 - caf1ffff) in e820 table
TBOOT: protecting TXT Private Space (fed20000 - fed2ffff) in e820 table
TBOOT: verifying e820 table against SINIT MDRs: verification succeeded.
TBOOT: verifying tboot and its page table (800000 - 974f8f) in e820 table
(range from 0000000000800000 to 0000000000974f90 is in E820_RAM)
TBOOT: : succeeded.
TBOOT: protecting tboot (800000 - 974fff) in e820 table
TBOOT: reserving tboot memory log (60000 - 67fff) in e820 table
TBOOT: adjusted e820 map:
TBOOT: 0000000000000000 - 0000000000060000 (1)
TBOOT: 0000000000060000 - 0000000000068000 (2)
TBOOT: 0000000000068000 - 0000000000091800 (1)
TBOOT: 0000000000091800 - 00000000000a0000 (2)
TBOOT: 00000000000e0000 - 0000000000100000 (2)
TBOOT: 0000000000100000 - 0000000000800000 (1)
TBOOT: 0000000000800000 - 0000000000975000 (5)
TBOOT: 0000000000975000 - 0000000020000000 (1)
TBOOT: 0000000020000000 - 0000000020200000 (2)
TBOOT: 0000000020200000 - 0000000040004000 (1)
TBOOT: 0000000040004000 - 0000000040005000 (2)
TBOOT: 0000000040005000 - 0000000060000000 (1)
TBOOT: 0000000060000000 - 0000000060200000 (2)
TBOOT: 0000000060200000 - 00000000c5e00000 (1)
TBOOT: 00000000c5e00000 - 00000000c5f0a000 (2)
TBOOT: 00000000c5f0a000 - 00000000c6000000 (2)
TBOOT: 00000000c6000000 - 00000000c6753000 (2)
TBOOT: 00000000c6753000 - 00000000c6800000 (2)
TBOOT: 00000000c6800000 - 00000000c6fb2000 (2)
TBOOT: 00000000c6fb2000 - 00000000c7000000 (2)
TBOOT: 00000000c7000000 - 00000000c86f8000 (2)
TBOOT: 00000000c86f8000 - 00000000c8800000 (4)
TBOOT: 00000000c8800000 - 00000000c99f5000 (2)
TBOOT: 00000000c99f5000 - 00000000ca3c5000 (2)
TBOOT: 00000000ca3c5000 - 00000000ca408000 (4)
TBOOT: 00000000ca408000 - 00000000ca6cf000 (2)
TBOOT: 00000000ca6cf000 - 00000000cabf0000 (2)
TBOOT: 00000000cabf0000 - 00000000cac00000 (2)
TBOOT: 00000000caf00000 - 00000000caf20000 (2)
TBOOT: 00000000caf20000 - 00000000cb000000 (2)
TBOOT: 00000000cb800000 - 00000000cfa00000 (2)
TBOOT: 00000000f8000000 - 00000000fc000000 (2)
TBOOT: 00000000fec00000 - 00000000fec01000 (2)
TBOOT: 00000000fed00000 - 00000000fed04000 (2)
TBOOT: 00000000fed1c000 - 00000000fed20000 (2)
TBOOT: 00000000fed20000 - 00000000fed30000 (2)
TBOOT: 00000000fee00000 - 00000000fee01000 (2)
TBOOT: 00000000ff000000 - 0000000100000000 (2)
TBOOT: 0000000100000000 - 000000012e600000 (1)
TBOOT: verifying module "FIXME console=com1 dom0_mem=256M max_dom0_vcpus=1 ioapi
c_ack=old com1=115200/921600,8n1,magic vga=current flask_enforcing=1 sync_consol
e"...
TBOOT: OK : e4 fa 5a d7 2c c0 24 9a da 46 5c b5 75 e7 b2 87 ec c5 4f b1
TBOOT: verifying module "FIXME console=hvc0 root=/dev/mapper/xenclient-root ro b
oot=/dev/mapper/xenclient-boot swiotlb=1M autostart earlyprintk=xen"...
TBOOT: OK : 70 aa 82 3e 5a 16 ed 52 b9 a2 fe 7c 7e b1 5f cc 2a 5d 62 75
TBOOT: verifying module ""...
TBOOT: OK : 82 44 c1 40 6e 43 a8 24 95 ef 35 be ec 01 a3 fb 83 b3 50 e5
TBOOT: verifying module ""...
TBOOT: OK : 60 b4 dd a0 ba 7a 03 b8 06 12 a3 88 1e 6f 91 1a ae 85 4d a3
TBOOT: all modules are verified
TBOOT: pre_k_s3_state:
TBOOT: vtd_pmr_lo_base: 0x0
TBOOT: vtd_pmr_lo_size: 0xc5e00000
TBOOT: vtd_pmr_hi_base: 0x100000000
TBOOT: vtd_pmr_hi_size: 0x2e600000
TBOOT: pol_hash: 19 9b 75 26 9f 9b e6 b9 88 b0 ae 6d 0d bb 3a 45 85 ea 81 df
TBOOT: VL measurements:
TBOOT: PCR 17: a4 7c a5 b2 0f 63 a9 b0 b7 77 6f 69 c3 e9 e4 03 5c cd e9 03
TBOOT: PCR 18: e4 fa 5a d7 2c c0 24 9a da 46 5c b5 75 e7 b2 87 ec c5 4f b1
TBOOT: PCR 19: 70 aa 82 3e 5a 16 ed 52 b9 a2 fe 7c 7e b1 5f cc 2a 5d 62 75
TBOOT: PCR 19: 82 44 c1 40 6e 43 a8 24 95 ef 35 be ec 01 a3 fb 83 b3 50 e5
TBOOT: PCR 19: 60 b4 dd a0 ba 7a 03 b8 06 12 a3 88 1e 6f 91 1a ae 85 4d a3
TBOOT: TPM: start OSAP, return value = 00000012
TBOOT: failed to seal data
TBOOT: PCRs before extending:
TBOOT: PCR 17: fd ae 9b d8 5f 0e 34 9c 5f b2 11 3d 01 cb 90 2f 0d f1 d0 a4
TBOOT: PCR 18: db 82 a1 39 16 5d e7 64 a1 86 91 37 00 12 4c f4 33 64 eb fb
TBOOT: Event:
TBOOT: PCRIndex: 17
TBOOT: Type: 0x501
TBOOT: Digest: a4 7c a5 b2 0f 63 a9 b0 b7 77 6f 69 c3 e9
e4 03 5c cd e9 03
TBOOT: Data: 0 bytes
TBOOT: Event:
TBOOT: PCRIndex: 18
TBOOT: Type: 0x501
TBOOT: Digest: e4 fa 5a d7 2c c0 24 9a da 46 5c b5 75 e7
b2 87 ec c5 4f b1
TBOOT: Data: 0 bytes
TBOOT: Event:
TBOOT: PCRIndex: 19
TBOOT: Type: 0x501
TBOOT: Digest: 70 aa 82 3e 5a 16 ed 52 b9 a2 fe 7c 7e b1
5f cc 2a 5d 62 75
TBOOT: Data: 0 bytes
TBOOT: Event:
TBOOT: PCRIndex: 19
TBOOT: Type: 0x501
TBOOT: Digest: 82 44 c1 40 6e 43 a8 24 95 ef 35 be ec 01
a3 fb 83 b3 50 e5
TBOOT: Data: 0 bytes
TBOOT: Event:
TBOOT: PCRIndex: 19
TBOOT: Type: 0x501
TBOOT: Digest: 60 b4 dd a0 ba 7a 03 b8 06 12 a3 88 1e 6f
91 1a ae 85 4d a3
TBOOT: Data: 0 bytes
TBOOT: PCRs after extending:
TBOOT: PCR 17: 20 63 3f 8e 06 0f 52 a5 4b 49 16 13 4c 40 d2 55 6b 12 53 6d
TBOOT: PCR 18: 2e 9d 94 7a 64 0d 23 43 f4 7b 2f c9 ab 01 7d 42 16 04 20 0f
TBOOT: tboot_shared data:
TBOOT: version: 6
TBOOT: log_addr: 0x00060000
TBOOT: shutdown_entry: 0x008041a0
TBOOT: shutdown_type: 0
TBOOT: tboot_base: 0x00804000
TBOOT: tboot_size: 0x170f90
TBOOT: num_in_wfs: 7
TBOOT: flags: 0x00000000
TBOOT: ap_wake_addr: 0x00000000
TBOOT: ap_wake_trigger: 0
TBOOT: no LCP module found
TBOOT: kernel is ELF format
TBOOT: writing error (0x0) to TXT.ERRORCODE
TBOOT: transfering control to kernel @0x100000...
__ __ _ _ _ _____ _
\ \/ /___ _ __ | || | / | |___ / _ __ ___/ | _ __ _ __ ___ __ _____
\ // _ \ '_ \ | || |_ | | |_ \ __| '__/ __| |__| '_ \| '__/ _ \_\ \/ / __|
/ \ __/ | | | |__ _|| |_ ___) |__| | | (__| |__| |_) | | | __/__> < (__
/_/\_\___|_| |_| |_|(_)_(_)____/ |_| \___|_| | .__/|_| \___| /_/\_\___|
|_|
(XEN) Xen version 4.1.3-rc1-pre-xc (build@cam.xci-test.com) (gcc version 4.4.5 (
Debian 4.4.5-8) ) Mon Mar 18 11:41:35 UTC 2013
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Bootloader: GRUB 1.98
(XEN) Command line: FIXME console=com1 dom0_mem=256M max_dom0_vcpus=1 ioapic_ack
=old com1=115200/921600,8n1,magic vga=current flask_enforcing=1 sync_console tbo
ot=0x82b000
(XEN) Video information:
(XEN) VGA is graphics mode 1024x768, 32 bpp
(XEN) Disc information:
(XEN) Found 0 MBR signatures
(XEN) Found 0 EDD information structures
(XEN) Multiboot-e820 RAM map:
(XEN) 0000000000000000 - 0000000000060000 (usable)
(XEN) 0000000000060000 - 0000000000068000 (reserved)
(XEN) 0000000000068000 - 0000000000091800 (usable)
(XEN) 0000000000091800 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000000800000 (usable)
(XEN) 0000000000800000 - 0000000000975000 (unusable)
(XEN) 0000000000975000 - 0000000020000000 (usable)
(XEN) 0000000020000000 - 0000000020200000 (reserved)
(XEN) 0000000020200000 - 0000000040004000 (usable)
(XEN) 0000000040004000 - 0000000040005000 (reserved)
(XEN) 0000000040005000 - 0000000060000000 (usable)
(XEN) 0000000060000000 - 0000000060200000 (reserved)
(XEN) 0000000060200000 - 00000000c5e00000 (usable)
(XEN) 00000000c5e00000 - 00000000c86f8000 (reserved)
(XEN) 00000000c86f8000 - 00000000c8800000 (ACPI NVS)
(XEN) 00000000c8800000 - 00000000ca3c5000 (reserved)
(XEN) 00000000ca3c5000 - 00000000ca408000 (ACPI NVS)
(XEN) 00000000ca408000 - 00000000cac00000 (reserved)
(XEN) 00000000caf00000 - 00000000cb000000 (reserved)
(XEN) 00000000cb800000 - 00000000cfa00000 (reserved)
(XEN) 00000000f8000000 - 00000000fc000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed00000 - 00000000fed04000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed30000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000012e600000 (usable)
(XEN) ACPI: RSDP 000F0490, 0024 (r2 DELL )
(XEN) ACPI: XSDT C6FF1090, 009C (r1 DELL CBX3 1072009 AMI 10013)
(XEN) ACPI: FACP C6FFB6D8, 010C (r5 DELL CBX3 1072009 AMI 10013)
(XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI 2.0 vers
ion, truncating length 0x10C to 0xF4 [20070126]
(XEN) ACPI: DSDT C6FF11B8, A51C (r2 DELL CBX3 21 INTL 20091112)
(XEN) ACPI: FACS C87ED080, 0040
(XEN) ACPI: APIC C6FFB7E8, 0092 (r3 DELL CBX3 1072009 AMI 10013)
(XEN) ACPI: FPDT C6FFB880, 0044 (r1 DELL CBX3 1072009 AMI 10013)
(XEN) ACPI: TCPA C6FFB8C8, 0032 (r2 APTIO4 NAPAASF 1 MSFT 1000013)
(XEN) ACPI: MCFG C6FFB900, 003C (r1 DELL CBX3 1072009 MSFT 97)
(XEN) ACPI: HPET C6FFB940, 0038 (r1 DELL CBX3 1072009 AMI. 5)
(XEN) ACPI: SSDT C6FFB978, 0415 (r1 SataRe SataTabl 1000 INTL 20091112)
(XEN) ACPI: SSDT C6FFBD90, 09B9 (r1 PmRef Cpu0Ist 3000 INTL 20051117)
(XEN) ACPI: SSDT C6FFC750, 0B22 (r1 PmRef CpuPm 3000 INTL 20051117)
(XEN) ACPI: DMAR C6FFD278, 00B8 (r1 INTEL SNB 1 INTL 1)
(XEN) ACPI: ASF! C6FFD330, 00A5 (r32 INTEL HCG 1 TFSM F4240)
(XEN) ACPI: SSDT C6FFD3D8, 0579 (r1 AMITCG PROC 1 INTL 20051117)
(XEN) ACPI: SLIC C6FFD958, 0176 (r3 DELL CBX3 1072009 MSFT 10013)
(XEN) ACPI: BGRT C6FFDAD0, 0038 (r0
1072009 AMI 10013)
(XEN) ACPI: SSDT C6FFDB08, 198A (r1 NvdRef NvdTabl 1000 INTL 20091112)
(XEN) System RAM: 3902MB (3995724kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000012e600000
(XEN) Domain heap initialised
(XEN) TBOOT: found shared page at phys addr 82b000:
(XEN) version: 6
(XEN) log_addr: 0x00060000
(XEN) shutdown_entry: 0x008041a0
(XEN) tboot_base: 0x00804000
(XEN) tboot_size: 0x170f90
(XEN) found SMP MP-table at 000fda40
(XEN) DMI 2.7 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - c87ed080/0000000000000000, us
ing 32
(XEN) ACPI: wakeup_vec[c87ed08c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
(XEN) Processor #1 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) Processor #3 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
(XEN) Processor #5 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) Processor #7 7:10 APIC version 21
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63
(XEN) PCI: MCFG area at f8000000 reserved in E820
(XEN) Table is not found!
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
(XEN) Not enabling x2APIC: disabled by cmdline.
(XEN) XSM Framework v1.0.0 initialized
(XEN) Policy len 0x2577, start at ffff83012e5fd000.
(XEN) Flask: Initializing.
(XEN) AVC INITIALIZED
(XEN) Flask: 128 avtab hash slots, 264 rules.
(XEN) Flask: 128 avtab hash slots, 264 rules.
(XEN) Flask: 3 users, 5 roles, 55 types, 0 bools
(XEN) Flask: 10 classes, 264 rules
(XEN) Flask: Starting in enforcing mode.
(XEN) Timer firing: normal
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2591.616 MHz processor.
(XEN) Initing memory sharing.
(XEN) mce_intel.c:1162: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extende
d MCE MSR 0
(XEN) CPU0: Thermal monitoring handled by SMI
(XEN) Intel machine check reporting enabled
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
TBOOT: VMXOFF done for cpu 1
TBOOT: cpu 1 waking up, SIPI vector=7c000
(XEN) CPU1: Thermal monitoring handled by SMI
TBOOT: VMXOFF done for cpu 2
TBOOT: cpu 2 waking up, SIPI vector=7c000
(XEN) CPU2: Thermal monitoring handled by SMI
TBOOT: VMXOFF done for cpu 3
TBOOT: cpu 3 waking up, SIPI vector=7c000
(XEN) CPU3: Thermal monitoring handled by SMI
TBOOT: VMXOFF done for cpu 4
TBOOT: cpu 4 waking up, SIPI vector=7c000
(XEN) CPU4: Thermal monitoring handled by SMI
TBOOT: VMXOFF done for cpu 5
TBOOT: cpu 5 waking up, SIPI vector=7c000
(XEN) CPU5: Thermal monitoring handled by SMI
TBOOT: VMXOFF done for cpu 6
TBOOT: cpu 6 waking up, SIPI vector=7c000
(XEN) CPU6: Thermal monitoring handled by SMI
TBOOT: VMXOFF done for cpu 7
TBOOT: cpu 7 waking up, SIPI vector=7c000
(XEN) CPU7: Thermal monitoring handled by SMI
(XEN) Brought up 8 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x659000
(XEN) elf_parse_binary: phdr: paddr=0x1659000 memsz=0x3ab000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x1a04000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc16bd22c
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc1002000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xf5800000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xc0000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xc0000000
(XEN) virt_kstart = 0xc1000000
(XEN) virt_kend = 0xc1a04000
(XEN) virt_entry = 0xc16bd22c
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1a04000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000126000000->0000000128000000 (53698 pages to be allo
cated)
(XEN) Init. ramdisk: 000000012d7bf000->000000012e5fcc00
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: 00000000c1000000->00000000c1a04000
(XEN) Init. ramdisk: 00000000c1a04000->00000000c2841c00
(XEN) Phys-Mach map: 00000000c2842000->00000000c2882000
(XEN) Start info: 00000000c2882000->00000000c28824b4
(XEN) Page tables: 00000000c2883000->00000000c289f000
(XEN) Boot stack: 00000000c289f000->00000000c28a0000
(XEN) TOTAL: 00000000c0000000->00000000c2c00000
(XEN) ENTRY ADDRESS: 00000000c16bd22c
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0x00000000c1000000 -> 0x00000000c1659000
(XEN) elf_load_binary: phdr 1 at 0x00000000c1659000 -> 0x00000000c1736000
(XEN) [VT-D]utils.c:60: Disabled protected memory registers
(XEN) [VT-D]utils.c:60: Disabled protected memory registers
(XEN) Scrubbing Free RAM: ....................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen
)
(XEN) Freed 224kB init memory.
mapping kernel into physical memory
about to get started...
(XEN) mm.c:901:d0 Error getting mfn 800 (pfn 5555555555555555) from L1 entry 000
0000000800463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 801 (pfn 5555555555555555) from L1 entry 000
0000000801463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 802 (pfn 5555555555555555) from L1 entry 000
0000000802463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 803 (pfn 5555555555555555) from L1 entry 000
0000000803463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 804 (pfn 5555555555555555) from L1 entry 000
0000000804463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 805 (pfn 5555555555555555) from L1 entry 000
0000000805463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 806 (pfn 5555555555555555) from L1 entry 000
0000000806463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 807 (pfn 5555555555555555) from L1 entry 000
0000000807463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 808 (pfn 5555555555555555) from L1 entry 000
0000000808463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 809 (pfn 5555555555555555) from L1 entry 000
0000000809463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 80a (pfn 5555555555555555) from L1 entry 000
000000080a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 80b (pfn 5555555555555555) from L1 entry 000
000000080b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 80c (pfn 5555555555555555) from L1 entry 000
000000080c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 80d (pfn 5555555555555555) from L1 entry 000
000000080d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 80e (pfn 5555555555555555) from L1 entry 000
000000080e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 80f (pfn 5555555555555555) from L1 entry 000
000000080f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 810 (pfn 5555555555555555) from L1 entry 000
0000000810463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 811 (pfn 5555555555555555) from L1 entry 000
0000000811463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 812 (pfn 5555555555555555) from L1 entry 000
0000000812463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 813 (pfn 5555555555555555) from L1 entry 000
0000000813463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 814 (pfn 5555555555555555) from L1 entry 000
0000000814463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 815 (pfn 5555555555555555) from L1 entry 000
0000000815463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 816 (pfn 5555555555555555) from L1 entry 000
0000000816463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 817 (pfn 5555555555555555) from L1 entry 000
0000000817463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 818 (pfn 5555555555555555) from L1 entry 000
0000000818463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 819 (pfn 5555555555555555) from L1 entry 000
0000000819463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 81a (pfn 5555555555555555) from L1 entry 000
000000081a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 81b (pfn 5555555555555555) from L1 entry 000
000000081b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 81c (pfn 5555555555555555) from L1 entry 000
000000081c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 81d (pfn 5555555555555555) from L1 entry 000
000000081d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 81e (pfn 5555555555555555) from L1 entry 000
000000081e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 81f (pfn 5555555555555555) from L1 entry 000
000000081f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 820 (pfn 5555555555555555) from L1 entry 000
0000000820463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 821 (pfn 5555555555555555) from L1 entry 000
0000000821463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 822 (pfn 5555555555555555) from L1 entry 000
0000000822463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 823 (pfn 5555555555555555) from L1 entry 000
0000000823463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 824 (pfn 5555555555555555) from L1 entry 000
0000000824463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 825 (pfn 5555555555555555) from L1 entry 000
0000000825463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 826 (pfn 5555555555555555) from L1 entry 000
0000000826463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 827 (pfn 5555555555555555) from L1 entry 000
0000000827463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 828 (pfn 5555555555555555) from L1 entry 000
0000000828463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 829 (pfn 5555555555555555) from L1 entry 000
0000000829463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 82a (pfn 5555555555555555) from L1 entry 000
000000082a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 82b (pfn 5555555555555555) from L1 entry 000
000000082b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 82c (pfn 5555555555555555) from L1 entry 000
000000082c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 82d (pfn 5555555555555555) from L1 entry 000
000000082d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 82e (pfn 5555555555555555) from L1 entry 000
000000082e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 82f (pfn 5555555555555555) from L1 entry 000
000000082f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 830 (pfn 5555555555555555) from L1 entry 000
0000000830463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 831 (pfn 5555555555555555) from L1 entry 000
0000000831463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 832 (pfn 5555555555555555) from L1 entry 000
0000000832463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 833 (pfn 5555555555555555) from L1 entry 000
0000000833463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 834 (pfn 5555555555555555) from L1 entry 000
0000000834463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 835 (pfn 5555555555555555) from L1 entry 000
0000000835463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 836 (pfn 5555555555555555) from L1 entry 000
0000000836463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 837 (pfn 5555555555555555) from L1 entry 000
0000000837463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 838 (pfn 5555555555555555) from L1 entry 000
0000000838463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 839 (pfn 5555555555555555) from L1 entry 000
0000000839463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 83a (pfn 5555555555555555) from L1 entry 000
000000083a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 83b (pfn 5555555555555555) from L1 entry 000
000000083b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 83c (pfn 5555555555555555) from L1 entry 000
000000083c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 83d (pfn 5555555555555555) from L1 entry 000
000000083d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 83e (pfn 5555555555555555) from L1 entry 000
000000083e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 83f (pfn 5555555555555555) from L1 entry 000
000000083f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 840 (pfn 5555555555555555) from L1 entry 000
0000000840463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 841 (pfn 5555555555555555) from L1 entry 000
0000000841463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 842 (pfn 5555555555555555) from L1 entry 000
0000000842463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 843 (pfn 5555555555555555) from L1 entry 000
0000000843463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 844 (pfn 5555555555555555) from L1 entry 000
0000000844463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 845 (pfn 5555555555555555) from L1 entry 000
0000000845463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 846 (pfn 5555555555555555) from L1 entry 000
0000000846463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 847 (pfn 5555555555555555) from L1 entry 000
0000000847463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 848 (pfn 5555555555555555) from L1 entry 000
0000000848463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 849 (pfn 5555555555555555) from L1 entry 000
0000000849463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 84a (pfn 5555555555555555) from L1 entry 000
000000084a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 84b (pfn 5555555555555555) from L1 entry 000
000000084b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 84c (pfn 5555555555555555) from L1 entry 000
000000084c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 84d (pfn 5555555555555555) from L1 entry 000
000000084d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 84e (pfn 5555555555555555) from L1 entry 000
000000084e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 84f (pfn 5555555555555555) from L1 entry 000
000000084f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 850 (pfn 5555555555555555) from L1 entry 000
0000000850463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 851 (pfn 5555555555555555) from L1 entry 000
0000000851463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 852 (pfn 5555555555555555) from L1 entry 000
0000000852463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 853 (pfn 5555555555555555) from L1 entry 000
0000000853463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 854 (pfn 5555555555555555) from L1 entry 000
0000000854463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 855 (pfn 5555555555555555) from L1 entry 000
0000000855463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 856 (pfn 5555555555555555) from L1 entry 000
0000000856463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 857 (pfn 5555555555555555) from L1 entry 000
0000000857463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 858 (pfn 5555555555555555) from L1 entry 000
0000000858463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 859 (pfn 5555555555555555) from L1 entry 000
0000000859463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 85a (pfn 5555555555555555) from L1 entry 000
000000085a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 85b (pfn 5555555555555555) from L1 entry 000
000000085b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 85c (pfn 5555555555555555) from L1 entry 000
000000085c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 85d (pfn 5555555555555555) from L1 entry 000
000000085d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 85e (pfn 5555555555555555) from L1 entry 000
000000085e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 85f (pfn 5555555555555555) from L1 entry 000
000000085f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 860 (pfn 5555555555555555) from L1 entry 000
0000000860463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 861 (pfn 5555555555555555) from L1 entry 000
0000000861463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 862 (pfn 5555555555555555) from L1 entry 000
0000000862463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 863 (pfn 5555555555555555) from L1 entry 000
0000000863463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 864 (pfn 5555555555555555) from L1 entry 000
0000000864463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 865 (pfn 5555555555555555) from L1 entry 000
0000000865463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 866 (pfn 5555555555555555) from L1 entry 000
0000000866463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 867 (pfn 5555555555555555) from L1 entry 000
0000000867463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 868 (pfn 5555555555555555) from L1 entry 000
0000000868463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 869 (pfn 5555555555555555) from L1 entry 000
0000000869463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 86a (pfn 5555555555555555) from L1 entry 000
000000086a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 86b (pfn 5555555555555555) from L1 entry 000
000000086b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 86c (pfn 5555555555555555) from L1 entry 000
000000086c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 86d (pfn 5555555555555555) from L1 entry 000
000000086d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 86e (pfn 5555555555555555) from L1 entry 000
000000086e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 86f (pfn 5555555555555555) from L1 entry 000
000000086f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 870 (pfn 5555555555555555) from L1 entry 000
0000000870463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 871 (pfn 5555555555555555) from L1 entry 000
0000000871463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 872 (pfn 5555555555555555) from L1 entry 000
0000000872463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 873 (pfn 5555555555555555) from L1 entry 000
0000000873463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 874 (pfn 5555555555555555) from L1 entry 000
0000000874463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 875 (pfn 5555555555555555) from L1 entry 000
0000000875463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 876 (pfn 5555555555555555) from L1 entry 000
0000000876463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 877 (pfn 5555555555555555) from L1 entry 000
0000000877463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 878 (pfn 5555555555555555) from L1 entry 000
0000000878463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 879 (pfn 5555555555555555) from L1 entry 000
0000000879463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 87a (pfn 5555555555555555) from L1 entry 000
000000087a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 87b (pfn 5555555555555555) from L1 entry 000
000000087b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 87c (pfn 5555555555555555) from L1 entry 000
000000087c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 87d (pfn 5555555555555555) from L1 entry 000
000000087d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 87e (pfn 5555555555555555) from L1 entry 000
000000087e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 87f (pfn 5555555555555555) from L1 entry 000
000000087f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 880 (pfn 5555555555555555) from L1 entry 000
0000000880463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 881 (pfn 5555555555555555) from L1 entry 000
0000000881463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 882 (pfn 5555555555555555) from L1 entry 000
0000000882463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 883 (pfn 5555555555555555) from L1 entry 000
0000000883463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 884 (pfn 5555555555555555) from L1 entry 000
0000000884463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 885 (pfn 5555555555555555) from L1 entry 000
0000000885463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 886 (pfn 5555555555555555) from L1 entry 000
0000000886463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 887 (pfn 5555555555555555) from L1 entry 000
0000000887463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 888 (pfn 5555555555555555) from L1 entry 000
0000000888463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 889 (pfn 5555555555555555) from L1 entry 000
0000000889463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 88a (pfn 5555555555555555) from L1 entry 000
000000088a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 88b (pfn 5555555555555555) from L1 entry 000
000000088b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 88c (pfn 5555555555555555) from L1 entry 000
000000088c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 88d (pfn 5555555555555555) from L1 entry 000
000000088d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 88e (pfn 5555555555555555) from L1 entry 000
000000088e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 88f (pfn 5555555555555555) from L1 entry 000
000000088f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 890 (pfn 5555555555555555) from L1 entry 000
0000000890463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 891 (pfn 5555555555555555) from L1 entry 000
0000000891463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 892 (pfn 5555555555555555) from L1 entry 000
0000000892463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 893 (pfn 5555555555555555) from L1 entry 000
0000000893463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 894 (pfn 5555555555555555) from L1 entry 000
0000000894463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 895 (pfn 5555555555555555) from L1 entry 000
0000000895463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 896 (pfn 5555555555555555) from L1 entry 000
0000000896463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 897 (pfn 5555555555555555) from L1 entry 000
0000000897463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 898 (pfn 5555555555555555) from L1 entry 000
0000000898463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 899 (pfn 5555555555555555) from L1 entry 000
0000000899463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 89a (pfn 5555555555555555) from L1 entry 000
000000089a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 89b (pfn 5555555555555555) from L1 entry 000
000000089b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 89c (pfn 5555555555555555) from L1 entry 000
000000089c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 89d (pfn 5555555555555555) from L1 entry 000
000000089d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 89e (pfn 5555555555555555) from L1 entry 000
000000089e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 89f (pfn 5555555555555555) from L1 entry 000
000000089f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a0 (pfn 5555555555555555) from L1 entry 000
00000008a0463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a1 (pfn 5555555555555555) from L1 entry 000
00000008a1463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a2 (pfn 5555555555555555) from L1 entry 000
00000008a2463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a3 (pfn 5555555555555555) from L1 entry 000
00000008a3463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a4 (pfn 5555555555555555) from L1 entry 000
00000008a4463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a5 (pfn 5555555555555555) from L1 entry 000
00000008a5463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a6 (pfn 5555555555555555) from L1 entry 000
00000008a6463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a7 (pfn 5555555555555555) from L1 entry 000
00000008a7463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a8 (pfn 5555555555555555) from L1 entry 000
00000008a8463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8a9 (pfn 5555555555555555) from L1 entry 000
00000008a9463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8aa (pfn 5555555555555555) from L1 entry 000
00000008aa463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ab (pfn 5555555555555555) from L1 entry 000
00000008ab463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ac (pfn 5555555555555555) from L1 entry 000
00000008ac463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ad (pfn 5555555555555555) from L1 entry 000
00000008ad463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ae (pfn 5555555555555555) from L1 entry 000
00000008ae463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8af (pfn 5555555555555555) from L1 entry 000
00000008af463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b0 (pfn 5555555555555555) from L1 entry 000
00000008b0463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b1 (pfn 5555555555555555) from L1 entry 000
00000008b1463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b2 (pfn 5555555555555555) from L1 entry 000
00000008b2463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b3 (pfn 5555555555555555) from L1 entry 000
00000008b3463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b4 (pfn 5555555555555555) from L1 entry 000
00000008b4463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b5 (pfn 5555555555555555) from L1 entry 000
00000008b5463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b6 (pfn 5555555555555555) from L1 entry 000
00000008b6463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b7 (pfn 5555555555555555) from L1 entry 000
00000008b7463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b8 (pfn 5555555555555555) from L1 entry 000
00000008b8463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8b9 (pfn 5555555555555555) from L1 entry 000
00000008b9463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ba (pfn 5555555555555555) from L1 entry 000
00000008ba463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8bb (pfn 5555555555555555) from L1 entry 000
00000008bb463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8bc (pfn 5555555555555555) from L1 entry 000
00000008bc463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8bd (pfn 5555555555555555) from L1 entry 000
00000008bd463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8be (pfn 5555555555555555) from L1 entry 000
00000008be463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8bf (pfn 5555555555555555) from L1 entry 000
00000008bf463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c0 (pfn 5555555555555555) from L1 entry 000
00000008c0463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c1 (pfn 5555555555555555) from L1 entry 000
00000008c1463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c2 (pfn 5555555555555555) from L1 entry 000
00000008c2463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c3 (pfn 5555555555555555) from L1 entry 000
00000008c3463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c4 (pfn 5555555555555555) from L1 entry 000
00000008c4463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c5 (pfn 5555555555555555) from L1 entry 000
00000008c5463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c6 (pfn 5555555555555555) from L1 entry 000
00000008c6463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c7 (pfn 5555555555555555) from L1 entry 000
00000008c7463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c8 (pfn 5555555555555555) from L1 entry 000
00000008c8463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8c9 (pfn 5555555555555555) from L1 entry 000
00000008c9463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ca (pfn 5555555555555555) from L1 entry 000
00000008ca463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8cb (pfn 5555555555555555) from L1 entry 000
00000008cb463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8cc (pfn 5555555555555555) from L1 entry 000
00000008cc463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8cd (pfn 5555555555555555) from L1 entry 000
00000008cd463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ce (pfn 5555555555555555) from L1 entry 000
00000008ce463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8cf (pfn 5555555555555555) from L1 entry 000
00000008cf463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d0 (pfn 5555555555555555) from L1 entry 000
00000008d0463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d1 (pfn 5555555555555555) from L1 entry 000
00000008d1463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d2 (pfn 5555555555555555) from L1 entry 000
00000008d2463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d3 (pfn 5555555555555555) from L1 entry 000
00000008d3463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d4 (pfn 5555555555555555) from L1 entry 000
00000008d4463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d5 (pfn 5555555555555555) from L1 entry 000
00000008d5463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d6 (pfn 5555555555555555) from L1 entry 000
00000008d6463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d7 (pfn 5555555555555555) from L1 entry 000
00000008d7463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d8 (pfn 5555555555555555) from L1 entry 000
00000008d8463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8d9 (pfn 5555555555555555) from L1 entry 000
00000008d9463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8da (pfn 5555555555555555) from L1 entry 000
00000008da463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8db (pfn 5555555555555555) from L1 entry 000
00000008db463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8dc (pfn 5555555555555555) from L1 entry 000
00000008dc463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8dd (pfn 5555555555555555) from L1 entry 000
00000008dd463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8de (pfn 5555555555555555) from L1 entry 000
00000008de463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8df (pfn 5555555555555555) from L1 entry 000
00000008df463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e0 (pfn 5555555555555555) from L1 entry 000
00000008e0463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e1 (pfn 5555555555555555) from L1 entry 000
00000008e1463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e2 (pfn 5555555555555555) from L1 entry 000
00000008e2463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e3 (pfn 5555555555555555) from L1 entry 000
00000008e3463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e4 (pfn 5555555555555555) from L1 entry 000
00000008e4463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e5 (pfn 5555555555555555) from L1 entry 000
00000008e5463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e6 (pfn 5555555555555555) from L1 entry 000
00000008e6463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e7 (pfn 5555555555555555) from L1 entry 000
00000008e7463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e8 (pfn 5555555555555555) from L1 entry 000
00000008e8463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8e9 (pfn 5555555555555555) from L1 entry 000
00000008e9463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ea (pfn 5555555555555555) from L1 entry 000
00000008ea463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8eb (pfn 5555555555555555) from L1 entry 000
00000008eb463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ec (pfn 5555555555555555) from L1 entry 000
00000008ec463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ed (pfn 5555555555555555) from L1 entry 000
00000008ed463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ee (pfn 5555555555555555) from L1 entry 000
00000008ee463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ef (pfn 5555555555555555) from L1 entry 000
00000008ef463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f0 (pfn 5555555555555555) from L1 entry 000
00000008f0463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f1 (pfn 5555555555555555) from L1 entry 000
00000008f1463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f2 (pfn 5555555555555555) from L1 entry 000
00000008f2463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f3 (pfn 5555555555555555) from L1 entry 000
00000008f3463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f4 (pfn 5555555555555555) from L1 entry 000
00000008f4463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f5 (pfn 5555555555555555) from L1 entry 000
00000008f5463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f6 (pfn 5555555555555555) from L1 entry 000
00000008f6463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f7 (pfn 5555555555555555) from L1 entry 000
00000008f7463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f8 (pfn 5555555555555555) from L1 entry 000
00000008f8463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8f9 (pfn 5555555555555555) from L1 entry 000
00000008f9463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8fa (pfn 5555555555555555) from L1 entry 000
00000008fa463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8fb (pfn 5555555555555555) from L1 entry 000
00000008fb463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8fc (pfn 5555555555555555) from L1 entry 000
00000008fc463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8fd (pfn 5555555555555555) from L1 entry 000
00000008fd463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8fe (pfn 5555555555555555) from L1 entry 000
00000008fe463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 8ff (pfn 5555555555555555) from L1 entry 000
00000008ff463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 900 (pfn 5555555555555555) from L1 entry 000
0000000900463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 901 (pfn 5555555555555555) from L1 entry 000
0000000901463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 902 (pfn 5555555555555555) from L1 entry 000
0000000902463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 903 (pfn 5555555555555555) from L1 entry 000
0000000903463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 904 (pfn 5555555555555555) from L1 entry 000
0000000904463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 905 (pfn 5555555555555555) from L1 entry 000
0000000905463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 906 (pfn 5555555555555555) from L1 entry 000
0000000906463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 907 (pfn 5555555555555555) from L1 entry 000
0000000907463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 908 (pfn 5555555555555555) from L1 entry 000
0000000908463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 909 (pfn 5555555555555555) from L1 entry 000
0000000909463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 90a (pfn 5555555555555555) from L1 entry 000
000000090a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 90b (pfn 5555555555555555) from L1 entry 000
000000090b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 90c (pfn 5555555555555555) from L1 entry 000
000000090c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 90d (pfn 5555555555555555) from L1 entry 000
000000090d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 90e (pfn 5555555555555555) from L1 entry 000
000000090e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 90f (pfn 5555555555555555) from L1 entry 000
000000090f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 910 (pfn 5555555555555555) from L1 entry 000
0000000910463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 911 (pfn 5555555555555555) from L1 entry 000
0000000911463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 912 (pfn 5555555555555555) from L1 entry 000
0000000912463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 913 (pfn 5555555555555555) from L1 entry 000
0000000913463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 914 (pfn 5555555555555555) from L1 entry 000
0000000914463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 915 (pfn 5555555555555555) from L1 entry 000
0000000915463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 916 (pfn 5555555555555555) from L1 entry 000
0000000916463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 917 (pfn 5555555555555555) from L1 entry 000
0000000917463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 918 (pfn 5555555555555555) from L1 entry 000
0000000918463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 919 (pfn 5555555555555555) from L1 entry 000
0000000919463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 91a (pfn 5555555555555555) from L1 entry 000
000000091a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 91b (pfn 5555555555555555) from L1 entry 000
000000091b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 91c (pfn 5555555555555555) from L1 entry 000
000000091c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 91d (pfn 5555555555555555) from L1 entry 000
000000091d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 91e (pfn 5555555555555555) from L1 entry 000
000000091e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 91f (pfn 5555555555555555) from L1 entry 000
000000091f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 920 (pfn 5555555555555555) from L1 entry 000
0000000920463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 921 (pfn 5555555555555555) from L1 entry 000
0000000921463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 922 (pfn 5555555555555555) from L1 entry 000
0000000922463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 923 (pfn 5555555555555555) from L1 entry 000
0000000923463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 924 (pfn 5555555555555555) from L1 entry 000
0000000924463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 925 (pfn 5555555555555555) from L1 entry 000
0000000925463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 926 (pfn 5555555555555555) from L1 entry 000
0000000926463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 927 (pfn 5555555555555555) from L1 entry 000
0000000927463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 928 (pfn 5555555555555555) from L1 entry 000
0000000928463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 929 (pfn 5555555555555555) from L1 entry 000
0000000929463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 92a (pfn 5555555555555555) from L1 entry 000
000000092a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 92b (pfn 5555555555555555) from L1 entry 000
000000092b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 92c (pfn 5555555555555555) from L1 entry 000
000000092c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 92d (pfn 5555555555555555) from L1 entry 000
000000092d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 92e (pfn 5555555555555555) from L1 entry 000
000000092e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 92f (pfn 5555555555555555) from L1 entry 000
000000092f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 930 (pfn 5555555555555555) from L1 entry 000
0000000930463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 931 (pfn 5555555555555555) from L1 entry 000
0000000931463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 932 (pfn 5555555555555555) from L1 entry 000
0000000932463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 933 (pfn 5555555555555555) from L1 entry 000
0000000933463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 934 (pfn 5555555555555555) from L1 entry 000
0000000934463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 935 (pfn 5555555555555555) from L1 entry 000
0000000935463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 936 (pfn 5555555555555555) from L1 entry 000
0000000936463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 937 (pfn 5555555555555555) from L1 entry 000
0000000937463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 938 (pfn 5555555555555555) from L1 entry 000
0000000938463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 939 (pfn 5555555555555555) from L1 entry 000
0000000939463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 93a (pfn 5555555555555555) from L1 entry 000
000000093a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 93b (pfn 5555555555555555) from L1 entry 000
000000093b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 93c (pfn 5555555555555555) from L1 entry 000
000000093c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 93d (pfn 5555555555555555) from L1 entry 000
000000093d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 93e (pfn 5555555555555555) from L1 entry 000
000000093e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 93f (pfn 5555555555555555) from L1 entry 000
000000093f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 940 (pfn 5555555555555555) from L1 entry 000
0000000940463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 941 (pfn 5555555555555555) from L1 entry 000
0000000941463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 942 (pfn 5555555555555555) from L1 entry 000
0000000942463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 943 (pfn 5555555555555555) from L1 entry 000
0000000943463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 944 (pfn 5555555555555555) from L1 entry 000
0000000944463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 945 (pfn 5555555555555555) from L1 entry 000
0000000945463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 946 (pfn 5555555555555555) from L1 entry 000
0000000946463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 947 (pfn 5555555555555555) from L1 entry 000
0000000947463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 948 (pfn 5555555555555555) from L1 entry 000
0000000948463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 949 (pfn 5555555555555555) from L1 entry 000
0000000949463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 94a (pfn 5555555555555555) from L1 entry 000
000000094a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 94b (pfn 5555555555555555) from L1 entry 000
000000094b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 94c (pfn 5555555555555555) from L1 entry 000
000000094c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 94d (pfn 5555555555555555) from L1 entry 000
000000094d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 94e (pfn 5555555555555555) from L1 entry 000
000000094e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 94f (pfn 5555555555555555) from L1 entry 000
000000094f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 950 (pfn 5555555555555555) from L1 entry 000
0000000950463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 951 (pfn 5555555555555555) from L1 entry 000
0000000951463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 952 (pfn 5555555555555555) from L1 entry 000
0000000952463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 953 (pfn 5555555555555555) from L1 entry 000
0000000953463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 954 (pfn 5555555555555555) from L1 entry 000
0000000954463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 955 (pfn 5555555555555555) from L1 entry 000
0000000955463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 956 (pfn 5555555555555555) from L1 entry 000
0000000956463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 957 (pfn 5555555555555555) from L1 entry 000
0000000957463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 958 (pfn 5555555555555555) from L1 entry 000
0000000958463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 959 (pfn 5555555555555555) from L1 entry 000
0000000959463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 95a (pfn 5555555555555555) from L1 entry 000
000000095a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 95b (pfn 5555555555555555) from L1 entry 000
000000095b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 95c (pfn 5555555555555555) from L1 entry 000
000000095c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 95d (pfn 5555555555555555) from L1 entry 000
000000095d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 95e (pfn 5555555555555555) from L1 entry 000
000000095e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 95f (pfn 5555555555555555) from L1 entry 000
000000095f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 960 (pfn 5555555555555555) from L1 entry 000
0000000960463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 961 (pfn 5555555555555555) from L1 entry 000
0000000961463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 962 (pfn 5555555555555555) from L1 entry 000
0000000962463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 963 (pfn 5555555555555555) from L1 entry 000
0000000963463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 964 (pfn 5555555555555555) from L1 entry 000
0000000964463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 965 (pfn 5555555555555555) from L1 entry 000
0000000965463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 966 (pfn 5555555555555555) from L1 entry 000
0000000966463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 967 (pfn 5555555555555555) from L1 entry 000
0000000967463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 968 (pfn 5555555555555555) from L1 entry 000
0000000968463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 969 (pfn 5555555555555555) from L1 entry 000
0000000969463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 96a (pfn 5555555555555555) from L1 entry 000
000000096a463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 96b (pfn 5555555555555555) from L1 entry 000
000000096b463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 96c (pfn 5555555555555555) from L1 entry 000
000000096c463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 96d (pfn 5555555555555555) from L1 entry 000
000000096d463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 96e (pfn 5555555555555555) from L1 entry 000
000000096e463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 96f (pfn 5555555555555555) from L1 entry 000
000000096f463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 970 (pfn 5555555555555555) from L1 entry 000
0000000970463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 971 (pfn 5555555555555555) from L1 entry 000
0000000971463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 972 (pfn 5555555555555555) from L1 entry 000
0000000972463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 973 (pfn 5555555555555555) from L1 entry 000
0000000973463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:901:d0 Error getting mfn 974 (pfn 5555555555555555) from L1 entry 000
0000000974463 for l1e_owner=0, pg_owner=0
[ 0.000000] Reserving virtual address space above 0xff800000
[ 0.000000] Linux version 3.8.10 (build@scratch) (gcc version 4.6.4 20120303
(prerelease) (GCC) ) #1 SMP Wed May 1 18:12:53 UTC 2013
[ 0.000000] Freeing 60-68 pfn range: 8 pages freed
[ 0.000000] Freeing 91-100 pfn range: 111 pages freed
[ 0.000000] Freeing 800-975 pfn range: 373 pages freed
[ 0.000000] Released 492 pages of unused memory
[ 0.000000] Set 239597 page(s) to 1-1 mapping
[ 0.000000] Populating 10000-101ec pfn range: 492 pages added
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] Xen: [mem 0x0000000000000000-0x000000000005ffff] usable
[ 0.000000] Xen: [mem 0x0000000000060000-0x0000000000067fff] reserved
[ 0.000000] Xen: [mem 0x0000000000068000-0x0000000000090fff] usable
[ 0.000000] Xen: [mem 0x0000000000091800-0x00000000000fffff] reserved
[ 0.000000] Xen: [mem 0x0000000000100000-0x00000000007fffff] usable
[ 0.000000] Xen: [mem 0x0000000000800000-0x0000000000974fff] unusable
[ 0.000000] Xen: [mem 0x0000000000975000-0x000000001fffffff] usable
[ 0.000000] Xen: [mem 0x0000000020000000-0x00000000201fffff] reserved
[ 0.000000] Xen: [mem 0x0000000020200000-0x0000000040003fff] usable
[ 0.000000] Xen: [mem 0x0000000040004000-0x0000000040004fff] reserved
[ 0.000000] Xen: [mem 0x0000000040005000-0x000000005fffffff] usable
[ 0.000000] Xen: [mem 0x0000000060000000-0x00000000601fffff] reserved
[ 0.000000] Xen: [mem 0x0000000060200000-0x00000000b1924fff] usable
[ 0.000000] Xen: [mem 0x00000000b1925000-0x00000000c5dfffff] unusable
[ 0.000000] Xen: [mem 0x00000000c5e00000-0x00000000c86f7fff] reserved
[ 0.000000] Xen: [mem 0x00000000c86f8000-0x00000000c87fffff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000c8800000-0x00000000ca3c4fff] reserved
[ 0.000000] Xen: [mem 0x00000000ca3c5000-0x00000000ca407fff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000ca408000-0x00000000cabfffff] reserved
[ 0.000000] Xen: [mem 0x00000000caf00000-0x00000000caffffff] unusable
[ 0.000000] Xen: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
[ 0.000000] Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] Xen: [mem 0x00000000fed20000-0x00000000fed2ffff] unusable
[ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] Xen: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] Xen: [mem 0x0000000100000000-0x000000012e5fffff] unusable
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] e820: last_pfn = 0xb1925 max_arch_pfn = 0x1000000
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x373fdfff]
(XEN) mm.c:901:d0 Error getting mfn 26800 (pfn 5555555555555555) from L1 entry 0
000000026800023 for l1e_owner=0, pg_owner=0
(XEN) mm.c:4971:d0 ptwr_emulate: fixing up invalid PAE PTE 0000000026800023
(XEN) mm.c:901:d0 Error getting mfn 800 (pfn 5555555555555555) from L1 entry 000
0000000800403 for l1e_owner=0, pg_owner=0
(XEN) mm.c:4976:d0 ptwr_emulate: could not get_page_from_l1e()
[ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 0.000000] IP: [<c16c0e77>] xen_set_pte_init+0x38/0x3d
[ 0.000000] *pdpt = 0000000000000000 *pde = c7959eb61908bedc
[ 0.000000] Oops: 0003 [#1] SMP
[ 0.000000] Modules linked in:
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.8.10 #1 Dell Inc. Latitude E6
530/07Y85M
[ 0.000000] EIP: e019:[<c16c0e77>] EFLAGS: 00010006 CPU: 0
[ 0.000000] EIP is at xen_set_pte_init+0x38/0x3d
[ 0.000000] EAX: 00800403 EBX: c0800000 ECX: 00800403 EDX: 00000000
[ 0.000000] ESI: c2889000 EDI: 00000800 EBP: c165bddc ESP: c165bdd8
[ 0.000000] DS: e021 ES: e021 FS: 00d8 GS: 0000 SS: e021
[ 0.000000] CR0: 80050033 CR2: 00000000 CR3: 01739000 CR4: 00002660
[ 0.000000] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 0.000000] DR6: 00000000 DR7: 00000000
[ 0.000000] Process swapper (pid: 0, ti=c165a000 task=c1667120 task.ti=c165a0
00)
[ 0.000000] Stack:
[ 0.000000] 00000000 c165bde4 c146a29b c165be30 c16d05b8 00000801 c2889000 0
0000000
[ 0.000000] c17b7020 00000004 000373fe 00000000 00800000 c1739018 00000003 0
0000001
[ 0.000000] 00000000 c1739018 00000003 c165be70 00000001 00000001 c165be8c c
145c4a8
[ 0.000000] Call Trace:
[ 0.000000] [<c146a29b>] set_pte+0x14/0x16
[ 0.000000] [<c16d05b8>] kernel_physical_mapping_init+0x19b/0x262
[ 0.000000] [<c145c4a8>] init_memory_mapping+0x1d8/0x510
[ 0.000000] [<c16c3127>] setup_arch+0x726/0xcba
[ 0.000000] [<c100993e>] ? __raw_callee_save_xen_restore_fl+0x6/0x8
[ 0.000000] [<c1009938>] ? __raw_callee_save_xen_save_fl+0x8/0x8
[ 0.000000] [<c1048d27>] ? vprintk_emit+0x217/0x4b0
[ 0.000000] [<c146b1b2>] ? printk+0x38/0x3a
[ 0.000000] [<c16bd6e5>] start_kernel+0x75/0x2e8
[ 0.000000] [<c16bd2d8>] i386_start_kernel+0x9b/0xa2
[ 0.000000] [<c16c02f9>] xen_start_kernel+0x60b/0x616
[ 0.000000] Code: 89 da 25 00 f0 ff ff 81 e2 ff 0f 00 00 0f ac d0 0c 40 74 0f
8b 06 a8 01 74 0d 83 c8 fd 21 c8 89 c1 eb 04 31 c9 31 db 89 5e 04 5b <89> 0e 5e
5d c3 55 89 e5 50 e8 61 fb 00 00 e8 26 40 94 ff a1 04
[ 0.000000] EIP: [<c16c0e77>] xen_set_pte_init+0x38/0x3d SS:ESP e021:c165bdd8
[ 0.000000] CR2: 0000000000000000
[ 0.000000] ---[ end trace b8b520ee82628943 ]---
[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
TBOOT: wait until all APs ready for txt shutdown
TBOOT: cap'ed dynamic PCRs
TBOOT: waiting for APs (0) to exit guests...
TBOOT: .
TBOOT:
TBOOT: all APs exited guests
TBOOT: secrets flag cleared
TBOOT: memory configuration unlocked
TBOOT: private config space closed
TBOOT: executing GETSEC[SEXIT]...
TBOOT: measured environment torn down
TBOOT: shutdown_system() called for shutdown_type: TB_SHUTDOWN_REBOOT
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 14:46 ` Jan Beulich
2013-05-14 15:14 ` Aurelien Chartier
@ 2013-05-14 16:49 ` David Vrabel
2013-05-14 17:02 ` Konrad Rzeszutek Wilk
2013-05-15 7:08 ` Jan Beulich
1 sibling, 2 replies; 14+ messages in thread
From: David Vrabel @ 2013-05-14 16:49 UTC (permalink / raw)
To: Jan Beulich
Cc: xen-devel, Aurelien Chartier, David Vrabel, Ross Philipson, konrad.wilk
On 14/05/13 15:46, Jan Beulich wrote:
>>>> On 14.05.13 at 16:33, Aurelien Chartier <aurelien.chartier@citrix.com> wrote:
>
> With
>
>> (XEN) 0000000000100000 - 0000000000800000 (usable)
>> (XEN) 0000000000800000 - 0000000000975000 (unusable)
>> (XEN) 0000000000975000 - 0000000020000000 (usable)
>> ...
>> The region 0000000000975000 - 0000000020000000 has been set to unusable
>> by tboot.
>
> ... you certainly mean the range 800000-975000.
>
>> Calls to update_va_mapping show the following error messages (with mfn
>> going from 800 to 974):
>>
>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from L1
>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
>
> Yes, the kernel has no business mapping that region, and the
> hypervisor rightly refuses the attempt.
Ok, so this is Xen checking the new PTE supplied in the
update_va_mapping hypercall and saying no.
I think there are two things the kernel can do here.
a) Change the type of UNUSABLE regions to RAM.
b) Release pages overlapping UNUSABLE regions, destroy their mapping and
clear/invalidate the region in the p2m.
Option a) is probably the easiest.
David
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 16:49 ` David Vrabel
@ 2013-05-14 17:02 ` Konrad Rzeszutek Wilk
2013-05-14 17:16 ` David Vrabel
2013-05-15 7:08 ` Jan Beulich
1 sibling, 1 reply; 14+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-14 17:02 UTC (permalink / raw)
To: David Vrabel, Jan Beulich; +Cc: Aurelien Chartier, xen-devel, Ross Philipson
David Vrabel <david.vrabel@citrix.com> wrote:
>On 14/05/13 15:46, Jan Beulich wrote:
>>>>> On 14.05.13 at 16:33, Aurelien Chartier
><aurelien.chartier@citrix.com> wrote:
>>
>> With
>>
>>> (XEN) 0000000000100000 - 0000000000800000 (usable)
>>> (XEN) 0000000000800000 - 0000000000975000 (unusable)
>>> (XEN) 0000000000975000 - 0000000020000000 (usable)
>>> ...
>>> The region 0000000000975000 - 0000000020000000 has been set to
>unusable
>>> by tboot.
>>
>> ... you certainly mean the range 800000-975000.
>>
>>> Calls to update_va_mapping show the following error messages (with
>mfn
>>> going from 800 to 974):
>>>
>>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from
>L1
>>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
>>
>> Yes, the kernel has no business mapping that region, and the
>> hypervisor rightly refuses the attempt.
>
>Ok, so this is Xen checking the new PTE supplied in the
>update_va_mapping hypercall and saying no.
>
>I think there are two things the kernel can do here.
>
>a) Change the type of UNUSABLE regions to RAM.
>
>b) Release pages overlapping UNUSABLE regions, destroy their mapping
>and
>clear/invalidate the region in the p2m.
>
>Option a) is probably the easiest.
>
>David
But option b) seems the proper one.
--
Sent from my Android phone. Please excuse my brevity.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 17:02 ` Konrad Rzeszutek Wilk
@ 2013-05-14 17:16 ` David Vrabel
2013-05-14 17:47 ` Konrad Rzeszutek Wilk
2013-05-15 8:28 ` Jan Beulich
0 siblings, 2 replies; 14+ messages in thread
From: David Vrabel @ 2013-05-14 17:16 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: Aurelien Chartier, xen-devel, Jan Beulich, Ross Philipson
On 14/05/13 18:02, Konrad Rzeszutek Wilk wrote:
> David Vrabel <david.vrabel@citrix.com> wrote:
>
>> On 14/05/13 15:46, Jan Beulich wrote:
>>>>>> On 14.05.13 at 16:33, Aurelien Chartier
>> <aurelien.chartier@citrix.com> wrote:
>>>
>>> With
>>>
>>>> (XEN) 0000000000100000 - 0000000000800000 (usable)
>>>> (XEN) 0000000000800000 - 0000000000975000 (unusable)
>>>> (XEN) 0000000000975000 - 0000000020000000 (usable)
>>>> ...
>>>> The region 0000000000975000 - 0000000020000000 has been set to
>> unusable
>>>> by tboot.
>>>
>>> ... you certainly mean the range 800000-975000.
>>>
>>>> Calls to update_va_mapping show the following error messages (with
>> mfn
>>>> going from 800 to 974):
>>>>
>>>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from
>> L1
>>>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
>>>
>>> Yes, the kernel has no business mapping that region, and the
>>> hypervisor rightly refuses the attempt.
>>
>> Ok, so this is Xen checking the new PTE supplied in the
>> update_va_mapping hypercall and saying no.
>>
>> I think there are two things the kernel can do here.
>>
>> a) Change the type of UNUSABLE regions to RAM.
>>
>> b) Release pages overlapping UNUSABLE regions, destroy their mapping
>> and
>> clear/invalidate the region in the p2m.
>>
>> Option a) is probably the easiest.
>>
>> David
>
> But option b) seems the proper one.
Well... The pfns currently overlapping the machine's UNUSABLE region
are usable RAM and nothing else is the kernel will want to access any
machine address within this region (and evidently can't, even if it
wanted to!).
If it helps, think of it as dom0 taking the pseudo-physical memory map
and putting holes in it to corresponding to interesting bits of the
machine memory map. UNUSABLE regions aren't interesting so we don't
make holes for them.
David
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 17:16 ` David Vrabel
@ 2013-05-14 17:47 ` Konrad Rzeszutek Wilk
2013-05-15 8:28 ` Jan Beulich
1 sibling, 0 replies; 14+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-14 17:47 UTC (permalink / raw)
To: David Vrabel; +Cc: Aurelien Chartier, xen-devel, Jan Beulich, Ross Philipson
On Tue, May 14, 2013 at 06:16:27PM +0100, David Vrabel wrote:
> On 14/05/13 18:02, Konrad Rzeszutek Wilk wrote:
> > David Vrabel <david.vrabel@citrix.com> wrote:
> >
> >> On 14/05/13 15:46, Jan Beulich wrote:
> >>>>>> On 14.05.13 at 16:33, Aurelien Chartier
> >> <aurelien.chartier@citrix.com> wrote:
> >>>
> >>> With
> >>>
> >>>> (XEN) 0000000000100000 - 0000000000800000 (usable)
> >>>> (XEN) 0000000000800000 - 0000000000975000 (unusable)
> >>>> (XEN) 0000000000975000 - 0000000020000000 (usable)
> >>>> ...
> >>>> The region 0000000000975000 - 0000000020000000 has been set to
> >> unusable
> >>>> by tboot.
> >>>
> >>> ... you certainly mean the range 800000-975000.
> >>>
> >>>> Calls to update_va_mapping show the following error messages (with
> >> mfn
> >>>> going from 800 to 974):
> >>>>
> >>>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from
> >> L1
> >>>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
> >>>
> >>> Yes, the kernel has no business mapping that region, and the
> >>> hypervisor rightly refuses the attempt.
> >>
> >> Ok, so this is Xen checking the new PTE supplied in the
> >> update_va_mapping hypercall and saying no.
> >>
> >> I think there are two things the kernel can do here.
> >>
> >> a) Change the type of UNUSABLE regions to RAM.
> >>
> >> b) Release pages overlapping UNUSABLE regions, destroy their mapping
> >> and
> >> clear/invalidate the region in the p2m.
> >>
> >> Option a) is probably the easiest.
> >>
> >> David
> >
> > But option b) seems the proper one.
>
> Well... The pfns currently overlapping the machine's UNUSABLE region
> are usable RAM and nothing else is the kernel will want to access any
> machine address within this region (and evidently can't, even if it
> wanted to!).
>
> If it helps, think of it as dom0 taking the pseudo-physical memory map
> and putting holes in it to corresponding to interesting bits of the
> machine memory map. UNUSABLE regions aren't interesting so we don't
> make holes for them.
We do in the Linux's P2M. We mark them as 1:1, meaning that they the
MFNs we get from the P2M should be the PFN value. And the M2P.. well
that looks to be always 55555.
And that logic looks to be same irregardless if the regions are
E820_RESERVED, E820_UNUSABLE or just MMIO gaps. This is looking at
xen_set_identity_and_release which calls the
xen_set_identity_and_release_chunk (which calls set_phys_range_identity
to set the P2M for 1-1 mapping).
I think I am missing something?
Or when you say 'p2m' you are referring to the hypervisor's direct map?
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 16:49 ` David Vrabel
2013-05-14 17:02 ` Konrad Rzeszutek Wilk
@ 2013-05-15 7:08 ` Jan Beulich
1 sibling, 0 replies; 14+ messages in thread
From: Jan Beulich @ 2013-05-15 7:08 UTC (permalink / raw)
To: David Vrabel; +Cc: Aurelien Chartier, xen-devel, Ross Philipson, konrad.wilk
>>> On 14.05.13 at 18:49, David Vrabel <david.vrabel@citrix.com> wrote:
> On 14/05/13 15:46, Jan Beulich wrote:
>>>>> On 14.05.13 at 16:33, Aurelien Chartier <aurelien.chartier@citrix.com> wrote:
>>> Calls to update_va_mapping show the following error messages (with mfn
>>> going from 800 to 974):
>>>
>>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from L1
>>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
>>
>> Yes, the kernel has no business mapping that region, and the
>> hypervisor rightly refuses the attempt.
>
> Ok, so this is Xen checking the new PTE supplied in the
> update_va_mapping hypercall and saying no.
>
> I think there are two things the kernel can do here.
>
> a) Change the type of UNUSABLE regions to RAM.
>
> b) Release pages overlapping UNUSABLE regions, destroy their mapping and
> clear/invalidate the region in the p2m.
>
> Option a) is probably the easiest.
But the wrong one - no matter what the kernel changes the region
type to, Xen will still know it as UNUSABLE, and refuse the
mapping.
Jan
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Kernel panic with tboot E820_UNUSABLE region
2013-05-14 17:16 ` David Vrabel
2013-05-14 17:47 ` Konrad Rzeszutek Wilk
@ 2013-05-15 8:28 ` Jan Beulich
1 sibling, 0 replies; 14+ messages in thread
From: Jan Beulich @ 2013-05-15 8:28 UTC (permalink / raw)
To: David Vrabel
Cc: Konrad Rzeszutek Wilk, Aurelien Chartier, Ross Philipson, xen-devel
>>> On 14.05.13 at 19:16, David Vrabel <david.vrabel@citrix.com> wrote:
> On 14/05/13 18:02, Konrad Rzeszutek Wilk wrote:
>> David Vrabel <david.vrabel@citrix.com> wrote:
>>
>>> On 14/05/13 15:46, Jan Beulich wrote:
>>>>>>> On 14.05.13 at 16:33, Aurelien Chartier
>>> <aurelien.chartier@citrix.com> wrote:
>>>>
>>>> With
>>>>
>>>>> (XEN) 0000000000100000 - 0000000000800000 (usable)
>>>>> (XEN) 0000000000800000 - 0000000000975000 (unusable)
>>>>> (XEN) 0000000000975000 - 0000000020000000 (usable)
>>>>> ...
>>>>> The region 0000000000975000 - 0000000020000000 has been set to
>>> unusable
>>>>> by tboot.
>>>>
>>>> ... you certainly mean the range 800000-975000.
>>>>
>>>>> Calls to update_va_mapping show the following error messages (with
>>> mfn
>>>>> going from 800 to 974):
>>>>>
>>>>> (XEN) mm.c:911:d0 Error getting mfn 800 (pfn 5555555555555555) from
>>> L1
>>>>> entry 0000000000800463 for l1e_owner=0, pg_owner=0
>>>>
>>>> Yes, the kernel has no business mapping that region, and the
>>>> hypervisor rightly refuses the attempt.
>>>
>>> Ok, so this is Xen checking the new PTE supplied in the
>>> update_va_mapping hypercall and saying no.
>>>
>>> I think there are two things the kernel can do here.
>>>
>>> a) Change the type of UNUSABLE regions to RAM.
>>>
>>> b) Release pages overlapping UNUSABLE regions, destroy their mapping
>>> and
>>> clear/invalidate the region in the p2m.
>>>
>>> Option a) is probably the easiest.
>>>
>>> David
>>
>> But option b) seems the proper one.
>
> Well... The pfns currently overlapping the machine's UNUSABLE region
> are usable RAM and nothing else is the kernel will want to access any
> machine address within this region (and evidently can't, even if it
> wanted to!).
>
> If it helps, think of it as dom0 taking the pseudo-physical memory map
> and putting holes in it to corresponding to interesting bits of the
> machine memory map. UNUSABLE regions aren't interesting so we don't
> make holes for them.
But then they must not be 1:1 mapped.
Jan
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2013-05-15 8:28 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-05-14 11:06 Kernel panic with tboot E820_UNUSABLE region Aurelien Chartier
2013-05-14 13:40 ` Konrad Rzeszutek Wilk
2013-05-14 14:11 ` Jan Beulich
2013-05-14 14:12 ` Aurelien Chartier
2013-05-14 13:53 ` David Vrabel
2013-05-14 14:33 ` Aurelien Chartier
2013-05-14 14:46 ` Jan Beulich
2013-05-14 15:14 ` Aurelien Chartier
2013-05-14 16:49 ` David Vrabel
2013-05-14 17:02 ` Konrad Rzeszutek Wilk
2013-05-14 17:16 ` David Vrabel
2013-05-14 17:47 ` Konrad Rzeszutek Wilk
2013-05-15 8:28 ` Jan Beulich
2013-05-15 7:08 ` Jan Beulich
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.