VirtualBox Problem

[Virtual-Tester]

Hello,

Yesterday, I have installed VirtualBox (last version available today on your web site : V 5.0.12-104815) and I have followed and do correctly all the installation steps on a Windows XP PC and after on a second Windows 7 PC. On both I have set the parameters to boot first on the virtual DVD where I have set to do it from an .ISO file (Linux ubuntu last version also downloaded yesterday from the Ubuntu web site : V 14.04.3-desktop-i386). I set the memory size to 1 Gbyte and the virtual dynamically allocated disk (VDI mode) to 8 Gbytes. I modified nothing else on the Virtualbox parameters list.

I watched some videos where it is explained how to install and run the Virtualbox application where I see all is running well and I have done exactly the same installation process ! But....

On my 2 PCs I have the same problem : nothing happens when I start the Virtualbox and after about 1 minute a small window opens that tell me that there is nothing to boot (exit with error code 1 ; Result code : E_Fail ; Component : MachineWrap ; Interface : IMachine) ?

I have the log file of my trial and I can send it by email if necessary.

I have in both case two 32 bits CPU. My Windows XP version is Professionnal Service pack 3 with 3Gbytes RAM and my second PC with Windows 7 is the Familly Edition Premium Service Pack 1 with 3Gbytes RAM.

Can you help me to solve this problem ?

Thank you in advance.

[mpack]

Please pick one scenario (one host, one VM) and post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Add the zip as an attachment to a message here.

[Virtual-Tester]

Thank you for this answer.

As you asked, I attach here my log file and a screen copy of my configuration as a .JPG file

Hope it will help !

[mpack]

Moved to "Windows Hosts".

In fact I asked for "VBox.log", not some arbitrary other file that happens to have a similar extension. I didn't ask for a screenshot at all.

But we are where we are. I suggest that you try disabling your antivirus, see if that makes a difference.

[Virtual-Tester]

Sorry, but there is no option to select only what you ask in the log popoup or I miss something when I called the "Show Log" item (Ctrl+L) in the menu.

I am ready to give you exactly what you ask, but how to do and where is the VBox.log file ? In the directory \VirtualBox\ubuntu\logs I found one file named VBoxHardening.log which contain what I send you previously.

Then as you propose, I desactivated my Avira antivirus and I get the same error message when I try to start my Ubuntu Virtualbox.

[mpack]

Avira is one of the words I expected to hear: the last Avira update is known to have contained a bug - see the "Hardening" sticky topic at the top of this forum.

Since you have a Windows 7 host the other possibility is that you may also be suffering from certificates database corruption caused by a Windows update bug. This happened a long time ago now and I would have expected you to have noticed it before, but I'll pass it along anyway :-

KB3004394 fiasco
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html

KB3045999
http://www.infoworld.com/article/291459 ... albox.html

[Virtual-Tester]

I have opened the topic you link to me and I found this one :

"Re: Discussion of Problems due to Hardened Security
by loukingjr » 8. Dec 2015, 16:09

Right now the only way would be to roll back to VB 4.3.12 which does no hardening checks. Of course it also limits some of the newer guests you can run."

Then, I have downloaded and just installed the Virtualbox VB 4.3.12 version in order to make a new trial and.... it is now working with this old version of Virtualbox when I launch my Ubuntu VirtualBox !

Now, on the opened Virtual OS window I can answer to the first installation questions of Linux Ubuntu...

I hope my experience will help other users !!!

[loukingjr]

Good Grief. He had to pick my comment.

Just so it's understood. Rolling back to 4.3.12 is not a recommendation. It is just a means to avoid the problem. As I said, it also limits which guests one can run.

[Virtual-Tester]

You have 200% right.... the use of an old version is a pitty.... but it is not my fault if the last one does not work with an added function which seen not really necessary !

However, can you tell me what are the limitations in this old version compared to the last one ?

Thank you in advance

[mpack]

You can get that information by viewing the changelog in the downloads area.