search for: bootmap

...0.000000] DMI not present or invalid. [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-00000001e0000000 [ 0.000000] Bootmem setup node 0 0000000000000000-00000001e0000000 [ 0.000000] NODE_DATA [0000000000001000 - 0000000000005fff] [ 0.000000] bootmap [0000000000008000 - 0000000000043fff] pages 3c [ 0.000000] (7 early reservations) ==> bootmem [0000000000 - 01e0000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [00000...

...otection: active [ 0.000000] RAMDISK: 0164c000 - 02c48000 [ 0.000000] 0MB HIGHMEM available. [ 0.000000] 128MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 08000000 [ 0.000000] low ram: 0 - 08000000 [ 0.000000] node 0 low ram: 00000000 - 08000000 [ 0.000000] node 0 bootmap 00002000 - 00003000 [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0008000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0002c6b000 - 0002c85000] XEN PAGETABLES ==> [0002c6b000 - 0002c85000] [ 0.0...

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...o servers: on the non working DL585: [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000180000000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000180000000 [ 0.000000] NODE_DATA [0000000000008000 - 000000000000ffff] [ 0.000000] bootmap [0000000000010000 - 000000000003ffff] pages 30 [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0180000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [00040de000 - 0004103000] XEN PAGETABLES ==> [000...

...00000] Using node hash shift of 27 [ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000228000000 [ 0.000000] NODE_DATA [0000000000010180 - 000000000001817f] [ 0.000000] bootmap [0000000000019000 - 000000000005dfff] pages 45 [ 0.000000] (12 early reservations) ==> bootmem [0000000000 - 0228000000] [ 0.0[ 0.000000] #1 [001480b000 - 00148b4000] XEN PAGETABLES ==> [001480b000 - 00148b4000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==&g...

...0.000000] RAMDISK: 01e63000 - 058c0000 [    0.000000] No NUMA configuration found [    0.000000] Faking a node at 0000000000000000-0000000080000000 [    0.000000] Initmem setup node 0 0000000000000000-0000000080000000 [    0.000000]   NODE_DATA [0000000001e42880 - 0000000001e5687f] [    0.000000]   bootmap [0000000005cf6000 -  0000000005d05fff] pages 10 [    0.000000] (9/32 early reservations) ==> bootmem [0000000000 - 0080000000] [    0.000000]   #0 [0005cc3000 - 0005cf6000]   XEN PAGETABLES ==> [0005cc3000 - 0005cf6000] [    0.000000]   #1 [0001000000 - 0001e42878]    TEXT DATA BSS ==> [00...

...1 DELL GX240 00000008 ASL 00000061) ACPI: BOOT 000fd678 00028 (v01 DELL GX240 00000008 ASL 00000061) ACPI: Local APIC address 0xfee00000 0MB HIGHMEM available. 511MB LOWMEM available. mapped low ram: 0 - 1ff77000 low ram: 0 - 1ff77000 node 0 low ram: 00000000 - 1ff77000 node 0 bootmap 00002000 - 00005ff0 (9 early reservations) ==> bootmem [0000000000 - 001ff77000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] #2 [0000006000 - 0000007000] TRAMPOLINE...

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here:

...00000000) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] 0MB HIGHMEM available. [ 0.000000] 446MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 1bef0000 [ 0.000000] low ram: 0 - 1bef0000 [ 0.000000] node 0 low ram: 00000000 - 1bef0000 [ 0.000000] node 0 bootmap 00011000 - 000147e0 [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 001bef0000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] [ 0.0...

I''m running the 2.6.31.6 pv_ops dom0 kernel, libvirt 0.7.0 and Xen 3.4.1. When I try connecting to the Xen hypervisor using virsh it gives me a "Connection refused": root@grp-01-23-02:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1020 4 r----- 858.3 root@grp-01-23-02:~# virsh -c

...00097) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] 1167MB HIGHMEM available. [ 0.000000] 719MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 2cffe000 [ 0.000000] low ram: 0 - 2cffe000 [ 0.000000] node 0 low ram: 00000000 - 2cffe000 [ 0.000000] node 0 bootmap 00010000 - 00015a00 [ 0.000000] (10 early reservations) ==> bootmem [0000000000 - 002cffe000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0002ee2000 - 0002eff000] XEN PAGETABLES ==> [0002ee2000 - 0002eff000] [ 0....

...000000) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] 647MB HIGHMEM available. [ 0.000000] 887MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 377fe000 [ 0.000000] low ram: 0 - 377fe000 [ 0.000000] node 0 low ram: 00000000 - 377fe000 [ 0.000000] node 0 bootmap 00011000 - 00017f00 [ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 00377fe000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] [ 0.0...

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

...0.000000] RAMDISK: 1f2f8000 - 1f3efa00 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-000000001f3fd000 [ 0.000000] Bootmem setup node 0 0000000000000000-000000001f3fd000 [ 0.000000] NODE_DATA [0000000000009000 - 000000000000dfff] [ 0.000000] bootmap [000000000000e000 - 0000000000011e7f] pages 4 [ 0.000000] (7 early reservations) ==> bootmem [0000000000 - 001f3fd000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [000000...

...0.000000] RAMDISK: 016fa000 - 03117000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000010000000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000010000000 [ 0.000000] NODE_DATA [000000000006a000 - 0000000000071fff] [ 0.000000] bootmap [0000000000072000 - 0000000000073fff] pages 2 [ 0.000000] (7 early reservations) ==> bootmem [0000000000 - 0010000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [000319a000 - 00031b7000] XEN PAGETABLES ==> [000319...

Hello, I have some diagnostic Info for you. Tried to get xen-4.0.1 working on another node of my cluster. Only difference: Newer revision of the Hardware. Exactly same Software Stack. Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt linux-2.6.32.27 from xen/stable-2.6.32.x Nodes working: HP DL380G5 16GB (Intel X5460) Node not working: HP DL380G6 16GB (Intel X5550) Effect: Xen