David F Barrera
2005-Sep-08 13:50 UTC
[Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
I am unable to create guest domains on my x86_64 SLES 9 SP2 (IBM HS20
Blades) boxes this morning.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=221
Error message:
Using config file "/tmp/xen/vm1.cfg".
Error: Error creating domain: (12, ''Cannot allocate memory'')
-----------
gcc version: 3.3.3 (SuSE Linux)
changeset: 6682:12ff9c954aceb9c84c9e730886d3cd538a6ec56a
tag: tip
user: iap10@freefall.cl.cam.ac.uk
date: Wed Sep 7 20:07:15 2005
summary: Give each domain some memory below 4GB. This solves the
"PGD''s must
be below 4GB" for the initial page tables. I''m not sure
we''ll stick with this
approach, but this is good enough for the time being.
xm dmesg:
__ __ _____ ___ _ _
\ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
\ // _ \ ''_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
/ \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
/_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version 3.3.3 (SuSE
Linux)) Thu Sep 8 08:04:04 CDT 2005
Latest ChangeSet: Wed Sep 7 20:07:15 2005
12ff9c954aceb9c84c9e730886d3cd538a6ec56a
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009d400 (usable)
(XEN) 000000000009d400 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000003ffbe680 (usable)
(XEN) 000000003ffbe680 - 000000003ffd0000 (ACPI data)
(XEN) 000000003ffd0000 - 0000000040000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1047916kB)
(XEN) Xen heap: 14MB (14668kB)
(XEN) found SMP MP-table at 0009d540
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 IBM ) @
0x00000000000fdfc0
(XEN) ACPI: RSDT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @
0x000000003ffcff80
(XEN) ACPI: FADT (v002 IBM SERBLADE 0x00001000 IBM 0x45444f43) @
0x000000003ffcfec0
(XEN) ACPI: MADT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @
0x000000003ffcfe00
(XEN) ACPI: MCFG (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @
0x000000003ffcfdc0
(XEN) ACPI: DSDT (v001 IBM SERBLADE 0x00001000 INTL 0x02002025) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x0d] address[0xfec10000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 13, version 32, address 0xfec10000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0c] address[0xfec81000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 12, version 32, address 0xfec81000, GSI 48-71
(XEN) ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72])
(XEN) IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI 72-95
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ11 used by override.
(XEN) Enabling APIC mode: Flat. Using 4 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 3600.321 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU2: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU3: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80000000,LOADER=generic''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000002800000->0000000003000000 (61952 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff8062f085
(XEN) Init. ramdisk: ffffffff80630000->ffffffff80630000
(XEN) Phys-Mach map: ffffffff80630000->ffffffff806ad000
(XEN) Start info: ffffffff806ad000->ffffffff806ae000
(XEN) Page tables: ffffffff806ae000->ffffffff806b5000
(XEN) Boot stack: ffffffff806b5000->ffffffff806b6000
(XEN) TOTAL: ffffffff80000000->ffffffff80800000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen).
(XEN) (file=page_alloc.c, line=561) Over-allocation for domain 1: 131073 >
131072
(XEN) (file=page_alloc.c, line=563) ...or the domain is dying (0)
(XEN) (file=memory.c, line=55) Could not allocate a frame id=1 0 flags=1
xm log:
[2005-09-08 08:30:27 xend] INFO (SrvDaemon:296) Xend Daemon started
[2005-09-08 08:30:27 xend] INFO (XendDomain:357) Creating entry for unknown
domain: id=0 uuid=26944109-5445-46c3-bfc8-d2d6c858bf1c
[2005-09-08 08:30:27 xend] DEBUG (XendDomainInfo:179)
info={''vcpu_to_cpu'': [0,
-1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
-1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1], ''cpu_time'':
31146549990L,
''ssidref'': 0, ''shutdown_reason'': 0,
''dying'': 0, ''dom'': 0,
''running'': 1,
''maxmem_kb'': 17179869180, ''paused'': 0,
''crashed'': 0, ''vcpus'': 1,
''shutdown'': 0,
''mem_kb'': 250880, ''cpumap'': [-1, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0}
[2005-09-08 08:30:27 xend] DEBUG (XendDomainInfo:180)
config=''None''
[2005-09-08 08:30:27 xend] INFO (XendRoot:141) EVENT> xend.domain.create
[''Domain-0'', 0]
[2005-09-08 08:30:27 xend] INFO (xsobj:326) DBMap>introduceDomain> 0 28728
<EventChannel dom1:0:11 dom2:0:12>
/domain/26944109-5445-46c3-bfc8-d2d6c858bf1c
[2005-09-08 08:30:27 xend] DEBUG (XendDomainInfo:697) writing key
availability=online to path /cpu/0 in store
[2005-09-08 08:30:27 xend] INFO (XendRoot:141) EVENT> xend.start 0
[2005-09-08 08:30:27 xend] INFO (SrvServer:83) unix
path=/var/lib/xend/xend-socket
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + set -e
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + OP=start
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + shift
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + export
bridge=xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + bridge=xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + export
antispoof=no
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + antispoof=no
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + bridge=xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + netdev=eth1
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + antispoof=no
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + echo
''*network
start bridge=xen-br0 netdev=eth1 antispoof=no''
[2005-09-08 08:30:27 xend] INFO (process:35) [network-bridge] network start
bridge=xen-br0 netdev=eth1 antispoof=no
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + op_start
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] +
''['' xen-br0 =null '']''
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + create_bridge
xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + local
bridge=xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + brctl show
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + grep -q xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + brctl addbr
xen-br0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + brctl stp
xen-br0 off
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + brctl setfd
xen-br0 0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + ifconfig
xen-br0 up
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + ifconfig
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + grep -q veth0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + ifconfig veth0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + grep -q veth0
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] ++ ifconfig eth1
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] ++ grep HWadd
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] ++ sed -e
''s/.*\(..:..:..:..:..:..\).*/\1/''
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] +
mac=00:11:25:9D:69:87
[2005-09-08 08:30:27 xend] ERROR (process:37) [network-bridge] + ifdown eth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ip link set
eth1 name peth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ip link set
veth0 name eth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ifconfig peth1
0.0.0.0 -arp down
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ifconfig peth1
hw ether fe:ff:ff:ff:ff:ff
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ifconfig eth1
hw ether 00:11:25:9D:69:87
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + add_to_bridge
xen-br0 vif0.0
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + local
bridge=xen-br0
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + local
dev=vif0.0
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + brctl show
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + grep -q vif0.0
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + brctl addif
xen-br0 vif0.0
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + add_to_bridge
xen-br0 peth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + local
bridge=xen-br0
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + local dev=peth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + brctl show
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + grep -q peth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + brctl addif
xen-br0 peth1
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ip link set
xen-br0 up
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ip link set
vif0.0 up
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ip link set
peth1 up
[2005-09-08 08:30:28 xend] ERROR (process:37) [network-bridge] + ifup eth1
[2005-09-08 08:30:57 xend] DEBUG (image:156) initDomain: cpu=-1 mem_kb=524288
ssidref=-1 dom=1
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Puthiyaparambil, Aravindh
2005-Sep-08 14:39 UTC
RE: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
How much memory have you given to Dom0?> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of David F Barrera > Sent: Thursday, September 08, 2005 9:51 AM > To: xen-devel > Subject: [Xen-devel] Unable to create guest domains on x86_64 SLES 9SP2> > > I am unable to create guest domains on my x86_64 SLES 9 SP2 (IBM HS20 > Blades) boxes this morning. > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=221 > > Error message: > > Using config file "/tmp/xen/vm1.cfg". > Error: Error creating domain: (12, ''Cannot allocate memory'') >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Sep-08 15:53 UTC
RE: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
On Thu, 2005-09-08 at 10:39 -0400, Puthiyaparambil, Aravindh wrote:> How much memory have you given to Dom0?dom0_mem=256000 These are configurations that have worked before, as recently as yesterday.> > > -----Original Message----- > > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > > bounces@lists.xensource.com] On Behalf Of David F Barrera > > Sent: Thursday, September 08, 2005 9:51 AM > > To: xen-devel > > Subject: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 > SP2 > > > > > > I am unable to create guest domains on my x86_64 SLES 9 SP2 (IBM HS20 > > Blades) boxes this morning. > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=221 > > > > Error message: > > > > Using config file "/tmp/xen/vm1.cfg". > > Error: Error creating domain: (12, ''Cannot allocate memory'') > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Sep-08 15:56 UTC
RE: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
I just read Jun Nakajima''s <jun.nakajima@intel.com> note about an hg problem. I may have the same problem as well. I need to repull and rebuild. Cheers On Thu, 2005-09-08 at 10:39 -0400, Puthiyaparambil, Aravindh wrote:> How much memory have you given to Dom0? > > > -----Original Message----- > > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > > bounces@lists.xensource.com] On Behalf Of David F Barrera > > Sent: Thursday, September 08, 2005 9:51 AM > > To: xen-devel > > Subject: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 > SP2 > > > > > > I am unable to create guest domains on my x86_64 SLES 9 SP2 (IBM HS20 > > Blades) boxes this morning. > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=221 > > > > Error message: > > > > Using config file "/tmp/xen/vm1.cfg". > > Error: Error creating domain: (12, ''Cannot allocate memory'') > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Sep-08 16:33 UTC
RE: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
On Thu, 2005-09-08 at 10:56 -0500, David F Barrera wrote:> I just read Jun Nakajima''s <jun.nakajima@intel.com> note about an hg > problem. I may have the same problem as well. I need to repull and > rebuild. >I repulled and rebuilt using a newer changeset, and the problems still occurs. The pull and builds were successful. Also, these are setups that I use routinely. changeset: 6683:c2705e74efbaba2bf1867a7391e6b76225dd10f9 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Thu Sep 8 10:22:01 2005 summary: Cleanups, and fix allocating DMA memory via> Cheers > > On Thu, 2005-09-08 at 10:39 -0400, Puthiyaparambil, Aravindh wrote: > > How much memory have you given to Dom0?Dom0 has 256M of memory. The machine has 1GB.> > > > > -----Original Message----- > > > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > > > bounces@lists.xensource.com] On Behalf Of David F Barrera > > > Sent: Thursday, September 08, 2005 9:51 AM > > > To: xen-devel > > > Subject: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 > > SP2 > > > > > > > > > I am unable to create guest domains on my x86_64 SLES 9 SP2 (IBM HS20 > > > Blades) boxes this morning. > > > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=221 > > > > > > Error message: > > > > > > Using config file "/tmp/xen/vm1.cfg". > > > Error: Error creating domain: (12, ''Cannot allocate memory'') > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nakajima, Jun
2005-Sep-08 16:58 UTC
RE: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
David F Barrera wrote:> On Thu, 2005-09-08 at 10:56 -0500, David F Barrera wrote: >> I just read Jun Nakajima''s <jun.nakajima@intel.com> note about an hg >> problem. I may have the same problem as well. I need to repull and >> rebuild. >> > I repulled and rebuilt using a newer changeset, and the problems still > occurs. The pull and builds were successful. Also, these are setups > that I use routinely.I''ve got the same problem; my machine has sufficient memory. Probably the builder is broken. To me the changeset 6682 is the primary suspect.> > changeset: 6683:c2705e74efbaba2bf1867a7391e6b76225dd10f9 > tag: tip > user: kaf24@firebug.cl.cam.ac.uk > date: Thu Sep 8 10:22:01 2005 > summary: Cleanups, and fix allocating DMA memory via > >> Cheers >> >> On Thu, 2005-09-08 at 10:39 -0400, Puthiyaparambil, Aravindh wrote: >>> How much memory have you given to Dom0? > Dom0 has 256M of memory. The machine has 1GB. >>> >>>> -----Original Message----- >>>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- >>>> bounces@lists.xensource.com] On Behalf Of David F Barrera >>>> Sent: Thursday, September 08, 2005 9:51 AM >>>> To: xen-devel >>>> Subject: [Xen-devel] Unable to create guest domains on x86_64 SLES >>>> 9 SP2 >>>> >>>> >>>> I am unable to create guest domains on my x86_64 SLES 9 SP2 (IBM >>>> HS20 Blades) boxes this morning. >>>> >>>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=221 >>>> >>>> Error message: >>>> >>>> Using config file "/tmp/xen/vm1.cfg". >>>> Error: Error creating domain: (12, ''Cannot allocate memory'') >>>>Jun --- Intel Open Source Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nakajima, Jun
2005-Sep-08 17:12 UTC
RE: [Xen-devel] Unable to create guest domains on x86_64 SLES 9 SP2
Nakajima, Jun wrote:> David F Barrera wrote: >> On Thu, 2005-09-08 at 10:56 -0500, David F Barrera wrote: >>> I just read Jun Nakajima''s <jun.nakajima@intel.com> note about an >>> hg problem. I may have the same problem as well. I need to repull >>> and rebuild. >>> >> I repulled and rebuilt using a newer changeset, and the problems >> still occurs. The pull and builds were successful. Also, these are >> setups that I use routinely. > > I''ve got the same problem; my machine has sufficient memory. Probably > the builder is broken. To me the changeset 6682 is the primary > suspect. >Yep, domU boots fine if I revert 6682.> Jun > --- > Intel Open Source Technology Center >Jun --- Intel Open Source Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel