@Michael, I can reproduce easily with the latest 20.04 installer for arm64, and running it on qemu with:
fallocate -l 8G disk.img && sync qemu-system-aarch64 -machine virt -cpu cortex-a57 -smp 2 -m 4096 \ -device virtio-gpu-pci \ -usb -device qemu-xhci,id=xhci -device usb-mouse -device usb-kbd \ -bios /usr/share/AAVMF/AAVMF_CODE.fd \ -netdev user,id=net0,hostfwd=tcp::8022-:22 \ -device virtio-net-pci,netdev=net0 \ -drive if=virtio,file=disk.img,format=raw \ -cdrom ubuntu-20.04.2-live-server-arm64.iso \ -serial mon:stdio -semihosting
Sometimes, the crash generator crashed itself, maybe that's the reason for the traceback not being the same as the file I attached.
Is the snap with the fix going to be available in some channel soon?
@Michael, I can reproduce easily with the latest 20.04 installer for arm64, and running it on qemu with:
fallocate -l 8G disk.img && sync
- device virtio-gpu-pci \
- usb -device qemu-xhci,id=xhci -device usb-mouse -device usb-kbd \
- bios /usr/share/ AAVMF/AAVMF_ CODE.fd \
- netdev user,id= net0,hostfwd= tcp::8022- :22 \
- device virtio- net-pci, netdev= net0 \
- drive if=virtio, file=disk. img,format= raw \
- cdrom ubuntu- 20.04.2- live-server- arm64.iso \
- serial mon:stdio -semihosting
qemu-system-aarch64 -machine virt -cpu cortex-a57 -smp 2 -m 4096 \
Sometimes, the crash generator crashed itself, maybe that's the reason for the traceback not being the same as the file I attached.
Is the snap with the fix going to be available in some channel soon?