Hello. I've found this thread :
https://lists.gnu.org/archive/html/qemu-devel/2020-02/msg05759.html that may help me to fix a bug that I've found while I was working on my project,that I'm going to explain : I'm trying to virtualize FreeBSD 13.2 for arm 32 bit on my laptop ARM Chromebook where KVM is enabled,libvirt and virt-manager are installed from the source code and everything works great. The qemu version that I'm using is the 5.1 (I can't use a qemu version higher than 5.1 because the kvm support for arm 32 ended with 5.1) The Host OS is Devuan 5. Using these qemu parameters,FreeBSD is able to boot entirely : DISK=/Dati/img/FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img qemu-system-arm -enable-kvm -serial stdio -m 1024 -M virt -cpu cortex-a15 -drive if=pflash,format=raw,unit=0,file=$UEFICODE -drive if=pflash,format=raw,unit=1,file=$UEFIVARS -drive file=$DISK,media=disk,format=raw -device i82559b,netdev=net0,mac="52:54:00:12:34:55" -netdev type=user,id=net0 -device virtio-gpu-pci -usb -device nec-usb-xhci -device usb-kbd -device usb-mouse -device vmware-svga,id=video0,vgamem_mb=16 As you can see from this boot log messages : https://pastebin.ubuntu.com/p/DWggdRRxVv/ So,this argument is good : -drive file=$DISK,media=disk,format=raw \ but these arguments used by libvirt aren't able to boot FreeBSD because the virtio disk attached is not recognized (I also tried with a SATA disk and it is not recognized as well) : <disk type="file" device="disk"> <driver name="qemu" type="raw"/> <source file="/Dati/img/FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img"/> <target dev="vda" bus="virtio"/> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/> </disk> as you can see : [image: r/freebsd - [Bds ] Expand VenHw (93E34C7E-B50E-11DF-9223-2443DFD72085,00) -> <null string>] <https://preview.redd.it/cjpa8mmuk7rb1.png?width=1530&format=png&auto=webp&s=e9e969ca865c2dd7d88dc83c85ded492fce36316> What's the difference ? Do you have some vague idea about the reason ? I don't know if the cause is related to libvirt or to FreeBSD,so I'm trying to exclude one of these. Anyway,I tried to boot the image going inside the bios settings and trying to boot directly the image disk,but I saw this error : [image: r/freebsd - [Bds ] Expand VenHw (93E34C7E-B50E-11DF-9223-2443DFD72085,00) -> <null string>] <https://preview.redd.it/hdqf6254l7rb1.png?width=911&format=png&auto=webp&s=2abd87028c14871218110d469e2edfc1f53c7ce1> If you want to see the whole boot sequence I've recorded and stored a short video here: peek-2023-09-29-16-17_75xtIj7S.mp4 <https://drive.google.com/file/d/1kRoAFH_6DH-vNEmNmg4PEQ8lQmKZnUi2/view?usp=sharing> there could be a bug in qemu,but I haven't the right experience to be sure that the fix is the following one : [PATCH] hw/char/pl011: Enable TxFIFO and async transmission <https://lists.gnu.org/archive/html/qemu-devel/2020-02/msg05759.html> and I would like to know which version of qemu is affected by this bug and which version has been fixed. Thanks. -- Mario.
