VM's not started with VirtualBox 4.2.4

[GoogleCodeExporter]

Hi,
I have a Fedora 16 x64, and I just installed VirtualBox and 4.2.4-81684 
phpVirtualBox 4.2-4, updating the new extension-pack, and uninstalling previous 
versions.
But now I can not boot the vm, and logs you can not figure out why.
In the dialog box,
To see the tab "Remote Access", I had to reboot the system, since the vbox * 
restart services alone were not resolved.
When I press "Start VM", a window appears for a moment, that I can not decipher 
because it disappears immediately.
Access to phpVirtualBox, and management of VM seems to work properly.
For safety I also disabled the second network card.
I have no idea why does not work now.
What could be the reason?

Original issue reported on code.google.com by carlotto...@gmail.com on 3 Nov 2012 at 4:29

[GoogleCodeExporter]

I tried to revert to version 4.1.11 phpVirtualBox, and with this release, 
despite various error messages version, VMs are started regularly.

Original comment by carlotto...@gmail.com on 4 Nov 2012 at 10:35

[GoogleCodeExporter]

Hello,

Using virtualbox 4.2.4, try starting the VM with:

VBoxHeadless -s vm-name-here

and see if any error messages are printed.

Original comment by imooreya...@gmail.com on 5 Nov 2012 at 12:33

[GoogleCodeExporter]

Forgive the delay in my response ...

The virtual machines are started regularly, as indicated in the log:
--------
# VBoxHeadless --startvm /home3/vbox/vm01/vm01.vbox
Oracle VM VirtualBox Headless Interface 4.2.4
(C) 2008-2012 Oracle Corporation
All rights reserved.

VRDE server is listening on port 3389.
VRDE server is inactive.
# 
--------
By logging in RDP on port 3389, the machine is accessible and functional.

Original comment by carlotto...@gmail.com on 7 Nov 2012 at 5:26

[GoogleCodeExporter]

Hello,

Come to think of it, you should not see a window that pops up at all. Have you 
tried clearing your browser's cache?

Original comment by imooreya...@gmail.com on 7 Nov 2012 at 5:57

[GoogleCodeExporter]

I'm also seeing this. No problems with previous phpVirtualBox releases but 
after updating I can log in, modify VM's fine but cannot start them. As with 
Carlotto I see the quick popup when selecting the start button and I can start 
VM's manually via VBoxHeadless.

Solaris 11.1 with VB4.2.4(81684) and phpVirtualBox 4.2.4

Original comment by markc...@gmail.com on 9 Nov 2012 at 12:37

[GoogleCodeExporter]

Forgot to note: rolling back to phpVirtualBox 4.2.0b allows me to start VM's 
fine and I did try clearing browser cache when using phpVirtualBox 4.2.4

Original comment by markc...@gmail.com on 9 Nov 2012 at 12:44

[GoogleCodeExporter]

Yes, I also had deleted the browser caches, etc. and eliminate Cokie.
I can change all the settings of the VM, but I can not run them from 
phpVirtualBox.

Original comment by carlotto...@gmail.com on 9 Nov 2012 at 10:17

[GoogleCodeExporter]

Hello,

Does attempting to start the VMs not start them at all or do they just not show 
as started in the phpVirtualBox window? What web browser are you using?

Original comment by imooreya...@gmail.com on 9 Nov 2012 at 12:57

[GoogleCodeExporter]

Using Firefox 16.0.2 (updated yesterday).
From what I see, is made an attempt, but the VM will not start.
As I wrote initially, a message appears, but disappears immediately, and I can 
not understand what it means.
The statusbar does not indicate the start ...

Original comment by carlotto...@gmail.com on 9 Nov 2012 at 3:17

[GoogleCodeExporter]

I experienced the issue, too. After starting over with a fresh config.php I 
observed that the problem only occurs after adding "var $vmMemoryStartLimitWarn 
= true;" to the config. Removing this line from config.php seems to be a 
workaround.

Original comment by hfroe...@gmail.com on 10 Nov 2012 at 1:37

[GoogleCodeExporter]

I commented the lines that you mentioned, and in fact now everything seems to 
work.
The VMs now started regularly.
Thanks

Original comment by carlotto...@gmail.com on 10 Nov 2012 at 10:04

[GoogleCodeExporter]

Agree, commented out the vmMemoryStartLimitWarn entry and can start VM's 
without problems. 

Original comment by markc...@gmail.com on 11 Nov 2012 at 9:13

[GoogleCodeExporter]

Hi 

I can also confirm that commenting out the vmMemoryStartLimitWarn entry 
eliminate this issue and I can now start my VMs again from phpVirtualBox. 

My system is as follows:
- Linux Mint 13 (64-bit)
- VirtualBox 4.2.4
- phpVirtualBox 4.2-4
- PHP 5.3.10
- Apache 2.2.22
- Firefox 16

PS: I did raise a duplicate ticket 626, but I do not know how to close it. 
Sorry for the duplicate issue.

Original comment by mawcik...@gmail.com on 12 Nov 2012 at 2:18

[GoogleCodeExporter]

Hello!

Had same problem as topic.
Commenting vmMemoryStartLimitWarn has solved my problem with starting virtual 
machines via phpVirtualBox.

My system is:
- Windows 7 Pro SP1 x64
- VirtualBox 4.2.4
- phpVirtualBox 4.2-4
- PHP 5.4.3
- Apache 2.4.2
- Google Chrome 23.0.1271.64 m

Original comment by Nesmiya...@gmail.com on 12 Nov 2012 at 9:04

[GoogleCodeExporter]

Issue 626 has been merged into this issue.

Original comment by imooreya...@gmail.com on 12 Nov 2012 at 12:07

[GoogleCodeExporter]

Good catch. I'll have this fixed in the next version.

Original comment by imooreya...@gmail.com on 12 Nov 2012 at 12:07

[GoogleCodeExporter]

Original comment by imooreya...@gmail.com on 12 Nov 2012 at 12:30

• Changed state: Started
• Added labels: Type-Defect
• Removed labels: Type-Support_Request

[GoogleCodeExporter]

This has now been fixed

Original comment by imooreya...@gmail.com on 11 Jul 2013 at 5:54

• Changed state: Done