Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 days ago.
Improve this question
I'm trying to create a virtual machine with virtualbox(Oracle) and macOS ventura using Windows 11 and Ryzen 7 5700x...
with this codes its workigs... but stuck on OS install.... it stuck on boot loop...
VBoxManage.exe modifyvm "mac" --cpuidset 00000001 000106e5 00100800
0098e3fd bfebfbff VBoxManage setextradata "mac"
"VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
VBoxManage setextradata "mac"
"VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage
setextradata "mac" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct"
"Iloveapple" VBoxManage setextradata "mac"
"VBoxInternal/Devices/smc/0/Config/DeviceKey"
"ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "mac"
"VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 VBoxManage
modifyvm "mac" --cpu-profile "Intel Core i7-6700K" VBoxManage
setextradata "mac" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
Suggestion how to fix?
Thanks
stucked on boot loop
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 months ago.
Improve this question
wsl is already installed on my computer.
I enter the following commands on powershell
wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.
It looks like that wsl 2 has been installed
but
wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.900
The first line say that I have WSL 1.0.3
I don't know if this give the right result. The last line says that I have windows 10 although I have windows 11
See the page Install Linux on Windows with WSL:
Check which version of WSL you are running
Upgrade version from WSL 1 to WSL 2
AFAIK, if you use an up to date version of Windows 10 (or Windows 11), and the Virtual Machine Platform Windows Feature is enabled, then WSL 2 is installed on your system. Virtual Machine Platform enables virtualization support required by WSL 2.
When you attempt to enable WSL 2 when Virtual Machine Platform is not yet enabled, you will receive the following error message:
Please enable the Virtual Machine Platform Windows feature and ensure
that virtualization is enabled in the BIOS.
Since you did not receive this error message, I think that everything is fine and you now have WSL 2.
Run the following command and check the VERSION column:
wsl -l -v
The command lists Linux distros you have installed for WSL. If you see version 1, then run the following command to change it to WSL 2:
wsl --set-version MyDistro 2
Replace MyDistro placeholder with an actual name.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I just upgraded my mac OS from Catalina to Big Sur. My vagrant used to be working normally before and then I encountered this issue. (Vagrant version: 2.2.13)
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
When I tried to start it manually on the VirtualBox this is the return message:
Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
Does anyone have a clue on how to fix this issue?
I had the same issue after updating to Big Sur. I downloaded the latest versions of Vagrant, Virtualbox and VirtualBox Extension Pack. Actually, I don't know if installing the Extension Pack was necessary.
And in the system preferences of MacOS, in Privacy and Security, I had to approve the update from Oracle.
After these steps, I was able to 'vagrant up' again.
Updating VirtualBox to 6.1.16 did it for me.
I did not update Vagrant
Updating VirtualBox to 6.1.16 did it for me, not working with 6.0.24.
Also reinstalled Vagrant but not sure if necessary.
The allow oracle button in privacy and security never showed up in my settings.
Eventually I got it working by booting in recovery mode and running the command
csrutil clear
After that I was able to allow oracle in security and privacy.
Fixed by reinstalling both Vagrant and VirtualBox :)
I Also just ran into this issue today after updating to Big Sur. Using homebrew to update VirtualBox (v. 6.1.16) and approving in Security & Privacy did not resolve the problem. I had to give VirtualBox Full Disk Access in the Privacy Tab of Security & Privacy to solve this.
The last comment form the virtualbox forum is what helped me with the last step.
https://forums.virtualbox.org/viewtopic.php?f=39&t=98763#p488757
Upgrading virtual box to latest version (6.1.16 at this moment) works for me. Didn't had to upgrade vagrant version.
vagrant up worked right after upgrading the virtual box.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I do not have cmake in terminal, so I went to it's webpage download page, downloaded the "Mac OSX 64/32-bit Universal (for Intel, Snow Leopard/10.6 or later)" item, and the installer does nothing! I tried all 3 of them!!!
can anyone help me install cmake ????? huge thanks in advance!
EDIT:
system info:
OSX 10.8.4 Build 12E55
processor 2.5 GHz Intel Core i5
You can install cmake via Homebrew.
Install Homebrew
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Install cmake via Homebrew
brew install cmake
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have tried all alternatives and resources that I found on internet to achieve to change screen resolution in my MacOS X guest. I have the latest VirtualBox version (4.1.22) and I have MacOS X 10.6.3 Snow Leopard running in a vm guest.
Some solutions that don't work for me are:
Tuning virtual machine settings:
Adding and in the .vbox file, or running these two commands:
vboxmanage setextradata "MAC OS X" "CustomVideoMode1" "1360x768x32"
vboxmanage setextradata "MAC OS X" "GUI/CustomVideoMode1" "1360x768x32"
Editing Guest OS boot configuration:
Modify /Library/Preferences/SystemConfiguration/com.apple.boot.plist with these lines:
<key>Kernel Flags</key>
<string>"Graphics Mode"="1360x768x32"</string>
<key>Graphics Mode</key>
<string>1360x768x32</string>
Any other suggestion, something that I was missing.
Thanks in advance,
I'm battling this as well. I've seen a third option mentioned in some places: in addition to the CustomVideoMode1 there's a VBoxInternal2/EfiGopMode parameter which can be set to one of six fixed resolutions:
VBoxManage setextradata "vmname" VBoxInternal2/EfiGopMode 3
The possible values for EfiGopMode are:
0: 640x480
1: 800x600
2: 1024x768
3: 1280x1024
4: 1440x900
5: 1920x1200
Not tried this method yet myself because I want to go to 1600x1200...
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I was able to install and use IBM DB2 Express-C 9.5.2. beta in Mac OS X Snow Leopard with no trouble at all. In Mac OS X 10.7 Lion, though, installation using the db2setup script fails with:
DBI1189E There has been an attempt to use db2setup on an image for a platform that does not match the current platform 'Darwin [x86_64]' on which it is being run.
How can I work around this to install DB2 Express-C on Lion?
edit: moved answer to answers
The problem is that the db2setup script does not properly recognize the architecture x86_64 reported by
uname -m
To make the installation script work, edit the db2setup script and change this:
"Darwin")
case ${OSM?} in
i*86)
INSTALLDIR="${PROGDIR?}/db2/macos/install"
PLATNAME="MacOS" ;;
esac ;;
"HP-UX")
to this:
"Darwin")
case ${OSM?} in
i*86)
INSTALLDIR="${PROGDIR?}/db2/macos/install"
PLATNAME="MacOS" ;;
x86_64)
INSTALLDIR="${PROGDIR?}/db2/macos/install"
PLATNAME="MacOS/x86_64" ;;
esac ;;
"HP-UX")
Now run db2setup. The script should recognize the architecture and proceed with installation as normal.
Also note that enabling the root account, see the instructions on: http://support.apple.com/kb/HT1528?viewlocale=en_US