Congratulations, this is an important milestone indeed!!!

Quoting one of our audio expert: >>>> As far as I’m aware SOS=>BE and GOS=>FE=>AaaG configurations are optimized. SOS snd_soc_skl_virtio_be snd_soc_sst_bxt_sos_tdf8532 snd_soc_skl snd_soc_tdf8532 snd_

Hi Thomas, Welcome to the ACRN community!! Your kernel command-line is most likely incorrect, change root=/dev/mmcblk0p1 to root=/dev/mmcblk0p3 (the first partition is typically the EFI System Partiti

Sounds good, I have filed https://github.com/projectacrn/acrn-hypervisor/issues/2830 to track this. Thanks! Geoffroy

Hi folks, I have noticed some warnings when buiding the ACRN hypervisor: gcc -I/home/gvancuts/work/acrn/acrn-hypervisor/build/hypervisor/include -I. -c -I. -I.. -I../hypervisor/include/arch/x86/guest

Hi folks, Why do we have "#define SHELL_ROWS 10" in hypervisor/debug.shell.c? I'm kind of guessing that the idea is to not scroll passed a maximum of 10 lines when displaying something. But it does no

Acrn-dm actually uses 'iasl' compiler from the Service OS (by default, the one in /usr/sbin)[1], could it be that it's the version of that tool that is causing trouble? The one shipped in Clear Linux

This is very similar to an issue we hit a little while ago related to ACPI (and IASL): https://github.com/projectacrn/acrn-hypervisor/issues/2568 Geoffroy

Hi Vanda, Thanks for your confirmation! I think Outlook has been messing with that line below, it’s not something I had copy-pasted from my dev machine but something I typed directly in the email body

Update since my initial mail. I have changed the SOS kernel command-line (in acrn.conf) to use ttyS1 (instead of ttyS0) and that allowed me to boot the system with uart=bdf@0:18.1 vuart=ttyS1@irq5. Bu

Hi folks, I have been setting up ACRN on my UP2 board, specifically: - ACRN: HV version 0.7-unstable-2019-03-01 (from Clear Linux 28100) - UP2 bios is the latest: https://downloads.up-community.org/do

I had started looking into this a bit since I knew the engineering was mostly out on holiday last week, the quick summary is that there are at least a number of virtio FE drivers that are not upstream

Great stuff - thanks for the update Ross!

Confirmed, acrn-dm will automatically add "acrn_" to the tap name you give it - see https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel/hw/pci/virtio/virtio_net.c#L667

I had missed that in your original email, but I think the correct parameter to be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the tap name). Were you ever able to run thi

Hi Ross, How did you set these up? The network set-up when you install ACRN in Clear Linux is controlled by the 4 systemd files located here: https://github.com/projectacrn/acrn-hypervisor/tree/master

Yeah, congrats!!