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 enable
> Which version of qemu are you using ?Try Debian Armhf > distribution:https://deb.debian.org/debian/dists/bookworm/main/installer-armhf/current/images/netboot/For > example, mini.iso (minimal size, network boot) boots with:1) machine virt;2) > cpu cortex-a15;3) efi bios AAVMF32_CODE.fd.With best regards,Valentine.
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 enable
> it does not boot,but I get the UEFI shell.But, by the way, if you're able to > boot UEFI bios with "-enable-kvm", at least it probably means that KVM is > working.With best regards,Valentine.
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 enable
> Which version of qemu are you using ?Version 5.1, aarch64 (but I tried 32-bit > virt machine too, so it should work with qemu-system-arm).So far I've tried > to boot with 64-bit EFI bios > (https://packages.debian.org/sid/misc/qemu-efi-aarch64) from rEFInd project's > CD: https://sourceforge.net/projects/refind/files/ (look for > refind-cd-*.zip).It boots.You are using 32-bit machine and emulator, > therefore you won't be able to boot it because the CD only contains Aarch64 > loader.But you could see the content of CD in EFI shell even with 32 bits, it > displays mounted CD and filesystem as "FS0:".But I'm not sure that it's > possible to make CD iso from SD image.With best regards,Valentine. Исходное сообщение От: Mario Marietto Дата: 13.08.2023 00:57 (GMT+03:00) Кому: Валентин Копия: qemu-discuss@nongnu.org, Peter Maydell Тема: 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 Which version of qemu are you using ?On Sat, Aug 12, 2023 at 10:40 PM Mario Marietto wrote:'ve removed the line : -drive file=/mnt/fisso/bhyve/img/FreeBSD/FreeBSD.img,id=virtio-blk,if=none \and I tried to boot only the boot image file :qemu-system-arm \ -enable-kvm -serial stdio \ -m 512 -M virt -cpu cortex-a15 \ -drive if=pflash,format=raw,unit=1,file=/usr/share/AAVMF/AAVMF32_VARS.fd \ -drive if=pflash,format=raw,unit=0,file=/usr/share/AAVMF/AAVMF32_CODE.fd \ -boot d -cdrom /mnt/fisso/OS/ISO/BSD/FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img \ -device virtio-blk,drive=virtio-blk \ -device virtio-net,netdev=net0,mac="52:54:00:12:34:55" \ -netdev type=user,id=net0 \ -device virtio-gpu-pci \ -device vmware-svga,id=video0,vgamem_mb=16it does not boot,but I get the UEFI shell. I see that the image that I have put there as cdrom is not detected. Maybe I should convert the img file to iso.On Sat, Aug 12, 2023 at 10:30 PM Валентин wrote:And one more thing, to enable keyboard and maybe mouse, try to add: -usb -device nec-usb-xhci \-device usb-kbd -device usb-mouse After that I'm able to input commands in EFI shell. With best regards, Valentine.-- Mario. -- Mario.
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 enable
And one more thing, to enable keyboard and maybe mouse, try to add: -usb -device nec-usb-xhci \-device usb-kbd -device usb-mouse After that I'm able to input commands in EFI shell. With best regards, Valentine.
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 enable
> Can you give me the qemu parameters that you use ? they should not be so > different from armhf. I'm running it with: qemu-system-aarch64 \-M virt -cpu > cortex-a15 -m 128 -net none \-k en-us \-device virtio-gpu-pci \-drive > if=pflash,readonly=on,format=raw,file=AAVMF32_CODE.fd \-L > /path/to/bioses/directory/ \-vnc unix:vncsocket \-qmp > unix:qmpsocket,server,nowait \-monitor vc \-overcommit mem-lock=off -rtc > base=localtime -nodefaults But you should probably skip the parts "-vnc", > "-qmp" and "-monitor" because they should be related to my particular setup > (I'm using it on a phone, the build is from limboemu/limbo project on > GitHub). The OVMF bios is from Debian distribution. I didn't connect any hdd > images, but at least the machine displays EFI shell prompt, so the bios > starts. Try to start the machine without KVM, maybe it causes problems? With > best regatds, Valentine.
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 enable
> qemu-system-arm -enable-kvm -serial stdio -m 512 -M virt -cpu cortex-a15 > -drive ... Try to explicitly add video adapter: "-device virtio-gpu-pci". > With best regards, Valentine.
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 enable
> -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 Дата: 12.08.2023 00:00 (GMT+03:00) Кому: Валентин Копия: Peter Maydell , 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.fdso 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@0x4e00:74:0 \ virtio_mmio.device=1M@0x4e10: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 wrote:I think that I've found it :qemu-efi-arm/stable 2020.11-2+deb11u1 all UEFI firmware for 32-bit ARM virtual machinesOn Fri, Aug 11, 2023 at 9:23 PM Mario Marietto 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@0x4e00:74:0 \ virtio_mmio.device=1M@0x4e10: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 ovmfSorting... DoneFull Text Search... Doneovmf/stable 2020.11-2+deb11u1 all UEFI firmware for 64-bit x86 virtual machinesovmf-ia32/stable 2020.11-2+deb11u1 all UEFI firmware for 32-bit x86 virtual machinesThese 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 Валентин 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.
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 enable
> 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.
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 enable
> I've thought to compile it directly on the devuan 4 installed on the ARM > chromebook. If you have native Arm toolchain, it's even simpler then – just > try to "./configure" and "make". QEMU v5.1 will compile with at least GCC > v4.8. With best regards, Valentine.
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 enable
Hello, I tried to compile executable for Arm64 some time ago. There is no special branch of QEMU for Arm hosts, you just need to find a toolchain to cross-compile for Arm. Try to look at Linaro site, they have complete cross-configured GCC toolchains. And then try script like this (note the LINARO_PATH variable, it should point to toolchain's bin directory):#!/bin/shexport LINARO_PATH="/linaro121_64/bin"export ARCH="arm"export LINARO_HOST="$ARCH-none-linux-gnueabihf"export CROSS_COMPILE="$LINARO_PATH/$LINARO_HOST-"export PATH="$PATH:$LINARO_PATH"./configure --host=$LINARO_HOST \--cc="$CROSS_COMPILE"gcc \--target-list=x86_64-softmmu \--cpu=$ARCH --with-coroutine=sigaltstack \--cross-prefix=$CROSS_COMPILE \--disable-plugins --disable-containers --disable-vhost-user --disable-libvduse --disable-tpm --disable-attr --disable-malloc-trim --disable-oss --disable-iconv \--extra-cflags="" \--extra-ldflags=""In short, you'll need to disable everything for a start, configure and see if you have a minimal set of development libraries, needed to compile QEMU (at least Glib, pixman and probably SDL2 if you won't connect via VNC). The configure script will tell you if some libraries are missing. If configure will succeed, try to "make". And maybe you'll need to add "--static" configure option (I didn't try it because my setup needs shared libraries). With best regards, Valentine.
Re: QEMU built-in RAM block device
Thank you very much. If RAM block device driver doesn't exist yet, there is probably no point to implement it this way, since most OSes have ability to mount RAM disks. I just thought that it existed and I could miss it. The issue #1797 is also mine, I'll reply there. Thank you kindly! With best regards, Valentine. On 03.08.2023 Hanna wrote:> No, we currently have no such block device. It’s effectively been asked > for in https://gitlab.com/qemu-project/qemu/-/issues/1797, too, but so > far I don’t know of any plans to implement it.>> Hanna
