On Mon, 27 Jul 2020, Maxime Villard wrote:
"-cpu max" is triggers this bug. It was working fine a few months ago.
Probably because of the CPU_ID_CORTEX_P test at the top of armgic_match. The entire dmesg would have been helpful.
So I switched to cortex-a53, with this time networking: qemu-system-aarch64 -M virt -cpu cortex-a53 -m 4g -drive if=none,file=arm64.img,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=mynet0,hostfwd=tcp:127.0.0.1:2222-:22 -device e1000,netdev=mynet0 -bios QEMU_EFI.fd And it gives a deadlock at boot time: Adding interface aliases:. Waiting for duplicate address detection to finish... Starting dhcpcd. [UNRESPONSIVE, HITTING "ENTER" DOES NOT EVEN DISPLAY '\n']
Not sure if qemu's e1000 driver ever worked here. Try e1000e or virtio-net instead.