首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >Android-仿真器启动卡住“QEMU管道设备:rw,wait_event错误”

Android-仿真器启动卡住“QEMU管道设备:rw,wait_event错误”
EN

Stack Overflow用户
提问于 2015-10-20 09:41:47
回答 1查看 3.1K关注 0票数 2

我正在尝试编译金鱼android内核,并使用模拟器运行它。我做了谷歌告诉我的每件事。( Android内核编译和测试android Emulator,如何编译android goldfish 3.4内核并在仿真器上运行)。昨天,我按照提示,成功地使用了android仿真器。但是今天当我再次启动仿真器时,它不工作了。启动日志显示卡住"QEMU管道设备:rw,wait_event错误“,谁能帮我?由衷地提前感谢。

环境:VMware10、ubuntu14.04,goldfish3.4,ASOP_arm,Android4.4

引导日志的一部分:

代码语言:javascript
复制
Freeing init memory: 148K
type=1403 audit(1445259070.600:2): policy loaded auid=4294967295 ses=4294967295
SELinux: Loaded policy from /sepolicy
type=1404 audit(1445259070.620:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: /dev/hw_random not found
init: cannot open '/initlogo.rle'
EXT4-fs (mtdblock0): mounted filesystem with ordered data mode. Opts: barrier=1
EXT4-fs (mtdblock1): VFS: Can't find ext4 filesystem
fs_mgr: Running /system/bin/e2fsck on /dev/block/mtdblock1
e2fsck: executing /system/bin/e2fsck failed: No such file or directory
e2fsck: e2fsck terminated by exit(255)
EXT4-fs (mtdblock1): VFS: Can't find ext4 filesystem
fs_mgr: Cannot mount filesystem on /dev/block/mtdblock1 at /data
init: fs_mgr_mount_all returned an error
init: /dev/hw_random not found
init: Unable to open persistent property directory /data/property errno: 2
type=1400 audit(1445259074.030:4): avc:  denied  { entrypoint } for  pid=36 comm="init" path="/sbin/healthd" dev="rootfs" ino=1232 scontext=u:r:healthd:s0 tcontext=u:object_r:rootfs:s0 tclass=file
healthd: wakealarm_init: timerfd_create failed
healthd: BatteryVoltagePath not found
healthd: BatteryTemperaturePath not found
binder: 36:36 transaction failed 29189, size 0-0
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
type=1405 audit(1445259074.370:5): bool=in_qemu val=1 old_val=0 auid=4294967295 ses=4294967295
avc:  received policyload notice (seqno=2)
init: property 'sys.powerctl' doesn't exist while expanding '${sys.powerctl}'
init: powerctl: cannot expand '${sys.powerctl}'
init: property 'sys.sysctl.extra_free_kbytes' doesn't exist while expanding '${sys.sysctl.extra_free_kbytes}'
init: cannot expand '${sys.sysctl.extra_free_kbytes}' while writing to '/proc/sys/vm/extra_free_kbytes'
type=1400 audit(1445259075.370:6): avc:  denied  { 0x10 } for  pid=36 comm="healthd" capability=36  scontext=u:r:healthd:s0 tcontext=u:r:healthd:s0 tclass=capability2
eth0: link up
warning: `rild' uses 32-bit capabilities (legacy support in use)
shell@generic:/ $ QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
QEMU Pipe Device:rw, wait_event error
EN

回答 1

Stack Overflow用户

发布于 2015-10-21 09:02:34

我自己解决的。出现此错误的原因是android-模拟器的switch参数导致的。所以如果你这样做的话:

代码语言:javascript
复制
root@virtual-machine:/work/android4.4/out/target/product/generic# mv userdata.img userdata.img.bak

然后重新启动模拟器,模拟器就不能使用那个userdata.img了。这一切都是因为userdata.img。这件事的细节我不知道。也许将来会有人告诉我们。

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/33226672

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档