Re: 64 bit Wheezy RAM Limitation
On Sun, Feb 03, 2013 at 09:56:12AM -0500, Stephen P. Molnar wrote: Let me start with a disclaimer - I am not a hardware person! I am using Oracle VirtualBox (v 4.2.6 r82870) as a testbed for Wheezy Testing before upgrading my production linux computer. The software is installed on my 64 bit Dell Inspiron laptop with 8 GB of RAM running MS Win 7 Professional as the primary OS. With a couple of exceptions that I attribute to a less than complete understanding of the VirtualBox environment, Wheezy is performing well. It was with a fair amount of surprise that I discovered, entirely by chance, that according to KInfoCenter that the system is using only 4.47 GB of total physical memory!!! Googling 'Debian Wheezy 64 bit memory limitation' only turn up references to Squeezy and the Debian Handbook doesn't seem to address the issue. I would greatly appreciate being pointed to any sources of information about this issue. Just a quick check, have you told VirtualBox that you'd like the guest to be 64-bit? When creating a VM, you typically tell VirtualBox what kind of OS will be installed. For Debian, there will be TWO entries: Debian and Debian (64 bit). The first will HIDE your CPU's 64-bit capabilities from the Guest OS (Wheezy). signature.asc Description: Digital signature
64 bit Wheezy RAM Limitation
Let me start with a disclaimer - I am not a hardware person! I am using Oracle VirtualBox (v 4.2.6 r82870) as a testbed for Wheezy Testing before upgrading my production linux computer. The software is installed on my 64 bit Dell Inspiron laptop with 8 GB of RAM running MS Win 7 Professional as the primary OS. With a couple of exceptions that I attribute to a less than complete understanding of the VirtualBox environment, Wheezy is performing well. It was with a fair amount of surprise that I discovered, entirely by chance, that according to KInfoCenter that the system is using only 4.47 GB of total physical memory!!! Googling 'Debian Wheezy 64 bit memory limitation' only turn up references to Squeezy and the Debian Handbook doesn't seem to address the issue. I would greatly appreciate being pointed to any sources of information about this issue. Thanks in advance.
Re: 64 bit Wheezy RAM Limitation
Stephen P. Molnar s.mol...@sbcglobal.net wrote: It was with a fair amount of surprise that I discovered, entirely by chance, that according to KInfoCenter that the system is using only 4.47 GB of total physical memory!!! Please post the output of free and the output of dmesg | grep BIOS-e820. Those will provide more input for the list to be able to help you. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/09foke8jv...@mids.svenhartge.de
Re: 64 bit Wheezy RAM Limitation
Dear Stephen, please do not post HTML to the list[1]. Stephen P. Molnar wrote: I am using Oracle VirtualBox (v 4.2.6 r82870) as a testbed for Wheezy Testing before upgrading my production linux computer. The software is installed on my 64 bit Dell Inspiron laptop with 8 GB of RAM running MS Win 7 Professional as the primary OS. With a couple of exceptions that I attribute to a less than complete understanding of the VirtualBox environment, Wheezy is performing well. Are you running Wheezy _inside_ VirtualBox with Windows 7 as the host OS, or is this a dual-boot system? If the latter, wheezy should easily detect 8 GB and use them. In case of the former, you probably only allocated 4.7 GB to Wheezy in the VirtualBox configuration, hence the ‘computer’ Wheezy runs on only has 4.7 GB. Best, Claudius [1] as by #9 in the Code of Conduct for Debian mailing lists, http://www.debian.org/MailingLists/#codeofconduct -- Please don’t CC me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130203163330.0fe02...@ares.home.chubig.net
FW: 64 bit Wheezy RAM Limitation
Unfortunately, I didn't look at the addressees. -Original Message- From: Stephen P. Molnar [mailto:s.mol...@sbcglobal.net] Sent: Sunday, February 03, 2013 11:16 AM To: 'Sven Hartge' Subject: RE: 64 bit Wheezy RAM Limitation -Original Message- From: Sven Hartge [mailto:s...@svenhartge.de] Sent: Sunday, February 03, 2013 10:27 AM To: debian-user@lists.debian.org Subject: Re: 64 bit Wheezy RAM Limitation Stephen P. Molnar s.mol...@sbcglobal.net wrote: It was with a fair amount of surprise that I discovered, entirely by chance, that according to KInfoCenter that the system is using only 4.47 GB of total physical memory!!! Please post the output of free and the output of dmesg | grep BIOS-e820. Those will provide more input for the list to be able to help you. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/09foke8jv...@mids.svenhartge.de Thanks for your reply. Here's what you asked, both a user and as su: computation@debian:~$ free total used free sharedbuffers cached Mem: 497263613058803666756 0 86828 668240 -/+ buffers/cache: 5508124421824 Swap: 10236924 0 10236924 computation@debian:~$ dmesg | grep BIOS-e820 [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - dfff (usable) [0.00] BIOS-e820: dfff - e000 (ACPI data) [0.00] BIOS-e820: fffc - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00015880 (usable) computation@debian:~$ su Password: root@debian:/home/computation# free total used free sharedbuffers cached Mem: 497263613102483662388 0 86868 675764 -/+ buffers/cache: 5476164425020 Swap: 10236924 0 10236924 root@debian:/home/computation# dmesg | grep BIOS-e820 [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - dfff (usable) [0.00] BIOS-e820: dfff - e000 (ACPI data) [0.00] BIOS-e820: fffc - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00015880 (usable) Stephen P. Molnar, Ph.D.Life is a fuzzy set Foundation for Chemistry Stochastic and multivariate www.FoundationForChemistry.com (614)312-7528 (c) Skype: smolnar1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/00c801ce022f$806e16e0$814a44a0$@mol...@sbcglobal.net
Re: 64 bit Wheezy RAM Limitation
On 2/3/2013 8:56 AM, Stephen P. Molnar wrote: I am using Oracle VirtualBox (v 4.2.6 r82870) as a testbed for Wheezy Testing before upgrading my production linux computer. The software is installed on my 64 bit Dell Inspiron laptop with 8 GB of RAM running MS Win 7 Professional as the primary OS. ... KInfoCenter ...using only 4.47 GB Debian Debian | | Virtual Hardware Box | Windows | Hardware Windows 7 and Virtual box are likely using and reserving RAM for the Windows environment, and allocating some amount to the virtual machine. In this case that' appears to be 4.5 to 5GB. Reading the VirtualBox documentation will very likely answer all of your questions relating to this. The problem is almost certainly not with Debian. There's probably a menu box somewhere that allows you to configure the amount of memory for the virtual machine. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/510e976e.1030...@hardwarefreak.com
RE: 64 bit Wheezy RAM Limitation
-Original Message- From: Claudius Hubig [mailto:debian_1...@chubig.net] Sent: Sunday, February 03, 2013 11:34 AM To: debian-user@lists.debian.org Subject: Re: 64 bit Wheezy RAM Limitation Dear Stephen, please do not post HTML to the list[1]. Stephen P. Molnar wrote: I am using Oracle VirtualBox (v 4.2.6 r82870) as a testbed for Wheezy Testing before upgrading my production linux computer. The software is installed on my 64 bit Dell Inspiron laptop with 8 GB of RAM running MS Win 7 Professional as the primary OS. With a couple of exceptions that I attribute to a less than complete understanding of the VirtualBox environment, Wheezy is performing well. Are you running Wheezy _inside_ VirtualBox with Windows 7 as the host OS, or is this a dual-boot system? If the latter, wheezy should easily detect 8 GB and use them. In case of the former, you probably only allocated 4.7 GB to Wheezy in the VirtualBox configuration, hence the ‘computer’ Wheezy runs on only has 4.7 GB. Best, Claudius [1] as by #9 in the Code of Conduct for Debian mailing lists, http://www.debian.org/MailingLists/#codeofconduct -- Please don’t CC me. Ah. That's the answer. Entirely my fault, I only allowed 5GB to the client. -- cl To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130203163330.0fe02...@ares.home.chubig.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/00c901ce022f$e0dc8570$a2959050$@mol...@sbcglobal.net
Re: FW: 64 bit Wheezy RAM Limitation
Stephen P. Molnar s.mol...@sbcglobal.net wrote: computation@debian:~$ free total used free sharedbuffers cached Mem: 497263613058803666756 0 86828 668240 -/+ buffers/cache: 5508124421824 Swap: 10236924 0 10236924 computation@debian:~$ dmesg | grep BIOS-e820 [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - dfff (usable) [0.00] BIOS-e820: dfff - e000 (ACPI data) [0.00] BIOS-e820: fffc - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00015880 (usable) So the upper memory limit is 0x15880 bytes, which equals 5779750912 bytes in decimal. Subtracting the reserved and ACPI data regions results 5242747904 bytes or 5119871 kbytes of usable memory. The kernel uses some of that for itself (147235 kbytes in your case) and the rest is usable for processes. Now, the interesting part is: how much memory did you tell Virtualbox to give to your VM? It is _not_ wise to use all memory the host has available because this will then starve the host itself, rendering it nearly unusable. But this is no Wheezy (or Debian or Linux) problem, it is a VirtualBox configuration issue. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/29foq61jv...@mids.svenhartge.de
