Lars Rasmusson
2005-Mar-04 22:37 UTC
[Xen-devel] Problems with balloons and HIGHMEM (>896MB)
Hi,
I''m running Xen-2.0.4 on a machine with 2 GB of memory.
I compiled a linux-2.6.10-xenU kernel with HIGHMEM=y
to make it able to use more than 896 MB of memory.
I then created a domain with memory=1024 name=Highmem, and then
did an ''xm balloon 256'', which caused the xenU-kernel to
crash.
# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 123 0 r---- 63.5
Highmem 1 1 1 ----c 5.5 9601
and ''xm destroy Highmem'' does not have any effect.
When I created a domain with memory=800 name=Highmem, and then
did an ''xm balloon 256'', it worked fine.
Am I doing something wrong? Is this a known problem, or
does it work for everybody else?
------------------------------------------------------------
Here is the xend.log (the last four lines keep on being
added infinitly)
[2005-03-04 14:08:55 xend] DEBUG (XendDomainInfo:720) init_domain> Created
domain=1 name=Highmem memory=1024
[2005-03-04 14:08:55 xend] INFO (console:92) Created console id=15 domain=1
port=9601
[2005-03-04 14:08:56 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=1
uname=file:/home/testlars/t1.ext3
[2005-03-04 14:08:56 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 1 0>
[2005-03-04 14:08:56 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=1 vif=0
mac=aa:00:00:0b:c7:5d
[2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> xend.console.create [15,
1, 9601]
[2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> xend.domain.create
[''Highmem'', ''1'']
[2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> xend.domain.unpause
[''Highmem'', ''1'']
[2005-03-04 14:08:57 xend] DEBUG (blkif:201) Connecting blkif to event channel
<BlkifBackendInterface 1 0> ports=16:3
[2005-03-04 14:14:42 xend] DEBUG (XendDomain:244) XendDomain>reap> domain
died name=Highmem id=1
[2005-03-04 14:14:42 xend] INFO (XendDomain:564) Destroying domain: name=Highmem
[2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:665) Destroying vifs for domain
1
[2005-03-04 14:14:42 xend] DEBUG (netif:290) Destroying vif domain=1 vif=0
[2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:674) Destroying vbds for domain
1
[2005-03-04 14:14:42 xend] DEBUG (blkif:550) Destroying blkif domain=1
[2005-03-04 14:14:42 xend] DEBUG (blkif:406) Destroying vbd domain=1 idx=0
[2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:634) Closing console, domain 1
[2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:622) Closing channel to domain
1
[2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.virq 4
[2005-03-04 14:14:45 xend] DEBUG (blkif:361) Unbinding vbd (type file) from
/dev/loop0
[2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
[''Highmem'', ''1'', ''crash'']
[2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
[''Highmem'', ''1'']
[2005-03-04 14:14:47 xend] DEBUG (XendDomain:244) XendDomain>reap> domain
died name=Highmem id=1
[2005-03-04 14:14:47 xend] INFO (XendDomain:564) Destroying domain: name=Highmem
[2005-03-04 14:14:47 xend] DEBUG (XendDomainInfo:634) Closing console, domain 1
[2005-03-04 14:14:47 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
[''Highmem'', ''1'', ''crash'']
[2005-03-04 14:14:47 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
[''Highmem'', ''1'']
[2005-03-04 14:14:49 xend] DEBUG (XendDomain:244) XendDomain>reap> domain
died name=Highmem id=1
[2005-03-04 14:14:49 xend] INFO (XendDomain:564) Destroying domain: name=Highmem
------------------------------------------------------------
Here is ''xm dmesg''
ERROR: cannot use unconfigured serial port COM1
__ __ ____ ___ _ _
\ \/ /___ _ __ |___ \ / _ \| || |
\ // _ \ ''_ \ __) || | | | || |_
/ \ __/ | | | / __/ | |_| |__ _|
/_/\_\___|_| |_| |_____(_)___(_) |_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 2.0.4 (larsr@hpl.hp.com) (gcc version 3.4.2 20041017 (Red Hat
3.4.2-6.fc3)) Fri Feb 25 18:01:50 PST 2005
Latest ChangeSet: information unavailable
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009ec00 (usable)
(XEN) 000000000009ec00 - 00000000000a0000 (reserved)
(XEN) 00000000000e9400 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fff0000 (usable)
(XEN) 000000007fff0000 - 000000007ffffc00 (ACPI data)
(XEN) 000000007ffffc00 - 0000000080000000 (ACPI NVS)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000fff80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096696kB)
(XEN) Xen heap: 10MB (10720kB)
(XEN) CPU0: Before vendor init, caps: 0387fbff 00000000 00000000, vendor = 0
(XEN) CPU caps: 0387fbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000f7570
(XEN) ACPI: RSDP (v000 PTLTD ) @ 0x000f7520
(XEN) ACPI: RSDT (v001 HP HWPC214 0x06040017 PTL 0x00000000) @ 0x7fffc8f7
(XEN) ACPI: FADT (v001 HP HWPC214 0x06040017 PTL 0x00000001) @ 0x7ffffb05
(XEN) ACPI: MADT (v001 PTLTD APIC 0x06040017 LTP 0x00000000) @ 0x7ffffb79
(XEN) ACPI: BOOT (v001 HP HWPC214 0x06040017 PTL 0x00000001) @ 0x7ffffbd9
(XEN) ACPI: DSDT (v001 HP HWPC214 0x06040017 MSFT 0x0100000b) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x03] enabled)
(XEN) Processor #3 Pentium(tm) Pro APIC version 17
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium(tm) Pro APIC version 17
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] 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: HP Product ID: LP 1Kr/2Kr APIC at: 0xFEE00000
(XEN) I/O APIC #1 Version 17 at 0xFEC00000.
(XEN) I/O APIC #2 Version 17 at 0xFEC01000.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Processors: 2
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 1000.129 MHz processor.
(XEN) CPU0: Before vendor init, caps: 0387fbff 00000000 00000000, vendor = 0
(XEN) CPU caps: 0387fbff 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) Booting processor 1/0 eip 90000
(XEN) Initializing CPU#1
(XEN) masked ExtINT on CPU#1
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU1: Before vendor init, caps: 0387fbff 00000000 00000000, vendor = 0
(XEN) CPU caps: 0387fbff 00000000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 1 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 1 ... ok.
(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=-1 pin2=0
(XEN) ...trying to set up timer (IRQ0) through the 8259A ...
(XEN) ..... (found pin 0) ...works.
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 1000.0497 MHz.
(XEN) ..... Bus speed is 133.3398 MHz.
(XEN) ..... bus_scale = 0x0000888D
(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... System Time: 61096354ns
(XEN) .... cpu_freq: 00000000:3B9CC1E8
(XEN) .... scale: 00000001:FFEF1809
(XEN) .... Wall Clock: 1109943491s 200000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfda11, last bus=1
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Discovered primary peer bus 01 [IRQ]
(XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 22
(XEN) PCI->APIC IRQ transform: (B0,I8,P0) -> 23
(XEN) PCI->APIC IRQ transform: (B0,I15,P0) -> 33
(XEN) PCI->APIC IRQ transform: (B1,I3,P0) -> 17
(XEN) PCI->APIC IRQ transform: (B1,I4,P0) -> 27
(XEN) PCI->APIC IRQ transform: (B1,I5,P0) -> 24
(XEN) PCI->APIC IRQ transform: (B1,I5,P1) -> 25
(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->00fbbeb8
(XEN) Initrd image: 00fbc000->01173a00
(XEN) Dom0 alloc.: 01400000->09400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c04ecf04
(XEN) Init. ramdisk: c04ed000->c06a4a00
(XEN) Phys-Mach map: c06a5000->c06c5000
(XEN) Page tables: c06c5000->c06c8000
(XEN) Start info: c06c8000->c06c9000
(XEN) Boot stack: c06c9000->c06ca000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ..done.
(XEN) Initrd len 0x1b7a00, start at 0xc04ed000
(XEN) Scrubbing Free RAM: .....................done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen).
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2005-Mar-05 11:04 UTC
Re: [Xen-devel] Problems with balloons and HIGHMEM (>896MB)
The balloon driver is somewhat broken in current stable. I added some fixes to the testing tree that will be in our forthcoming 2.0.5 release (real soon now) that hopefully fix the bad behaviour. -- Keir On 4 Mar 2005, at 22:37, Lars Rasmusson wrote:> > Hi, > > I''m running Xen-2.0.4 on a machine with 2 GB of memory. > > I compiled a linux-2.6.10-xenU kernel with HIGHMEM=y > to make it able to use more than 896 MB of memory. > > I then created a domain with memory=1024 name=Highmem, and then > did an ''xm balloon 256'', which caused the xenU-kernel to crash. > > # xm list > Name Id Mem(MB) CPU State Time(s) Console > Domain-0 0 123 0 r---- 63.5 > Highmem 1 1 1 ----c 5.5 9601 > > and ''xm destroy Highmem'' does not have any effect. > > When I created a domain with memory=800 name=Highmem, and then > did an ''xm balloon 256'', it worked fine. > > > Am I doing something wrong? Is this a known problem, or > does it work for everybody else? > > > > > > ------------------------------------------------------------ > > Here is the xend.log (the last four lines keep on being > added infinitly) > > [2005-03-04 14:08:55 xend] DEBUG (XendDomainInfo:720) init_domain> > Created domain=1 name=Highmem memory=1024 > [2005-03-04 14:08:55 xend] INFO (console:92) Created console id=15 > domain=1 port=9601 > [2005-03-04 14:08:56 xend] DEBUG (XendDomainInfo:1130) Creating vbd > dom=1 uname=file:/home/testlars/t1.ext3 > [2005-03-04 14:08:56 xend] DEBUG (blkif:155) Connecting blkif > <BlkifBackendInterface 1 0> > [2005-03-04 14:08:56 xend] DEBUG (XendDomainInfo:1107) Creating vif > dom=1 vif=0 mac=aa:00:00:0b:c7:5d > [2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> > xend.console.create [15, 1, 9601] > [2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> > xend.domain.create [''Highmem'', ''1''] > [2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> > xend.domain.unpause [''Highmem'', ''1''] > [2005-03-04 14:08:57 xend] DEBUG (blkif:201) Connecting blkif to event > channel <BlkifBackendInterface 1 0> ports=16:3 > [2005-03-04 14:14:42 xend] DEBUG (XendDomain:244) XendDomain>reap> > domain died name=Highmem id=1 > [2005-03-04 14:14:42 xend] INFO (XendDomain:564) Destroying domain: > name=Highmem > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:665) Destroying vifs > for domain 1 > [2005-03-04 14:14:42 xend] DEBUG (netif:290) Destroying vif domain=1 > vif=0 > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:674) Destroying vbds > for domain 1 > [2005-03-04 14:14:42 xend] DEBUG (blkif:550) Destroying blkif domain=1 > [2005-03-04 14:14:42 xend] DEBUG (blkif:406) Destroying vbd domain=1 > idx=0 > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:634) Closing console, > domain 1 > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:622) Closing channel > to domain 1 > [2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.virq 4 > [2005-03-04 14:14:45 xend] DEBUG (blkif:361) Unbinding vbd (type file) > from /dev/loop0 > [2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.domain.exit > [''Highmem'', ''1'', ''crash''] > [2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> > xend.domain.destroy [''Highmem'', ''1''] > [2005-03-04 14:14:47 xend] DEBUG (XendDomain:244) XendDomain>reap> > domain died name=Highmem id=1 > [2005-03-04 14:14:47 xend] INFO (XendDomain:564) Destroying domain: > name=Highmem > [2005-03-04 14:14:47 xend] DEBUG (XendDomainInfo:634) Closing console, > domain 1 > [2005-03-04 14:14:47 xend] INFO (XendRoot:91) EVENT> xend.domain.exit > [''Highmem'', ''1'', ''crash''] > [2005-03-04 14:14:47 xend] INFO (XendRoot:91) EVENT> > xend.domain.destroy [''Highmem'', ''1''] > [2005-03-04 14:14:49 xend] DEBUG (XendDomain:244) XendDomain>reap> > domain died name=Highmem id=1 > [2005-03-04 14:14:49 xend] INFO (XendDomain:564) Destroying domain: > name=Highmem > > > > ------------------------------------------------------------ > > Here is ''xm dmesg'' > > ERROR: cannot use unconfigured serial port COM1 > __ __ ____ ___ _ _ > \ \/ /___ _ __ |___ \ / _ \| || | > \ // _ \ ''_ \ __) || | | | || |_ > / \ __/ | | | / __/ | |_| |__ _| > /_/\_\___|_| |_| |_____(_)___(_) |_| > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 2.0.4 (larsr@hpl.hp.com) (gcc version 3.4.2 20041017 (Red > Hat 3.4.2-6.fc3)) Fri Feb 25 18:01:50 PST 2005 > Latest ChangeSet: information unavailable > > (XEN) Physical RAM map: > (XEN) 0000000000000000 - 000000000009ec00 (usable) > (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > (XEN) 00000000000e9400 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000007fff0000 (usable) > (XEN) 000000007fff0000 - 000000007ffffc00 (ACPI data) > (XEN) 000000007ffffc00 - 0000000080000000 (ACPI NVS) > (XEN) 00000000fec00000 - 00000000fec10000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000fff80000 - 0000000100000000 (reserved) > (XEN) System RAM: 2047MB (2096696kB) > (XEN) Xen heap: 10MB (10720kB) > (XEN) CPU0: Before vendor init, caps: 0387fbff 00000000 00000000, > vendor = 0 > (XEN) CPU caps: 0387fbff 00000000 00000000 00000000 > (XEN) found SMP MP-table at 000f7570 > (XEN) ACPI: RSDP (v000 PTLTD ) @ > 0x000f7520 > (XEN) ACPI: RSDT (v001 HP HWPC214 0x06040017 PTL 0x00000000) @ > 0x7fffc8f7 > (XEN) ACPI: FADT (v001 HP HWPC214 0x06040017 PTL 0x00000001) @ > 0x7ffffb05 > (XEN) ACPI: MADT (v001 PTLTD APIC 0x06040017 LTP 0x00000000) @ > 0x7ffffb79 > (XEN) ACPI: BOOT (v001 HP HWPC214 0x06040017 PTL 0x00000001) @ > 0x7ffffbd9 > (XEN) ACPI: DSDT (v001 HP HWPC214 0x06040017 MSFT 0x0100000b) @ > 0x00000000 > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x03] enabled) > (XEN) Processor #3 Pentium(tm) Pro APIC version 17 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > (XEN) Processor #0 Pentium(tm) Pro APIC version 17 > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] 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: HP Product ID: LP 1Kr/2Kr APIC at: 0xFEE00000 > (XEN) I/O APIC #1 Version 17 at 0xFEC00000. > (XEN) I/O APIC #2 Version 17 at 0xFEC01000. > (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs > (XEN) Processors: 2 > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > (XEN) Initializing CPU#0 > (XEN) Detected 1000.129 MHz processor. > (XEN) CPU0: Before vendor init, caps: 0387fbff 00000000 00000000, > vendor = 0 > (XEN) CPU caps: 0387fbff 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) Booting processor 1/0 eip 90000 > (XEN) Initializing CPU#1 > (XEN) masked ExtINT on CPU#1 > (XEN) ESR value before enabling vector: 00000000 > (XEN) ESR value after enabling vector: 00000000 > (XEN) CPU1: Before vendor init, caps: 0387fbff 00000000 00000000, > vendor = 0 > (XEN) CPU caps: 0387fbff 00000000 00000000 00000000 > (XEN) CPU1 has booted. > (XEN) Total of 2 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) Setting 1 in the phys_id_present_map > (XEN) ...changing IO-APIC physical APIC ID to 1 ... ok. > (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=-1 pin2=0 > (XEN) ...trying to set up timer (IRQ0) through the 8259A ... > (XEN) ..... (found pin 0) ...works. > (XEN) Using local APIC timer interrupts. > (XEN) Calibrating APIC timer for CPU0... > (XEN) ..... CPU speed is 1000.0497 MHz. > (XEN) ..... Bus speed is 133.3398 MHz. > (XEN) ..... bus_scale = 0x0000888D > (XEN) checking TSC synchronization across CPUs: passed. > (XEN) Time init: > (XEN) .... System Time: 61096354ns > (XEN) .... cpu_freq: 00000000:3B9CC1E8 > (XEN) .... scale: 00000001:FFEF1809 > (XEN) .... Wall Clock: 1109943491s 200000us > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfda11, last bus=1 > (XEN) PCI: Using configuration type 1 > (XEN) PCI: Probing PCI hardware > (XEN) PCI: Probing PCI hardware (bus 00) > (XEN) PCI: Discovered primary peer bus 01 [IRQ] > (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 22 > (XEN) PCI->APIC IRQ transform: (B0,I8,P0) -> 23 > (XEN) PCI->APIC IRQ transform: (B0,I15,P0) -> 33 > (XEN) PCI->APIC IRQ transform: (B1,I3,P0) -> 17 > (XEN) PCI->APIC IRQ transform: (B1,I4,P0) -> 27 > (XEN) PCI->APIC IRQ transform: (B1,I5,P0) -> 24 > (XEN) PCI->APIC IRQ transform: (B1,I5,P1) -> 25 > (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=g > eneric,PT_MODE_WRITABLE'' > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Kernel image: 00c00000->00fbbeb8 > (XEN) Initrd image: 00fbc000->01173a00 > (XEN) Dom0 alloc.: 01400000->09400000 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0100000->c04ecf04 > (XEN) Init. ramdisk: c04ed000->c06a4a00 > (XEN) Phys-Mach map: c06a5000->c06c5000 > (XEN) Page tables: c06c5000->c06c8000 > (XEN) Start info: c06c8000->c06c9000 > (XEN) Boot stack: c06c9000->c06ca000 > (XEN) TOTAL: c0000000->c0800000 > (XEN) ENTRY ADDRESS: c0100000 > (XEN) Scrubbing DOM0 RAM: ..done. > (XEN) Initrd len 0x1b7a00, start at 0xc04ed000 > (XEN) Scrubbing Free RAM: .....................done. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input to Xen). > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Lars Rasmusson
2005-Mar-07 19:11 UTC
Re: [Xen-devel] Problems with balloons and HIGHMEM (>896MB)
Hi, I tried the latest xen-2.0-testing-src.tgz, compiled the user domain with HIGHMEM=y and HIGHMEM4G=y, and the domain 0 with NOHIGHMEM=y, but I got the same error: when I balloon a user domain with more than 896 MB, it crashes and messes up Xen, so unfortunately it does not appear to be fixed by the patches so far... Has anyone else had success with ballooning user domains with HIGHMEM4G=y and memory > 896 MB? The balloning seems to work when the user domain gets less than 896 MB, which perhaps is useful for debugging. It hints that there is some problem with xen and the HIGHMEM4G enabled code in the kernel. The fact that ballooning messes up the domain data for xend is disturbing, since it hints that the problem is not constrained to the user domain, but also outside... Here is the commands I run. See domain t1 with 1024 MB below: # xm create t1.conf memory=1024 # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 66.1 t1 3 1024 1 -b--- 5.0 9603 # xm balloon t1 256 # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 70.0 t1 3 1 1 ----c 5.0 9603 ************ t1 crashed Mem say 1 MB! # xm destroy t1 # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 79.9 t1 3 1 1 ----c 5.0 9603 ************ couldn''t even destroy t1! # xm create t2.conf memory=800 # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 94.9 t1 3 1 1 ----c 5.0 9603 t2 4 800 0 -b--- 3.7 9604 # xm balloon t2 256 # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 97.1 t1 3 1 1 ----c 5.0 9603 t2 4 256 0 -b--- 5.3 9604 *********** t2 seems to work, but it started out with only 800 MB /Lars On Sat, 2005-03-05 at 11:04 +0000, Keir Fraser wrote:> The balloon driver is somewhat broken in current stable. I added some > fixes to the testing tree that will be in our forthcoming 2.0.5 release > (real soon now) that hopefully fix the bad behaviour. > > -- Keir > > On 4 Mar 2005, at 22:37, Lars Rasmusson wrote: > > > > > Hi, > > > > I''m running Xen-2.0.4 on a machine with 2 GB of memory. > > > > I compiled a linux-2.6.10-xenU kernel with HIGHMEM=y > > to make it able to use more than 896 MB of memory. > > > > I then created a domain with memory=1024 name=Highmem, and then > > did an ''xm balloon 256'', which caused the xenU-kernel to crash. > > > > # xm list > > Name Id Mem(MB) CPU State Time(s) Console > > Domain-0 0 123 0 r---- 63.5 > > Highmem 1 1 1 ----c 5.5 9601 > > > > and ''xm destroy Highmem'' does not have any effect. > > > > When I created a domain with memory=800 name=Highmem, and then > > did an ''xm balloon 256'', it worked fine. > > > > > > Am I doing something wrong? Is this a known problem, or > > does it work for everybody else? > > > > > > > > > > > > ------------------------------------------------------------ > > > > Here is the xend.log (the last four lines keep on being > > added infinitly) > > > > [2005-03-04 14:08:55 xend] DEBUG (XendDomainInfo:720) init_domain> > > Created domain=1 name=Highmem memory=1024 > > [2005-03-04 14:08:55 xend] INFO (console:92) Created console id=15 > > domain=1 port=9601 > > [2005-03-04 14:08:56 xend] DEBUG (XendDomainInfo:1130) Creating vbd > > dom=1 uname=file:/home/testlars/t1.ext3 > > [2005-03-04 14:08:56 xend] DEBUG (blkif:155) Connecting blkif > > <BlkifBackendInterface 1 0> > > [2005-03-04 14:08:56 xend] DEBUG (XendDomainInfo:1107) Creating vif > > dom=1 vif=0 mac=aa:00:00:0b:c7:5d > > [2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> > > xend.console.create [15, 1, 9601] > > [2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> > > xend.domain.create [''Highmem'', ''1''] > > [2005-03-04 14:08:56 xend] INFO (XendRoot:91) EVENT> > > xend.domain.unpause [''Highmem'', ''1''] > > [2005-03-04 14:08:57 xend] DEBUG (blkif:201) Connecting blkif to event > > channel <BlkifBackendInterface 1 0> ports=16:3 > > [2005-03-04 14:14:42 xend] DEBUG (XendDomain:244) XendDomain>reap> > > domain died name=Highmem id=1 > > [2005-03-04 14:14:42 xend] INFO (XendDomain:564) Destroying domain: > > name=Highmem > > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:665) Destroying vifs > > for domain 1 > > [2005-03-04 14:14:42 xend] DEBUG (netif:290) Destroying vif domain=1 > > vif=0 > > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:674) Destroying vbds > > for domain 1 > > [2005-03-04 14:14:42 xend] DEBUG (blkif:550) Destroying blkif domain=1 > > [2005-03-04 14:14:42 xend] DEBUG (blkif:406) Destroying vbd domain=1 > > idx=0 > > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:634) Closing console, > > domain 1 > > [2005-03-04 14:14:42 xend] DEBUG (XendDomainInfo:622) Closing channel > > to domain 1 > > [2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.virq 4 > > [2005-03-04 14:14:45 xend] DEBUG (blkif:361) Unbinding vbd (type file) > > from /dev/loop0 > > [2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> xend.domain.exit > > [''Highmem'', ''1'', ''crash''] > > [2005-03-04 14:14:45 xend] INFO (XendRoot:91) EVENT> > > xend.domain.destroy [''Highmem'', ''1''] > > [2005-03-04 14:14:47 xend] DEBUG (XendDomain:244) XendDomain>reap> > > domain died name=Highmem id=1 > > [2005-03-04 14:14:47 xend] INFO (XendDomain:564) Destroying domain: > > name=Highmem > > [2005-03-04 14:14:47 xend] DEBUG (XendDomainInfo:634) Closing console, > > domain 1 > > [2005-03-04 14:14:47 xend] INFO (XendRoot:91) EVENT> xend.domain.exit > > [''Highmem'', ''1'', ''crash''] > > [2005-03-04 14:14:47 xend] INFO (XendRoot:91) EVENT> > > xend.domain.destroy [''Highmem'', ''1''] > > [2005-03-04 14:14:49 xend] DEBUG (XendDomain:244) XendDomain>reap> > > domain died name=Highmem id=1 > > [2005-03-04 14:14:49 xend] INFO (XendDomain:564) Destroying domain: > > name=Highmem > > > > > > > > ------------------------------------------------------------ > > > > Here is ''xm dmesg'' > > > > ERROR: cannot use unconfigured serial port COM1 > > __ __ ____ ___ _ _ > > \ \/ /___ _ __ |___ \ / _ \| || | > > \ // _ \ ''_ \ __) || | | | || |_ > > / \ __/ | | | / __/ | |_| |__ _| > > /_/\_\___|_| |_| |_____(_)___(_) |_| > > > > http://www.cl.cam.ac.uk/netos/xen > > University of Cambridge Computer Laboratory > > > > Xen version 2.0.4 (larsr@hpl.hp.com) (gcc version 3.4.2 20041017 (Red > > Hat 3.4.2-6.fc3)) Fri Feb 25 18:01:50 PST 2005 > > Latest ChangeSet: information unavailable > > > > (XEN) Physical RAM map: > > (XEN) 0000000000000000 - 000000000009ec00 (usable) > > (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > > (XEN) 00000000000e9400 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 000000007fff0000 (usable) > > (XEN) 000000007fff0000 - 000000007ffffc00 (ACPI data) > > (XEN) 000000007ffffc00 - 0000000080000000 (ACPI NVS) > > (XEN) 00000000fec00000 - 00000000fec10000 (reserved) > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > (XEN) 00000000fff80000 - 0000000100000000 (reserved) > > (XEN) System RAM: 2047MB (2096696kB) > > (XEN) Xen heap: 10MB (10720kB) > > (XEN) CPU0: Before vendor init, caps: 0387fbff 00000000 00000000, > > vendor = 0 > > (XEN) CPU caps: 0387fbff 00000000 00000000 00000000 > > (XEN) found SMP MP-table at 000f7570 > > (XEN) ACPI: RSDP (v000 PTLTD ) @ > > 0x000f7520 > > (XEN) ACPI: RSDT (v001 HP HWPC214 0x06040017 PTL 0x00000000) @ > > 0x7fffc8f7 > > (XEN) ACPI: FADT (v001 HP HWPC214 0x06040017 PTL 0x00000001) @ > > 0x7ffffb05 > > (XEN) ACPI: MADT (v001 PTLTD APIC 0x06040017 LTP 0x00000000) @ > > 0x7ffffb79 > > (XEN) ACPI: BOOT (v001 HP HWPC214 0x06040017 PTL 0x00000001) @ > > 0x7ffffbd9 > > (XEN) ACPI: DSDT (v001 HP HWPC214 0x06040017 MSFT 0x0100000b) @ > > 0x00000000 > > (XEN) ACPI: Local APIC address 0xfee00000 > > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x03] enabled) > > (XEN) Processor #3 Pentium(tm) Pro APIC version 17 > > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > > (XEN) Processor #0 Pentium(tm) Pro APIC version 17 > > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > > (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] 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: HP Product ID: LP 1Kr/2Kr APIC at: 0xFEE00000 > > (XEN) I/O APIC #1 Version 17 at 0xFEC00000. > > (XEN) I/O APIC #2 Version 17 at 0xFEC01000. > > (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs > > (XEN) Processors: 2 > > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > > (XEN) Initializing CPU#0 > > (XEN) Detected 1000.129 MHz processor. > > (XEN) CPU0: Before vendor init, caps: 0387fbff 00000000 00000000, > > vendor = 0 > > (XEN) CPU caps: 0387fbff 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) Booting processor 1/0 eip 90000 > > (XEN) Initializing CPU#1 > > (XEN) masked ExtINT on CPU#1 > > (XEN) ESR value before enabling vector: 00000000 > > (XEN) ESR value after enabling vector: 00000000 > > (XEN) CPU1: Before vendor init, caps: 0387fbff 00000000 00000000, > > vendor = 0 > > (XEN) CPU caps: 0387fbff 00000000 00000000 00000000 > > (XEN) CPU1 has booted. > > (XEN) Total of 2 processors activated. > > (XEN) ENABLING IO-APIC IRQs > > (XEN) Setting 1 in the phys_id_present_map > > (XEN) ...changing IO-APIC physical APIC ID to 1 ... ok. > > (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=-1 pin2=0 > > (XEN) ...trying to set up timer (IRQ0) through the 8259A ... > > (XEN) ..... (found pin 0) ...works. > > (XEN) Using local APIC timer interrupts. > > (XEN) Calibrating APIC timer for CPU0... > > (XEN) ..... CPU speed is 1000.0497 MHz. > > (XEN) ..... Bus speed is 133.3398 MHz. > > (XEN) ..... bus_scale = 0x0000888D > > (XEN) checking TSC synchronization across CPUs: passed. > > (XEN) Time init: > > (XEN) .... System Time: 61096354ns > > (XEN) .... cpu_freq: 00000000:3B9CC1E8 > > (XEN) .... scale: 00000001:FFEF1809 > > (XEN) .... Wall Clock: 1109943491s 200000us > > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfda11, last bus=1 > > (XEN) PCI: Using configuration type 1 > > (XEN) PCI: Probing PCI hardware > > (XEN) PCI: Probing PCI hardware (bus 00) > > (XEN) PCI: Discovered primary peer bus 01 [IRQ] > > (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 22 > > (XEN) PCI->APIC IRQ transform: (B0,I8,P0) -> 23 > > (XEN) PCI->APIC IRQ transform: (B0,I15,P0) -> 33 > > (XEN) PCI->APIC IRQ transform: (B1,I3,P0) -> 17 > > (XEN) PCI->APIC IRQ transform: (B1,I4,P0) -> 27 > > (XEN) PCI->APIC IRQ transform: (B1,I5,P0) -> 24 > > (XEN) PCI->APIC IRQ transform: (B1,I5,P1) -> 25 > > (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=g > > eneric,PT_MODE_WRITABLE'' > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Kernel image: 00c00000->00fbbeb8 > > (XEN) Initrd image: 00fbc000->01173a00 > > (XEN) Dom0 alloc.: 01400000->09400000 > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: c0100000->c04ecf04 > > (XEN) Init. ramdisk: c04ed000->c06a4a00 > > (XEN) Phys-Mach map: c06a5000->c06c5000 > > (XEN) Page tables: c06c5000->c06c8000 > > (XEN) Start info: c06c8000->c06c9000 > > (XEN) Boot stack: c06c9000->c06ca000 > > (XEN) TOTAL: c0000000->c0800000 > > (XEN) ENTRY ADDRESS: c0100000 > > (XEN) Scrubbing DOM0 RAM: ..done. > > (XEN) Initrd len 0x1b7a00, start at 0xc04ed000 > > (XEN) Scrubbing Free RAM: .....................done. > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > > input to Xen). > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real > > users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2005-Mar-10 16:29 UTC
Re: [Xen-devel] Problems with balloons and HIGHMEM (>896MB)
> > Hi, I tried the latest xen-2.0-testing-src.tgz, compiled > the user domain with HIGHMEM=y and HIGHMEM4G=y, and the > domain 0 with NOHIGHMEM=y, but I got the > same error: when I balloon a user domain with more than 896 MB, > it crashes and messes up Xen, so unfortunately it does not > appear to be fixed by the patches so far...This is now fixed in the 2.0-testing tree, and so will also be okay in the 2.0.5 release that we''ll be pushing out this week. -- Keir ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel