virtualbox.org

Hi,

I did enter some details of my problem in another thread and got asked to create my own, so here goes.

My laptop (host) runs Windows 8.1 and my VPC (guest) also ran Windows 8.1 fine until about a couple of days ago. I think the cause was my host machine freezing while the guest was also running on it. I think I did a shutdown using the laptop's Power button (I know, naughty, but hey).

Now, my VPC doesn't even start and gets to this stage: when the 'spinning white dots' under the Windows logo stop moving. Then, that is it: it just freezes right there.

Interestingly, today when I tried to run my VPC, I got the following error message: and underneath this error message was the following: mpack asked me to provide the following data:

Size according to Windows Explorer on Host:
Size: 99.7 GB (107,099,455,488 bytes)
Size on disk: 99.7 GB (107,099,455,488 bytes)

In Settings>Storage it says:
Virtual Size: 100.00 GB
Actual Size: 99.74 GB
Details: Dynamically allocted storage

I am limited to 3 attachments, so in the next post ...

I will attach the first 2MB of the Frhed output file (2*1024*1024 B, to be precise), zipped using Winrar. I also attach the files VBox.log and VBox.png as suggested elsewhere.

To be continued ...

... continued ...

Here, I am finishing off the attachments for my previous post.

OK, so that's the VBox.log, VBox.png files and the first 2 MB of the Frhed output file.

If anything else is needed, please just holler and I will send.

Many thanks in anticipation of your help!

00:00:02.278204 Host RAM: 16273MB total, 2708MB available
00:00:02.885055 RamSize <integer> = 0x00000001b5800000 (7 340 032 000, 6 GB)
....
00:00:13.861501 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"

Memory overcommitted.

That's an awful lot of RAM being gobbled up somewhere. So it had nothing to do with disk corruption at all. It's a good job I asked for details (in other other thread) before wasting my time trying to find the corruption.

@Cyman. For future reference, the sign that virtual disk header corruption has occurred is that VirtualBox on the host refuses to open the virtual disk file. I.e. nothing like what was described here.

... and the reason why this VM has been running fine alongside several other applications for over a year and suddenly stopped working even when it's the only thing running might be ???

If you want Windows support you need to contact Microsoft. You can see for yourself what the log says.