Hello,*I just installed Wheezy on my laptop using debootstrap to test Xen advancements from Squeeze. *Everything seems to be working great, except the memory is reported incorrectly under the Xen enabled OS. *Normal boot reports correct memory. *Included below are the details I think are pertinent, if you need more information, please let me know.

Thanks for your help with this.*
Shane

-------------------uname -a:Linux sdj-lt 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux
-------------------free (Normal Debian boot):* * * * * * *total * * * used * * * free * * shared * *buffers * * cachedMem: * * * 5590240 * * 152952 * *5437288 * * * * *0 * * *10928 * * *57548
-/+ buffers/cache: * * *84476 * *5505764Swap: * * *4194300 * * * * *0 * *4194300-------------------free(Xen enabled):* * * * * * *total * * * used * * * free * * shared * *buffers * * cached

Mem: * * * 3788868 * * 437224 * *3351644 * * * * *0 * * *21760 * * 258504-/+ buffers/cache: * * 156960 * *3631908Swap: * * *4194300 * * * * *0 * *4194300-------------------
/boot/grub/grub.cfgportions pertaining to Debian)
### BEGIN /etc/grub.d/20_linux_xen ###submenu "Xen 4.1-amd64" {menuentry 'Debian GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-2-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {

insmod lvm insmod part_msdos insmod ext2
set root='(vg-os)' search --no-floppy --fs-uuid --set=root 0601ad5f-3e78-4b6e-a06c-3f0af7519905
echo 'Loading Xen 4.1-amd64 ...' multiboot /boot/xen-4.1-amd64.gz placeholder *

echo 'Loading Linux 3.2.0-2-amd64 ...' module /boot/vmlinuz-3.2.0-2-amd64 placeholder root=/dev/mapper/vg-os ro *quiet

echo 'Loading initial ramdisk ...' module /boot/initrd.img-3.2.0-2-amd64

}menuentry 'Debian GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-2-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os --class xen { insmod lvm

insmod part_msdos insmod ext2 set root='(vg-os)'
search --no-floppy --fs-uuid --set=root 0601ad5f-3e78-4b6e-a06c-3f0af7519905 echo 'Loading Xen 4.1-amd64 ...'

multiboot /boot/xen-4.1-amd64.gz placeholder* echo 'Loading Linux 3.2.0-2-amd64 ...'

module /boot/vmlinuz-3.2.0-2-amd64 placeholder root=/dev/mapper/vg-os ro single* echo 'Loading initial ramdisk ...'

module /boot/initrd.img-3.2.0-2-amd64}}### END /etc/grub.d/20_linux_xen ###
-------------------

On Fri, 27 Apr 2012 12:11:00 -0600, Shane Johnson wrote:

(please, no html posts, thanks)

> I just installed Wheezy on my laptop using debootstrap to test Xen
> advancements from Squeeze. Everything seems to be working great, except
> the memory is reported incorrectly under the Xen enabled OS. Normal
> boot reports correct memory. Included below are the details I think are
> pertinent, if you need more information, please let me know. Thanks for
> your help with this.

(...)

> uname -a:

(...)

Google suggests that since Xen >4 based kernels you have to use "xm info"
to get the full amount of ram (dom0+domu), meaning the above "uname -a"
run it from a Xen kernel just displays the amount of ram which is
available for the host (dom0-domu).

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jnguf7$s83$13@dough.gmane.org">http://lists.debian.org/jnguf7$s83$13@dough.gmane.org