Host machine was ported from 11.10 to 12.04 LTS (Xubuntu)
Virtualbox image is win7 x64
With upgrade /dev/vboxdrv was missing, so within synaptics I reinstalled:
virtualbox (4.1.12dsfg-2 not OSE)
virtualbox-qt 4.1.12dsfg
virtualbox-dkms 4.1.12dsfg
Then it works again but my windows is badly crashed. Once started and desktop icons pops out it's really slow and crash (network icon is also blocked)
I reinstalled guest additions, but does not make any difference.
Nothing is serious because I still have available snapshots.
I'm asking for advices, like for example how do I clean reinstall (clear parameters) vbox ?
Is there any workaround, or do I need to wait fresh 12.04LTS updates to fix this pbm by magic ?
I can confirm this bug on two of my Ubuntu 12.04 machines (i7 Desktop, Samsung Dual Core Laptop):
All my Windows (Win7, WinServer2003,WinServer 2008) 64bit guest machines which were working under Ubuntu 11.10 behave the same way after upgrading / reinstalling to Ubuntu Precise:
During guest bootup or shortly after bootup (sometimes I can even access the guest's desktop for a moment) the complete system host + guest freezes completly.
The Vbox.log doesnt contain any hint. Even a fresh install of Ubuntu Precise has the same error (with the same guest machines).
I have not found any combination of guest settings which prevents this freeze yet. Even using the OSE edition of Virtualbox 4.1.12-UbuntuR7724S has the same error.
The probably-related VirtualBox bug ticket says it is fixed in VirtualBox source, and also details a workaround via grub.
The Debian bug is here.
Hopefully the patch will be applied to Ubuntu-12.04 .
(This answer is also at: https://askubuntu.com/questions/130726/win-7-virtual-box-vm-fails-to-start-after-upgrade-to-12-04 )
I can't be sure that I was having the same problem, but I also just upgraded from ubuntu 11.10 to 12.04 and attempting to boot my virtual machine (xp 32bit) would cause the host to freeze.
The fix was to do the following:
Enable absolute pointing device (almost certainly wasnt this that fixed it but hey ho!)
Enable VT-x/AMD-V acceleration and nested paging (found under settings->System->Acceleration)
Disable video acceleration (again dont think it was this but I don't fancy fiddling now it works)
Hope this works for you too.
Related
Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.
I recently got a new computer - macbook, 2020, m1 chip, running Big Sur, and I wanted to install a windows 10 64-bit guest on virtualbox on it. However, no 64 bit options of any kind appear in the menu when I try to create a new machine. On my old computer, virtualbox still seems totally capable of creating and running a 64-bit guest. I noticed other people had this issue, but there was no clear explanation for how to fix this if the host is a mac. There seemed only to be fixes for Windows Users. Is there anyway to fix this?
I am running Ubuntu 14.04 LTS inside of VirtualBox. Functionally it is great, it is just very slow compared to 12.04. I've seen some posts about changing the desktop to XFCE and other desktops so that the OS runs faster. I like the 12.04 desktop and am wondering if it is possible to use the 12.04 desktop with 14.04. If so, how do I do this?
-Angus
For me, the newest edition of XFCE runs really fast, not slower than any previous version (much faster than default Ubuntu desktop).
To install older version of XFCE, choose version you want and download all the files you need from here
Installation manual I recommend is available on this site.
Hope this will help.
Trying to solve my problem I did the next:
Added 'Ubuntu_64' to config file.
Switched my WiFi off (saw this solution at Laravel forums) before 'vagrant up' execution.
Enabled GUI.
Rolled the VirtualBox and its extension back (also from Laravel forums).
The VMs which were successfully run with Vagrant are the Debian Wheezy 7.5 x32 built with puphpet and precise32.
As we can see, only x32 VMs could be run on my machine. I don't know why.
Here is my machine info:
OS: Ubuntu 12.04 64
Processor: AMD A8-4500M, 2 cores
Virtualization is enabled in BIOS. See screenshot similar to my BIOS view: screenshot
The latest Vagrant, VirtualBox and VirtualBox Extensions pack are installed
my user is added to virtualbox group
Thanks in advance.
Dude, your question helped me to fix my problem!
I was getting this connection timeout, turned my wifi off and bam! All working fine!
Double check if your ubuntu is really 64 bit.
I got some problems with some linux architectures for AMD in the pest!
There are a few and sometimes they can be a headache.. I think I got this problem with centos, it was i686 instead of simple x64. I don't really know the difference but what you can try doing is:
Instead of adding the homestead box (vagrant box add laravel/homestead)
Why dont you try adding a simple ubuntu-32 machine and then you run vagrant up.
I dont really know if it's going to work, but it's worth trying!
Thanks again for your answer, it really helped me
After a recent update of my OS from Windows 8 to Windows 8.1 my vagrant setup has stopped working.
I try running vagrant up on boxes and I get the following:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it to boot Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again.
I've tried updating vagrant. I've updated VirtualBox to 4.3. I've tried specifically setting VirtualBox to run as Administrator and in compatibility mode for Windows 8. That didn't work. Also tried compatibility mode for Windows 7. No dice.
Anyone else having these problems? Windows 8.1 is to new to find reports of this through Google searching. hopefully someone here can help out.
So, here is how I actually managed to fix it.
The newest versions of Vagrant (1.3.5) and VirtualBox (4.3.4) do not play together at all on Windows. So, I kept Vagrant 1.3.5 and went down to VirtualBox 4.2.2.
Once you have that, you have to get rid of a couple folders so that everything resets itself correctly:
Users\<<USERNAME>>\.VirtualBox
Users\<<USERNAME>>\.vagrant.d
Delete those before trying to run
vagrant up
With that, I was able to get everything running again. However, I have noticed that running vagrant up does go a tad slower than it had been previously. I can live with that though.
Thank you for all of your help and suggestions.
Ran into this problem and figured out the problem. Turns out I did not have the proper virtualization settings enabled in my bios.
Vagrant emitted a helpful error:
If the provider you're using has a GUI that comes with it, it is often
helpful to open that and watch the machine, since the GUI often has
more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.
Followed the instructions and tried to power on the vm via the GUI and was greeted with this error:
Was able to vagrant up after turning on the proper settings in my bios.
OS: Windows 8.1, Vagrant version: 1.3.5, Virtual Box version: 4.3.4
opening VirtualBox GUI may give you a better idea of what's going on. 4.3 has been recently released, so if you've updated, your issue may be related to that
Running Vagrant on Windows 8.1 has caused Windows 8.1 to reboot shortly after a vagrant up for me. I am able to recreate this every time.