Have trouble with qemu-efi-aarch64 run ARM64 VM

FlankerZzzz

New Member
Nov 5, 2023
19
0
1
Shanghai
Hi all, any suggestion would be greatly appreciated

ENV information at first;

PVE 8.0.4
Linux flanker 6.2.16-15-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-15 (2023-09-28T13:53Z) x86_64 GNU/Linux
qemu-efi-aarch64 2022.11-6 all UEFI firmware for 64-bit ARM virtual machines

The ISO for test, [uos-desktop-20-professional-1060-arm64-202309.iso]a kind of linux with GUI desktop much more like Ubuntu/deepin.

Problem1:
For now, i can successfully boot into GRUB menu(controllable,with button up/down)
However, when i get into the installation process(have GUI,usually I can control with my mouse and keyboard according to the experience with X64 version),
But now, I can't control with my my mouse and keyboard

First guess, probably due to the low efficiency by emulation with X64?I'm afraid not,cuz I keep waiting for hours, still not controllable,(usually when our mouse put on with some options will make it highlight, in this case I dont see this appearance,so I dont think thats cuz by low efficiency, its definitely not controllable! )

Problem2:
About efficiency, which mode is best? physical machine is operated by I9-9900T.
And when I modify the config with file cpu option like "cpu : cortex-a76" it just not work, i check the cmd line(qm showcmd xxx) still using the default mode "cortex-a57", I have to modify the cmdlind manually and boot the VM by shell cmdline, WHY????


config file and cmd line you may check below, any suggestion would be greatly appreciated, if any part make you confused I would like to explan more detail for you

ti925t root@flanker:~# qemu-system-aarch64 -cpu ? Available CPUs: a64fx arm1026 arm1136 arm1136-r2 arm1176 arm11mpcore arm926 arm946 cortex-a15 cortex-a35 cortex-a53 cortex-a55 cortex-a57 cortex-a7 cortex-a72 cortex-a76 cortex-a8 cortex-a9 cortex-m0 cortex-m3 cortex-m33 cortex-m4 cortex-m55 cortex-m7 cortex-r5 cortex-r52 cortex-r5f max neoverse-n1 pxa250 pxa255 pxa260 pxa261 pxa262 pxa270-a0 pxa270-a1 pxa270 pxa270-b0 pxa270-b1 pxa270-c0 pxa270-c5 sa1100 sa1110 ti925t

CONFIG FILE
1 #vmgenid%3A 8aca1e90-0dce-4282-b210-e5c13810c96b 2 #meta%3A creation-qemu=8.0.2,ctime=1699873054 3 arch: aarch64 4 bios: ovmf 5 cpu: neoverse-n1 6 cores: 8 7 efidisk0: ZFS_workspace:vm-200-disk-1,efitype=4m,pre-enrolled-keys=1,size=64M 8 hotplug: 0 9 memory: 4096 10 name: ARM 11 net0: virtio=0A:C4:33:23:AE:65,bridge=vmbr0 12 numa: 0 13 ostype: l26 14 scsi0: CoreDataBase:vm-200-disk-0,iothread=1,size=50G,ssd=1 15 scsi1: DSM_NFS_ISO:iso/uos-desktop-20-professional-1060-arm64-202309.iso,media=cdrom,size=3588150K 16 scsihw: virtio-scsi-pci 17 smbios1: uuid=8c1ea502-b56a-47e4-bc9e-4a72dc3807ac 18 sockets: 1 19 vga: virtio

cmdline
root@flanker:~# qm showcmd 200 vm 200 - unable to parse value of 'cpu' - Built-in cputype 'neoverse-n1' is not defined (missing 'custom-' prefix?) WARN: iothread is only valid with virtio disk or virtio-scsi-single controller, ignoring /usr/bin/qemu-system-aarch64 -id 200 -name 'ARM,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/200.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/200.pid -daemonize -smbios 'type=1,uuid=8c1ea502-b56a-47e4-bc9e-4a72dc3807ac' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//AAVMF_CODE.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/zvol/ZFS_workspace/vm-200-disk-1,size=67108864' -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/200.vnc,password=on' -cpu cortex-a57 -m 4096 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pcie.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pcie.0,addr=0x1f' -device 'usb-ehci,id=ehci,bus=pcie.0,addr=0x1' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'usb-kbd,id=keyboard,bus=ehci.0,port=2' -device 'virtio-gpu,id=vga,bus=pcie.0,addr=0x2' -device 'virtio-serial,id=spice,bus=pcie.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61000,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' -device 'virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:dc8a864c80c9' -device 'virtio-scsi-pci,id=scsihw0,bus=pcie.0,addr=0x5' -drive 'file=/dev/zvol/CoreDataBase/vm-200-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,rotation_rate=1' -drive 'file=/mnt/pve/DSM_NFS_ISO/template/iso/uos-desktop-20-professional-1060-arm64-202309.iso,if=none,id=drive-scsi1,media=cdrom,aio=io_uring' -device 'scsi-cd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap200i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'virtio-net-pci,mac=0A:C4:33:23:AE:65,netdev=net0,bus=pcie.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=300' -machine 'accel=tcg,type=virt+pve0'
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!