Page 1 of 1
More issues with Big Sur
Posted: 19. Jul 2021, 20:33
by Franklin S Werren
Well;
Still having issues with BigSur
Thought I had it fixed but after a bad shut down it, I am back to trying to figure out what happen.
But I did includ a log of both my VM start ups...
Franklin Werren N2JYG
Re: More issues with Big Sur
Posted: 20. Jul 2021, 16:48
by Franklin S Werren
Update!!!!!!
I got Virtual Box to work with Big Sur and here is the easy fix.
Go to this site:
https://brew.sh/
Then copy this line into a Terminal Window
/bin/bash -c "$(curl -fsSL
https://raw.githubusercontent.com/Homeb ... install.sh)"
Then install Virtual Box with this line:
brew install --cask virtualbox
You do not need to uninstall your existing Virtual Box
You will need to re-install the Virtual Box Extention Pack from
https://download.virtualbox.org/virtual ... ox-extpack
If you use it.
Bingo!!! Virtual Box Works as advertised ......
Franklin S Werren N2JYG
Re: More issues with Big Sur
Posted: 21. Jul 2021, 17:22
by scottgus1
I deleted your duplicated topic on the above: duplicates are against forum rules.
Interesting solution, though.
Re: More issues with Big Sur
Posted: 14. Sep 2021, 16:10
by dtran
WIth recently Big Sur 11.6 update, I'm no longer able to run VBoxManage in the command line.
Code: Select all
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "7ec52ef5-daac-4cfd-a356-26ce50cc5ef9", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'ACS-3636_default_1631546276308_27804' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
These steps no longer worked:
https://github.com/hashicorp/vagrant/is ... -727812340
Please advice.
Is there a workaround? Thank you.