I have recently switched from Windows to linux, Windows 10 pro to Ubuntu version 22.04 LTS to be exact. I now wanted to install Unity on my computer.
The problem is that when I open the Unity Hub, all I see is a grey screen with the sub Menus having no options when hovering over them.
What I found is that it apparently is this way because Unity only works on ubuntu 16.04 and 18.04.
However, I have found people that claim it works on versions 20.04 and 22.04. Having received contradictory information, I dont know what the truth is, so now I'm here.
I try to create Linux Kali on Mac with using VirtualBox. And I want to run android emulator on this Virtual Box.
My VirtualBox settings look like:
After all, I installed android-studio and I've tried to run android emulator but it gives error like:
A critical error has occurred while running the virtual machine and machine
execution has been stopped...
VirtualBox is not recommended.
it seems that android emulator inside vm's using VirtualBox has
historically had a lot of issues. It seems most of the recommendations
are to either use VMWare, Hypver-V, or just install the emulator
natively on your base machine.
Ring Zero Labs
Installed VMWare and solved.
i wanted to take my first steps into a linux dist. So I got myself Parallels Desktop and downloaded Linux Mint. Now im stuck because I don't have internet connection inside my VM. The network seems to be established correctly and i can ping anything but not browse. Anyone knows this problem and can help me out? Parallels Network Settings are using "Shared Network". Im using Mint 20 and because of the problem im not able to install the necessary "parallels tools"
It seems that its a problem with the version of parallels desktop from the app store. I tried my luck with the normal version of parallels desktop downloaded from their website and after setting up my linux everything works now.
CentOS system installed on VMware 15.5 worstation which installed on my windows system computer. several days ago, it worked well.But there was an error appeared when starting CentsOS in the VMware workstation shown as the picture below enter image description here
Whenever I have Virtualbox running, I cannot start an Android emulator image (and vice versa). The error message in the AVD manager is
ioctl(KVM_CREATE_VM) failed: Device or resource busy
ko:failed to initialize KVM
How can I make both run at the same time?
That is a Ubuntu 64 bit, all involved software is of the latest released version.
Removing the kvm kernel modules (using 'sudo rmmod kvm_intel kvm') makes it possible to run the Virtualbox and the Android emulator at the same time but the performance of the Android emulator in such a setup is extremely bad. If possible it is better to shutdown the Virtualbox emulator and unload its driver (vboxdrv) by running 'sudo /etc/init.d/vboxdrv stop'. Google suggests this "solution" on its Android Emulator page in the section about Linux.
I got the same VirtualBox conflict.
Solved it by using ABI different from "x86" (armeabi-v7a in my case)
I stopped the virtual machines I had running with VirtualBox. This made the error disappear.
I had the same problem on Ubuntu 13.10.
Try to remove kvm and kvm_intel kernel modules.
To do this:
Stop all emulators.
Run command: 'sudo rmmod kvm_intel kvm'
Without these kernel modules Virtualbox and Android emulators can work at the same time.
BTW, I do not know why the modules are loaded.
There is finally a fix for this.
Follow these steps for macOS:
In Android Studio Go to Tools -> Android -> SDK Manager
Confirm you have the latest version of Intel Emulator Accelerator HAXM installed (v6.1.1) .
Go to the extras directory of the Android SDK location displayed in the preferences. On MacOS you can do this:
open ~/Library/Android/sdk/extras
Install the HAXM packing by opening IntelHAXM_6.1.1.dmg, then opening IntelHAXM_6.1.1.mpkg in the mounted folder, and following the installer instructions.
Follow these steps for Windows:
In Android Studio Go to Tools -> Android -> SDK Manager
Confirm you have the latest version of Intel Emulator Accelerator HAXM installed (v6.1.1) .
Go to the extras directory of the Android SDK location displayed in the preferences. Something like:
C:\Users\<username>\AppData\Local\Android\sdk\extras
In that directory is some kind of file like intelhaxm-android.exe. Run it.
You also can change CPT/ABI setting from x86 to arm in emulator settings.
I finally made this problem obsolete by using Genymotion instead of the standard Android emulator. Besides not having this conflict, it is several times faster than the normal emulator.
Another solution is to use libvirt backed vagrant using vagrant-libvirt plugin.
For those who are developing on Linux and are stuck with a host of back-end systems running inside virtualbox, a simple solution is simply to create a virtualbox X86 Android VM and expose the 5555 port on the NAT interface tunnelled from localhost through PAT.
No need for slow arm AVD, no need for libvirt/vagrant let alone killing kvm!
Then let adb know about it
$ adb tcpip 5555
restarting in TCP mode port: 5555
$ adb connect 127.0.0.1
connected to 127.0.0.1:5555
$ adb devices
List of devices attached adb server
* daemon started successfully
emulator-5554 device
Then, pressing run or debug, in Android Studio will deploy and execute on that VM.
You have complete control under Android Studio debugger.
Though it's a workaround either, but definitely better than disabling KVM as everyone suggesting.
Just run the virtualbox guest in KVM instead. For example (kvm here is just a script running a qemu-system-x86_64 -enable-kvm):
kvm Win7.vdi -boot c -m 2G -vga qxl
In some cases, we need to keep virtualbox machines up and running therefore let all the virtualbox machines keep running, switch to physical mobile device to test your application instead of emulator.
you can use expo if you are doing with react-native or your real android/ios device.
I resolved it by installing HAXM 6.1.2.
Please refer to the following link for details :- https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11
This might be out of topic, due to the fact that OP requested VirtualBox + KVM in the same time, but still, it might be the workaround:
I was looking for a way to launch Windows 7 and AVD on Ubuntu 18.10 x64. Turning off KVM is not an option due to the fact that performance of AVD is critical to me. I have installed Windows 7 via Virtual Machine Manager (virt-manager package) and now both the AVD and Windows 7 are hardware accelerated.
Here is how solved this issue, using vagrant and it's two plugins 'libvirt' and 'mutate':
Open terminal and set environment variables:
export VAGRANT_DEFAULT_PROVIDER=libvirt
export VAGRANT_HOME=/home/directoryToStoreVagrant/
VBoxManage list vms
Now copy the a the code obtained from last command like
"c1530713-aec2-4415-a6b5-b057928c7e5f" and use in the following:
vagrant package --base c1530713-aec2-4415-a6b5-b057928c7e5f
--output window7.box
vagrant init window7
vagrant up window7 --provider=libvirt
vagrant box list
You need to install some vagrant plugins like libvirt and
mutate. Mutate will convert .box to libvirt VM:
vagrant plugin install vagrant-libvirt
vagrant plugin install vagrant-mutate
Converting vagrant box to libvirt:
vagrant mutate window7_.box libvirt
Now you can initialise the vagrant VM. If any error persist move to
edit your Vagrant file. Like for me I uncomment the line starts with
config.vm.network and then run command below:
vagrant up --provider=libvirt
This is how I was able get rid of this error completely