how to get a more stable version of the qemu driver for the usb 3 controller.

Hello to everyone. I'm trying to connect two kinects 2 to a two different qemu-kvm virtual machines. On the first one VM I have passed the IGD video card from ubuntu to windows 10,following this tutorial : https://blog.tmm.cx/2020/05/15/passing-an-intel-gpu-to-a-linux-kvm-virtual-machine/ and o

Error : EGL_NO_SURFACE, EGL_NO_SURFACE when I try to compile qemu on the jetson nano

Hello. I’m trying to compile qemu 6.0 (but also 5.2) from source code on my jetson nano,but I get this error : $ git clone https://github.com/qemu/qemu.git $ cd qemu $ git checkout v5.2.0 $ git submodule init $ git submodule update --recursive $ ./configure --prefix=/opt/qemu-5.2.0 --target-list=

Hda and error 43 go hand in hand when I try to virtualize windows 10 with bhyve on FreeBSD

Hello, We are a team composed of 2 hypervisor programmers,one system administrator and one nvidia developer and we are working together to improve the bhyve hypervisor for freebsd. We have been able to enable the passthrough for the most powerful nVidia graphic cards within Linux as guest os and n

https://superuser.com/questions/1691407/trying-to-passthru-my-rtx-2080-ti-to-a-windows-7-x64-bit-vm-using-virt-manager-o

e installed the ssh server inside windows 7 and from Linux I tried to connect to that server and I've issued the following command : mario@MARIETTO-PC C:\Users\mario>wmic path win32_videocontroller get configmanagererrorcode ConfigManagerErrorCode 0 12 because I wanted to check the status of my

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

Hello to everyone. This will be a long and high technical post about a nice toy that comes back from the past. So,keep ready to brush up some old knowledge. I've enabled KVM on a more recent kernel version,to be precise on the 5.4.244,on the old ARM Chromebook model xe303c12,following mainly thi

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

the devuan 4 host os that I have installed I'm using kernel 5.4,that's lower than 5.7,so the qemu support for it should be there. point 3) if I use the "virt" board,does the KVM acceleration work ? thanks. On Thu, Aug 10, 2023 at 7:07 PM Peter Maydell wrote: > On

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

t the same error : qemu-system-arm: invalid accelerator kvm On Thu, Aug 10, 2023 at 7:27 PM Mario Marietto wrote: > ---> You can't use KVM with the vexpress-a15 board. The only Arm guest > machine that will work with KVM is the "virt" board. > > point 1) > > On

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

need is the place where I should grab the source code of qemu for armhf. I also need the compilation parameters :) thanks... On Fri, Aug 11, 2023 at 12:01 PM Peter Maydell wrote: > On Thu, 10 Aug 2023 at 18:28, Mario Marietto > wrote: > > > > ---> You can't use KVM w

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

r armhf ? 5.1 should still have the support for kvm. I've also been unlucky because devuan 4 has 5.2 by default. It's only one minor version than 5.1. And anyway,if the version was good, I could not enjoy myself with this new challenge. On Fri, Aug 11, 2023 at 12:48 PM 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 enable

ok. Can you share the github address ? I found the source code for x86-x64 but not for armhf. On Fri, Aug 11, 2023 at 1:49 PM Peter Maydell wrote: > On Fri, 11 Aug 2023 at 12:19, Mario Marietto > wrote: > > Anyway,can you tell me where is the branch 5.1 for the qemu source code

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

/vda rw ip=dhcp --no-log" I used -M virt,because you said that -M vexpress-a15 is not good. I hope that -cpu cortex-a15 is good,anyway. On Fri, Aug 11, 2023 at 2:36 PM Paul Menzel wrote: > Dear Mario, > > > Am 11.08.23 um 14:29 schrieb Mario Marietto: > > ok. Can you sh

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

On Fri, Aug 11, 2023 at 3:00 PM Mario Marietto wrote: > ok thanks. Are the following parameters correct still today ? something is > missing ? thanks. > > a) to compile qemu : > > ./configure \ > --target-list=arm-softmmu \ > --audio-drv-list=alsa,pa \ >

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. On Fri, Aug 11, 2023 at 3:20 PM Валентин wrote: > 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-

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 made some progress,but unfortunately I've got an error : root@devuan:~/Desktop/qemu-v5.1.0# ./configure --target-list=arm-softmmu --enable-opengl --enable-gtk --enable-kvm --enable-guest-agent --enable-spice --audio-drv-list="oss pa" --enable-libusb no errors here. root@devuan:~/Desktop/qemu-v

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

n for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. On Fri, Aug 11, 2023 at 6:04 PM Mario Marietto wrote: > I made some progress,but unfortunately I've got an error : > > root@devuan:~/Desktop/qemu-v5.1.0# ./configure --target-list=arm-softmmu > --enable-opengl --enable-gtk --ena

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

mg". On Fri, Aug 11, 2023 at 6:17 PM Peter Maydell wrote: > On Fri, 11 Aug 2023 at 17:05, Mario Marietto > wrote: > > > > I made some progress,but unfortunately I've got an error : > > > > root@devuan:~/Desktop/qemu-v5.1.0# ./configure > --target-list=

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

ed my vms,neither with qemu,nor with bhyve. On Fri, Aug 11, 2023 at 7:44 PM Peter Maydell wrote: > On Fri, 11 Aug 2023 at 18:27, Mario Marietto > wrote: > > > > ok. I've been lucky. Qemu compiled successfully. Now I'm going to > execute this command : > >

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 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,ne

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 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 wrote: > I remember. So,more or less,it should be something like this : > > qemu-system-arm \ > -enable-

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

yAMA0 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 : &g

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

ounted 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 enable

I tried with this : 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/

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. On Sat, Aug 12, 2023 at 6:35 PM Mario Marietto wrote: > I tried with this : > > qemu-system-arm \ > -enable-kvm -serial stdio \ > -m 512 -M virt -cpu cortex-a15 \ >

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

'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/A

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 ? 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-s

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

Thanks. It's good as a try,but my final goal is to virtualize FreeBSD. On Sun, Aug 13, 2023 at 8:13 AM Валентин wrote: > > Which version of qemu are you using ? > > Try Debian Armhf distribution: > > https://deb.debian.org/debian/dists/bookworm/main/installer-armhf/current/images/netboot/ > > Fo

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

=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 but the error is always there. On Sun, Aug 13, 2023 at 2:54 PM Mario Marie

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

nt), jid 0, uid 0: exited on signal 11 pid 88 (sh), jid 0, uid 0: exited on signal 11 pid 15 (sh), jid 0, uid 0: exited on signal 11 the installation stops here,the error is : Guest disabled display. I think that this error should be fixed by asking help on the FreeBSD forum because it is related to it

[Bds ] Expand VenHw (93E34C7E-B50E-11DF-9223-2443DFD72085,00) ->

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 wher

Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

Hello. I want to emulate Android 14 by KonstaKang using qemu-system-aarch64 and as model virt on Ubuntu 24.04 x64 bit installed on my PC (Intel I9 + RTX 2080 ti). I've chosen the parameters to boot it,according with the files provided by that version of Android,that you can find here : https://k

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

] __primary_switched+0xc4/0xd0 [0.00] Rebooting in 5 seconds.. [0.00] Reboot failed -- System halted On Sat, Aug 24, 2024 at 6:36 PM Philippe Mathieu-Daudé wrote: > Hi Mario, > > Cc'ing Sergey & qemu-arm@ list. > > On 24/8/24 18:11, Mario Marietto wrote: >

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

sumed that 0.fat is initrd... On Sun, Aug 25, 2024 at 1:26 PM Peter Maydell wrote: > On Sun, 25 Aug 2024 at 11:45, Mario Marietto > wrote: > > > > Please look at this example : > > > > qemu-system-aarch64 \ > > -smp 4 \ > > -m 2048 \ > &g

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

ta [0.895672] Waiting 5 sec before mounting root device... [6.132758] RAMDISK: Couldn't find valid RAM disk image starting at 0. [6.133865] Waiting for root device /dev/vdd1... [ 10.994096] platform gpio-keys: deferred probe pending On Sun, Aug 25, 2024 at 2:30 PM Mario M

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

wc2,dr_mode=peripheral [cm4] dtoverlay=dwc2,dr_mode=otg [all] include config_user.txt On Sun, Aug 25, 2024 at 2:44 PM Mario Marietto wrote: > Appending the root device does not change the scenario : > > qemu-system-aarch64 \ > -smp 4 \ > -m 2048 \ &g

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

nit: Reboot ending, jumping to kernel [5.091556] reboot: Restarting system with command 'bootloader' On Sun, Aug 25, 2024 at 3:31 PM Mario Marietto wrote: > The file below is called config.txt and it's available only if Android is > installed physically. I don't

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

nel/common not found thanks. On Sun, Aug 25, 2024 at 5:58 PM Mario Marietto wrote: > ok,I've understood that initrd is ramdisk.img,so : > > qemu-system-aarch64 \ > -smp 4 \ > -m 2048 \ > -cpu cortex-a72 \ > -machine virt \ > -

Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

Hello. I would like to emulate Android 14 on my Ubuntu 24.04 OS X64 bit using qemu-system-aarch64. I tried using the following parameters : qemu-system-aarch64 \ -smp 4 \ -m 2048 \ -cpu cortex-a72 \ -M virt \ -device virtio-gpu-pci,xres=1024,yres=768 \

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

img: machine type does not support if=sd,bus=0,unit=1 qemu-system-aarch64: -drive if=sd,format=raw,file=/mnt/zroot-133/_OS/Android/rpi4/vendor.img: machine type does not support if=sd,bus=0,unit=2 On Mon, Sep 2, 2024 at 4:00 PM Peter Maydell wrote: > On Mon, 2 Sept 2024 at 14:50, Mario Marietto &

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

Failed to read vbmeta partitions. [2.046632] init: bool android::init::BlockDevInitializer::InitDevices(std::set): partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 On Mon, Sep 2, 2024 at 4:05 PM Mario Marietto wrote: > ---> I think it would be better

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

n, 2 Sept 2024 at 15:06, Mario Marietto > wrote: > > > > ---> I think it would be better to fix the guest > > > > I have no idea what to do. Please elaborate more. > > I know very little about Android -- you'd need to talk to > somebody who does to find out

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

e same ? Thanks. On Mon, Sep 2, 2024 at 10:23 PM Pierrick Bouvier < pierrick.bouv...@linaro.org> wrote: > > > On 9/2/24 13:20, Pierrick Bouvier wrote: > > On 9/2/24 12:53, Mario Marietto wrote: > >> Hello Pierrick. > >> > >> With Cuttlefish can

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

"127" qemu: uncaught target signal 6 (Aborted) - core dumped 09-02 23:27:31.223 2729990 2729990 E launch_cvd: subprocess.cpp:207 Subprocess 2730018 was interrupted by a signal 'Aborted' (6) 09-02 23:27:31.224 2729990 2729990 E launch_cvd: main.cc:323 assemble_cvd returned -1 On Mon

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

as /mnt/zroot-133/_OS/Android/aosp_14/android-image/bin/aarch64-linux-gnu/qemu/qemu-system-aarch64: error while loading shared libraries: libncursesw.so.6: cannot open shared object file: No such file or directory On Mon, Sep 2, 2024 at 11:30 PM Mario Marietto wrote: > Something is not right

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

You seem to be involved in this old project. You don't seem to be so unexperienced of qemu and Android : https://www.cnx-software.com/2014/08/23/how-to-build-and-run-android-l-64-bit-arm-in-qemu/ On Mon, Sep 2, 2024 at 7:33 PM Peter Maydell wrote: > On Mon, 2 Sept 2024 at 18:12, Mario

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

ne used (which disk goes where), and iterate from that. > > Instructions: > > https://linaro.atlassian.net/wiki/spaces/QEMU/pages/29464068097/Run+Android+using+QEMU > > As you'll see, I could not get a direct graphic output, but using > scrcpy, it worked well for me. Hope it can fit

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

thing related to that,the last chance I have is to try qemu 5.1.0 instead of 5.0. On Tue, Sep 3, 2024 at 5:32 PM Peter Maydell wrote: > On Tue, 3 Sept 2024 at 16:25, Mario Marietto > wrote: > > > > Hello. > > > > Actually I'm using my Jetson Nano and I'm

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

It was only an hypothesis : https://pastebin.ubuntu.com/p/zjjgXf8xXM/ On Tue, Sep 3, 2024 at 5:56 PM Peter Maydell wrote: > On Tue, 3 Sept 2024 at 16:46, Mario Marietto > wrote: > > > > Nope,I don't need 9pfs. I'm trying to understand what parameter I had > ena

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

> Hopefully you are right, but unlikely: > https://github.com/antmicro/kvm-aosp-qemu/compare/fdd76fecdd...5.0.0-kvm-aosp What do you mean ? On Tue, Sep 3, 2024 at 7:51 PM Philippe Mathieu-Daudé wrote: > On 3/9/24 19:17, Mario Marietto wrote: > > @Pierrick Bouvier : > > >

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

ght, but unlikely: > https://github.com/antmicro/kvm-aosp-qemu/compare/fdd76fecdd...5.0.0-kvm-aosp <https://github.com/antmicro/kvm-aosp-qemu/compare/fdd76fecdd...5.0.0-kvm-aosp> What do you mean with "Hopefully you are right,but unlikely" ? On Wed, Sep 4, 2024 at 11:54 AM Philippe Ma

Re: Error : init: partition(s) not found in /sys, waiting for their uevent(s): mmcblk0p2, mmcblk0p3 while trying to emulate Android 14 on Ubuntu 24.04 X64 bit using qemu-system-aarch64.

mu/compare/fdd76fecdd...5.0.0-kvm-aosp > < > https://github.com/antmicro/kvm-aosp-qemu/compare/fdd76fecdd...5.0.0-kvm-aosp > > > > > > What do you mean with "Hopefully you are right,but unlikely" ? > > There are only 3 small patches, barely changing UI size and

Re: Kernel panic - not syncing: Unable to initialise architected timer : unable to boot Android 14 with qemu-system-aarch64 on Ubuntu 24.04 X64 bit

48 -gpu host -ports 5554, -skip-adb-auth -no-boot-anim -no-snapshot -no-metrics -qemu -machine gic-version=2 or similar... On Wed, Sep 11, 2024 at 12:19 PM Peter Maydell wrote: > On Wed, 11 Sept 2024 at 01:02, Mario Marietto > wrote: > > > > Hello to everyone. > >

How to enable KVM nesting virtualization on the Jetson nano.

Hello to everyone. while I was looking for a way to enable the nesting virtualization on my Jetson nano,after having enabled KVM applying these patches : https://github.com/OE4T/linux-tegra-4.9/blob/oe4t-patches-l4t-r37.4/

How to use UEFI_VARS.fd using virt-manager on Ubuntu 24.04...

Hello. On FreeBSD I've installed Windows 11 on the first partition of a 200 GB disk and Android X86 on the second partition of a 200 GB image file called "Android.img". This is how I boot Android : /usr/sbin/./bhyve-win -S -c sockets=4,cores=2,threads=1 -m 8G -w -H -A \ -s 0,hostbridge \ -s 1,ahc