Hi all,
I have a Proxmox server 8.3-1 (21. November 2024), running on Intel Xeon X5667, and I am trying to install FreeBSD AARCH64 through emulation.
There is a nice guide on how to do this for Debian here.
I follow the guide but, instead of installing Debian, I install FreeBSD 14.2
All goes well, until the system starts - it gets stuck at "Generating RSA host key".
If I CTRL+C, after lots of investigation, I found out more bizarre problems - RSA signatures cannot be validated.
For example, if I issue the command pkg update, it fails completely:
For reference, here is how qemu is started by Proxmox:
Hmmm... it could be a bug in qemu by the Proxmox project but then, why does Debian Bookworm work without problems....
Additionally, if I try to run the very same FreeBSD distribution in qemu under MacOS with UTM, all runs fine - so, it is not a problem of the installation media.
Any ideas what I might be missing?
Thanks!
I have a Proxmox server 8.3-1 (21. November 2024), running on Intel Xeon X5667, and I am trying to install FreeBSD AARCH64 through emulation.
There is a nice guide on how to do this for Debian here.
I follow the guide but, instead of installing Debian, I install FreeBSD 14.2
All goes well, until the system starts - it gets stuck at "Generating RSA host key".
If I CTRL+C, after lots of investigation, I found out more bizarre problems - RSA signatures cannot be validated.
For example, if I issue the command pkg update, it fails completely:
For reference, here is how qemu is started by Proxmox:
/usr/bin/qemu-system-aarch64 -id 102 -name test,debug-threads=on -no-shutdown -chardev socket,id=qmp,path=/var/run/qemu-server/102.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/102.pid -daemonize -smbios type=1,uuid=e1b90329-623c-4bb6-b467-99cf4522cf8d -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/rpool/data/vm-102-disk-2,size=67108864 -smp 1,sockets=1,cores=1,maxcpus=1 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg -nographic -cpu cortex-a57 -m 4192 -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 -chardev socket,id=serial0,path=/var/run/qemu-server/102.serial0,server=on,wait=off -serial chardev:serial0 -device virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x3,free-page-reporting=on -iscsi initiator-name=iqn.1993-08.org.debian:01:b894dabdb95 -device virtio-scsi-pci,id=scsihw0,bus=pcie.0,addr=0x5 -drive file=/dev/zvol/rpool/data/vm-102-disk-1,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,bootindex=101 -drive 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=100 -netdev type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown -device virtio-net-pci,mac=BC:24:11:7E:82:8B,netdev=net0,bus=pcie.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=102 -machine accel=tcg,type=virt+pve0
Hmmm... it could be a bug in qemu by the Proxmox project but then, why does Debian Bookworm work without problems....
Additionally, if I try to run the very same FreeBSD distribution in qemu under MacOS with UTM, all runs fine - so, it is not a problem of the installation media.
Any ideas what I might be missing?
Thanks!