Hello.
I've upgraded from 2Gig to 4Gig ram and when I run 2 Virtualbox machines that nomally run without problem, they both freeze (debian etch stable, ubuntu hardy 8.041).
Ubuntu Hardy 8.041 is the host, all updates current.
Question;
Will a change in host pysical RAM (increase) affect running previously
created Vbox machines?
Thank you.
PV
RAM upgrade 2Gig to 4Gig Freezes existing multiple Vboxes
I had a similar experience with Ubuntu 8.0.4 on an AMD 64 box.
I upgraded from 2*1GB memory sticks to 4*1GB (the original 2,
and 2 extra). After that I got random crashes / lockups with VB
guests.
It turned out there were two things wrong. These problems only
manifested themselves when I started to exercise the additional RAM.
First of all, the network driver for my motherboard's 100bT ethernet
wasn't (still isn't) very good and caused crashes when the BIOS
was configured to see the whole 4GB of RAM.
Changing the BIOS settings so I effectively removed a few hundred
MB helped a bit, but the machine was still flakey. More investigations
led me to the conclusion that a lot of motherboards say they
support 4GB, but in reality are only good up to 3GB. The reason
being that Microsoft can only use 3GB, so they think they're safe
advertising 4GB, in the knowledge that only us freaks would bother
loading the full amount - windows users would stop at 3GB and so
would never see any problems (to be fair, they may well say that
only microsoft is "supported" on their MBs).
I upgraded from 2*1GB memory sticks to 4*1GB (the original 2,
and 2 extra). After that I got random crashes / lockups with VB
guests.
It turned out there were two things wrong. These problems only
manifested themselves when I started to exercise the additional RAM.
First of all, the network driver for my motherboard's 100bT ethernet
wasn't (still isn't) very good and caused crashes when the BIOS
was configured to see the whole 4GB of RAM.
Changing the BIOS settings so I effectively removed a few hundred
MB helped a bit, but the machine was still flakey. More investigations
led me to the conclusion that a lot of motherboards say they
support 4GB, but in reality are only good up to 3GB. The reason
being that Microsoft can only use 3GB, so they think they're safe
advertising 4GB, in the knowledge that only us freaks would bother
loading the full amount - windows users would stop at 3GB and so
would never see any problems (to be fair, they may well say that
only microsoft is "supported" on their MBs).
-
Sasquatch
- Volunteer
- Posts: 17798
- Joined: 17. Mar 2008, 13:41
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP, Windows 7, Linux
- Location: /dev/random
You can try to run the 'big mem kernel' on your system. That kernel is build to be able to allocate more than the limit of 3,5 GB of RAM. Else you need to run a 64 bit Host if you have a 64 bit CPU.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
Yes.Popovitch wrote:pete_I,
Did you solve the freezes entirely?
( should say this is an AMD_64 system running 64-bit Ubuntu)
What I did was drop back to 3GB of memory (my original 2*1GB sticks
and swapped out the extra 2*1GB - replaced them with 2*512MB)
It's still better than the 2GB I started with (didn't leave much
headroom with a decent-sized VB guest running) but I was
disappointed that I was not able to run Ubuntu with 4GB visible.
However with 3GB my system is rock solid.
Well, all the VB guests I had created for my 2GB system worked thePopovitch wrote:Will 'any' change in host pysical RAM (increase) affect running previously created Vbox machines? For example, 2 Gigs to 3 Gigs.
same with the extra RAM. There was one effect, they ran faster as the
box didn't have to page-out any memory when I had memory-
intensive (e.g. firefox: 500MB++) processes running on the host.
However, I didn't try increasing the amount of memory allocated to
the guests, (or the size of the video buffer) as they had sufficient for
my needs and weren't constrained by insufficient memory.
So yes, it is possible for changes to the host to affect the guests.
Since they all share resources (CPU - either single or multi, disks,
USB/network bandwidth, RAM) you can't say that the performance
- or stability of a guest will always be unaffected by changes made
to the underlying hardware.
-
stephanecharette
- Volunteer
- Posts: 300
- Joined: 10. Nov 2007, 22:03
- Primary OS: Ubuntu other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Ubuntu-64bit, Windows
- Location: Kelowna, British Columbia, Canada
- Contact:
I had a bucketload of VMs created back when I had 2G of ram. At Christmas (9 months ago) I received another 2G for a total of 4G. Haven't had any problems running any of the guests I created before -- they still run exactly the same. Only difference is I can run more of them before I run out of memory...Popovitch wrote:Will 'any' change in host pysical RAM (increase) affect running previously created Vbox machines? For example, 2 Gigs to 3 Gigs.
But the descriptions above about memory problems related to motherboard and/or bios issues is worrysome. I'm glad I haven't had to deal with hardware issues.
(Not only did they run the same -- but I had created my VMs when my host was 32-bit Ubuntu. When I received the extra ram, I backed up the VMs, formated my drive and installed 64-bit Ubuntu & 64-bit VirtualBox. Restored my VMs, and was glad to see they continued to work fine. VB should be glad to advertise binary compatibility between their 32-bit and 64-bit products, as it saved me *lots* of time re-installing all my VMs.)
Stéphane