Alright, Fedi of the verse. Got a tech question for you that I seemingly cannot find an answer for, so I come to y'all nerds!
I'm currently trying to make an aarch64 VM on x86_64 hardware, which afaik, is entirely possible. I wanna emulate Windows on Arm, basically.
I'm using QEMU/KVM & Virt Manager, and I can get to the "posting" process, at which point it just... maxes out ONE core of my CPU, forever, until I close virt-manager. I've no idea why?
Any takers? #Tech#AskFedi#VirtualMachine
I haven't gotten this to work, but in my efforts to boot arm devices I believe more of the firmware tends to be on the storage devices than with x86 PCs.
My hunch is it's trying to read the next stage of the boot loader and not finding it.
This is based on how raspberry pis or the pinephone have extremely picky partioning layouts where certain software must be at specific offsets or the device wont boot.
I've only succeeded by getting an image from someone else.
I got a Debian arm64 image to run with this command
qemu-system-aarch64 -m 2G -M virt -cpu max \
-bios /usr/share/qemu-efi-aarch64/QEMU_EFI.fd \
-drive if=none,file=debian-13-nocloud-arm64.qcow2,id=hd0 -device virtio-blk-device,drive=hd0 \
-device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:5555-:22 \
-nographic
using this image file
https://cdimage.debian.org/cdimage/cloud/trixie/latest/debian-13-nocloud-arm64.qcow2
Poking around this or one of the other image files might help find some of the details about expected disk layout.
