VM cannot be started after upgrade to v5

[jof2jc]

Hello,

After installing new version 5, all my VMs cannot be started. It thrown this error:

Failed to open a session for the virtual machine srvubuntu.

Loading VD plugins failed (VERR_FILE_NOT_FOUND).

Failed to attach driver below us! File not found. (VERR_FILE_NOT_FOUND).

AHCI: Failed to attach drive to Port0 (VERR_FILE_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Anybody can help why and what to do?
Before I was using v4.3.28

Thanks

[Perryg]

Post the guests log file ( as an attachment )

[jof2jc]

Please find attached

[Perryg]

Couple of things. First you are over committing your RAM.

00:00:01.882990 Host RAM: 2718MB total, 999MB available
00:00:02.466668 RamSize <integer> = 0x0000000053200000 (1 394 606 080, 1 330 MB)


But the real issue seems to be with disk encryption. What VirtualBox version did you have before?

[jof2jc]

I used v4.3.28 before and everything was working fine..

I upgraded to v5 to test new encryption feature. I enabled encryption in one VM and then.... it just could not start..
But other VMs are just same like before (no changes made) but they also could not start. The error was the same as shown on my first post in this thread.

Please find attached another VM log (this was working fine in v4.3.28), after installed v5..it just could not start

Any ideas?

[Perryg]

Well the encryption issue is something I have not dealt with. I don't use it so I can't tell you what is going on. I do know that there is a lot of overhead running 64bit guests in a 32bit host and you are still over committing the memory. That said I don't know that encryption is your issue. You say that you added it to one ( I assume you did not test if it worked before you turned on the encryption ) and that the other guests don't work either. Sounds like the real issue is the achi portion. I would first remove VirtualBox reboot the host and install it again to see if that fixes some of you problems.

[jof2jc]

I moved back to v4.3 and everything worked fine (all VMs have no encryption). I adjusted RAM and installed v5 again, reboot host and still could not start at all for every VM.
Anybody has same experience?

I do know that there is a lot of overhead running 64bit guests in a 32bit host

My host is using Win 7 32bit. Is this the issue? But using VBox v4.3 all worked fine...

How is the steps to upgrade from v4.3 to v5? First, I installed v5 over existing v4.3. Secondly, I removed v4.3 first then installed v5. Both are not working for me...

Tks

[jof2jc]

I'm really stuck on this.. all VMs were working fine on v4.3. After installed v5, all VMs cannot start (failed to open session). I uninstalled/reinstalled, rebooted host for several times but didn't help. Then I installed back v4.3 and all VMs works fine.

Anybody have some hints?

Thanks

[noteirak]

The exact error message, VBoxSVC.log and the VM log file would help to know what happened. Nobody can help with such little information.

[jof2jc]

please find attached

[renatus]

I had exactly the same issue on Windows 7 32bit. (VirtualBox v5 runs without problems on my Windows 7 64bit host.)

It occurs to me that there's an issue with users privileges in the 32bit version.

Everything works well, when I run VirtualBox 5 as Administrator on the Windows 7 32bit host.

[mpack]

This is probably not the first hurdle, but you shouldn't gloss over the fact that you are still overcommitting RAM. The VM can never run reliably when you do that.

Basically you can't give 1GB to a VM on this host. You need to cut that in half, or free up a LOT of host memory. The rule of thumb is not to give the VM more than about a half or two thirds of available host RAM. Your host has 1041MB available.

On the other hand, 12MB for VRAM is probably too low.

[mpack]

As to the main problem, AFAIK the only file that the VM needs to open (after the .vbox file), is the VDI file "C:\Users\Fanny Lie\VirtualBox VMs\srvubuntu\srvubuntu.vdi". Can you demonstrate that this file exists?

Have you changed any of the default values in the Storage section of the VM settings?

[jof2jc]

Everything works well, when I run VirtualBox 5 as Administrator on the Windows 7 32bit host.

I run as Administrator, Ubuntu VM can start but failed/crashed --> General error mounting filesystems

Attached is the log.

I didn't change any default values in the Storage section. Total physical memory is 3072 MB, I allocated 1024 MB to a VM. Is that still over-committed?

I suspect the problem might be one of these:
-VBox 5 is not compatible with Win 7 32bit host?
-Ubuntu 14.04 is not compatible running on VBox 5? Or need further configs?

[mpack]

The second log doesn't show overcommittment, so it's much better. But, you are still allocating a high fraction of available host RAM (about 75%). It leaves your host with very little elbow room.