RE: [Xen-devel] using 3.1.1 with 256GB host, 11_create_concurrent_pos of xm-test fails with Cannotallocate memory

["Krysan, Susan" <KRYSANS@xxxxxxxxxx>]

I found the solution to this problem.  I added xen boot parameter
xenheap_megabytes=64 and now test 11_create_concurrent_pos of xm-test
passes.

Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
 

-----Original Message-----
From: Krysan, Susan 
Sent: Thursday, October 18, 2007 2:31 PM
To: 'Ian Pratt'; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] using 3.1.1 with 256GB
host,11_create_concurrent_pos of xm-test fails with Cannotallocate
memory

Thanks for your response.  This is the first time xen has actually been
allotted 256GB.  I've booted unstable with 256GB before, but xen is only
allotted 166gb (truncated for 32on64 support).  Next week I will run
with a debug build and provide you with the memory stats.

Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
 
-----Original Message-----
From: Ian Pratt [mailto:Ian.Pratt@xxxxxxxxxxxx] 
Sent: Thursday, October 18, 2007 4:00 AM
To: Krysan, Susan; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: ian.pratt@xxxxxxxxxxxx
Subject: RE: [Xen-devel] using 3.1.1 with 256GB
host,11_create_concurrent_pos of xm-test fails with Cannotallocate
memory

> Test 11_create_concurrent_pos of xm-test suite only creates 33 domains
> and then gets: Cannot allocate memory.  The host has c/s 15464 of
3.1.1
> and it has plenty of memory - 256GB.

That's interesting. Is this a regression, or the first time you've tried
256GB?

Please can you use a debug build of xen then try sending it 'debug key'
events so we can see the memory stats. You can do this from the serial
console, or inject the key presses via xm.

Ian

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