Yo,
Anyone here use a VM (VirtualBox or VMware) and code on MacOS Catalina 10.15.x or Big Sur as guest ? Personally, I can't connect my iphone to xcode 11 and 12 (Iphone 5S: ios 14.4).
I tried multiple fix from the forum, as change the vmx file (skip-reset, skip-refresh, skip-setconfig" with the right pid and vid), set USB device to 2.0 (in VMware and VirtualBox), upgrade the IOS, but nothing was successful for now. However, the iphone is recognized and listed in the System information but nowhere else.
Somebody here have the same config and can use his iphone ? Had you do something in particular ?
Edit: The host is Windows 10
The only solution i found is to install "Catalina" and only Catalina, on VMware (with usb 2.0 of course). Don't use virtual box. Don't upgrade to big sur on Vmware lol. peace
I'm using Ubuntu 18.04 host with VMWare Workstation 15 Player Mac OS Catalina 10.15.2 as guest. I installed VMWare tools. My USB config is USB2.0, all three options is selected. I can see iPhone inside Mac OS System Report->USB, but Finder and Xcode cannot see iPhone. Host can successfully see it, if I disconnect. What may be the problem?
P.S. Used solution with usb.quirks.device0 = "0x05ac:0x12a8 skip-reset, skip-refresh, skip-setconfig", doesn't help.
I have been doing some googling to figure out a way to mirror my iPhone in Linux Mint 19, using either USB or WiFi-direct (AirServer-ish).
I've been trying several work-arounds, e.g. Linux' Totem (Video player), using Wine to install QuickTime Player (and other mirror-apps for Windows).
I've also tried using Darling (a solution for installing Mac OS apps on Linux), but it seems like Darling doesn't work with Linux Mint 19.
I was wondering if anyone could give a, more or less, detailed tutorial on making it possible to mirror iPhone on Linux (Mint 19, that is). I have no trouble using a commercial solution (licensed mirroring apps).
I found a working solution - using Google Chrome. It costs 4.99$ though.
Follow this link for a detailed description on installing, and using "Mirror to Windows PC":
https://itunes.apple.com/us/app/mirror-to-windows-pc/id1350663974?mt=8
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
I installed on PC/XP USB driver for Acer Tab A100 from acer.com
plugin A100 to PC
Hardware A100 regognized as ACER MTP
THEH:
"Cannot install this Hardware
There was a problem installing This hardware Acer MTP
An error occurred during the installation of the device
The required section was not found in the INF"
Please, explain where i'm wrong..
Thanks, Victor
I had some of the same problems on Win 7 x64. The solution boiled down to I went to Acer support and downloaded the USB drivers for the A500 and installed those. I can now see the device storage, the MicroSD storage on the device and connect with adb (currently debugging through the Eclipse plugin). So it looks like those drivers do the trick, I think their installer for the A100 USB drivers is just plain junk right now.
One problem remains: I was getting a .Net error with Acer Sync when I plugged in the device, but I really don't care about that, so I just uninstalled that bad boy.
Wasted the whole afternoon yesterday on the phone and chatting with Acer, don't make that mistake, when it comes to connecting up a dev environment they are clueless.
It´s the only way to connect it, installing USB drivers for the A500 requires you to have installed windows media player 11.