blocks|key|114314|text|删除kvm内核模块(使用'sudo+rmmod+kvm_intel+kvm')可以同时运行Virtualbox和Android仿真器，但Android仿真器在这种设置下的性能非常差。如果可能，最好关闭Virtualbox模拟器并通过运行'sudo+/etc/init.d/vboxdrv+stop‘卸载它的驱动程序(vboxdrv)。谷歌在其Android+Emulator+page上关于Linux的部分推荐了这个“解决方案”。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|114315|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/tools/devices/emulator.html#accel-vm^0|4R|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

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 <a href="http://developer.android.com/tools/devices/emulator.html#accel-vm" rel="noreferrer">Android Emulator page</a> in the section about Linux.

blocks|key|331737|text|我也遇到了同样的VirtualBox冲突。通过使用不同于"x86“的ABI解决了这个问题(在我的例子中是armeabi-v7a)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|331738|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got the same VirtualBox conflict.
Solved it by using ABI different from "x86" (armeabi-v7a in my case)

blocks|key|331697|text|我停止了使用VirtualBox运行的虚拟机。这使得错误消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|331698|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I stopped the virtual machines I had running with VirtualBox. This made the error disappear.

blocks|key|114333|text|您还可以在仿真器设置中将CPT/ABI设置从x86更改为arm。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|114334|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You also can change CPT/ABI setting from x86 to arm in emulator settings.

blocks|key|114408|text|通过使用Genymotion而不是标准的Android模拟器，我最终解决了这个问题。除了没有这种冲突，它比普通的仿真器快几倍。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|114409|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|114543|text|另一种解决方案是通过vagrant-libvirt插件使用libvirt支持的流浪者。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|114544|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/vagrant-libvirt/vagrant-libvirt^0|A|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Another solution is to use libvirt backed vagrant using <a href="https://github.com/vagrant-libvirt/vagrant-libvirt" rel="nofollow noreferrer">vagrant-libvirt</a> plugin.

blocks|key|114445|text|我通过安装HAXM+6.1.2解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|114446|有关详细信息，请参阅以下链接:-+https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11|offset|length|114447|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11^0|0|H|2G|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I resolved it by installing HAXM 6.1.2.

Please refer to the following link for details :- <a href="https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11" rel="nofollow noreferrer">https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11</a>

blocks|key|114503|text|在某些情况下，我们需要保持virtualbox机器的启动和运行，因此让所有的virtualbox机器继续运行，切换到物理移动设备来测试您的应用程序，而不是模拟器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|114504|如果你使用的是原生的react或者你真正的android/ios设备，你可以使用expo。|114505|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|332089|text|对于那些在Linux上进行开发并被许多运行在virtualbox中的后端系统所困扰的人来说，一个简单的解决方案是创建一个virtualbox+X86+Android虚拟机，并在从本地主机通过PAT隧道传输的NAT接口上公开5555端口。不需要慢臂AVD，不需要libvirt/流浪汉，更不用说杀死kvm了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|332090|​|332091|📷|atomic|offset|length|332092|332093|那就让亚行知道吧。|332094|$+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|code-block|syntax|javascript|332095|然后，在Android+Studio中按run或debug，将在该VM上部署和执行。您可以完全控制Android+Studio调试器。|332096|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1123c21512a628f98f3a180b022504d4.png|imageAlt^0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|13|8|@]|9|@$G|14|H|15|1|16]]|A|$]]|$1|I|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|19|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1A|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z|10|-4]]]]

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!
<a href="https://i.stack.imgur.com/UM6Dm.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/UM6Dm.png" alt="enter image description here" /></a>
Then let adb know about it
<pre><code>$ 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
</code></pre>
Then, pressing run or debug, in Android Studio will deploy and execute on that VM.
You have complete control under Android Studio debugger.

blocks|key|331994|text|这可能超出了主题，因为OP在同一时间请求VirtualBox+%2B+KVM，但它仍然可能是解决办法:我正在寻找一种在Ubuntu18.10+x64上启动Windows7和AVD的方法。关闭KVM不是一个选项，因为AVD的性能对我来说非常重要。我已经通过Virtual+Machine+Manager+(virt-manager软件包)安装了Windows7，现在AVD和Windows7都是硬件加速的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|331995|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

Whenever I have Virtualbox running, I cannot start an Android emulator image (and vice versa). The error message in the AVD manager is

<pre><code>ioctl(KVM_CREATE_VM) failed: Device or resource busy
ko:failed to initialize KVM
</code></pre>

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.

Android emulator and virtualbox cannot run at same time

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

每当我运行Virtualbox时，我都不能启动Android模拟器镜像(反之亦然)。AVD管理器中的错误消息为ioctl(KVM_CREATE_VM) failed: Device or resource busyko:failed to initialize KVM我怎样才能让两者同时运行呢？这是一个Ubuntu 64位，所有涉及的软件都是最新发布的版本。

问Android模拟器和virtualbox不能同时运行
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android模拟器和virtualbox不能同时运行EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android模拟器和virtualbox不能同时运行
EN