Page 1 of 1

memory usage

Posted: 18. Sep 2008, 18:16
by void64
I'm running VB 1.6.6 on a Win XP x64 host, with a Linux xubuntu guest. I have allocated 128 MB of ram to the Linux guest, but memory use in the windows host routinely exceeds 2GB? I have noticed that memory usage creeps up over time (leak?) but will fall again significantly if I take a guest snapshot, and will drop to what I think is normal if I restart the guest OS.

Also, the process using all this memory does not list in Window's "Task Manager". If I add up all the numbers for memory use listed there they hardly sum to 1GB, yet my 4GB host machine reaches redline within 1 or 2 days of running the guest machine :shock:.

Any ideas what's going ons? I'm working around it now simply by restarting the Linux guest every two days, but it's getting annoying. I've considered upgrading to the 2.x version of VH, but wasn't sure if my existing virtual machine would transfer without problems, so I'm weary of going that way. Any suggestions / help are appreciated - thanks!

Posted: 18. Sep 2008, 18:29
by TerryE
This is an MS problem if you search the recent posts in this forum you will see a link to the MS hotfix which cures this issue.

Posted: 18. Sep 2008, 18:33
by void64
found it - thanks! I'll give it a try ... if anybody else needs it:
http://www.virtualbox.org/ticket/2242

Posted: 18. Sep 2008, 19:49
by void64
ok that didn't work :( The hotfix is for VISTA only, and I'm running Win XP x64 (= Server 2003 x64 if I'm not mistaken). Any other suggestions?

Posted: 18. Sep 2008, 22:43
by TerryE
Oops you're correct. Sorry. It's basically the same but MS have only produced the hotfix for Vista-x64. I am not sure we can help. We can't produce hotfixes for MS problems.

Posted: 19. Sep 2008, 06:04
by void64
TerryE wrote:Oops you're correct. Sorry. It's basically the same but MS have only produced the hotfix for Vista-x64. I am not sure we can help. We can't produce hotfixes for MS problems.
hehe ... I'm sure if you could fix all of MS' screw-ups you would have been bought out by them by now anyway ;). The entry in the bug tracker says it's fixed for version 2.0.4 - would that mean I can cure it by upgrading VB even without a hotfix for my OS? Thanks for all the help!

Posted: 19. Sep 2008, 14:59
by TerryE
As with a lot of MS "features by design" it is just easier to code around it. This is what the team did in this case.

Posted: 19. Sep 2008, 15:02
by void64
That sounds promising - any danger of loosing my virtual machines or specific precautions I should take before doing the upgrade?

Posted: 19. Sep 2008, 15:17
by TerryE
Things can always go wrong: heads crash, ... A cautious person might want to wait at least a few days and scan the forum just to make sure that there are no major probs.