#qemu
1 messages · Page 1 of 1 (latest)
Eh can I dm u a pic or ill just upload it and share link
share a link
1sec
take your time
oh this is easy
ok
when you do qemu-img create, you're creating a virtual disk
so imagine you created a physical harddrive
when you launch the VM, you need to create a partition because as far as the VM is aware, the disk is completely fresh
after the partition is made, you can write a filesystem to it and you'll be on your way
ohhh
yeah there isnt a way it can access your main drive
do u think the command is full? i tried to ge tthe most out of the man but its huge
i think that looks good
there are a few guides online on making android vms with qemu that could help you out if you arent sure
oh
well im already following one to aim for arm emulation
so now i see if my own is good otherwsie i follow that too
lets see
thx for help btw ill let u kno
no problem, gl
Its stuck at formatting at 99 since 10 mins bro lmao is it supposed to do that
132% WTF
https://ibb.co/rbB9WH7 WTF IS THIS A JOKE
Bro
Its a virtual partition
Inside the image you created, not your actual system's /dev/sda
Why do you get surprised?
132%
Btw it wont finish
@abstract cargo i know there might be a particular reason you know you absolutely need Android-x86 virtual machine in QEMU to run an ARM Android app, but just in case there isn't or your current strategy doesn't end up working, I'd like you to be aware of the existence of other potential options, such as my personal favorite redroid https://github.com/remote-android/redroid-doc
Just, mount the hard disk, decompress the android filesystem in there, qemu chroot into the mounted hard disk and install grub or whatever bootloader It may include from the chroot
Qemu is trying to reformat because it cant install it there if not
Thx if it works with arm emulation ill read ab it after
yes it does
Choosing fat32 made it work anyway