Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Xen>
  3. Users
Error: "8MB is greater than 0MB limit"
kju at fqdn
May 16, 2005, 2:56 PM
Post #1 of 9 (1192 views)
Permalink
I want to try out Xen, but i can't get it working. All i get is the
error:

(XEN) Initial guest OS requires too much space
(XEN) (8MB is greater than 0MB limit)

I'm using Xen 2.05 (self-built), with a customized xen0 kernel. My kernel does
_not_ use initrd, because i hate initrd. The "0 MB" limit looks suspicious and
is probably the source of my problem. How is it caused?


Here is the complete bootlog:

kernel /xen.gz dom0_mem=128M com1=57600,8n1
[Multiboot-elf, <0x100000:0x3ef5c:0x360a4>, shtab=0x175078, entry=0x100000]
module /vmlinuz-xen0 ro root=/dev/sda3 console=tty1 console=ttyS0,57600
[Multiboot-module @ 0x176000, 0x40919c bytes]

__ __ ____ ___ ____
\ \/ /___ _ __ |___ \ / _ \ | ___|
\ // _ \ '_ \ __) || | | ||___ \
/ \ __/ | | | / __/ | |_| | ___) |
/_/\_\___|_| |_| |_____(_)___(_)____/

http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory

Xen version 2.0.5 (root@keleos.net) (gcc version 3.3.5 (Debian 1:3.3.5-6)) Mon May 16 00:16:42 CEST 2005
Latest ChangeSet: information unavailable

(XEN) Physical RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000001f7f0000 (usable)
(XEN) 000000001f7f0000 - 000000001f7f3000 (ACPI NVS)
(XEN) 000000001f7f3000 - 000000001f800000 (ACPI data)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 503MB (515648kB)
(XEN) Xen heap: 10MB (10780kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Hyper-Threading is disabled
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000f4ed0
(XEN) ACPI: RSDP (v000 VIAP4M ) @ 0x000f6870
(XEN) ACPI: RSDT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f3000
(XEN) ACPI: FADT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f3040
(XEN) ACPI: MADT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f6c80
(XEN) ACPI: DSDT (v001 VIAP4M AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 17 at 0xFEC00000.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Processors: 1
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2404.128 MHz processor.
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Hyper-Threading is disabled
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Error: only one processor found.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2404.1072 MHz.
(XEN) ..... Bus speed is 100.1710 MHz.
(XEN) ..... bus_scale = 0x00006695
(XEN) Time init:
(XEN) .... System Time: 20002419ns
(XEN) .... cpu_freq: 00000000:8F4C17D0
(XEN) .... scale: 00000001:A9EF1633
(XEN) .... Wall Clock: 1116279984s 170000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfb300, last bus=1
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Using IRQ router VIA [1106/3177] at 00:11.0
(XEN) PCI->APIC IRQ transform: (B0,I9,P0) -> 17
(XEN) PCI->APIC IRQ transform: (B0,I17,P0) -> 15
(XEN) PCI->APIC IRQ transform: (B0,I18,P0) -> 23
(XEN) PCI->APIC IRQ transform: (B1,I0,P0) -> 16
(XEN) PCI: Via IRQ fixup for 00:10.1, from 255 to 0
(XEN) PCI: Via IRQ fixup for 00:10.2, from 255 to 0
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found: 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 00c00000->0100919c
(XEN) Initrd image: 00000000->00000000
(XEN) Dom0 alloc.: 01400000->01420000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c053a604
(XEN) Init. ramdisk: c053b000->c053b000
(XEN) Phys-Mach map: c053b000->c053b080
(XEN) Page tables: c053c000->c053f000
(XEN) Start info: c053f000->c0540000
(XEN) Boot stack: c0540000->c0541000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Initial guest OS requires too much space
(XEN) (8MB is greater than 0MB limit)

****************************************
Could not set up DOM0 guest OS
Aieee! CPU0 is toast...
****************************************

Reboot in five seconds...





Regards
Michael

--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
James.Bulpin at cl
May 16, 2005, 3:04 PM
Post #2 of 9 (1169 views)
Permalink
Probably a dom0_mem= problem - see
http://lists.xensource.com/archives/html/xen-users/2005-05/msg00191.html

On Mon, May 16, 2005 9:56 pm, Michael Holzt said:
> I want to try out Xen, but i can't get it working. All i get is the
> error:
>
> (XEN) Initial guest OS requires too much space
> (XEN) (8MB is greater than 0MB limit)
> [snipped]


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
fernando.souto.maior at gmail
May 16, 2005, 3:12 PM
Post #3 of 9 (1176 views)
Permalink
On 5/16/05, Michael Holzt <kju@fqdn.org> wrote:
> I want to try out Xen, but i can't get it working. All i get is the
> error:
>
> (XEN) Initial guest OS requires too much space
> (XEN) (8MB is greater than 0MB limit)
>
> I'm using Xen 2.05 (self-built), with a customized xen0 kernel. My kernel does
> _not_ use initrd, because i hate initrd. The "0 MB" limit looks suspicious and
> is probably the source of my problem. How is it caused?
>
> Here is the complete bootlog:
>
> kernel /xen.gz dom0_mem=128M com1=57600,8n1
> [Multiboot-elf, <0x100000:0x3ef5c:0x360a4>, shtab=0x175078, entry=0x100000]
> module /vmlinuz-xen0 ro root=/dev/sda3 console=tty1 console=ttyS0,57600
> [Multiboot-module @ 0x176000, 0x40919c bytes]
>
> __ __ ____ ___ ____
> \ \/ /___ _ __ |___ \ / _ \ | ___|
> \ // _ \ '_ \ __) || | | ||___ \
> / \ __/ | | | / __/ | |_| | ___) |
> /_/\_\___|_| |_| |_____(_)___(_)____/
>
> http://www.cl.cam.ac.uk/netos/xen
> University of Cambridge Computer Laboratory
>
> Xen version 2.0.5 (root@keleos.net) (gcc version 3.3.5 (Debian 1:3.3.5-6)) Mon May 16 00:16:42 CEST 2005
> Latest ChangeSet: information unavailable
>
> (XEN) Physical RAM map:
> (XEN) 0000000000000000 - 00000000000a0000 (usable)
> (XEN) 00000000000f0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 000000001f7f0000 (usable)
> (XEN) 000000001f7f0000 - 000000001f7f3000 (ACPI NVS)
> (XEN) 000000001f7f3000 - 000000001f800000 (ACPI data)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) System RAM: 503MB (515648kB)
> (XEN) Xen heap: 10MB (10780kB)
> (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
> (XEN) CPU#0: Hyper-Threading is disabled
> (XEN) CPU caps: bfebfbff 00000000 00000000 00000000
> (XEN) found SMP MP-table at 000f4ed0
> (XEN) ACPI: RSDP (v000 VIAP4M ) @ 0x000f6870
> (XEN) ACPI: RSDT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f3000
> (XEN) ACPI: FADT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f3040
> (XEN) ACPI: MADT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f6c80
> (XEN) ACPI: DSDT (v001 VIAP4M AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> (XEN) Using ACPI for processor (LAPIC) configuration information
> (XEN) Intel MultiProcessor Specification v1.4
> (XEN) Virtual Wire compatibility mode.
> (XEN) OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
> (XEN) I/O APIC #2 Version 17 at 0xFEC00000.
> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
> (XEN) Processors: 1
> (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> (XEN) Initializing CPU#0
> (XEN) Detected 2404.128 MHz processor.
> (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
> (XEN) CPU#0: Hyper-Threading is disabled
> (XEN) CPU caps: bfebfbff 00000000 00000000 00000000
> (XEN) CPU0 booted
> (XEN) enabled ExtINT on CPU#0
> (XEN) ESR value before enabling vector: 00000000
> (XEN) ESR value after enabling vector: 00000000
> (XEN) Error: only one processor found.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) Setting 2 in the phys_id_present_map
> (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
> (XEN) init IO_APIC IRQs
> (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
> (XEN) Using local APIC timer interrupts.
> (XEN) Calibrating APIC timer for CPU0...
> (XEN) ..... CPU speed is 2404.1072 MHz.
> (XEN) ..... Bus speed is 100.1710 MHz.
> (XEN) ..... bus_scale = 0x00006695
> (XEN) Time init:
> (XEN) .... System Time: 20002419ns
> (XEN) .... cpu_freq: 00000000:8F4C17D0
> (XEN) .... scale: 00000001:A9EF1633
> (XEN) .... Wall Clock: 1116279984s 170000us
> (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfb300, last bus=1
> (XEN) PCI: Using configuration type 1
> (XEN) PCI: Probing PCI hardware
> (XEN) PCI: Probing PCI hardware (bus 00)
> (XEN) PCI: Using IRQ router VIA [1106/3177] at 00:11.0
> (XEN) PCI->APIC IRQ transform: (B0,I9,P0) -> 17
> (XEN) PCI->APIC IRQ transform: (B0,I17,P0) -> 15
> (XEN) PCI->APIC IRQ transform: (B0,I18,P0) -> 23
> (XEN) PCI->APIC IRQ transform: (B1,I0,P0) -> 16
> (XEN) PCI: Via IRQ fixup for 00:10.1, from 255 to 0
> (XEN) PCI: Via IRQ fixup for 00:10.2, from 255 to 0
> (XEN) mtrr: v2.0 (20020519)
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found: 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) Kernel image: 00c00000->0100919c
> (XEN) Initrd image: 00000000->00000000
> (XEN) Dom0 alloc.: 01400000->01420000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: c0100000->c053a604
> (XEN) Init. ramdisk: c053b000->c053b000
> (XEN) Phys-Mach map: c053b000->c053b080
> (XEN) Page tables: c053c000->c053f000
> (XEN) Start info: c053f000->c0540000
> (XEN) Boot stack: c0540000->c0541000
> (XEN) TOTAL: c0000000->c0800000
> (XEN) ENTRY ADDRESS: c0100000
> (XEN) Initial guest OS requires too much space
> (XEN) (8MB is greater than 0MB limit)
>
> ****************************************
> Could not set up DOM0 guest OS
> Aieee! CPU0 is toast...
> ****************************************
>
> Reboot in five seconds...
>
> Regards
> Michael
>
> --
> It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

Michael,

It is not clear from the documentation that the parameter
dom0_mem must be in kbytes. Actually, if you go to the
docs in the home page, you will see that 128M is OK,
and it is NOT true.

May be that is the source of your problems.

Also, may be it is a good idea to update the docs, online
and in the source/rpm packages...

--
Bye,
Fernando Maior
LPIC/1 31908

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
kju at fqdn
May 16, 2005, 3:16 PM
Post #4 of 9 (1174 views)
Permalink
> Probably a dom0_mem= problem - see
> http://lists.xensource.com/archives/html/xen-users/2005-05/msg00191.html

Thanks to you and Fernando, actually that was really the problem. However it
seems a little bit strange that the User Guide at
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html
gives examples using the "xxxM" notation.

I think a user guide should actually give examples which work.

Gruss
Michael

--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
kju-xen at fqdn
May 16, 2005, 3:19 PM
Post #5 of 9 (1172 views)
Permalink
> Probably a dom0_mem= problem - see
> http://lists.xensource.com/archives/html/xen-users/2005-05/msg00191.html

Thanks to you and Fernando, that was really the problem. However it seems
a little bit strange that the User Guide at
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html
gives examples using the "xxxM" notation.

I think a user guide should actually give examples which work.

Gruss
Michael

--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
RE: Error: "8MB is greater than 0MB limit" [ In reply to ]
m+Ian.Pratt at cl
May 16, 2005, 3:25 PM
Post #6 of 9 (1171 views)
Permalink
> Thanks to you and Fernando, that was really the problem.
> However it seems a little bit strange that the User Guide at
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html
> gives examples using the "xxxM" notation.
>
> I think a user guide should actually give examples which work.

That's the proto 3.0 user manual you're looking at, hence that syntax
works in the unstable tree, but not in 2.0.5. There aren't many user
visible differences between 2.x and 3.x but that's one of them.

Ian

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
kju-xen at fqdn
May 16, 2005, 3:30 PM
Post #7 of 9 (1169 views)
Permalink
> That's the proto 3.0 user manual you're looking at,

Actually that would make sense. However on the top of the page is stated
"Xen v2.0 for x86", and throughout the text a few times "v2.0" of xen is
referenced.



Regards
Michael

--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
mark.williamson at cl
May 16, 2005, 3:31 PM
Post #8 of 9 (1168 views)
Permalink
On Monday 16 May 2005 23:30, Michael Holzt wrote:
> > That's the proto 3.0 user manual you're looking at,
>
> Actually that would make sense. However on the top of the page is stated
> "Xen v2.0 for x86", and throughout the text a few times "v2.0" of xen is
> referenced.

Unfortunately because 3.0 isn't yet releasable, the docs haven't been fully
updated - the syntax described is v3.0 but the version numbers haven't been
updated.

Ian: do you think it would be worth changing the nightly build so that the 2.0
docs are shown on the web? Or provide links to both? I think most people
will be looking for 2.0 docs...

Cheers,
Mark

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Error: "8MB is greater than 0MB limit" [ In reply to ]
Steven.Hand at cl
May 17, 2005, 1:56 AM
Post #9 of 9 (1170 views)
Permalink
>> Probably a dom0_mem= problem - see
>> http://lists.xensource.com/archives/html/xen-users/2005-05/msg00191.html
>
>Thanks to you and Fernando, actually that was really the problem. However it
>seems a little bit strange that the User Guide at
>http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html
>gives examples using the "xxxM" notation.
>
>I think a user guide should actually give examples which work.

The change to the parameter passing for Xen unstable happened very
recently.

Anyway, I've updated the docs (in the repository) to reflect the
differences between 2.x and 3.x -- the nightly build will update
the documentation.

cheers,

S.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal