Sorry, there may be something wrong in the additions I made to qemu-5.1.0 code (I added a peripheral).
(this us while trying https://futurewei-cloud.github.io/ARM-Datacenter/qemu/how-to-launch-aarch64- vm/ ) So I tried now with original qemu-5.2.0 version. (arm virt machine) After I selected "Install Ubuntu" in the grub2 menu, (and I removed 'quiet' option) I see the boot message scroll up, and it gets stuck. [ 15.768125] evm: security.SMACK64MMAP [ 15.768363] evm: security.apparmor [ 15.768595] evm: security.ima [ 15.768802] evm: security.capability [ 15.769078] evm: HMAC attrs: 0x1 [ 15.794433] rtc-efi rtc-efi: setting system clock to 2021-06-11T07:50:20 UTC (1623397820) [ 16.003521] Freeing unused kernel memory: 6912K [ 16.077774] Checked W+X mappings: passed, no W+X pages found [ 16.079263] Run /init as init process Loading, please wait... /scripts/init-top/udev: line 24: /lib/systemd/systemd-udevd: not found Begin: Loading essential drivers ... /init: line 155: modprobe: not found /init: line 155: modprobe: not found /init: line 155: modprobe: not found /init: line 155: modprobe: not found /init: line 155: modprobe: not found /init: line 155: modprobe: not found /init: line 155: modprobe: not found /init: line 155: modprobe: not found done. Begin: Running /scripts/init-premount ... /scripts/init-premount/plymouth: line 36: /sbin/plymouthd: not found done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. This is the script I used. dd if=/dev/zero of=flash1.img bs=1M count=64 dd if=/dev/zero of=flash0.img bs=1M count=64 dd if=/usr/share/qemu-efi-aarch64/QEMU_EFI.fd of=flash0.img conv=notrunc wget http://cdimage.ubuntu.com/releases/20.04/release/ubuntu-20.04.2-live-server- arm64.iso qemu-img create ubuntu-image.img 20G qemu-system-aarch64 -nographic -machine virt,gic-version=max -m 512M -cpu max -smp 4 \ -netdev user,id=vnet,hostfwd=:127.0.0.1:0-:22 -device virtio-net-pci,netdev=vnet \ -drive file=ubuntu-image.img,if=none,id=drive0,cache=writeback -device virtio-blk,drive=drive0,bootindex=0 \ -drive file=ubuntu-20.04.2-live-server-arm64.iso,if=none,id=drive1,cache=writeback -device virtio-blk,drive=drive1,bootindex=1 \ -drive file=flash0.img,format=raw,if=pflash -drive file=flash1.img,format=raw,if=pflash Can anyone tell me what I can do here? Could be a network problem? Thanks! Chan Kim From: c...@etri.re.kr <c...@etri.re.kr> Sent: Friday, June 11, 2021 3:40 PM To: 'qemu-discuss@nongnu.org' <qemu-discuss@nongnu.org> Subject: RE: How should I give the command to install ubuntu on aarch64 virt machine? (error in arm_gicv3_cpuif.c during boot) I tried this page : https://futurewei-cloud.github.io/ARM-Datacenter/qemu/how-to-launch-aarch64- vm/ (last time my OS version was low so couldn't try). To my delight, It gives me grub2 menu and after a short while, it gives me this error message. ERROR:/home/ckim/prj1/QEMU/qemu-5.1.0/hw/intc/arm_gicv3_cpuif.c:1375:icc_eoi r_write: code should not be reached Bail out! ERROR:/home/ckim/prj1/QEMU/qemu-5.1.0/hw/intc/arm_gicv3_cpuif.c:1375:icc_eoi r_write: code should not be reached Aborted (core dumped) I tried with both with the recent patch to hw/intc/arm_gicv3_cpuif.c and without. Don't the developers need have a look into this case? Chan Kim From: c...@etri.re.kr <mailto:c...@etri.re.kr> <c...@etri.re.kr <mailto:c...@etri.re.kr> > Sent: Friday, June 11, 2021 3:04 PM To: 'qemu-discuss@nongnu.org' <qemu-discuss@nongnu.org <mailto:qemu-discuss@nongnu.org> > Subject: How should I give the command to install ubuntu on aarch64 virt machine? Hello all, To install ubuntu 20.04 on aarch64 virt machine, I tried this but it's stuck. I made the disk image using : qemu-img create -f qcow2 ubuntu-20.04.2-live-server-arm64.img.qcow2. And then did : qemu-system-aarch64 \ -M virt -cpu cortex-a72 \ -cdrom ubuntu-20.04.2-live-server-arm64.iso \ -drive "file=ubuntu-20.04.2-live-server-arm64.img.qcow2,format=qcow2" \ -m 2G \ -smp 2 \ ; Can anyone tell me what command option I should add or fix? And because I can't debug see the kernel program (because it's .iso file) it's very difficult to debug. Thank you! Chan Kim
