Dear ACRN community, The ACRN team is hosting a virtual Meet-Up, brought to you by Intel. Please join us to learn more about ACRN, how far it has come over the last three years, and where it is headed

Thanks Kishore. I see the same error message as reported below if I increase the loglevel for the console to 5 or 6. In that case, there is no Service VM started, ‘vm_list’ does not list any VM and ‘v

Do you see the ACRN shell prompt (ACRN:\>) if you press “Enter” at that point? I do on my setup and I can then switch to the Service VM console by typing ‘vm_console 0’ (press Ctrl+spacebar from there

Hi Kishore, You also need the gnu-efi package installed to compile the 2.0 version – see https://projectacrn.github.io/2.0/getting-started/building-from-source.html#install-build-tools-and-dependencie

Hi! Which version of ACRN are you using? The error looks a bit different but be aware that the latest version of ACRN has a regression on QEMU: https://github.com/projectacrn/acrn-hypervisor/issues/59

Dear ACRN community, The ACRN team is hosting a virtual Meet-Up, brought to you by Intel. Please join us to learn more about ACRN, how far it has come over the last three years, and where it is headed

Hi Lonnie, I have never heard of anyone attempting to boot ACRN in a VirtualBox VM… do let us know if you and have any success there! 😉 One other path you could take is to QEMU on Windows and follow t

Hi Zhangshuai, What is your version of Ubuntu? I'm running Ubuntu 20.04 on a machine and did not have to update Grub to install ACRN. This is the right location, do you see the Grub menu at all after

Fuzhong, do we have more details on this issue documented somewhere? Is there any plan to fix this? Jacky, I assume the different content for the various screens will be coming from different VMs, is

Fuzhong, is this something you can help with? Thanks, Geoffroy

Hi, Were you following this tutorial when you hit this issue? https://projectacrn.github.io/latest/tutorials/using_windows_as_uos.html We switched at some point and are now using GVT-d (direct assigne

That’s very good to hear! :-) Have fun with it and let us know of any questions or feedback you may have! Cheers, Geoffroy

I believe it is. Can you confirm you have VT-d enabled in your bios? My understanding is that the DMAR table is set-up by the firmware if VT-d is enabled. If it does not do so, that is the sign of a b

Hi! Can you send the dmesg output when booting up a regular kernel. This error seems to indicate a problem with the bios. It would also be worthwhile running the board information script that we have

Hi Lonnie, I’m not expert in this but as far as I know this has not been tried yet. We do compile specifically for 64-bit architecture (see the “-m64” flag in the Makefile [1]). This option does the f

Hi Lonnie, No real plan yet unfortunately. Thanks, Geoffroy

Thanks Jacky. We’ll be limited in what we can try as I assume you do not have a serial port on that platform, do you? This would be the most efficient way to debug this as it’s the only output for deb

Hi! You may need to “port” it to your hardware. But in general, this is a Kaby Lake processor and we already use that on the NUCs so we may be able to get this to work without too much effort (famous

Sounds good, I look forward to hearing back from you once you’ve started to get your hands dirty!! 😉

Hi Lonnie, Yes, you can share the graphics between VMs (Service and User VMs) on that platform. The technology is called GVT-g. Our latest release focusses more on GVT-d (i.e. direct assignment of the