SRU justification:
Impact: The config option XEN_MAX_DOMAIN_MEMORY controls how much memory a Xen instance is seeing. The default for 64bit is 32GB, which is the reason that m2.4xlarge instances only report this amount of memory.
Fix: Setting this limit to 70GB as there is a known restriction for t1.micro instances at about 80GB.
Testcase: Booted m2.4xlarge with this set to 32GB shows 32GB of memory, when set to 70GB, it correctly reports 68GB. Booted a t1.micro as well to verify this has not caused problems there.
---
The following is copied from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651370/comments/14 . I'm fairly sure that The problem is also with a stock image (without the additional command line options suggested in that bug).
Brandon's and Scott's workaround works for me partly, but the kernel on an instance started in such a way seems to detect only 32 GB of memory even for a m2.4xlarge instance which should have 68.4 GB available, according to the EC2 instances page. Is this a side-effect of the workaround, or a completely separate bug?
Maveric results:
ubuntu@ip-10-230-9-87:~$ uname -a
Linux ip-10-230-9-87 2.6.35-22-virtual #35-Ubuntu SMP Sat Oct 16 23:19:29 UTC 2010 x86_64 GNU/Linux
ubuntu@ip-10-230-9-87:~$ ec2metadata --instance-type
m2.4xlarge
ubuntu@ip-10-230-9-87:~$ free
total used free shared buffers cached
Mem: 32810684 667628 32143056 0 6444 32152
-/+ buffers/cache: 629032 32181652
Swap: 0 0 0
Expected results (from a SUSE 11 guest):
ip-10-230-45-187:~ # uname -a
Linux ip-10-230-45-187 2.6.32.19-0.3-ec2 #1 SMP 2010-09-17 20:28:21 +0200 x86_64 x86_64 x86_64 GNU/Linux
ip-10-230-45-187:~ # curl http://169.254.169.254/latest/meta-data/instance-type
m2.4xlarge
ip-10-230-45-187:~ # free
total used free shared buffers cached
Mem: 71705116 2361584 69343532 0 10972 126424
-/+ buffers/cache: 2224188 69480928
Swap: 0 0 0
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-virtual 2.6.35-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4
Uname: Linux 2.6.35-22-virtual x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CurrentDmesg:
Date: Thu Oct 28 13:35:42 2010
Ec2AMI: ami-548c783d
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-427d952b
Ec2Ramdisk: unavailable
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: root=LABEL=uec-rootfs ro console=hvc0
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcModules: acpiphp 18752 0 - Live 0xffffffffa0000000
SourcePackage: linux
I added linux-ec2. This issue is a problem also on lucid.
I tested on:
us-east-1 ami-4a0df923 canonical ebs/ubuntu-
$ wget http://
m2.2xlarge
$ free
total used free shared buffers cached
Mem: 35840228 1561456 34278772 0 22996 359664
-/+ buffers/cache: 1178796 34661432
Swap: 0 0 0
$ uname -a
Linux domU-12-