| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] boot Xen 4.0
> Linux version 2.6.32.13 (root@xyz) (gcc version 4.1.2 20080704 (Red
> Hat0095800 (usable)
> (XEN) 00000
> 4.1.2-44)) #2 SMP Thu May 20 17:22:39 PDT
> 2010
>
> Xen: 0000000000000000 - 0000000000095800 (usable)
> (XEN) 00000000fed45000 - 0000000100000000 (r
> Xen: 0000000000095800 - 0000000000100000 (reserved)
> (XEN) System RAM: 3033MB (3106320kB)
> Xen: 0000000000100000 - 00000000b5164000 (usable)9010, 0024 (r2
> HPQOEM)
> Xen: 00000000bf7a5800 - 00000000c0000000 (reserved)PQOEM SLIC-WKS
> 20091208 0)
> Xen: 00000000f0000000 - 00000000f8000000 (reserved)
>
> last_pfn = 0xb5164 max_arch_pfn = 0x400000000
> (XEN) ACPI: APIC BF7B8B7C, 01
> x86 PAT enabled: cpu 0, old 0x50100070406, new
> 0x7010600070106
> (XE
> initial memory mapped : 0 - 20000000OEM TYLSBURG 1 0)
> init_memory_mapping: 0000000000000000-00000000b5164000
> (XEN) ACPI: MCFG BF7B8CF3, 003C
> 0000000000 - 00b5164000 page 4k 0)
> kernel direct mapping tables up to b5164000 @ 100000-6ad000ACPI: TCPA
> BF7B8D2F, 0032 (r1 HPQOEM TYLSBURG 1
> RAMDISK: 02768000 - 02c1ec00
> ACPI: FACS 00000000bf7b8800 00040
> ACPI: APIC 00000000bf7b8b7c 00114 (v01 HPQOEM TYLSBURG 00000001 00000000)
> ACPI: ASF! 00000000bf7b8c90 00063 (v32 HPQOEM TYLSBURG 00000001 00000000)
> ACPI: MCFG 00000000bf7b8cf3 0003C (v01 HPQOEM TYLSBURG 00000001 00000000)
> ACPI: TCPA 00000000bf7b8d2f 00032 (v01 HPQOEM TYLSBURG 00000001 00000000)
> ACPI: SLIC 00000000bf7b8d61 00176 (v01 HPQOEM SLIC-WKS 00000001 00000000)
> ACPI: HPET 00000000bf7b8ed7 00038 (v01 HPQOEM TYLSBURG 00000001 00000000)
> ACPI: 00000000bf7b8f0f 001B8 (v01 HPQOEM TYLSBURG 00000001 00000000)
> ACPI: SSDT 00000000bf7c4ee6 011FC (v01 INTEL PPM RCM 80000001 INTL 20061109)
> ACPI: Local APIC address 0xfee00000
> No NUMA configuration found
> Faking a node at 0000000000000000-00000000b5164000
> Bootmem setup node 0 0000000000000000-00000000b5164000
> NODE_DATA [0000000000008000 - 000000000001ffff]
> bootmap [0000000000020000 - 0000000000036a2f] pages 17
> (8 early reservations) ==> bootmem [0000000000 - 00b5164000]
> #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
> #1 [00031c9000 - 00031e6000] XEN PAGETABLES ==> [00031c9000 - 00031e6000]
> #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
> #3 [0001000000 - 0002747680] TEXT DATA BSS ==> [0001000000 - 0002747680]
> #4 [0002768000 - 0002c1ec00] RAMDISK ==> [0002768000 - 0002c1ec00]
> #5 [0002c1f000 - 00031c9000] XEN START INFO ==> [0002c1f000 - 00031c9000]
> #6 [0002748000 - 0002748120] BRK ==> [0002748000 - 0002748120]
> #7 [0000100000 - 000068d000] PGTABLE ==> [0000100000
>
>
This points to the E820 being wacked, but I can't see how that is
possible considering Xen boots. Try forcing your domain to a smaller
memory amount. Use 'dom0_mem=max:1G' in your Xen command line.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home