FreeBSD 15 for Aarch64 fails to run Xorg #7598
Description
Describe the issue
Hi there,
I have a FreeBSD 15 Aarch64 VM running (default settings) in text mode. However, I wanted to run Xorg on this, so on a fresh install of FreeBSD 15 I did as root:
cp /etc/pkg/FreeBSD.conf /usr/local/etc/pkg/repos/FreeBSD.conf
edited the copied FreeBSD.conf to replace all two occurrences of quarterly with latest to get the most recent software available:
vi /usr/local/etc/pkg/repos/FreeBSD.conf
initialized the ports system:
pkg update && pkg upgrade
and finally installed xorg:
pkg install xorg
which completed just fine.
However, trying to start an Xorg session with startx failed:
In /var/log/Xorg.0.log it says:
(EE) scfb(0): scfb_mmap: Invalid argument:
Trying to debug this I exported the QEMU command from the VM's settings and tried to run it in MacPorts QEMU. The command (slightly edited the paths to point to copied disk images) looks like this:
qemu-system-aarch64 -L /Users/lars/Library/Containers/com.utmapp.UTM/Data/Library/Caches/qemu -S -spice unix=on,addr=5250B3E0-6F0D-40E2-A2C8-5D5DD2585227.spice,disable-ticketing=on,image-compression=off,playback-compression=off,streaming-video=off -chardev spiceport,name=org.qemu.monitor.qmp.0,id=org.qemu.monitor.qmp -mon chardev=org.qemu.monitor.qmp,mode=control -nodefaults -vga none -device virtio-net-pci,mac=7A:50:20:29:45:F5,netdev=net0 -netdev user,id=net0 -device virtio-ramfb -cpu host -smp cpus=4,sockets=1,cores=4,threads=1 -machine virt -accel hvf -drive if=pflash,format=raw,unit=0,file.filename=/Users/lars/Library/Containers/com.utmapp.UTM/Data/Library/Caches/qemu/edk2-aarch64-code.fd,file.locking=off,readonly=on -drive "if=pflash,unit=1,file.filename=/Users/lars/Library/Containers/com.utmapp.UTM/Data/Documents/FreeBSD 15 ARM64 Gershwin.utm/Data/efi_vars.fd" -m 16384 -audiodev spice,id=audio0 -device intel-hda -device hda-duplex,audiodev=audio0 -device nec-usb-xhci,id=usb-bus -device usb-tablet,bus=usb-bus.0 -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -device qemu-xhci,id=usb-controller-0 -chardev spicevmc,name=usbredir,id=usbredirchardev0 -device usb-redir,chardev=usbredirchardev0,id=usbredirdev0,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=usb-controller-0.0 -device usb-storage,drive=drive8D368A2E-C67B-473A-B472-5B139E7A584C,removable=true,bootindex=0,bus=usb-bus.0 -drive if=none,media=cdrom,id=drive8D368A2E-C67B-473A-B472-5B139E7A584C,readonly=on -device virtio-blk-pci,drive=driveAC21E650-11F8-4910-ACF8-C64315C48634,serial=AC21E65011F84910ACF8,bootindex=1 -drive "if=none,media=disk,id=driveAC21E650-11F8-4910-ACF8-C64315C48634,file.filename=AC21E650-11F8-4910-ACF8-C64315C48634.qcow2,discard=unmap,detect-zeroes=unmap" -device virtio-serial -device virtserialport,chardev=org.qemu.guest_agent,name=org.qemu.guest_agent.0 -chardev spiceport,name=org.qemu.guest_agent.0,id=org.qemu.guest_agent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -device virtserialport,chardev=charchannel1,id=channel1,name=org.spice-space.webdav.0 -chardev spiceport,name=org.spice-space.webdav.0,id=charchannel1 -name "FreeBSD 15 ARM64 Gershwin" -uuid 5250B3E0-6F0D-40E2-A2C8-5D5DD2585227 -device virtio-rng-pci
when I tried to run it it resulted in this error:
qemu-system-aarch64: -device virtio-ramfb: 'virtio-ramfb' is not a valid device model name
Googles AI says on this: "The error -device virtio-ramfb : virtio-ramfb is not a valid device model name usually occurs because virtio-ramfb is not a standard built-in QEMU device in official upstream releases. It is often a custom or specialized model used in specific forks like UTM (for macOS/iOS) or specific ARM/RISC-V environments."
So I suspect the 'virtio-ramfb' used by UTM's QEMU to be the cause of this.
Here is the corresponding FreeBSD bug ticket on this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283646
Configuration
- UTM Version: Version 4.7.5 (118) (AppStore version)
- macOS Version: 15.7.3 (24G419)
- Mac Chip (Intel, M1, ...): M4 max
Debug log
For all issues related to running a VM, including crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.
Upload VM
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.