Custom Query (16363 matches)
Results (2500 - 2502 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15335 | invalid | Empty environment createvm --register fails to finish correctly | ||
| Description |
Oddly, if you run these repros steps fast enough (i.e. <5 seconds) it does not repro # repro steps mv ~/.VirtualBox ~/V.bk #for testing a clean env mv ~/.config/VirtualBox ~/Vconfig.bk #for testing a clean env VBoxManage createvm --name test --register # exit 0 sleep 10 VBoxManage modifyvm test --memory 8192 # fails, test not found ls -la ~/.VirtualBox # no VirtualBox.xml ls -la ~/.config/VirtualBox # has VirtualBox.xml, even shows where VBoxManage createvm --name test --register # fails, test already exists VBoxManage modifyvm test --memory 8192 # still fails, test not found # test is located, but doesn't seem to use this information # scenario 2, strange work around mv ~/.VirtualBox ~/V2.bk #for testing a clean env mv ~/.config/VirtualBox ~/Vconfig2.bk #for testing a clean env VBoxManage createvm --name test # don't register sleep 10 # to ensure we are hitting the bug VBoxManage registervm Machines/test/test.vbox # notice the path i used VBoxManage modifyvm test --memory 8192 # works # scenario 3, better workaround mv ~/.VirtualBox ~/V3.bk #for testing a clean env mv ~/.config/VirtualBox ~/Vconfig3.bk #for testing a clean env mkdir -p ~/.config/VirtualBox mkdir ~/.VirtualBox # just have the dirs appears to be good enough VBoxManage createvm --name test --register sleep 10 # again, just for testing the race bug VBoxManage modifyvm test --memory 8192 # works |
|||
| #15334 | fixed | vboxmanage startvm reports success even if virtualization is turned of and the vm won't start | ||
| Description |
vboxmanage startvm reports: VM successfully started, but the VM is not started, and if you try to start the vm from the GUI, you get an error message with the error code: VERR_VMX_MSR_ALL_VMX_DISABLED I'm running a Debian wheezy64 guest on Windows 7 SP1. So the workaround is to enable virtualization in the BIOS, but I would like to know that my script starting the server failed, instead of succeeded. |
|||
| #15333 | obsolete | I can not login into Ubuntu 14 after installing VBoxAdditions 5.0.18 -> obsolete | ||
| Description |
Hi, I know that there are some issues with VBoxAdditions 5.0.18. I want just to warn that after installing VBoxAdditions 5.0.18 in a new created virtual machine (RAM:2048 MB, 128Mb Graphic Memory, 2 processors MB, 3D Acceleration) with a fresh Ubuntu 14.04.2 installation, I was not able to login in anymore. I had to install VBoxAdditions 5.0.16 to fix the problem. |
|||

