virtualbox.org

This has happened several times...should I receive a Virtual Memory error on my VM, it's not long before my Host computer crashes. There's no crash if there's not a Virtual Memory problem. I'm at a loss to determine how to stop this.

Here's my specs...

Virtual Machine:
Windows XP Pro 32-bit
IDE controller
IO APIC enabled
1024 MB 'Base Memory' selected (plenty of virtual disk space available)
Processor set to '2'
VT-x/AMD-V and Nested Paging enabled

Host Computer:
Win 7 x64
8 GB RAM
Plenty of HDD space
1GB discrete video card
Quad 3.0 AMD CPU

Thanks,
Scott

Provided a log file please - as a zipped attachment. The VM log file is called "VBox.log", and can be found in the "Logs" subfolder of your VM folder.

mpack wrote:Provided a log file please - as a zipped attachment. The VM log file is called "VBox.log", and can be found in the "Logs" subfolder of your VM folder.

I have a number of log files in that folder; please see attached zip file/folder.

Thank you!

-Scott

cableghost2 wrote:I have a number of log files in that folder; please see attached zip file/folder.

The only one I asked for was "VBox.log", and the host ensures that you cannot have two or more files with that name in the same folder. However at least this gives me the chance to look at four sessions instead of just one.

And in fact, of the four sessions I only see one which ended in a crash, which occurred while the VM was attempting to resume from a saved state. Did you upgrade VirtualBox recently?

mpack wrote:

cableghost2 wrote:I have a number of log files in that folder; please see attached zip file/folder.

The only one I asked for was "VBox.log", and the host ensures that you cannot have two or more files with that name in the same folder. However at least this gives me the chance to look at four sessions instead of just one.

And in fact, of the four sessions I only see one which ended in a crash, which occurred while the VM was attempting to resume from a saved state. Did you upgrade VirtualBox recently?

I sent all because they had different dates...pardon, and thanks for reviewing the log(s).

Not certain if this makes a difference, but the crash occurs on the Host computer, as stated previously...not certain there would be any error written to the VB log, in such a case.

VB Update: I have 4.1.16, and see now there's an update to 4.1.22...I'll update and see if that resolves anything.

EDIT: I just had another BSOD event and in a review of the minidmp, I noticed one of the files involved was my antivirus. It seems there's a correlation between my antivirus (Bitdefender 2013) and Virtualbox when the VM Virtual Memory becomes lean, for whatever reason.

-Scott

cableghost2 wrote:Not certain if this makes a difference, but the crash occurs on the Host computer, as stated previously...not certain there would be any error written to the VB log, in such a case.

There wouldn't, but I could tell it happened because the log would terminate abruptly, which was only true of one out of the 4 logs provided, as I mentioned.

cableghost2 wrote:EDIT: I just had another BSOD event and in a review of the minidmp, I noticed one of the files involved was my antivirus. It seems there's a correlation between my antivirus (Bitdefender 2013) and Virtualbox when the VM Virtual Memory becomes lean, for whatever reason.

The VM virtual memory can't become "lean", if you mean what I think you mean. Aside from special cases I won't go into, VM RAM is allocated at startup and remains a fixed size and locked throughout. A virtual PC which runs low on memory will do what a physical PC will do: start thrashing (simulated) paged memory, and some poorly written guest applications may crash if they don't check return values properly.

I do not use antivirus inside VMs, so I can't discuss what effect BitDefender has.

mpack wrote:I do not use antivirus inside VMs, so I can't discuss what effect BitDefender has.

Clarification...Antivirus on my Host computer. It seems Bitdefender has an issue with the VM; possibly related to amount of resources, etc? The only time a BSOD occurs is when a notice of Low Virtual Memory on the VM is displayed. Shortly thereafter, the Host crashes. I can run multiple VM's all day otherwise, without Low Virtual Memory errors and no BSOD's.

I just spent some time uninstalling/reinstalling Bitdefender on my host. I'll report back here if there's another episode or not over the next week or so.

Thanks for your help/input.

-Scott