I think to be close,but it still does not work.These are the parameters
that I used :
/mnt/./monta-fisso
sleep 2
qemu-system-arm \
-enable-kvm -serial stdio \
-m 512 -M virt -cpu cortex-a15 \
-drive
file=/mnt/fisso/OS/FreeBSD/FreeBSD-13.2.qcow2,id=virtio-blk,if=none \
-device virtio-blk,drive=virtio-blk \
-device virtio-net,netdev=net0,mac="52:54:00:12:34:55" \
-netdev type=user,id=net0 \
-drive if=pflash,format=raw,file=/usr/share/AAVMF/AAVMF32_CODE.fd \
unfortunately :
[image: 2023-08-12_13-29.png]
where could be the error ?
On Sat, Aug 12, 2023 at 4:24 AM Валентин <val15032...@mail.ru> wrote:
> > -bios "*.fd"
>
> Try "-pflash *.fd" or "-drive if=pflash,format=raw,file=*.fd", if it works
> for Arm machines.
>
> I saw that OVMF developers didn't recommend to use "-bios" because image
> will be mounted as ROM and will not be able to save bios settings.
>
> With best regards,
> Valentine.
>
> -------- Исходное сообщение --------
> От: Mario Marietto <marietto2...@gmail.com>
> Дата: 12.08.2023 00:00 (GMT+03:00)
> Кому: Валентин <val15032...@mail.ru>
> Копия: Peter Maydell <peter.mayd...@linaro.org>, qemu-discuss@nongnu.org
> Тема: Re: Invalid accelerator kvm / error: kvm run failed Function not
> implemented ERRORS trying to virtualize a guest OS on the ARM Chromebook
> running with a relatively recent kernel version and KVM enabled
>
> I've found the right uefi file to use :
>
> /usr/share/AAVMF/AAVMF32_CODE.fd
>
> so now every piece is on the right place (I hope) :
>
> qemu-system-arm \
> -enable-kvm -serial stdio \
> -m 512 -M virt -cpu cortex-a15 \
> -drive
> file=/mnt/fisso/OS/FreeBSD/FreeBSD-13.2.qcow2,id=virtio-blk,if=none \
> -device virtio-blk,drive=virtio-blk \
> -device virtio-net,netdev=net0,mac="52:54:00:12:34:55" \
> -smbios type=2 -nodefaults \
> -netdev type=user,id=net0 \
> -bios "/usr/share/AAVMF/AAVMF32_CODE.fd"
> -append "earlyprintk=ttyAMA0 console=ttyAMA0 mem=512M \
> virtio_mmio.device=1M@0x4e000000:74:0 \
> virtio_mmio.device=1M@0x4e100000:75:1 \
> root=/dev/vda rw ip=dhcp --no-log"
>
> Does anyone still see some mistakes ?
>
>
> On Fri, Aug 11, 2023 at 9:26 PM Mario Marietto <marietto2...@gmail.com>
> wrote:
>
>> I think that I've found it :
>>
>> qemu-efi-arm/stable 2020.11-2+deb11u1 all
>> UEFI firmware for 32-bit ARM virtual machines
>>
>> On Fri, Aug 11, 2023 at 9:23 PM Mario Marietto <marietto2...@gmail.com>
>> wrote:
>>
>>> I remember. So,more or less,it should be something like this :
>>>
>>> qemu-system-arm \
>>> -enable-kvm -serial stdio \
>>> -m 512 -M virt -cpu cortex-a15 \
>>> -drive
>>> file=/mnt/fisso/OS/FreeBSD/FreeBSD-13.2.qcow2,id=virtio-blk,if=none \
>>> -device virtio-blk,drive=virtio-blk \
>>> -device virtio-net,netdev=net0,mac="52:54:00:12:34:55" \
>>> -smbios type=2 -nodefaults \
>>> -netdev type=user,id=net0 \
>>> -bios "OVMF_CODE.fd"
>>> -append "earlyprintk=ttyAMA0 console=ttyAMA0 mem=512M \
>>> virtio_mmio.device=1M@0x4e000000:74:0 \
>>> virtio_mmio.device=1M@0x4e100000:75:1 \
>>> root=/dev/vda rw ip=dhcp --no-log"
>>>
>>> The problem is that devuan does not offer the proper OVMF file,as you can
>>> see :
>>>
>>> # apt search ovmf
>>>
>>> Sorting... Done
>>> Full Text Search... Done
>>>
>>> ovmf/stable 2020.11-2+deb11u1 all
>>> UEFI firmware for 64-bit x86 virtual machines
>>>
>>> ovmf-ia32/stable 2020.11-2+deb11u1 all
>>> UEFI firmware for 32-bit x86 virtual machines
>>>
>>> These UEFI files are for x86-64 bit,so they are not good for armhf. Where I
>>> can find the right ones ?
>>>
>>>
>>> On Fri, Aug 11, 2023 at 8:33 PM Валентин <val15032...@mail.ru> wrote:
>>>
>>>> > between the qemu parameters I should put : initrd and vmlinuz,right ?
>>>>
>>>> Try "-kernel kernel.img -initrd initrd.img".
>>>> Oh, too late. :)
>>>>
>>>> By the way, I myself didn't experiment much with qemu-system-arm, but
>>>> people successfully ran hdd/iso images with EFI bioses (for Arm
>>>> architecture), if I'm not mistaken.
>>>>
>>>> With regards.
>>>>
>>>>
>>>
>>> --
>>> Mario.
>>>
>>
>>
>> --
>> Mario.
>>
>
>
> --
> Mario.
>
--
Mario.
