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?
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.
Setting up a Mac development build system on Windows using VirtualBox and Mojave. I got everything installed correctly, and it’s basically functioning fine, but whenever I try to build a project or do anything memory intensive in Xcode, it just freezes and beachballs. I never get any error messages or anything, and it does it on different types of projects. I have 8GB of RAM allocated, so I think that should be sufficient. Anyone running to this issue? Thanks!
Host: Windows 10
Guest: macOS Mojave
Switched to a High Sierra VM and it’s working alright now, guess the Mojave VM isn’t as stable or something.
I got an error whilst installing Windows 10 from .iso file as virtual machine via Parallels 9 on OSX 10.10 which read something like: Media driver missing. It leaves you in a loop which requires you to add the drivers. But you cannot install any cause there are no suggestions.
Now the main issue seemed that the iso wasn't on a bootable device which is what most sources say you need to do. Obviously that seemed like an unneeded step and i got the installation going. Mostly because you were already inside the installation that had been booted in the first place.
Software i use:
OSX 10.10 (latest)
Parallels 9 (latest updates, i know Parallels 10 is out)
Windows 10 iso from http://preview.windows.com
VM setup with iso from external HD (NTFS) and locally stored.
So what to do?
(see my answer below)
What you can do is shut down your virtual machine (close out the installation first to make sure). Go to the settings of the parallels by clicking:
-> Menubar: Virtual Machine
-> Configure
-> Hardware tab
-> CD/DVD 1 (where your image is inserted)
-> Location dropdown
-> Select IDE 0:1 (instead of SATA 0:1)
-> Restart VM
Done!
Installation will continue normally and you can start trying Windows 10 from Parallels 9 on your Mac.
I'm not sure if this works for Parallels 10 (i think so) and i'm also not sure if this will work for other (older) Windows installations. But to remove the steps required for making a bootable disk is good enough for me.
You can tell to parallels to install it as windows xp and it will work fine.
This issue occurs, also, when you have a MacBook Pro (10,2 or similar) without a DVD drive, while installing Windows 10 via USB.
So, during the Parallels 10 or 11 Guest setup, choose to configure using an ISO instead.
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.
I am using win7. I wish to use Fedora on my machine, but don't know just how much I will be needing either of my OS. I wish to install Ferdora and configure it as a dual boot system.
At the same time, when time calls for it, I want to run the same Fedora installation as a virtual machine on top of win7. Is there a way to do it?
VMWare Workstation supports this, but I've never tried in Windows.
Here's an article on their site (it discusses VMWare 5 and they're now on 7.1, so a newer one can probably be unearthed):
http://www.vmware.com/support/ws5/doc/ws_disk_dualboot.html