Hi Steve, The default way is change it through "make menuconfig" command and rebuild the ACRN. Changing Kconfig is kind of hack here. For default value, we need trade off like whether there are many

Hi Yin, What is the preferred way? Is there any chance of having the default value increased as I guess it would be nice to support Samsung SSDs "out of the box", without having to rebuild. Cheers

Hi Steve, The easiest way to try is change the file: hypervisor/arch/x86/Kconfig which has: config MAX_MSIX_TABLE_NUM int "Maximum number of MSI-X tables per device" range 1

Hi Yin, I have a Samsung PCI SSD installed. Looking at it's capabilities I get: Capabilities: [b0] MSI-X: Enable+ Count=33 Masked- So looks like this is the problem. It it easy to up the number of

Hi Geoffroy, Have installed 2*8GB SODIMM plus a SATA hard disk and a PCI SSD (Samsung 500GB Evo). Cheers Steve. -- Engineering Director IOTech Systems Ltd.

Hi Osselton, It looks like there is one PCI device in your system which has more than 16 MSIX table. Can you boot to native linux and dump the MSI table of each PCI devices on your

How much memory do you have installed on that system? Any additional PCI that you have installed (exotic or not) that could cause this? Geoffroy From: acrn-users@... <acrn-users@...>On

Great – thanks for confirming this Alfonso! From: acrn-users@... <acrn-users@...>On Behalf Of Alfonso Sanchez-Beato Sent: Thursday, January 9, 2020 12:35 PM To: acrn-users@... Subject: Re:

Thanks all, yes, that was the problem. I can finally launch the RT kernel! I had skipped the "Prepare the User OS (UOS)" section (I wanted to try the RT kernel instead), and had not noticed that bit.

Hi Alfonso, Maybe, you miss following steps mentioned in the guide: https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html BR. Fuzhong

Hi Liz, Was just following the instructions for example industry scenario for the 1.4 release, didn't build anything myself. Have tried again from scratch using latest updates for 1.5: 1 - Installed

Hi Fengwei,

Hi Alfonso, You are not building with CONFIG_RELEASE=y by any chance? (If the tag info below is correct, the default is not to use that). In case you did, note that it will disable the use of the

Hi Alfonso, It's related with iasl in your SOS. We have constrain for iasl version. Regards Yin, Fengwei

Hi Liu and Geoffroy, Right, I had forgotten to copy acrn.efi to the EFI partition after re-compiling, thanks for reminding me. With that things move forward a bit, but I still get

Just ignore this email, sorry for interrupt. Thanks & Best Regards, Jason Chen SSP -> Intel ACRN Hypervisor Team From: acrn-users@... <acrn-users@...>On Behalf Of Chen, Jason CJ Sent:

Please check the latest SDM, it’s actually new ISA instruction, I think we just need emulate their CPUID. Thanks & Best Regards, Jason Chen SSP -> Intel ACRN Hypervisor Team From:

Hi Steve Seem like, you are using very old codebase, can you try with v1.4 codebase first? If not; please share the commit id. Thanks! BR. Fuzhong From: acrn-users@... <acrn-users@...>On

Hi Alfonso Could you please share acrn.efi and acrn-dm commit info? With following steps: run “acrn-dm -v” in sos run “version” in HV console We need them to reproduce this

Your build instruction below should be fine (you can always also check the content of build/hypervisor/.config to make sure that you have CONFIG_INDUSTRY=y in it). Note though that “sudo make