Date   

Re: Problem with Industry Scenario on a NUC7i7DNH

Geoffroy Van Cutsem
 

We use a gcc 9.2.1 in Clear Linux to build ACRN these days, I’ll see if I can spin up an Ubuntu 19.04 machine to reproduce the failure.

 

Geoffroy

 

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Friday, January 10, 2020 11:03 AM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Liu,

 

Followed exactly these instructions, except on Ubuntu 19.10. To me looks like a gcc 9 or config issue as clearly

doesn't like ‘-mindirect-branch’ and ‘-fcf-protection’ used together. Am building a Clear Linux VM now ....

 

Cheers Steve

 

On Fri, 10 Jan 2020 at 09:45, Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Steve,

 

We don’t met this issue with Ubuntu 18.04.

Do you install following package? As mentioned on: https://projectacrn.github.io/1.5/getting-started/building-from-source.html

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Friday, January 10, 2020 5:33 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Yin,

 

Will validate whether suggested quick fix works. Looks like not happy building with gcc 9 (am using Ubuntu 19.10):

 

cc  -Iinclude  -Iinclude/lib  -Iinclude/lib/crypto  -Iinclude/common  -Iinclude/arch/x86  -Iinclude/arch/x86/boot  -Iinclude/arch/x86/guest  -Iinclude/arch/x86/lib  -Iinclude/debug  -Iinclude/public  -Iinclude/dm  -Iinclude/hw  -Iboot/include  -Iboot/include/guest  -I/home/steve/git/acrn-hypervisor/build/hypervisor/include  -Iarch/x86/configs/nuc7i7dnb  -Iscenarios/industry -I. -c  -include /home/steve/git/acrn-hypervisor/build/hypervisor/include/config.h -Wall -W -ffunction-sections -fdata-sections -fshort-wchar -ffreestanding -fsigned-char -m64 -mno-mmx -mno-sse -mno-sse2 -mno-80387 -mno-fp-ret-in-387 -mno-red-zone -mpopcnt -nostdinc -nostdlib -fno-common -Werror -O2 -fpie -fstack-protector-strong -DSTACK_PROTECTOR -mindirect-branch=thunk-extern -mindirect-branch-register -DCONFIG_RETPOLINE -DHV_DEBUG -DPROFILING_ON -fno-omit-frame-pointer  -gdwarf-2 pre_build/static_checks.c -o /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o -MMD -MT /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o
In file included from pre_build/static_checks.c:7:
include/lib/util.h: In function ‘mem_aligned_check’:
include/lib/util.h:30:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible

 

Should I submit this as a bug report? Will try building on Clear Linux ...

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 09:18, Yin, Fengwei <fengwei.yin@...> wrote:

Hi Steve,

On 2020/1/10 下午5:12, Steve Osselton wrote:
> 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.
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 such
devices.

Could you please try the hack first so we could know whether this is
the root cause of your issue? Thanks.


Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@...
> <mailto:fengwei.yin@...>> wrote:
>
>     Hi Steve,
>
>     On 2020/1/10 下午5:02, Steve Osselton wrote:
>      > 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
>      > supported MSIX tables?
>     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 2048
>               default 16  ---> 64
>
>     You could try it as quick check. It's not the preferred way...
>
>
>     Regards
>     Yin, Fengwei
>
>      >
>      > Cheers Steve.
>      >
>      > On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
>     <mailto:fengwei.yin@...>
>      > <mailto:fengwei.yin@... <mailto:fengwei.yin@...>>> wrote:
>      >
>      >     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 board?
>      >
>      >
>      >     Regards
>      >     Yin, Fengwei
>      >
>      >     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      >      > 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 clear-32030-live-server.iso onto hard disk.
>      >      > 2 - Boot:
>      >      >
>      >      > # wget
>      >      >
>      >
>     https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      >      > # chmod +x acrn_quick_setup.sh
>      >      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      >      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1
>     -L ACRN -u
>      >      > "uart=port@0x3f8"
>      >      >
>      >      > 3 - Reboot:
>      >      >
>      >      > Console output:
>      >      >
>      >      > ACRN Hypervisor
>      >      > calibrate_tsc, tsc_khz=2100000
>      >      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      >      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>      >     mockbuild,
>      >      > start time 11171478us
>      >      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      >      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect
>     processor: Intel(R)
>      >      > Core(TM) i7-8650U CPU @ 1.90GHz
>      >      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed
>     in file
>      >      > hw/pci.c,line 448 : fatal error
>      >      >
>      >      > Still failing ...
>      >      >
>      >      > Cheers Steve.
>      >      >
>      >      >
>      >      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      > <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...> <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:
>      >      >
>      >      >     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@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >     Osselton
>      >      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >      >     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     *Subject:* Re: [acrn-users] Problem with Industry
>     Scenario on a
>      >      >     NUC7i7DNH____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Hi Liu,____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On inspection was running an old BIOS version, have
>     upgraded to
>      >      >     latest version (DNi70067) and disabled hyper
>     threading.____
>      >      >
>      >      >     Things are improved in that I now get diagnostics from
>     the serial
>      >      >     port:____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     ACRN Hypervisor
>      >      >     calibrate_tsc, tsc_khz=2100000
>      >      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>      >     1.4-unstable-2019-11-18
>      >      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>      >     11028016us
>      >      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor:
>     Intel(R)
>      >      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >      >     hw/pci.c,line 250 : fatal error____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     So still failing.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Also as a comment, the BIOS settings descriptions, are
>     badly
>      >     out of
>      >      >     step with what you see from the latest visual BIOS.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Cheers Steve.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>      >     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:____
>      >      >
>      >      >         Hi Steve,____
>      >      >
>      >      >         Please disable Hyper thread in BIOS for
>     workaround.____
>      >      >
>      >      >         This issue is fixed in  v1.5; will release soon.____
>      >      >
>      >      >         ____
>      >      >
>      >      >         BR.____
>      >      >
>      >      >         Fuzhong____
>      >      >
>      >      >         ____
>      >      >
>      >      >         *From:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >      >         Osselton
>      >      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >      >         *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         *Subject:* [acrn-users] Problem with Industry
>     Scenario on a
>      >      >         NUC7i7DNH____
>      >      >
>      >      >         ____
>      >      >
>      >      >         Hi,
>      >      >
>      >      >         Am essentially following the deployment
>     instructions for the
>      >      >         ACRN industry scenario
>      >      >         using a NUC7i7DNH with a serial port connected.
>      >      >
>      >      >
>     https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >      >
>      >      >         Flashing clear-31670-live-server.iso worked fine. Then
>      >     followed
>      >      >         the "Use the pre-installed industry ACRN hypervisor"
>      >      >         section and installed serial port support. Again
>     this all
>      >     worked
>      >      >         fine and looked good.
>      >      >
>      >      >         I then rebooted the NUC. At HDMI console get
>     "Intel NUC"
>      >     banner
>      >      >         with the following at top LHS of screen:
>      >      >
>      >      >         detected 8 processes, 8 enabled
>      >      >         current on process 0
>      >      >
>      >      >         And on serial port:
>      >      >
>      >      >         E0S0 S0
>      >      >
>      >      >         Not sure what has happened here. Am I missing
>     something
>      >     obvious ?
>      >      >
>      >      >         Thanks Steve ____
>      >      >
>      >      >
>      >      >     ____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     -- ____
>      >      >
>      >      >     Engineering Director____
>      >      >
>      >      >     IOTech Systems Ltd.____
>      >      >
>      >      >     __
>      >      >
>      >      >
>      >      >
>      >      > --
>      >      > Engineering Director
>      >      > IOTech Systems Ltd.
>      >      >
>      >
>      >
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>


 

--

Engineering Director

IOTech Systems Ltd.


 

--

Engineering Director

IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Geoffroy Van Cutsem
 

We also have a Docker container you can use to build ACRN, if that’s any easier to you – here are the instructions on how to use it: https://projectacrn.github.io/latest/tutorials/building_acrn_in_docker.html

 

Thanks,

Geoffroy

 

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Friday, January 10, 2020 11:03 AM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Liu,

 

Followed exactly these instructions, except on Ubuntu 19.10. To me looks like a gcc 9 or config issue as clearly

doesn't like ‘-mindirect-branch’ and ‘-fcf-protection’ used together. Am building a Clear Linux VM now ....

 

Cheers Steve

 

On Fri, 10 Jan 2020 at 09:45, Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Steve,

 

We don’t met this issue with Ubuntu 18.04.

Do you install following package? As mentioned on: https://projectacrn.github.io/1.5/getting-started/building-from-source.html

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Friday, January 10, 2020 5:33 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Yin,

 

Will validate whether suggested quick fix works. Looks like not happy building with gcc 9 (am using Ubuntu 19.10):

 

cc  -Iinclude  -Iinclude/lib  -Iinclude/lib/crypto  -Iinclude/common  -Iinclude/arch/x86  -Iinclude/arch/x86/boot  -Iinclude/arch/x86/guest  -Iinclude/arch/x86/lib  -Iinclude/debug  -Iinclude/public  -Iinclude/dm  -Iinclude/hw  -Iboot/include  -Iboot/include/guest  -I/home/steve/git/acrn-hypervisor/build/hypervisor/include  -Iarch/x86/configs/nuc7i7dnb  -Iscenarios/industry -I. -c  -include /home/steve/git/acrn-hypervisor/build/hypervisor/include/config.h -Wall -W -ffunction-sections -fdata-sections -fshort-wchar -ffreestanding -fsigned-char -m64 -mno-mmx -mno-sse -mno-sse2 -mno-80387 -mno-fp-ret-in-387 -mno-red-zone -mpopcnt -nostdinc -nostdlib -fno-common -Werror -O2 -fpie -fstack-protector-strong -DSTACK_PROTECTOR -mindirect-branch=thunk-extern -mindirect-branch-register -DCONFIG_RETPOLINE -DHV_DEBUG -DPROFILING_ON -fno-omit-frame-pointer  -gdwarf-2 pre_build/static_checks.c -o /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o -MMD -MT /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o
In file included from pre_build/static_checks.c:7:
include/lib/util.h: In function ‘mem_aligned_check’:
include/lib/util.h:30:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible

 

Should I submit this as a bug report? Will try building on Clear Linux ...

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 09:18, Yin, Fengwei <fengwei.yin@...> wrote:

Hi Steve,

On 2020/1/10 下午5:12, Steve Osselton wrote:
> 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.
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 such
devices.

Could you please try the hack first so we could know whether this is
the root cause of your issue? Thanks.


Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@...
> <mailto:fengwei.yin@...>> wrote:
>
>     Hi Steve,
>
>     On 2020/1/10 下午5:02, Steve Osselton wrote:
>      > 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
>      > supported MSIX tables?
>     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 2048
>               default 16  ---> 64
>
>     You could try it as quick check. It's not the preferred way...
>
>
>     Regards
>     Yin, Fengwei
>
>      >
>      > Cheers Steve.
>      >
>      > On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
>     <mailto:fengwei.yin@...>
>      > <mailto:fengwei.yin@... <mailto:fengwei.yin@...>>> wrote:
>      >
>      >     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 board?
>      >
>      >
>      >     Regards
>      >     Yin, Fengwei
>      >
>      >     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      >      > 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 clear-32030-live-server.iso onto hard disk.
>      >      > 2 - Boot:
>      >      >
>      >      > # wget
>      >      >
>      >
>     https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      >      > # chmod +x acrn_quick_setup.sh
>      >      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      >      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1
>     -L ACRN -u
>      >      > "uart=port@0x3f8"
>      >      >
>      >      > 3 - Reboot:
>      >      >
>      >      > Console output:
>      >      >
>      >      > ACRN Hypervisor
>      >      > calibrate_tsc, tsc_khz=2100000
>      >      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      >      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>      >     mockbuild,
>      >      > start time 11171478us
>      >      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      >      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect
>     processor: Intel(R)
>      >      > Core(TM) i7-8650U CPU @ 1.90GHz
>      >      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed
>     in file
>      >      > hw/pci.c,line 448 : fatal error
>      >      >
>      >      > Still failing ...
>      >      >
>      >      > Cheers Steve.
>      >      >
>      >      >
>      >      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      > <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...> <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:
>      >      >
>      >      >     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@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >     Osselton
>      >      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >      >     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     *Subject:* Re: [acrn-users] Problem with Industry
>     Scenario on a
>      >      >     NUC7i7DNH____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Hi Liu,____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On inspection was running an old BIOS version, have
>     upgraded to
>      >      >     latest version (DNi70067) and disabled hyper
>     threading.____
>      >      >
>      >      >     Things are improved in that I now get diagnostics from
>     the serial
>      >      >     port:____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     ACRN Hypervisor
>      >      >     calibrate_tsc, tsc_khz=2100000
>      >      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>      >     1.4-unstable-2019-11-18
>      >      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>      >     11028016us
>      >      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor:
>     Intel(R)
>      >      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >      >     hw/pci.c,line 250 : fatal error____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     So still failing.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Also as a comment, the BIOS settings descriptions, are
>     badly
>      >     out of
>      >      >     step with what you see from the latest visual BIOS.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Cheers Steve.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>      >     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:____
>      >      >
>      >      >         Hi Steve,____
>      >      >
>      >      >         Please disable Hyper thread in BIOS for
>     workaround.____
>      >      >
>      >      >         This issue is fixed in  v1.5; will release soon.____
>      >      >
>      >      >         ____
>      >      >
>      >      >         BR.____
>      >      >
>      >      >         Fuzhong____
>      >      >
>      >      >         ____
>      >      >
>      >      >         *From:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >      >         Osselton
>      >      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >      >         *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         *Subject:* [acrn-users] Problem with Industry
>     Scenario on a
>      >      >         NUC7i7DNH____
>      >      >
>      >      >         ____
>      >      >
>      >      >         Hi,
>      >      >
>      >      >         Am essentially following the deployment
>     instructions for the
>      >      >         ACRN industry scenario
>      >      >         using a NUC7i7DNH with a serial port connected.
>      >      >
>      >      >
>     https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >      >
>      >      >         Flashing clear-31670-live-server.iso worked fine. Then
>      >     followed
>      >      >         the "Use the pre-installed industry ACRN hypervisor"
>      >      >         section and installed serial port support. Again
>     this all
>      >     worked
>      >      >         fine and looked good.
>      >      >
>      >      >         I then rebooted the NUC. At HDMI console get
>     "Intel NUC"
>      >     banner
>      >      >         with the following at top LHS of screen:
>      >      >
>      >      >         detected 8 processes, 8 enabled
>      >      >         current on process 0
>      >      >
>      >      >         And on serial port:
>      >      >
>      >      >         E0S0 S0
>      >      >
>      >      >         Not sure what has happened here. Am I missing
>     something
>      >     obvious ?
>      >      >
>      >      >         Thanks Steve ____
>      >      >
>      >      >
>      >      >     ____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     -- ____
>      >      >
>      >      >     Engineering Director____
>      >      >
>      >      >     IOTech Systems Ltd.____
>      >      >
>      >      >     __
>      >      >
>      >      >
>      >      >
>      >      > --
>      >      > Engineering Director
>      >      > IOTech Systems Ltd.
>      >      >
>      >
>      >
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>


 

--

Engineering Director

IOTech Systems Ltd.


 

--

Engineering Director

IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

Hi Liu,

Followed exactly these instructions, except on Ubuntu 19.10. To me looks like a gcc 9 or config issue as clearly
doesn't like ‘-mindirect-branch’ and ‘-fcf-protection’ used together. Am building a Clear Linux VM now ....

Cheers Steve

On Fri, 10 Jan 2020 at 09:45, Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Steve,

 

We don’t met this issue with Ubuntu 18.04.

Do you install following package? As mentioned on: https://projectacrn.github.io/1.5/getting-started/building-from-source.html

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Friday, January 10, 2020 5:33 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Yin,

 

Will validate whether suggested quick fix works. Looks like not happy building with gcc 9 (am using Ubuntu 19.10):

 

cc  -Iinclude  -Iinclude/lib  -Iinclude/lib/crypto  -Iinclude/common  -Iinclude/arch/x86  -Iinclude/arch/x86/boot  -Iinclude/arch/x86/guest  -Iinclude/arch/x86/lib  -Iinclude/debug  -Iinclude/public  -Iinclude/dm  -Iinclude/hw  -Iboot/include  -Iboot/include/guest  -I/home/steve/git/acrn-hypervisor/build/hypervisor/include  -Iarch/x86/configs/nuc7i7dnb  -Iscenarios/industry -I. -c  -include /home/steve/git/acrn-hypervisor/build/hypervisor/include/config.h -Wall -W -ffunction-sections -fdata-sections -fshort-wchar -ffreestanding -fsigned-char -m64 -mno-mmx -mno-sse -mno-sse2 -mno-80387 -mno-fp-ret-in-387 -mno-red-zone -mpopcnt -nostdinc -nostdlib -fno-common -Werror -O2 -fpie -fstack-protector-strong -DSTACK_PROTECTOR -mindirect-branch=thunk-extern -mindirect-branch-register -DCONFIG_RETPOLINE -DHV_DEBUG -DPROFILING_ON -fno-omit-frame-pointer  -gdwarf-2 pre_build/static_checks.c -o /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o -MMD -MT /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o
In file included from pre_build/static_checks.c:7:
include/lib/util.h: In function ‘mem_aligned_check’:
include/lib/util.h:30:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible

 

Should I submit this as a bug report? Will try building on Clear Linux ...

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 09:18, Yin, Fengwei <fengwei.yin@...> wrote:

Hi Steve,

On 2020/1/10 下午5:12, Steve Osselton wrote:
> 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.
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 such
devices.

Could you please try the hack first so we could know whether this is
the root cause of your issue? Thanks.


Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@...
> <mailto:fengwei.yin@...>> wrote:
>
>     Hi Steve,
>
>     On 2020/1/10 下午5:02, Steve Osselton wrote:
>      > 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
>      > supported MSIX tables?
>     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 2048
>               default 16  ---> 64
>
>     You could try it as quick check. It's not the preferred way...
>
>
>     Regards
>     Yin, Fengwei
>
>      >
>      > Cheers Steve.
>      >
>      > On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
>     <mailto:fengwei.yin@...>
>      > <mailto:fengwei.yin@... <mailto:fengwei.yin@...>>> wrote:
>      >
>      >     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 board?
>      >
>      >
>      >     Regards
>      >     Yin, Fengwei
>      >
>      >     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      >      > 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 clear-32030-live-server.iso onto hard disk.
>      >      > 2 - Boot:
>      >      >
>      >      > # wget
>      >      >
>      >
>     https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      >      > # chmod +x acrn_quick_setup.sh
>      >      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      >      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1
>     -L ACRN -u
>      >      > "uart=port@0x3f8"
>      >      >
>      >      > 3 - Reboot:
>      >      >
>      >      > Console output:
>      >      >
>      >      > ACRN Hypervisor
>      >      > calibrate_tsc, tsc_khz=2100000
>      >      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      >      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>      >     mockbuild,
>      >      > start time 11171478us
>      >      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      >      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect
>     processor: Intel(R)
>      >      > Core(TM) i7-8650U CPU @ 1.90GHz
>      >      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed
>     in file
>      >      > hw/pci.c,line 448 : fatal error
>      >      >
>      >      > Still failing ...
>      >      >
>      >      > Cheers Steve.
>      >      >
>      >      >
>      >      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      > <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...> <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:
>      >      >
>      >      >     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@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >     Osselton
>      >      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >      >     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     *Subject:* Re: [acrn-users] Problem with Industry
>     Scenario on a
>      >      >     NUC7i7DNH____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Hi Liu,____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On inspection was running an old BIOS version, have
>     upgraded to
>      >      >     latest version (DNi70067) and disabled hyper
>     threading.____
>      >      >
>      >      >     Things are improved in that I now get diagnostics from
>     the serial
>      >      >     port:____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     ACRN Hypervisor
>      >      >     calibrate_tsc, tsc_khz=2100000
>      >      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>      >     1.4-unstable-2019-11-18
>      >      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>      >     11028016us
>      >      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor:
>     Intel(R)
>      >      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >      >     hw/pci.c,line 250 : fatal error____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     So still failing.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Also as a comment, the BIOS settings descriptions, are
>     badly
>      >     out of
>      >      >     step with what you see from the latest visual BIOS.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Cheers Steve.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>      >     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:____
>      >      >
>      >      >         Hi Steve,____
>      >      >
>      >      >         Please disable Hyper thread in BIOS for
>     workaround.____
>      >      >
>      >      >         This issue is fixed in  v1.5; will release soon.____
>      >      >
>      >      >         ____
>      >      >
>      >      >         BR.____
>      >      >
>      >      >         Fuzhong____
>      >      >
>      >      >         ____
>      >      >
>      >      >         *From:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >      >         Osselton
>      >      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >      >         *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         *Subject:* [acrn-users] Problem with Industry
>     Scenario on a
>      >      >         NUC7i7DNH____
>      >      >
>      >      >         ____
>      >      >
>      >      >         Hi,
>      >      >
>      >      >         Am essentially following the deployment
>     instructions for the
>      >      >         ACRN industry scenario
>      >      >         using a NUC7i7DNH with a serial port connected.
>      >      >
>      >      >
>     https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >      >
>      >      >         Flashing clear-31670-live-server.iso worked fine. Then
>      >     followed
>      >      >         the "Use the pre-installed industry ACRN hypervisor"
>      >      >         section and installed serial port support. Again
>     this all
>      >     worked
>      >      >         fine and looked good.
>      >      >
>      >      >         I then rebooted the NUC. At HDMI console get
>     "Intel NUC"
>      >     banner
>      >      >         with the following at top LHS of screen:
>      >      >
>      >      >         detected 8 processes, 8 enabled
>      >      >         current on process 0
>      >      >
>      >      >         And on serial port:
>      >      >
>      >      >         E0S0 S0
>      >      >
>      >      >         Not sure what has happened here. Am I missing
>     something
>      >     obvious ?
>      >      >
>      >      >         Thanks Steve ____
>      >      >
>      >      >
>      >      >     ____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     -- ____
>      >      >
>      >      >     Engineering Director____
>      >      >
>      >      >     IOTech Systems Ltd.____
>      >      >
>      >      >     __
>      >      >
>      >      >
>      >      >
>      >      > --
>      >      > Engineering Director
>      >      > IOTech Systems Ltd.
>      >      >
>      >
>      >
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>



 

--

Engineering Director

IOTech Systems Ltd.



--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Liu, Fuzhong
 

Hi Steve,

 

We don’t met this issue with Ubuntu 18.04.

Do you install following package? As mentioned on: https://projectacrn.github.io/1.5/getting-started/building-from-source.html

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Friday, January 10, 2020 5:33 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Yin,

 

Will validate whether suggested quick fix works. Looks like not happy building with gcc 9 (am using Ubuntu 19.10):

 

cc  -Iinclude  -Iinclude/lib  -Iinclude/lib/crypto  -Iinclude/common  -Iinclude/arch/x86  -Iinclude/arch/x86/boot  -Iinclude/arch/x86/guest  -Iinclude/arch/x86/lib  -Iinclude/debug  -Iinclude/public  -Iinclude/dm  -Iinclude/hw  -Iboot/include  -Iboot/include/guest  -I/home/steve/git/acrn-hypervisor/build/hypervisor/include  -Iarch/x86/configs/nuc7i7dnb  -Iscenarios/industry -I. -c  -include /home/steve/git/acrn-hypervisor/build/hypervisor/include/config.h -Wall -W -ffunction-sections -fdata-sections -fshort-wchar -ffreestanding -fsigned-char -m64 -mno-mmx -mno-sse -mno-sse2 -mno-80387 -mno-fp-ret-in-387 -mno-red-zone -mpopcnt -nostdinc -nostdlib -fno-common -Werror -O2 -fpie -fstack-protector-strong -DSTACK_PROTECTOR -mindirect-branch=thunk-extern -mindirect-branch-register -DCONFIG_RETPOLINE -DHV_DEBUG -DPROFILING_ON -fno-omit-frame-pointer  -gdwarf-2 pre_build/static_checks.c -o /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o -MMD -MT /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o
In file included from pre_build/static_checks.c:7:
include/lib/util.h: In function ‘mem_aligned_check’:
include/lib/util.h:30:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible

 

Should I submit this as a bug report? Will try building on Clear Linux ...

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 09:18, Yin, Fengwei <fengwei.yin@...> wrote:

Hi Steve,

On 2020/1/10 下午5:12, Steve Osselton wrote:
> 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.
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 such
devices.

Could you please try the hack first so we could know whether this is
the root cause of your issue? Thanks.


Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@...
> <mailto:fengwei.yin@...>> wrote:
>
>     Hi Steve,
>
>     On 2020/1/10 下午5:02, Steve Osselton wrote:
>      > 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
>      > supported MSIX tables?
>     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 2048
>               default 16  ---> 64
>
>     You could try it as quick check. It's not the preferred way...
>
>
>     Regards
>     Yin, Fengwei
>
>      >
>      > Cheers Steve.
>      >
>      > On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
>     <mailto:fengwei.yin@...>
>      > <mailto:fengwei.yin@... <mailto:fengwei.yin@...>>> wrote:
>      >
>      >     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 board?
>      >
>      >
>      >     Regards
>      >     Yin, Fengwei
>      >
>      >     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      >      > 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 clear-32030-live-server.iso onto hard disk.
>      >      > 2 - Boot:
>      >      >
>      >      > # wget
>      >      >
>      >
>     https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      >      > # chmod +x acrn_quick_setup.sh
>      >      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      >      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1
>     -L ACRN -u
>      >      > "uart=port@0x3f8"
>      >      >
>      >      > 3 - Reboot:
>      >      >
>      >      > Console output:
>      >      >
>      >      > ACRN Hypervisor
>      >      > calibrate_tsc, tsc_khz=2100000
>      >      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      >      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>      >     mockbuild,
>      >      > start time 11171478us
>      >      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      >      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect
>     processor: Intel(R)
>      >      > Core(TM) i7-8650U CPU @ 1.90GHz
>      >      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed
>     in file
>      >      > hw/pci.c,line 448 : fatal error
>      >      >
>      >      > Still failing ...
>      >      >
>      >      > Cheers Steve.
>      >      >
>      >      >
>      >      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      > <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...> <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:
>      >      >
>      >      >     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@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >     Osselton
>      >      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >      >     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     *Subject:* Re: [acrn-users] Problem with Industry
>     Scenario on a
>      >      >     NUC7i7DNH____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Hi Liu,____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On inspection was running an old BIOS version, have
>     upgraded to
>      >      >     latest version (DNi70067) and disabled hyper
>     threading.____
>      >      >
>      >      >     Things are improved in that I now get diagnostics from
>     the serial
>      >      >     port:____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     ACRN Hypervisor
>      >      >     calibrate_tsc, tsc_khz=2100000
>      >      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>      >     1.4-unstable-2019-11-18
>      >      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>      >     11028016us
>      >      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor:
>     Intel(R)
>      >      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >      >     hw/pci.c,line 250 : fatal error____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     So still failing.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Also as a comment, the BIOS settings descriptions, are
>     badly
>      >     out of
>      >      >     step with what you see from the latest visual BIOS.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Cheers Steve.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>      >     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:____
>      >      >
>      >      >         Hi Steve,____
>      >      >
>      >      >         Please disable Hyper thread in BIOS for
>     workaround.____
>      >      >
>      >      >         This issue is fixed in  v1.5; will release soon.____
>      >      >
>      >      >         ____
>      >      >
>      >      >         BR.____
>      >      >
>      >      >         Fuzhong____
>      >      >
>      >      >         ____
>      >      >
>      >      >         *From:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >      >         Osselton
>      >      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >      >         *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         *Subject:* [acrn-users] Problem with Industry
>     Scenario on a
>      >      >         NUC7i7DNH____
>      >      >
>      >      >         ____
>      >      >
>      >      >         Hi,
>      >      >
>      >      >         Am essentially following the deployment
>     instructions for the
>      >      >         ACRN industry scenario
>      >      >         using a NUC7i7DNH with a serial port connected.
>      >      >
>      >      >
>     https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >      >
>      >      >         Flashing clear-31670-live-server.iso worked fine. Then
>      >     followed
>      >      >         the "Use the pre-installed industry ACRN hypervisor"
>      >      >         section and installed serial port support. Again
>     this all
>      >     worked
>      >      >         fine and looked good.
>      >      >
>      >      >         I then rebooted the NUC. At HDMI console get
>     "Intel NUC"
>      >     banner
>      >      >         with the following at top LHS of screen:
>      >      >
>      >      >         detected 8 processes, 8 enabled
>      >      >         current on process 0
>      >      >
>      >      >         And on serial port:
>      >      >
>      >      >         E0S0 S0
>      >      >
>      >      >         Not sure what has happened here. Am I missing
>     something
>      >     obvious ?
>      >      >
>      >      >         Thanks Steve ____
>      >      >
>      >      >
>      >      >     ____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     -- ____
>      >      >
>      >      >     Engineering Director____
>      >      >
>      >      >     IOTech Systems Ltd.____
>      >      >
>      >      >     __
>      >      >
>      >      >
>      >      >
>      >      > --
>      >      > Engineering Director
>      >      > IOTech Systems Ltd.
>      >      >
>      >
>      >
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>



 

--

Engineering Director

IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

Hi Yin,

Will validate whether suggested quick fix works. Looks like not happy building with gcc 9 (am using Ubuntu 19.10):

cc  -Iinclude  -Iinclude/lib  -Iinclude/lib/crypto  -Iinclude/common  -Iinclude/arch/x86  -Iinclude/arch/x86/boot  -Iinclude/arch/x86/guest  -Iinclude/arch/x86/lib  -Iinclude/debug  -Iinclude/public  -Iinclude/dm  -Iinclude/hw  -Iboot/include  -Iboot/include/guest  -I/home/steve/git/acrn-hypervisor/build/hypervisor/include  -Iarch/x86/configs/nuc7i7dnb  -Iscenarios/industry -I. -c  -include /home/steve/git/acrn-hypervisor/build/hypervisor/include/config.h -Wall -W -ffunction-sections -fdata-sections -fshort-wchar -ffreestanding -fsigned-char -m64 -mno-mmx -mno-sse -mno-sse2 -mno-80387 -mno-fp-ret-in-387 -mno-red-zone -mpopcnt -nostdinc -nostdlib -fno-common -Werror -O2 -fpie -fstack-protector-strong -DSTACK_PROTECTOR -mindirect-branch=thunk-extern -mindirect-branch-register -DCONFIG_RETPOLINE -DHV_DEBUG -DPROFILING_ON -fno-omit-frame-pointer  -gdwarf-2 pre_build/static_checks.c -o /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o -MMD -MT /home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_checks.o
In file included from pre_build/static_checks.c:7:
include/lib/util.h: In function ‘mem_aligned_check’:
include/lib/util.h:30:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible

Should I submit this as a bug report? Will try building on Clear Linux ...

Cheers Steve.

On Fri, 10 Jan 2020 at 09:18, Yin, Fengwei <fengwei.yin@...> wrote:
Hi Steve,

On 2020/1/10 下午5:12, Steve Osselton wrote:
> 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.
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 such
devices.

Could you please try the hack first so we could know whether this is
the root cause of your issue? Thanks.


Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@...
> <mailto:fengwei.yin@...>> wrote:
>
>     Hi Steve,
>
>     On 2020/1/10 下午5:02, Steve Osselton wrote:
>      > 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
>      > supported MSIX tables?
>     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 2048
>               default 16  ---> 64
>
>     You could try it as quick check. It's not the preferred way...
>
>
>     Regards
>     Yin, Fengwei
>
>      >
>      > Cheers Steve.
>      >
>      > On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
>     <mailto:fengwei.yin@...>
>      > <mailto:fengwei.yin@... <mailto:fengwei.yin@...>>> wrote:
>      >
>      >     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 board?
>      >
>      >
>      >     Regards
>      >     Yin, Fengwei
>      >
>      >     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      >      > 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 clear-32030-live-server.iso onto hard disk.
>      >      > 2 - Boot:
>      >      >
>      >      > # wget
>      >      >
>      >
>     https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      >      > # chmod +x acrn_quick_setup.sh
>      >      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      >      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1
>     -L ACRN -u
>      >      > "uart=port@0x3f8"
>      >      >
>      >      > 3 - Reboot:
>      >      >
>      >      > Console output:
>      >      >
>      >      > ACRN Hypervisor
>      >      > calibrate_tsc, tsc_khz=2100000
>      >      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      >      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>      >     mockbuild,
>      >      > start time 11171478us
>      >      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      >      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect
>     processor: Intel(R)
>      >      > Core(TM) i7-8650U CPU @ 1.90GHz
>      >      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed
>     in file
>      >      > hw/pci.c,line 448 : fatal error
>      >      >
>      >      > Still failing ...
>      >      >
>      >      > Cheers Steve.
>      >      >
>      >      >
>      >      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      > <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...> <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:
>      >      >
>      >      >     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@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >     Osselton
>      >      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >      >     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >     *Subject:* Re: [acrn-users] Problem with Industry
>     Scenario on a
>      >      >     NUC7i7DNH____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Hi Liu,____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On inspection was running an old BIOS version, have
>     upgraded to
>      >      >     latest version (DNi70067) and disabled hyper
>     threading.____
>      >      >
>      >      >     Things are improved in that I now get diagnostics from
>     the serial
>      >      >     port:____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     ACRN Hypervisor
>      >      >     calibrate_tsc, tsc_khz=2100000
>      >      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>      >     1.4-unstable-2019-11-18
>      >      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>      >     11028016us
>      >      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor:
>     Intel(R)
>      >      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >      >     hw/pci.c,line 250 : fatal error____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     So still failing.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Also as a comment, the BIOS settings descriptions, are
>     badly
>      >     out of
>      >      >     step with what you see from the latest visual BIOS.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     Cheers Steve.____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>      >     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>>> wrote:____
>      >      >
>      >      >         Hi Steve,____
>      >      >
>      >      >         Please disable Hyper thread in BIOS for
>     workaround.____
>      >      >
>      >      >         This issue is fixed in  v1.5; will release soon.____
>      >      >
>      >      >         ____
>      >      >
>      >      >         BR.____
>      >      >
>      >      >         Fuzhong____
>      >      >
>      >      >         ____
>      >      >
>      >      >         *From:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >      >         Osselton
>      >      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >      >         *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>>
>      >      >         *Subject:* [acrn-users] Problem with Industry
>     Scenario on a
>      >      >         NUC7i7DNH____
>      >      >
>      >      >         ____
>      >      >
>      >      >         Hi,
>      >      >
>      >      >         Am essentially following the deployment
>     instructions for the
>      >      >         ACRN industry scenario
>      >      >         using a NUC7i7DNH with a serial port connected.
>      >      >
>      >      >
>     https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >      >
>      >      >         Flashing clear-31670-live-server.iso worked fine. Then
>      >     followed
>      >      >         the "Use the pre-installed industry ACRN hypervisor"
>      >      >         section and installed serial port support. Again
>     this all
>      >     worked
>      >      >         fine and looked good.
>      >      >
>      >      >         I then rebooted the NUC. At HDMI console get
>     "Intel NUC"
>      >     banner
>      >      >         with the following at top LHS of screen:
>      >      >
>      >      >         detected 8 processes, 8 enabled
>      >      >         current on process 0
>      >      >
>      >      >         And on serial port:
>      >      >
>      >      >         E0S0 S0
>      >      >
>      >      >         Not sure what has happened here. Am I missing
>     something
>      >     obvious ?
>      >      >
>      >      >         Thanks Steve ____
>      >      >
>      >      >
>      >      >     ____
>      >      >
>      >      >     __ __
>      >      >
>      >      >     -- ____
>      >      >
>      >      >     Engineering Director____
>      >      >
>      >      >     IOTech Systems Ltd.____
>      >      >
>      >      >     __
>      >      >
>      >      >
>      >      >
>      >      > --
>      >      > Engineering Director
>      >      > IOTech Systems Ltd.
>      >      >
>      >
>      >
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>





--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Yin, Fengwei <fengwei.yin@...>
 

Hi Steve,

On 2020/1/10 下午5:12, Steve Osselton wrote:
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.
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 such
devices.

Could you please try the hack first so we could know whether this is
the root cause of your issue? Thanks.


Regards
Yin, Fengwei

Cheers Steve.
On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@... <mailto:fengwei.yin@...>> wrote:
Hi Steve,
On 2020/1/10 下午5:02, Steve Osselton wrote:
> 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
> supported MSIX tables?
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 2048
         default 16  ---> 64
You could try it as quick check. It's not the preferred way...
Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
<mailto:fengwei.yin@...>
> <mailto:fengwei.yin@... <mailto:fengwei.yin@...>>> wrote:
>
>     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 board?
>
>
>     Regards
>     Yin, Fengwei
>
>     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      > 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 clear-32030-live-server.iso onto hard disk.
>      > 2 - Boot:
>      >
>      > # wget
>      >
>
https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      > # chmod +x acrn_quick_setup.sh
>      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1
-L ACRN -u
>      > "uart=port@0x3f8"
>      >
>      > 3 - Reboot:
>      >
>      > Console output:
>      >
>      > ACRN Hypervisor
>      > calibrate_tsc, tsc_khz=2100000
>      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>     mockbuild,
>      > start time 11171478us
>      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect
processor: Intel(R)
>      > Core(TM) i7-8650U CPU @ 1.90GHz
>      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed
in file
>      > hw/pci.c,line 448 : fatal error
>      >
>      > Still failing ...
>      >
>      > Cheers Steve.
>      >
>      >
>      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong
<fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      > <mailto:fuzhong.liu@...
<mailto:fuzhong.liu@...> <mailto:fuzhong.liu@...
<mailto:fuzhong.liu@...>>>> wrote:
>      >
>      >     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@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>      >     <mailto:acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>>
>      >     <acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>      >     <mailto:acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>>> *On Behalf Of *Steve
>     Osselton
>      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >     *To:* acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>      >     <mailto:acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>>
>      >     *Subject:* Re: [acrn-users] Problem with Industry
Scenario on a
>      >     NUC7i7DNH____
>      >
>      >     __ __
>      >
>      >     Hi Liu,____
>      >
>      >     __ __
>      >
>      >     On inspection was running an old BIOS version, have
upgraded to
>      >     latest version (DNi70067) and disabled hyper
threading.____
>      >
>      >     Things are improved in that I now get diagnostics from
the serial
>      >     port:____
>      >
>      >     __ __
>      >
>      >     ACRN Hypervisor
>      >     calibrate_tsc, tsc_khz=2100000
>      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>     1.4-unstable-2019-11-18
>      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>     11028016us
>      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor:
Intel(R)
>      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >     hw/pci.c,line 250 : fatal error____
>      >
>      >     __ __
>      >
>      >     So still failing.____
>      >
>      >     __ __
>      >
>      >     Also as a comment, the BIOS settings descriptions, are
badly
>     out of
>      >     step with what you see from the latest visual BIOS.____
>      >
>      >     __ __
>      >
>      >     Cheers Steve.____
>      >
>      >     __ __
>      >
>      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
<mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>
>      >     <mailto:fuzhong.liu@...
<mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@...
<mailto:fuzhong.liu@...>>>> wrote:____
>      >
>      >         Hi Steve,____
>      >
>      >         Please disable Hyper thread in BIOS for
workaround.____
>      >
>      >         This issue is fixed in  v1.5; will release soon.____
>      >
>      >         ____
>      >
>      >         BR.____
>      >
>      >         Fuzhong____
>      >
>      >         ____
>      >
>      >         *From:* acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>      >         <mailto:acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>>
>      >         <acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>      >         <mailto:acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>>> *On Behalf Of *Steve
>      >         Osselton
>      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >         *To:* acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>      >         <mailto:acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>>
>      >         *Subject:* [acrn-users] Problem with Industry
Scenario on a
>      >         NUC7i7DNH____
>      >
>      >         ____
>      >
>      >         Hi,
>      >
>      >         Am essentially following the deployment
instructions for the
>      >         ACRN industry scenario
>      >         using a NUC7i7DNH with a serial port connected.
>      >
>      >
https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >
>      >         Flashing clear-31670-live-server.iso worked fine. Then
>     followed
>      >         the "Use the pre-installed industry ACRN hypervisor"
>      >         section and installed serial port support. Again
this all
>     worked
>      >         fine and looked good.
>      >
>      >         I then rebooted the NUC. At HDMI console get
"Intel NUC"
>     banner
>      >         with the following at top LHS of screen:
>      >
>      >         detected 8 processes, 8 enabled
>      >         current on process 0
>      >
>      >         And on serial port:
>      >
>      >         E0S0 S0
>      >
>      >         Not sure what has happened here. Am I missing
something
>     obvious ?
>      >
>      >         Thanks Steve ____
>      >
>      >
>      >     ____
>      >
>      >     __ __
>      >
>      >     -- ____
>      >
>      >     Engineering Director____
>      >
>      >     IOTech Systems Ltd.____
>      >
>      >     __
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>
--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

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 Steve.

On Fri, 10 Jan 2020 at 09:06, Yin, Fengwei <fengwei.yin@...> wrote:
Hi Steve,

On 2020/1/10 下午5:02, Steve Osselton wrote:
> 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
> supported MSIX tables?
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 2048
         default 16  ---> 64

You could try it as quick check. It's not the preferred way...


Regards
Yin, Fengwei

>
> Cheers Steve.
>
> On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...
> <mailto:fengwei.yin@...>> wrote:
>
>     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 board?
>
>
>     Regards
>     Yin, Fengwei
>
>     On 2020/1/9 下午6:30, Steve Osselton wrote:
>      > 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 clear-32030-live-server.iso onto hard disk.
>      > 2 - Boot:
>      >
>      > # wget
>      >
>     https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
>      > # chmod +x acrn_quick_setup.sh
>      > # ./acrn_quick_setup.sh -s 32030 -d -i
>      > # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u
>      > "uart=port@0x3f8"
>      >
>      > 3 - Reboot:
>      >
>      > Console output:
>      >
>      > ACRN Hypervisor
>      > calibrate_tsc, tsc_khz=2100000
>      > [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
>      > 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
>     mockbuild,
>      > start time 11171478us
>      > [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
>      > [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R)
>      > Core(TM) i7-8650U CPU @ 1.90GHz
>      > [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file
>      > hw/pci.c,line 448 : fatal error
>      >
>      > Still failing ...
>      >
>      > Cheers Steve.
>      >
>      >
>      > On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@...
>     <mailto:fuzhong.liu@...>
>      > <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>> wrote:
>      >
>      >     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@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >     <acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>> *On Behalf Of *Steve
>     Osselton
>      >     *Sent:* Wednesday, January 8, 2020 11:34 PM
>      >     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >     <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >     *Subject:* Re: [acrn-users] Problem with Industry Scenario on a
>      >     NUC7i7DNH____
>      >
>      >     __ __
>      >
>      >     Hi Liu,____
>      >
>      >     __ __
>      >
>      >     On inspection was running an old BIOS version, have upgraded to
>      >     latest version (DNi70067) and disabled hyper threading.____
>      >
>      >     Things are improved in that I now get diagnostics from the serial
>      >     port:____
>      >
>      >     __ __
>      >
>      >     ACRN Hypervisor
>      >     calibrate_tsc, tsc_khz=2100000
>      >     [11041475us][cpu=0][sev=2][seq=1]:HV version
>     1.4-unstable-2019-11-18
>      >     09:13:55- DBG (daily tag:) build by mockbuild, start time
>     11028016us
>      >     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>      >     [11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R)
>      >     Core(TM) i7-8650U CPU @ 1.90GHz
>      >     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>      >     hw/pci.c,line 250 : fatal error____
>      >
>      >     __ __
>      >
>      >     So still failing.____
>      >
>      >     __ __
>      >
>      >     Also as a comment, the BIOS settings descriptions, are badly
>     out of
>      >     step with what you see from the latest visual BIOS.____
>      >
>      >     __ __
>      >
>      >     Cheers Steve.____
>      >
>      >     __ __
>      >
>      >     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
>     <fuzhong.liu@... <mailto:fuzhong.liu@...>
>      >     <mailto:fuzhong.liu@...
>     <mailto:fuzhong.liu@...>>> wrote:____
>      >
>      >         Hi Steve,____
>      >
>      >         Please disable Hyper thread in BIOS for workaround.____
>      >
>      >         This issue is fixed in  v1.5; will release soon.____
>      >
>      >         ____
>      >
>      >         BR.____
>      >
>      >         Fuzhong____
>      >
>      >         ____
>      >
>      >         *From:* acrn-users@...
>     <mailto:acrn-users@...>
>      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >         <acrn-users@...
>     <mailto:acrn-users@...>
>      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>>> *On Behalf Of *Steve
>      >         Osselton
>      >         *Sent:* Wednesday, January 8, 2020 8:32 PM
>      >         *To:* acrn-users@...
>     <mailto:acrn-users@...>
>      >         <mailto:acrn-users@...
>     <mailto:acrn-users@...>>
>      >         *Subject:* [acrn-users] Problem with Industry Scenario on a
>      >         NUC7i7DNH____
>      >
>      >         ____
>      >
>      >         Hi,
>      >
>      >         Am essentially following the deployment instructions for the
>      >         ACRN industry scenario
>      >         using a NUC7i7DNH with a serial port connected.
>      >
>      > https://projectacrn.github.io/latest/getting-started/rt_industry.html
>      >
>      >         Flashing clear-31670-live-server.iso worked fine. Then
>     followed
>      >         the "Use the pre-installed industry ACRN hypervisor"
>      >         section and installed serial port support. Again this all
>     worked
>      >         fine and looked good.
>      >
>      >         I then rebooted the NUC. At HDMI console get "Intel NUC"
>     banner
>      >         with the following at top LHS of screen:
>      >
>      >         detected 8 processes, 8 enabled
>      >         current on process 0
>      >
>      >         And on serial port:
>      >
>      >         E0S0 S0
>      >
>      >         Not sure what has happened here. Am I missing something
>     obvious ?
>      >
>      >         Thanks Steve ____
>      >
>      >
>      >     ____
>      >
>      >     __ __
>      >
>      >     -- ____
>      >
>      >     Engineering Director____
>      >
>      >     IOTech Systems Ltd.____
>      >
>      >     __
>      >
>      >
>      >
>      > --
>      > Engineering Director
>      > IOTech Systems Ltd.
>      >
>
>
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>





--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Yin, Fengwei <fengwei.yin@...>
 

Hi Steve,

On 2020/1/10 下午5:02, Steve Osselton wrote:
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 supported MSIX tables?
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 2048
default 16 ---> 64

You could try it as quick check. It's not the preferred way...


Regards
Yin, Fengwei

Cheers Steve.
On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@... <mailto:fengwei.yin@...>> wrote:
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 board?
Regards
Yin, Fengwei
On 2020/1/9 下午6:30, Steve Osselton wrote:
> 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 clear-32030-live-server.iso onto hard disk.
> 2 - Boot:
>
> # wget
>
https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
> # chmod +x acrn_quick_setup.sh
> # ./acrn_quick_setup.sh -s 32030 -d -i
> # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u
> "uart=port@0x3f8"
>
> 3 - Reboot:
>
> Console output:
>
> ACRN Hypervisor
> calibrate_tsc, tsc_khz=2100000
> [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
> 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by
mockbuild,
> start time 11171478us
> [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
> [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R)
> Core(TM) i7-8650U CPU @ 1.90GHz
> [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file
> hw/pci.c,line 448 : fatal error
>
> Still failing ...
>
> Cheers Steve.
>
>
> On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@...
<mailto:fuzhong.liu@...>
> <mailto:fuzhong.liu@... <mailto:fuzhong.liu@...>>> wrote:
>
>     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@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>     <acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>> *On Behalf Of *Steve
Osselton
>     *Sent:* Wednesday, January 8, 2020 11:34 PM
>     *To:* acrn-users@...
<mailto:acrn-users@...>
>     <mailto:acrn-users@...
<mailto:acrn-users@...>>
>     *Subject:* Re: [acrn-users] Problem with Industry Scenario on a
>     NUC7i7DNH____
>
>     __ __
>
>     Hi Liu,____
>
>     __ __
>
>     On inspection was running an old BIOS version, have upgraded to
>     latest version (DNi70067) and disabled hyper threading.____
>
>     Things are improved in that I now get diagnostics from the serial
>     port:____
>
>     __ __
>
>     ACRN Hypervisor
>     calibrate_tsc, tsc_khz=2100000
>     [11041475us][cpu=0][sev=2][seq=1]:HV version
1.4-unstable-2019-11-18
>     09:13:55- DBG (daily tag:) build by mockbuild, start time
11028016us
>     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>     [11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R)
>     Core(TM) i7-8650U CPU @ 1.90GHz
>     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>     hw/pci.c,line 250 : fatal error____
>
>     __ __
>
>     So still failing.____
>
>     __ __
>
>     Also as a comment, the BIOS settings descriptions, are badly
out of
>     step with what you see from the latest visual BIOS.____
>
>     __ __
>
>     Cheers Steve.____
>
>     __ __
>
>     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong
<fuzhong.liu@... <mailto:fuzhong.liu@...>
>     <mailto:fuzhong.liu@...
<mailto:fuzhong.liu@...>>> wrote:____
>
>         Hi Steve,____
>
>         Please disable Hyper thread in BIOS for workaround.____
>
>         This issue is fixed in  v1.5; will release soon.____
>
>         ____
>
>         BR.____
>
>         Fuzhong____
>
>         ____
>
>         *From:* acrn-users@...
<mailto:acrn-users@...>
>         <mailto:acrn-users@...
<mailto:acrn-users@...>>
>         <acrn-users@...
<mailto:acrn-users@...>
>         <mailto:acrn-users@...
<mailto:acrn-users@...>>> *On Behalf Of *Steve
>         Osselton
>         *Sent:* Wednesday, January 8, 2020 8:32 PM
>         *To:* acrn-users@...
<mailto:acrn-users@...>
>         <mailto:acrn-users@...
<mailto:acrn-users@...>>
>         *Subject:* [acrn-users] Problem with Industry Scenario on a
>         NUC7i7DNH____
>
>         ____
>
>         Hi,
>
>         Am essentially following the deployment instructions for the
>         ACRN industry scenario
>         using a NUC7i7DNH with a serial port connected.
>
> https://projectacrn.github.io/latest/getting-started/rt_industry.html
>
>         Flashing clear-31670-live-server.iso worked fine. Then
followed
>         the "Use the pre-installed industry ACRN hypervisor"
>         section and installed serial port support. Again this all
worked
>         fine and looked good.
>
>         I then rebooted the NUC. At HDMI console get "Intel NUC"
banner
>         with the following at top LHS of screen:
>
>         detected 8 processes, 8 enabled
>         current on process 0
>
>         And on serial port:
>
>         E0S0 S0
>
>         Not sure what has happened here. Am I missing something
obvious ?
>
>         Thanks Steve ____
>
>
>     ____
>
>     __ __
>
>     -- ____
>
>     Engineering Director____
>
>     IOTech Systems Ltd.____
>
>     __
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>
--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

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 supported MSIX tables?

Cheers Steve.

On Fri, 10 Jan 2020 at 05:00, Yin, Fengwei <fengwei.yin@...> wrote:
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 board?


Regards
Yin, Fengwei

On 2020/1/9 下午6:30, Steve Osselton wrote:
> 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 clear-32030-live-server.iso onto hard disk.
> 2 - Boot:
>
> # wget
> https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
> # chmod +x acrn_quick_setup.sh
> # ./acrn_quick_setup.sh -s 32030 -d -i
> # efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u
> "uart=port@0x3f8"
>
> 3 - Reboot:
>
> Console output:
>
> ACRN Hypervisor
> calibrate_tsc, tsc_khz=2100000
> [11187656us][cpu=0][(null)][sev=2][seq=1]:HV version
> 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by mockbuild,
> start time 11171478us
> [11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
> [11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R)
> Core(TM) i7-8650U CPU @ 1.90GHz
> [11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file
> hw/pci.c,line 448 : fatal error
>
> Still failing ...
>
> Cheers Steve.
>
>
> On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@...
> <mailto:fuzhong.liu@...>> wrote:
>
>     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@...
>     <mailto:acrn-users@...>
>     <acrn-users@...
>     <mailto:acrn-users@...>> *On Behalf Of *Steve Osselton
>     *Sent:* Wednesday, January 8, 2020 11:34 PM
>     *To:* acrn-users@...
>     <mailto:acrn-users@...>
>     *Subject:* Re: [acrn-users] Problem with Industry Scenario on a
>     NUC7i7DNH____
>
>     __ __
>
>     Hi Liu,____
>
>     __ __
>
>     On inspection was running an old BIOS version, have upgraded to
>     latest version (DNi70067) and disabled hyper threading.____
>
>     Things are improved in that I now get diagnostics from the serial
>     port:____
>
>     __ __
>
>     ACRN Hypervisor
>     calibrate_tsc, tsc_khz=2100000
>     [11041475us][cpu=0][sev=2][seq=1]:HV version 1.4-unstable-2019-11-18
>     09:13:55- DBG (daily tag:) build by mockbuild, start time 11028016us
>     [11054921us][cpu=0][sev=2][seq=2]:API version 1.0
>     [11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R)
>     Core(TM) i7-8650U CPU @ 1.90GHz
>     [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
>     hw/pci.c,line 250 : fatal error____
>
>     __ __
>
>     So still failing.____
>
>     __ __
>
>     Also as a comment, the BIOS settings descriptions, are badly out of
>     step with what you see from the latest visual BIOS.____
>
>     __ __
>
>     Cheers Steve.____
>
>     __ __
>
>     On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong <fuzhong.liu@...
>     <mailto:fuzhong.liu@...>> wrote:____
>
>         Hi Steve,____
>
>         Please disable Hyper thread in BIOS for workaround.____
>
>         This issue is fixed in  v1.5; will release soon.____
>
>         ____
>
>         BR.____
>
>         Fuzhong____
>
>         ____
>
>         *From:* acrn-users@...
>         <mailto:acrn-users@...>
>         <acrn-users@...
>         <mailto:acrn-users@...>> *On Behalf Of *Steve
>         Osselton
>         *Sent:* Wednesday, January 8, 2020 8:32 PM
>         *To:* acrn-users@...
>         <mailto:acrn-users@...>
>         *Subject:* [acrn-users] Problem with Industry Scenario on a
>         NUC7i7DNH____
>
>         ____
>
>         Hi,
>
>         Am essentially following the deployment instructions for the
>         ACRN industry scenario
>         using a NUC7i7DNH with a serial port connected.
>
>         https://projectacrn.github.io/latest/getting-started/rt_industry.html
>
>         Flashing clear-31670-live-server.iso worked fine. Then followed
>         the "Use the pre-installed industry ACRN hypervisor"
>         section and installed serial port support. Again this all worked
>         fine and looked good.
>
>         I then rebooted the NUC. At HDMI console get "Intel NUC" banner
>         with the following at top LHS of screen:
>
>         detected 8 processes, 8 enabled
>         current on process 0
>
>         And on serial port:
>
>         E0S0 S0
>
>         Not sure what has happened here. Am I missing something obvious ?
>
>         Thanks Steve ____
>
>
>     ____
>
>     __ __
>
>     -- ____
>
>     Engineering Director____
>
>     IOTech Systems Ltd.____
>
>     __
>
>
>
> --
> Engineering Director
> IOTech Systems Ltd.
>





--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

Hi Geoffroy,

Have installed 2*8GB SODIMM plus a SATA hard disk and a PCI SSD (Samsung 500GB Evo).

Cheers Steve.

On Thu, 9 Jan 2020 at 22:36, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

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 Behalf Of Steve Osselton
Sent: Thursday, January 9, 2020 11:30 AM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

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 clear-32030-live-server.iso onto hard disk.

2 - Boot:

 

# ./acrn_quick_setup.sh -s 32030 -d -i

# efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u "uart=port@0x3f8"

 

3 - Reboot:

 

Console output:

 

ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11187656us][cpu=0][(null)][sev=2][seq=1]:HV version 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by mockbuild, start time 11171478us
[11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
[11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 448 : fatal error

 

Still failing ...

 

Cheers Steve.

 

 

On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@...> wrote:

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 Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 11:34 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Liu,

 

On inspection was running an old BIOS version, have upgraded to latest version (DNi70067) and disabled hyper threading.

Things are improved in that I now get diagnostics from the serial port:

 

ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11041475us][cpu=0][sev=2][seq=1]:HV version 1.4-unstable-2019-11-18 09:13:55- DBG (daily tag:) build by mockbuild, start time 11028016us
[11054921us][cpu=0][sev=2][seq=2]:API version 1.0
[11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 250 : fatal error

 

So still failing.

 

Also as a comment, the BIOS settings descriptions, are badly out of step with what you see from the latest visual BIOS.

 

Cheers Steve.

 

On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Steve,

Please disable Hyper thread in BIOS for workaround.

This issue is fixed in  v1.5; will release soon.

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 8:32 PM
To: acrn-users@...
Subject: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi,

Am essentially following the deployment instructions for the ACRN industry scenario
using a NUC7i7DNH with a serial port connected.

https://projectacrn.github.io/latest/getting-started/rt_industry.html

Flashing clear-31670-live-server.iso worked fine. Then followed the "Use the pre-installed industry ACRN hypervisor"
section and installed serial port support. Again this all worked fine and looked good.

I then rebooted the NUC. At HDMI console get "Intel NUC" banner with the following at top LHS of screen:

detected 8 processes, 8 enabled
current on process 0

And on serial port:

E0S0 S0

Not sure what has happened here. Am I missing something obvious ?

Thanks Steve


 

--

Engineering Director

IOTech Systems Ltd.


 

--

Engineering Director

IOTech Systems Ltd.



--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Yin, Fengwei <fengwei.yin@...>
 

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


Regards
Yin, Fengwei

On 2020/1/9 下午6:30, Steve Osselton wrote:
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 clear-32030-live-server.iso onto hard disk.
2 - Boot:
# wget https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/acrn_quick_setup.sh
# chmod +x acrn_quick_setup.sh
# ./acrn_quick_setup.sh -s 32030 -d -i
# efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u "uart=port@0x3f8"
3 - Reboot:
Console output:
ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11187656us][cpu=0][(null)][sev=2][seq=1]:HV version 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by mockbuild, start time 11171478us
[11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
[11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 448 : fatal error
Still failing ...
Cheers Steve.
On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@... <mailto:fuzhong.liu@...>> wrote:
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@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Steve Osselton
*Sent:* Wednesday, January 8, 2020 11:34 PM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* Re: [acrn-users] Problem with Industry Scenario on a
NUC7i7DNH____
__ __
Hi Liu,____
__ __
On inspection was running an old BIOS version, have upgraded to
latest version (DNi70067) and disabled hyper threading.____
Things are improved in that I now get diagnostics from the serial
port:____
__ __
ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11041475us][cpu=0][sev=2][seq=1]:HV version 1.4-unstable-2019-11-18
09:13:55- DBG (daily tag:) build by mockbuild, start time 11028016us
[11054921us][cpu=0][sev=2][seq=2]:API version 1.0
[11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R)
Core(TM) i7-8650U CPU @ 1.90GHz
[11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file
hw/pci.c,line 250 : fatal error____
__ __
So still failing.____
__ __
Also as a comment, the BIOS settings descriptions, are badly out of
step with what you see from the latest visual BIOS.____
__ __
Cheers Steve.____
__ __
On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong <fuzhong.liu@...
<mailto:fuzhong.liu@...>> wrote:____
Hi Steve,____
Please disable Hyper thread in BIOS for workaround.____
This issue is fixed in  v1.5; will release soon.____
____
BR.____
Fuzhong____
____
*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Steve
Osselton
*Sent:* Wednesday, January 8, 2020 8:32 PM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* [acrn-users] Problem with Industry Scenario on a
NUC7i7DNH____
____
Hi,
Am essentially following the deployment instructions for the
ACRN industry scenario
using a NUC7i7DNH with a serial port connected.
https://projectacrn.github.io/latest/getting-started/rt_industry.html
Flashing clear-31670-live-server.iso worked fine. Then followed
the "Use the pre-installed industry ACRN hypervisor"
section and installed serial port support. Again this all worked
fine and looked good.
I then rebooted the NUC. At HDMI console get "Intel NUC" banner
with the following at top LHS of screen:
detected 8 processes, 8 enabled
current on process 0
And on serial port:
E0S0 S0
Not sure what has happened here. Am I missing something obvious ?
Thanks Steve ____
____
__ __
-- ____
Engineering Director____
IOTech Systems Ltd.____
__
--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Geoffroy Van Cutsem
 

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 Behalf Of Steve Osselton
Sent: Thursday, January 9, 2020 11:30 AM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

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 clear-32030-live-server.iso onto hard disk.

2 - Boot:

 

# ./acrn_quick_setup.sh -s 32030 -d -i

# efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u "uart=port@0x3f8"

 

3 - Reboot:

 

Console output:

 

ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11187656us][cpu=0][(null)][sev=2][seq=1]:HV version 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by mockbuild, start time 11171478us
[11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
[11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 448 : fatal error

 

Still failing ...

 

Cheers Steve.

 

 

On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@...> wrote:

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 Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 11:34 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Liu,

 

On inspection was running an old BIOS version, have upgraded to latest version (DNi70067) and disabled hyper threading.

Things are improved in that I now get diagnostics from the serial port:

 

ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11041475us][cpu=0][sev=2][seq=1]:HV version 1.4-unstable-2019-11-18 09:13:55- DBG (daily tag:) build by mockbuild, start time 11028016us
[11054921us][cpu=0][sev=2][seq=2]:API version 1.0
[11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 250 : fatal error

 

So still failing.

 

Also as a comment, the BIOS settings descriptions, are badly out of step with what you see from the latest visual BIOS.

 

Cheers Steve.

 

On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Steve,

Please disable Hyper thread in BIOS for workaround.

This issue is fixed in  v1.5; will release soon.

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 8:32 PM
To: acrn-users@...
Subject: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi,

Am essentially following the deployment instructions for the ACRN industry scenario
using a NUC7i7DNH with a serial port connected.

https://projectacrn.github.io/latest/getting-started/rt_industry.html

Flashing clear-31670-live-server.iso worked fine. Then followed the "Use the pre-installed industry ACRN hypervisor"
section and installed serial port support. Again this all worked fine and looked good.

I then rebooted the NUC. At HDMI console get "Intel NUC" banner with the following at top LHS of screen:

detected 8 processes, 8 enabled
current on process 0

And on serial port:

E0S0 S0

Not sure what has happened here. Am I missing something obvious ?

Thanks Steve


 

--

Engineering Director

IOTech Systems Ltd.


 

--

Engineering Director

IOTech Systems Ltd.


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Geoffroy Van Cutsem
 

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: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

 

 

On Thu, Jan 9, 2020 at 11:39 AM Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Alfonso,

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

 

 

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.

 

BR.

Fuzhong

Best,

Alfonso 

 

-----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of Geoffroy Van Cutsem
Sent: Thursday, January 9, 2020 5:54 PM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Fengwei,

 

> -----Original Message-----

> From: acrn-users@...

> <acrn-users@...> On Behalf Of Yin, Fengwei

> Sent: Thursday, January 9, 2020 10:42 AM

> To: acrn-users@...

> Subject: Re: [acrn-users] Cannot launch hart RT UOS when running

> Ubuntu as SOS

>

> Hi Alfonso,

>

> On 2020/1/9 下午5:11, Alfonso Sanchez-Beato wrote:

> > 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 errors:

> >

> > https://paste.ubuntu.com/p/R7THmm3hK6/

> It's related with iasl in your SOS. We have constrain for iasl version.

 

Do you know which version Alfonso should use? I believe it is 20191018 but it would be appreciated if you could confirm.

 

@Alfonso, if true, you can install it as follows $ sudo apt update $ sudo apt install m4 bison flex zlib1g-dev $ cd ~ $ wget https://acpica.org/sites/acpica/files/acpica-unix-20191018.tar.gz

$ tar zxvf acpica-unix-20191018.tar.gz

$ cd acpica-unix-20191018

$ make clean && make iasl

$ sudo cp ./generate/unix/bin/iasl /usr/sbin/

 

Thanks,

Geoffroy

 

>

>

> Regards

> Yin, Fengwei

>

> >

> > Version info:

> >

> > $ acrn-dm -v

> > DM version is: 1.4-unstable-bcefd673 (daily

> > tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17

> >

> > ubuntu@nuc:~$ uname -a

> > Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18

> > 09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

> >

> > I have not been able yet to get output from the serial port, unfortunately.

> >

> > Full dmesg output: https://paste.ubuntu.com/p/G8DtQTMrbS/

> >

> > I see there an hvlog error which I do not know if it is relevant or not:

> >

> > $ sudo dmesg | grep -i ACRN

> > [    0.000000] Command line:

> > BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98

> > pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0

> > root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check

> > consoleblank=0

> > i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F

> > i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1

> > i915.enable_guc=0 hvlog=2M@0x1FE00000 [    0.000000] Hypervisor

> > detected: ACRN [    0.054541] Kernel command

> > line:

> > BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98

> > pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0

> > root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check

> > consoleblank=0

> > i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F

> > i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1

> > i915.enable_guc=0 hvlog=2M@0x1FE00000 [    1.058634] acrngt found [    

> > 1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu [

> > 1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19 [

> > 1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu

> >

> > Thanks

> > Alfonso

> >

> > On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@...

> > <mailto:fuzhong.liu@...>> wrote:

> >

> >     Hi Alfonso____

> >

> >     Could you please share acrn.efi and acrn-dm commit info?____

> >

> >     __ __

> >

> >     With following steps:____

> >

> >      1. run “acrn-dm -v” in sos ____

> >      2. run “version” in HV console____

> >

> >     We need them to reproduce this issue.____

> >

> >     Thanks!____

> >

> >     __ __

> >

> >     BR.____

> >

> >     Fuzhong____

> >

> >     __ __

> >

> >     *From:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     <acrn-users@...

> >     <mailto:acrn-users@...>> *On Behalf Of *Liu, Fuzhong

> >     *Sent:* Thursday, January 9, 2020 5:36 AM

> >     *To:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     *Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running

> >     Ubuntu as SOS____

> >

> >     __ __

> >

> >     Hi Alfonso____

> >

> >     Please share your acrn.efi and acrn-dm, will reproduce this issue on

> >     our side.____

> >

> >     Thanks!____

> >

> >     __ __

> >

> >     BR.____

> >

> >     Fuzhong____

> >

> >     __ __

> >

> >     *From:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     <acrn-users@...

> >     <mailto:acrn-users@...>> *On Behalf Of *Alfonso

> >     Sanchez-Beato

> >     *Sent:* Wednesday, January 8, 2020 7:39 PM

> >     *To:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     *Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running

> >     Ubuntu as SOS____

> >

> >     __ __

> >

> >     Hi Liu,____

> >

> >     __ __

> >

> >     On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...

> >     <mailto:fuzhong.liu@...>> wrote:____

> >

> >         Hi Alfonso,____

> >

> >         You are using default launch_hard_rt_vm.sh, right?____

> >

> >         Maybe, it is SDC(by default) scenario for your acrn.efi,

> > ____

> >

> >         Please refer following patch:____

> >

> >         ____

> >

> >         *diff --git a/hypervisor/arch/x86/Kconfig

> >         b/hypervisor/arch/x86/Kconfig*____

> >

> >         *index 41a78fe7..386a074b 100644*____

> >

> >         *--- a/hypervisor/arch/x86/Kconfig*____

> >

> >         *+++ b/hypervisor/arch/x86/Kconfig*____

> >

> >         @@ -1,6 +1,6 @@____

> >

> >         choice____

> >

> >                  prompt "ACRN Scenario"____

> >

> >         -       default SDC____

> >

> >         +default INDUSTRY____

> >

> >                  help____

> >

> >                    Select the scenario name to load corresponding VM

> >         configuration.____

> >

> >         ____

> >

> >         Then;____

> >

> >         ____

> >

> >         cd ~/acrn-hypervisor____

> >

> >         make____

> >

> >         sudo make install____

> >

> >         ____

> >

> >         And try again.____

> >

> >     __ __

> >

> >     I tried with that, but no difference in the traces :-/.____

> >

> >     Actually I had already tried with 'make all BOARD=nuc7i7dnb

> >     SCENARIO=industry', which I guess i the same.____

> >

> >     ____

> >

> >         ____

> >

> >         Thanks!____

> >

> >         ____

> >

> >         BR.____

> >

> >         Fuzhong____

> >

> >     __ __

> >

> >     Thanks____

> >

> >     Alfonso____

> >

> >     ____

> >

> >         ____

> >

> >         *From:* acrn-users@...

> >         <mailto:acrn-users@...>

> >         <acrn-users@...

> >         <mailto:acrn-users@...>> *On Behalf Of

> >         *alfonso.sanchez-beato@...

> >         <mailto:alfonso.sanchez-beato@...>

> >         *Sent:* Wednesday, January 8, 2020 5:44 PM

> >         *To:* acrn-users@...

> >         <mailto:acrn-users@...>

> >         *Subject:* [acrn-users] Cannot launch hart RT UOS when running

> >         Ubuntu as SOS____

> >

> >         ____

> >

> >         Hi,

> >

> >         I have set-up Ubuntu as service OS by following the instructions

> >         in

> >         https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html.

> >

> <https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.ht

> ml>ACRN

> >         is recognized as hypervisor and all looks good in principle.

> >         However, after that I followed the instructions on how to start

> >         an RT UOS

> >         <https://projectacrn.github.io/latest/getting-

> started/rt_industry.html#install-and-launch-the-preempt-rt-vm>

> >         and things fail:____

> >

> >         $ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh____

> >

> >         cpu1 online=1____

> >

> >         cpu2 online=1____

> >

> >         cpu3 online=1____

> >

> >         pm by vuart node-index = 1____

> >

> >         SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size

> >         0x200000____

> >

> >         vm_create: hard_rtvm____

> >

> >         VHM api version 1.0____

> >

> >         failed to create VM hard_rtvm____

> >

> >

> >         The kernel output is:____

> >

> >         [ 1530.397790] smpboot: CPU 1 is now offline____

> >

> >         [ 1530.398653] vhm: try to offline cpu 1 with lapicid 2____

> >

> >         [ 1530.409744] smpboot: CPU 2 is now offline____

> >

> >         [ 1530.410476] vhm: try to offline cpu 2 with lapicid 4____

> >

> >         [ 1530.429694] smpboot: CPU 3 is now offline____

> >

> >         [ 1530.430509] vhm: try to offline cpu 3 with lapicid 6____

> >

> >         [ 1530.575078] nvme nvme0: failed to set APST feature

> > (-19)____

> >

> >         [ 1530.579387] pci-stub 0000:02:00.0: claimed by stub____

> >

> >         [ 1530.661794] vhm_dev_open: opening device node____

> >

> >         [ 1530.663654] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1531.163905] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1531.664126] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1532.164360] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1532.664589] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1533.164775] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1533.664987] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1534.165215] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1534.665435] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1535.165656] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1535.682037] vhm: freed vm____

> >

> >         ____

> >

> >         Any hint on what might be going wrong and instructions on how to

> >         debug? I followed previously the tutorial for Clear Linux and

> >         was able to launch the RT image. I am using a NUC7i7DNH device.

> >

> >         Thanks!

> >         Alfonso____

> >

> >     __

> >

> >

>

>

 

 

 


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Alfonso Sanchez-Beato
 



On Thu, Jan 9, 2020 at 11:39 AM Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Alfonso,

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

 


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.
 

BR.

Fuzhong

Best,
Alfonso 

 

-----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of Geoffroy Van Cutsem
Sent: Thursday, January 9, 2020 5:54 PM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Fengwei,

 

> -----Original Message-----

> From: acrn-users@...

> <acrn-users@...> On Behalf Of Yin, Fengwei

> Sent: Thursday, January 9, 2020 10:42 AM

> To: acrn-users@...

> Subject: Re: [acrn-users] Cannot launch hart RT UOS when running

> Ubuntu as SOS

>

> Hi Alfonso,

>

> On 2020/1/9 下午5:11, Alfonso Sanchez-Beato wrote:

> > 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 errors:

> >

> > https://paste.ubuntu.com/p/R7THmm3hK6/

> It's related with iasl in your SOS. We have constrain for iasl version.

 

Do you know which version Alfonso should use? I believe it is 20191018 but it would be appreciated if you could confirm.

 

@Alfonso, if true, you can install it as follows $ sudo apt update $ sudo apt install m4 bison flex zlib1g-dev $ cd ~ $ wget https://acpica.org/sites/acpica/files/acpica-unix-20191018.tar.gz

$ tar zxvf acpica-unix-20191018.tar.gz

$ cd acpica-unix-20191018

$ make clean && make iasl

$ sudo cp ./generate/unix/bin/iasl /usr/sbin/

 

Thanks,

Geoffroy

 

>

>

> Regards

> Yin, Fengwei

>

> >

> > Version info:

> >

> > $ acrn-dm -v

> > DM version is: 1.4-unstable-bcefd673 (daily

> > tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17

> >

> > ubuntu@nuc:~$ uname -a

> > Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18

> > 09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

> >

> > I have not been able yet to get output from the serial port, unfortunately.

> >

> > Full dmesg output: https://paste.ubuntu.com/p/G8DtQTMrbS/

> >

> > I see there an hvlog error which I do not know if it is relevant or not:

> >

> > $ sudo dmesg | grep -i ACRN

> > [    0.000000] Command line:

> > BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98

> > pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0

> > root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check

> > consoleblank=0

> > i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F

> > i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1

> > i915.enable_guc=0 hvlog=2M@0x1FE00000 [    0.000000] Hypervisor

> > detected: ACRN [    0.054541] Kernel command

> > line:

> > BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98

> > pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0

> > root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check

> > consoleblank=0

> > i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F

> > i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1

> > i915.enable_guc=0 hvlog=2M@0x1FE00000 [    1.058634] acrngt found [    

> > 1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu [

> > 1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19 [

> > 1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu

> >

> > Thanks

> > Alfonso

> >

> > On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@...

> > <mailto:fuzhong.liu@...>> wrote:

> >

> >     Hi Alfonso____

> >

> >     Could you please share acrn.efi and acrn-dm commit info?____

> >

> >     __ __

> >

> >     With following steps:____

> >

> >      1. run “acrn-dm -v” in sos ____

> >      2. run “version” in HV console____

> >

> >     We need them to reproduce this issue.____

> >

> >     Thanks!____

> >

> >     __ __

> >

> >     BR.____

> >

> >     Fuzhong____

> >

> >     __ __

> >

> >     *From:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     <acrn-users@...

> >     <mailto:acrn-users@...>> *On Behalf Of *Liu, Fuzhong

> >     *Sent:* Thursday, January 9, 2020 5:36 AM

> >     *To:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     *Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running

> >     Ubuntu as SOS____

> >

> >     __ __

> >

> >     Hi Alfonso____

> >

> >     Please share your acrn.efi and acrn-dm, will reproduce this issue on

> >     our side.____

> >

> >     Thanks!____

> >

> >     __ __

> >

> >     BR.____

> >

> >     Fuzhong____

> >

> >     __ __

> >

> >     *From:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     <acrn-users@...

> >     <mailto:acrn-users@...>> *On Behalf Of *Alfonso

> >     Sanchez-Beato

> >     *Sent:* Wednesday, January 8, 2020 7:39 PM

> >     *To:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     *Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running

> >     Ubuntu as SOS____

> >

> >     __ __

> >

> >     Hi Liu,____

> >

> >     __ __

> >

> >     On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...

> >     <mailto:fuzhong.liu@...>> wrote:____

> >

> >         Hi Alfonso,____

> >

> >         You are using default launch_hard_rt_vm.sh, right?____

> >

> >         Maybe, it is SDC(by default) scenario for your acrn.efi,

> > ____

> >

> >         Please refer following patch:____

> >

> >         ____

> >

> >         *diff --git a/hypervisor/arch/x86/Kconfig

> >         b/hypervisor/arch/x86/Kconfig*____

> >

> >         *index 41a78fe7..386a074b 100644*____

> >

> >         *--- a/hypervisor/arch/x86/Kconfig*____

> >

> >         *+++ b/hypervisor/arch/x86/Kconfig*____

> >

> >         @@ -1,6 +1,6 @@____

> >

> >         choice____

> >

> >                  prompt "ACRN Scenario"____

> >

> >         -       default SDC____

> >

> >         +default INDUSTRY____

> >

> >                  help____

> >

> >                    Select the scenario name to load corresponding VM

> >         configuration.____

> >

> >         ____

> >

> >         Then;____

> >

> >         ____

> >

> >         cd ~/acrn-hypervisor____

> >

> >         make____

> >

> >         sudo make install____

> >

> >         ____

> >

> >         And try again.____

> >

> >     __ __

> >

> >     I tried with that, but no difference in the traces :-/.____

> >

> >     Actually I had already tried with 'make all BOARD=nuc7i7dnb

> >     SCENARIO=industry', which I guess i the same.____

> >

> >     ____

> >

> >         ____

> >

> >         Thanks!____

> >

> >         ____

> >

> >         BR.____

> >

> >         Fuzhong____

> >

> >     __ __

> >

> >     Thanks____

> >

> >     Alfonso____

> >

> >     ____

> >

> >         ____

> >

> >         *From:* acrn-users@...

> >         <mailto:acrn-users@...>

> >         <acrn-users@...

> >         <mailto:acrn-users@...>> *On Behalf Of

> >         *alfonso.sanchez-beato@...

> >         <mailto:alfonso.sanchez-beato@...>

> >         *Sent:* Wednesday, January 8, 2020 5:44 PM

> >         *To:* acrn-users@...

> >         <mailto:acrn-users@...>

> >         *Subject:* [acrn-users] Cannot launch hart RT UOS when running

> >         Ubuntu as SOS____

> >

> >         ____

> >

> >         Hi,

> >

> >         I have set-up Ubuntu as service OS by following the instructions

> >         in

> >         https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html.

> >

> <https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.ht

> ml>ACRN

> >         is recognized as hypervisor and all looks good in principle.

> >         However, after that I followed the instructions on how to start

> >         an RT UOS

> >         <https://projectacrn.github.io/latest/getting-

> started/rt_industry.html#install-and-launch-the-preempt-rt-vm>

> >         and things fail:____

> >

> >         $ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh____

> >

> >         cpu1 online=1____

> >

> >         cpu2 online=1____

> >

> >         cpu3 online=1____

> >

> >         pm by vuart node-index = 1____

> >

> >         SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size

> >         0x200000____

> >

> >         vm_create: hard_rtvm____

> >

> >         VHM api version 1.0____

> >

> >         failed to create VM hard_rtvm____

> >

> >

> >         The kernel output is:____

> >

> >         [ 1530.397790] smpboot: CPU 1 is now offline____

> >

> >         [ 1530.398653] vhm: try to offline cpu 1 with lapicid 2____

> >

> >         [ 1530.409744] smpboot: CPU 2 is now offline____

> >

> >         [ 1530.410476] vhm: try to offline cpu 2 with lapicid 4____

> >

> >         [ 1530.429694] smpboot: CPU 3 is now offline____

> >

> >         [ 1530.430509] vhm: try to offline cpu 3 with lapicid 6____

> >

> >         [ 1530.575078] nvme nvme0: failed to set APST feature

> > (-19)____

> >

> >         [ 1530.579387] pci-stub 0000:02:00.0: claimed by stub____

> >

> >         [ 1530.661794] vhm_dev_open: opening device node____

> >

> >         [ 1530.663654] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1531.163905] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1531.664126] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1532.164360] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1532.664589] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1533.164775] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1533.664987] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1534.165215] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1534.665435] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1535.165656] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1535.682037] vhm: freed vm____

> >

> >         ____

> >

> >         Any hint on what might be going wrong and instructions on how to

> >         debug? I followed previously the tutorial for Clear Linux and

> >         was able to launch the RT image. I am using a NUC7i7DNH device.

> >

> >         Thanks!

> >         Alfonso____

> >

> >     __

> >

> >

>

>

 

 

 


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Liu, Fuzhong
 

Hi Alfonso,

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

 

BR.

Fuzhong

 

-----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of Geoffroy Van Cutsem
Sent: Thursday, January 9, 2020 5:54 PM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Fengwei,

 

> -----Original Message-----

> From: acrn-users@...

> <acrn-users@...> On Behalf Of Yin, Fengwei

> Sent: Thursday, January 9, 2020 10:42 AM

> To: acrn-users@...

> Subject: Re: [acrn-users] Cannot launch hart RT UOS when running

> Ubuntu as SOS

>

> Hi Alfonso,

>

> On 2020/1/9 下午5:11, Alfonso Sanchez-Beato wrote:

> > 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 errors:

> >

> > https://paste.ubuntu.com/p/R7THmm3hK6/

> It's related with iasl in your SOS. We have constrain for iasl version.

 

Do you know which version Alfonso should use? I believe it is 20191018 but it would be appreciated if you could confirm.

 

@Alfonso, if true, you can install it as follows $ sudo apt update $ sudo apt install m4 bison flex zlib1g-dev $ cd ~ $ wget https://acpica.org/sites/acpica/files/acpica-unix-20191018.tar.gz

$ tar zxvf acpica-unix-20191018.tar.gz

$ cd acpica-unix-20191018

$ make clean && make iasl

$ sudo cp ./generate/unix/bin/iasl /usr/sbin/

 

Thanks,

Geoffroy

 

>

>

> Regards

> Yin, Fengwei

>

> >

> > Version info:

> >

> > $ acrn-dm -v

> > DM version is: 1.4-unstable-bcefd673 (daily

> > tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17

> >

> > ubuntu@nuc:~$ uname -a

> > Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18

> > 09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

> >

> > I have not been able yet to get output from the serial port, unfortunately.

> >

> > Full dmesg output: https://paste.ubuntu.com/p/G8DtQTMrbS/

> >

> > I see there an hvlog error which I do not know if it is relevant or not:

> >

> > $ sudo dmesg | grep -i ACRN

> > [    0.000000] Command line:

> > BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98

> > pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0

> > root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check

> > consoleblank=0

> > i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F

> > i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1

> > i915.enable_guc=0 hvlog=2M@0x1FE00000 [    0.000000] Hypervisor

> > detected: ACRN [    0.054541] Kernel command

> > line:

> > BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98

> > pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0

> > root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check

> > consoleblank=0

> > i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F

> > i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1

> > i915.enable_guc=0 hvlog=2M@0x1FE00000 [    1.058634] acrngt found [    

> > 1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu [

> > 1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19 [

> > 1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu

> >

> > Thanks

> > Alfonso

> >

> > On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@...

> > <mailto:fuzhong.liu@...>> wrote:

> >

> >     Hi Alfonso____

> >

> >     Could you please share acrn.efi and acrn-dm commit info?____

> >

> >     __ __

> >

> >     With following steps:____

> >

> >      1. run “acrn-dm -v” in sos ____

> >      2. run “version” in HV console____

> >

> >     We need them to reproduce this issue.____

> >

> >     Thanks!____

> >

> >     __ __

> >

> >     BR.____

> >

> >     Fuzhong____

> >

> >     __ __

> >

> >     *From:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     <acrn-users@...

> >     <mailto:acrn-users@...>> *On Behalf Of *Liu, Fuzhong

> >     *Sent:* Thursday, January 9, 2020 5:36 AM

> >     *To:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     *Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running

> >     Ubuntu as SOS____

> >

> >     __ __

> >

> >     Hi Alfonso____

> >

> >     Please share your acrn.efi and acrn-dm, will reproduce this issue on

> >     our side.____

> >

> >     Thanks!____

> >

> >     __ __

> >

> >     BR.____

> >

> >     Fuzhong____

> >

> >     __ __

> >

> >     *From:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     <acrn-users@...

> >     <mailto:acrn-users@...>> *On Behalf Of *Alfonso

> >     Sanchez-Beato

> >     *Sent:* Wednesday, January 8, 2020 7:39 PM

> >     *To:* acrn-users@...

> >     <mailto:acrn-users@...>

> >     *Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running

> >     Ubuntu as SOS____

> >

> >     __ __

> >

> >     Hi Liu,____

> >

> >     __ __

> >

> >     On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...

> >     <mailto:fuzhong.liu@...>> wrote:____

> >

> >         Hi Alfonso,____

> >

> >         You are using default launch_hard_rt_vm.sh, right?____

> >

> >         Maybe, it is SDC(by default) scenario for your acrn.efi,

> > ____

> >

> >         Please refer following patch:____

> >

> >         ____

> >

> >         *diff --git a/hypervisor/arch/x86/Kconfig

> >         b/hypervisor/arch/x86/Kconfig*____

> >

> >         *index 41a78fe7..386a074b 100644*____

> >

> >         *--- a/hypervisor/arch/x86/Kconfig*____

> >

> >         *+++ b/hypervisor/arch/x86/Kconfig*____

> >

> >         @@ -1,6 +1,6 @@____

> >

> >         choice____

> >

> >                  prompt "ACRN Scenario"____

> >

> >         -       default SDC____

> >

> >         +default INDUSTRY____

> >

> >                  help____

> >

> >                    Select the scenario name to load corresponding VM

> >         configuration.____

> >

> >         ____

> >

> >         Then;____

> >

> >         ____

> >

> >         cd ~/acrn-hypervisor____

> >

> >         make____

> >

> >         sudo make install____

> >

> >         ____

> >

> >         And try again.____

> >

> >     __ __

> >

> >     I tried with that, but no difference in the traces :-/.____

> >

> >     Actually I had already tried with 'make all BOARD=nuc7i7dnb

> >     SCENARIO=industry', which I guess i the same.____

> >

> >     ____

> >

> >         ____

> >

> >         Thanks!____

> >

> >         ____

> >

> >         BR.____

> >

> >         Fuzhong____

> >

> >     __ __

> >

> >     Thanks____

> >

> >     Alfonso____

> >

> >     ____

> >

> >         ____

> >

> >         *From:* acrn-users@...

> >         <mailto:acrn-users@...>

> >         <acrn-users@...

> >         <mailto:acrn-users@...>> *On Behalf Of

> >         *alfonso.sanchez-beato@...

> >         <mailto:alfonso.sanchez-beato@...>

> >         *Sent:* Wednesday, January 8, 2020 5:44 PM

> >         *To:* acrn-users@...

> >         <mailto:acrn-users@...>

> >         *Subject:* [acrn-users] Cannot launch hart RT UOS when running

> >         Ubuntu as SOS____

> >

> >         ____

> >

> >         Hi,

> >

> >         I have set-up Ubuntu as service OS by following the instructions

> >         in

> >         https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html.

> >

> <https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.ht

> ml>ACRN

> >         is recognized as hypervisor and all looks good in principle.

> >         However, after that I followed the instructions on how to start

> >         an RT UOS

> >         <https://projectacrn.github.io/latest/getting-

> started/rt_industry.html#install-and-launch-the-preempt-rt-vm>

> >         and things fail:____

> >

> >         $ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh____

> >

> >         cpu1 online=1____

> >

> >         cpu2 online=1____

> >

> >         cpu3 online=1____

> >

> >         pm by vuart node-index = 1____

> >

> >         SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size

> >         0x200000____

> >

> >         vm_create: hard_rtvm____

> >

> >         VHM api version 1.0____

> >

> >         failed to create VM hard_rtvm____

> >

> >

> >         The kernel output is:____

> >

> >         [ 1530.397790] smpboot: CPU 1 is now offline____

> >

> >         [ 1530.398653] vhm: try to offline cpu 1 with lapicid 2____

> >

> >         [ 1530.409744] smpboot: CPU 2 is now offline____

> >

> >         [ 1530.410476] vhm: try to offline cpu 2 with lapicid 4____

> >

> >         [ 1530.429694] smpboot: CPU 3 is now offline____

> >

> >         [ 1530.430509] vhm: try to offline cpu 3 with lapicid 6____

> >

> >         [ 1530.575078] nvme nvme0: failed to set APST feature

> > (-19)____

> >

> >         [ 1530.579387] pci-stub 0000:02:00.0: claimed by stub____

> >

> >         [ 1530.661794] vhm_dev_open: opening device node____

> >

> >         [ 1530.663654] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1531.163905] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1531.664126] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1532.164360] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1532.664589] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1533.164775] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1533.664987] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1534.165215] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1534.665435] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1535.165656] vhm: failed to create VM from Hypervisor

> > !____

> >

> >         [ 1535.682037] vhm: freed vm____

> >

> >         ____

> >

> >         Any hint on what might be going wrong and instructions on how to

> >         debug? I followed previously the tutorial for Clear Linux and

> >         was able to launch the RT image. I am using a NUC7i7DNH device.

> >

> >         Thanks!

> >         Alfonso____

> >

> >     __

> >

> >

>

>

 

 

 


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

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 clear-32030-live-server.iso onto hard disk.
2 - Boot:

# ./acrn_quick_setup.sh -s 32030 -d -i
# efibootmgr -c -l '\EFI\acrn\acrn.efi' -d /dev/sda -p 1 -L ACRN -u "uart=port@0x3f8"

3 - Reboot:

Console output:

ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11187656us][cpu=0][(null)][sev=2][seq=1]:HV version 1.5-unstable-2020-01-05 11:33:11- DBG (daily tag:) build by mockbuild, start time 11171478us
[11201829us][cpu=0][(null)][sev=2][seq=2]:API version 1.0
[11207570us][cpu=0][(null)][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11218392us][cpu=0][(null)][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 448 : fatal error

Still failing ...

Cheers Steve.


On Thu, 9 Jan 2020 at 02:40, Liu, Fuzhong <fuzhong.liu@...> wrote:

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 Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 11:34 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi Liu,

 

On inspection was running an old BIOS version, have upgraded to latest version (DNi70067) and disabled hyper threading.

Things are improved in that I now get diagnostics from the serial port:

 

ACRN Hypervisor
calibrate_tsc, tsc_khz=2100000
[11041475us][cpu=0][sev=2][seq=1]:HV version 1.4-unstable-2019-11-18 09:13:55- DBG (daily tag:) build by mockbuild, start time 11028016us
[11054921us][cpu=0][sev=2][seq=2]:API version 1.0
[11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
[11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 250 : fatal error

 

So still failing.

 

Also as a comment, the BIOS settings descriptions, are badly out of step with what you see from the latest visual BIOS.

 

Cheers Steve.

 

On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Steve,

Please disable Hyper thread in BIOS for workaround.

This issue is fixed in  v1.5; will release soon.

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 8:32 PM
To: acrn-users@...
Subject: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

 

Hi,

Am essentially following the deployment instructions for the ACRN industry scenario
using a NUC7i7DNH with a serial port connected.

https://projectacrn.github.io/latest/getting-started/rt_industry.html

Flashing clear-31670-live-server.iso worked fine. Then followed the "Use the pre-installed industry ACRN hypervisor"
section and installed serial port support. Again this all worked fine and looked good.

I then rebooted the NUC. At HDMI console get "Intel NUC" banner with the following at top LHS of screen:

detected 8 processes, 8 enabled
current on process 0

And on serial port:

E0S0 S0

Not sure what has happened here. Am I missing something obvious ?

Thanks Steve


 

--

Engineering Director

IOTech Systems Ltd.



--
Engineering Director
IOTech Systems Ltd.


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Geoffroy Van Cutsem
 

Hi Fengwei,

-----Original Message-----
From: acrn-users@... <acrn-users@...> On
Behalf Of Yin, Fengwei
Sent: Thursday, January 9, 2020 10:42 AM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as
SOS

Hi Alfonso,

On 2020/1/9 下午5:11, Alfonso Sanchez-Beato wrote:
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 errors:

https://paste.ubuntu.com/p/R7THmm3hK6/
It's related with iasl in your SOS. We have constrain for iasl version.
Do you know which version Alfonso should use? I believe it is 20191018 but it would be appreciated if you could confirm.

@Alfonso, if true, you can install it as follows
$ sudo apt update
$ sudo apt install m4 bison flex zlib1g-dev
$ cd ~
$ wget https://acpica.org/sites/acpica/files/acpica-unix-20191018.tar.gz
$ tar zxvf acpica-unix-20191018.tar.gz
$ cd acpica-unix-20191018
$ make clean && make iasl
$ sudo cp ./generate/unix/bin/iasl /usr/sbin/

Thanks,
Geoffroy



Regards
Yin, Fengwei


Version info:

$ acrn-dm -v
DM version is: 1.4-unstable-bcefd673 (daily
tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17

ubuntu@nuc:~$ uname -a
Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18
09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

I have not been able yet to get output from the serial port, unfortunately.

Full dmesg output: https://paste.ubuntu.com/p/G8DtQTMrbS/

I see there an hvlog error which I do not know if it is relevant or not:

$ sudo dmesg | grep -i ACRN
[    0.000000] Command line:
BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98
pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3
rw rootwait ignore_loglevel no_timer_check consoleblank=0
i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1
i915.enable_guc=0 hvlog=2M@0x1FE00000
[    0.000000] Hypervisor detected: ACRN [    0.054541] Kernel command
line:
BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98
pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3
rw rootwait ignore_loglevel no_timer_check consoleblank=0
i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1
i915.enable_guc=0 hvlog=2M@0x1FE00000
[    1.058634] acrngt found
[    1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu [
1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19 [
1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu

Thanks
Alfonso

On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@...
<mailto:fuzhong.liu@...>> wrote:

Hi Alfonso____

Could you please share acrn.efi and acrn-dm commit info?____

__ __

With following steps:____

1. run “acrn-dm -v” in sos ____
2. run “version” in HV console____

We need them to reproduce this issue.____

Thanks!____

__ __

BR.____

Fuzhong____

__ __

*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Liu, Fuzhong
*Sent:* Thursday, January 9, 2020 5:36 AM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running
Ubuntu as SOS____

__ __

Hi Alfonso____

Please share your acrn.efi and acrn-dm, will reproduce this issue on
our side.____

Thanks!____

__ __

BR.____

Fuzhong____

__ __

*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Alfonso
Sanchez-Beato
*Sent:* Wednesday, January 8, 2020 7:39 PM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running
Ubuntu as SOS____

__ __

Hi Liu,____

__ __

On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...
<mailto:fuzhong.liu@...>> wrote:____

Hi Alfonso,____

You are using default launch_hard_rt_vm.sh, right?____

Maybe, it is SDC(by default) scenario for your acrn.efi, ____

Please refer following patch:____

____

*diff --git a/hypervisor/arch/x86/Kconfig
b/hypervisor/arch/x86/Kconfig*____

*index 41a78fe7..386a074b 100644*____

*--- a/hypervisor/arch/x86/Kconfig*____

*+++ b/hypervisor/arch/x86/Kconfig*____

@@ -1,6 +1,6 @@____

choice____

        prompt "ACRN Scenario"____

-       default SDC____

+default INDUSTRY____

        help____

          Select the scenario name to load corresponding VM
configuration.____

____

Then;____

____

cd ~/acrn-hypervisor____

make____

sudo make install____

____

And try again.____

__ __

I tried with that, but no difference in the traces :-/.____

Actually I had already tried with 'make all BOARD=nuc7i7dnb
SCENARIO=industry', which I guess i the same.____

____

____

Thanks!____

____

BR.____

Fuzhong____

__ __

Thanks____

Alfonso____

____

____

*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of
*alfonso.sanchez-beato@...
<mailto:alfonso.sanchez-beato@...>
*Sent:* Wednesday, January 8, 2020 5:44 PM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* [acrn-users] Cannot launch hart RT UOS when running
Ubuntu as SOS____

____

Hi,

I have set-up Ubuntu as service OS by following the instructions
in
https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html.
<https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html>ACRN
is recognized as hypervisor and all looks good in principle.
However, after that I followed the instructions on how to start
an RT UOS
<https://projectacrn.github.io/latest/getting-
started/rt_industry.html#install-and-launch-the-preempt-rt-vm>
and things fail:____

$ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh____

cpu1 online=1____

cpu2 online=1____

cpu3 online=1____

pm by vuart node-index = 1____

SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size
0x200000____

vm_create: hard_rtvm____

VHM api version 1.0____

failed to create VM hard_rtvm____


The kernel output is:____

[ 1530.397790] smpboot: CPU 1 is now offline____

[ 1530.398653] vhm: try to offline cpu 1 with lapicid 2____

[ 1530.409744] smpboot: CPU 2 is now offline____

[ 1530.410476] vhm: try to offline cpu 2 with lapicid 4____

[ 1530.429694] smpboot: CPU 3 is now offline____

[ 1530.430509] vhm: try to offline cpu 3 with lapicid 6____

[ 1530.575078] nvme nvme0: failed to set APST feature
(-19)____

[ 1530.579387] pci-stub 0000:02:00.0: claimed by stub____

[ 1530.661794] vhm_dev_open: opening device node____

[ 1530.663654] vhm: failed to create VM from Hypervisor !____

[ 1531.163905] vhm: failed to create VM from Hypervisor !____

[ 1531.664126] vhm: failed to create VM from Hypervisor !____

[ 1532.164360] vhm: failed to create VM from Hypervisor !____

[ 1532.664589] vhm: failed to create VM from Hypervisor !____

[ 1533.164775] vhm: failed to create VM from Hypervisor !____

[ 1533.664987] vhm: failed to create VM from Hypervisor !____

[ 1534.165215] vhm: failed to create VM from Hypervisor !____

[ 1534.665435] vhm: failed to create VM from Hypervisor !____

[ 1535.165656] vhm: failed to create VM from Hypervisor !____

[ 1535.682037] vhm: freed vm____

____

Any hint on what might be going wrong and instructions on how to
debug? I followed previously the tutorial for Clear Linux and
was able to launch the RT image. I am using a NUC7i7DNH device.

Thanks!
Alfonso____

__


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Geoffroy Van Cutsem
 

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 serial port.

 

Based on the output I see, it should work though with the default settings. Are you seeing any output at all on the serial port (e.g. Bios output)? Make sure to use these settings in minicom (or whatever else you use): 115200 8N1, both HW and SW flow control should turned off (this last one often gets me, the default may be that one is on).

 

As far as I know, the HVlog error shouldn’t affect the functionality, so there is something else going wrong in your set-up. Let me continue dig through the logs and see if I can spot some other useful info.

 

Geoffroy

 

 

From: acrn-users@... <acrn-users@...> On Behalf Of Alfonso Sanchez-Beato
Sent: Thursday, January 9, 2020 10:12 AM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

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 errors:

 

 

Version info:

 

$ acrn-dm -v
DM version is: 1.4-unstable-bcefd673 (daily tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17

 

ubuntu@nuc:~$ uname -a
Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18 09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

 

I have not been able yet to get output from the serial port, unfortunately.

 

 

I see there an hvlog error which I do not know if it is relevant or not:

 

$ sudo dmesg | grep -i ACRN
[    0.000000] Command line: BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98 pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000
[    0.000000] Hypervisor detected: ACRN
[    0.054541] Kernel command line: BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98 pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000
[    1.058634] acrngt found
[    1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu
[    1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19
[    1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu

 

Thanks

Alfonso

 

On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Alfonso

Could you please share acrn.efi and acrn-dm commit info?

 

With following steps:

  1. run “acrn-dm -v” in sos
  2. run “version” in HV console

We need them to reproduce this issue.

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Liu, Fuzhong
Sent: Thursday, January 9, 2020 5:36 AM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Alfonso

Please share your acrn.efi and acrn-dm, will reproduce this issue on our side.

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Alfonso Sanchez-Beato
Sent: Wednesday, January 8, 2020 7:39 PM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Liu,

 

On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Alfonso,

You are using default launch_hard_rt_vm.sh, right?

Maybe, it is SDC(by default) scenario for your acrn.efi,

Please refer following patch:

 

diff --git a/hypervisor/arch/x86/Kconfig b/hypervisor/arch/x86/Kconfig

index 41a78fe7..386a074b 100644

--- a/hypervisor/arch/x86/Kconfig

+++ b/hypervisor/arch/x86/Kconfig

@@ -1,6 +1,6 @@

choice

        prompt "ACRN Scenario"

-       default SDC

+       default INDUSTRY

        help

          Select the scenario name to load corresponding VM configuration.

 

Then;

 

cd ~/acrn-hypervisor

make

sudo make install

 

And try again.

 

I tried with that, but no difference in the traces :-/.

Actually I had already tried with 'make all BOARD=nuc7i7dnb SCENARIO=industry', which I guess i the same.

 

 

Thanks!

 

BR.

Fuzhong

 

Thanks

Alfonso

 

 

From: acrn-users@... <acrn-users@...> On Behalf Of alfonso.sanchez-beato@...
Sent: Wednesday, January 8, 2020 5:44 PM
To: acrn-users@...
Subject: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi,

I have set-up Ubuntu as service OS by following the instructions in https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html. ACRN is recognized as hypervisor and all looks good in principle. However, after that I followed the instructions on how to start an RT UOS and things fail:

$ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh

cpu1 online=1

cpu2 online=1

cpu3 online=1

pm by vuart node-index = 1

SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000

vm_create: hard_rtvm

VHM api version 1.0

failed to create VM hard_rtvm


The kernel output is:

[ 1530.397790] smpboot: CPU 1 is now offline

[ 1530.398653] vhm: try to offline cpu 1 with lapicid 2

[ 1530.409744] smpboot: CPU 2 is now offline

[ 1530.410476] vhm: try to offline cpu 2 with lapicid 4

[ 1530.429694] smpboot: CPU 3 is now offline

[ 1530.430509] vhm: try to offline cpu 3 with lapicid 6

[ 1530.575078] nvme nvme0: failed to set APST feature (-19)

[ 1530.579387] pci-stub 0000:02:00.0: claimed by stub

[ 1530.661794] vhm_dev_open: opening device node

[ 1530.663654] vhm: failed to create VM from Hypervisor !

[ 1531.163905] vhm: failed to create VM from Hypervisor !

[ 1531.664126] vhm: failed to create VM from Hypervisor !

[ 1532.164360] vhm: failed to create VM from Hypervisor !

[ 1532.664589] vhm: failed to create VM from Hypervisor !

[ 1533.164775] vhm: failed to create VM from Hypervisor !

[ 1533.664987] vhm: failed to create VM from Hypervisor !

[ 1534.165215] vhm: failed to create VM from Hypervisor !

[ 1534.665435] vhm: failed to create VM from Hypervisor !

[ 1535.165656] vhm: failed to create VM from Hypervisor !

[ 1535.682037] vhm: freed vm

 

Any hint on what might be going wrong and instructions on how to debug? I followed previously the tutorial for Clear Linux and was able to launch the RT image. I am using a NUC7i7DNH device.

Thanks!
Alfonso


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Yin, Fengwei <fengwei.yin@...>
 

Hi Alfonso,

On 2020/1/9 下午5:11, Alfonso Sanchez-Beato wrote:
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 errors:
https://paste.ubuntu.com/p/R7THmm3hK6/
It's related with iasl in your SOS. We have constrain for iasl version.


Regards
Yin, Fengwei

Version info:
$ acrn-dm -v
DM version is: 1.4-unstable-bcefd673 (daily tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17
ubuntu@nuc:~$ uname -a
Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18 09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
I have not been able yet to get output from the serial port, unfortunately.
Full dmesg output: https://paste.ubuntu.com/p/G8DtQTMrbS/
I see there an hvlog error which I do not know if it is relevant or not:
$ sudo dmesg | grep -i ACRN
[    0.000000] Command line: BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98 pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000
[    0.000000] Hypervisor detected: ACRN
[    0.054541] Kernel command line: BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98 pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000
[    1.058634] acrngt found
[    1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu
[    1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19
[    1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu
Thanks
Alfonso
On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@... <mailto:fuzhong.liu@...>> wrote:
Hi Alfonso____
Could you please share acrn.efi and acrn-dm commit info?____
__ __
With following steps:____
1. run “acrn-dm -v” in sos ____
2. run “version” in HV console____
We need them to reproduce this issue.____
Thanks!____
__ __
BR.____
Fuzhong____
__ __
*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Liu, Fuzhong
*Sent:* Thursday, January 9, 2020 5:36 AM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running
Ubuntu as SOS____
__ __
Hi Alfonso____
Please share your acrn.efi and acrn-dm, will reproduce this issue on
our side.____
Thanks!____
__ __
BR.____
Fuzhong____
__ __
*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Alfonso
Sanchez-Beato
*Sent:* Wednesday, January 8, 2020 7:39 PM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* Re: [acrn-users] Cannot launch hart RT UOS when running
Ubuntu as SOS____
__ __
Hi Liu,____
__ __
On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...
<mailto:fuzhong.liu@...>> wrote:____
Hi Alfonso,____
You are using default launch_hard_rt_vm.sh, right?____
Maybe, it is SDC(by default) scenario for your acrn.efi, ____
Please refer following patch:____
____
*diff --git a/hypervisor/arch/x86/Kconfig
b/hypervisor/arch/x86/Kconfig*____
*index 41a78fe7..386a074b 100644*____
*--- a/hypervisor/arch/x86/Kconfig*____
*+++ b/hypervisor/arch/x86/Kconfig*____
@@ -1,6 +1,6 @@____
choice____
        prompt "ACRN Scenario"____
-       default SDC____
+default INDUSTRY____
        help____
          Select the scenario name to load corresponding VM
configuration.____
____
Then;____
____
cd ~/acrn-hypervisor____
make____
sudo make install____
____
And try again.____
__ __
I tried with that, but no difference in the traces :-/.____
Actually I had already tried with 'make all BOARD=nuc7i7dnb
SCENARIO=industry', which I guess i the same.____
____
____
Thanks!____
____
BR.____
Fuzhong____
__ __
Thanks____
Alfonso____
____
____
*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of
*alfonso.sanchez-beato@...
<mailto:alfonso.sanchez-beato@...>
*Sent:* Wednesday, January 8, 2020 5:44 PM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* [acrn-users] Cannot launch hart RT UOS when running
Ubuntu as SOS____
____
Hi,
I have set-up Ubuntu as service OS by following the instructions
in
https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html.
<https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html>ACRN
is recognized as hypervisor and all looks good in principle.
However, after that I followed the instructions on how to start
an RT UOS
<https://projectacrn.github.io/latest/getting-started/rt_industry.html#install-and-launch-the-preempt-rt-vm>
and things fail:____
$ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh____
cpu1 online=1____
cpu2 online=1____
cpu3 online=1____
pm by vuart node-index = 1____
SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size
0x200000____
vm_create: hard_rtvm____
VHM api version 1.0____
failed to create VM hard_rtvm____
The kernel output is:____
[ 1530.397790] smpboot: CPU 1 is now offline____
[ 1530.398653] vhm: try to offline cpu 1 with lapicid 2____
[ 1530.409744] smpboot: CPU 2 is now offline____
[ 1530.410476] vhm: try to offline cpu 2 with lapicid 4____
[ 1530.429694] smpboot: CPU 3 is now offline____
[ 1530.430509] vhm: try to offline cpu 3 with lapicid 6____
[ 1530.575078] nvme nvme0: failed to set APST feature (-19)____
[ 1530.579387] pci-stub 0000:02:00.0: claimed by stub____
[ 1530.661794] vhm_dev_open: opening device node____
[ 1530.663654] vhm: failed to create VM from Hypervisor !____
[ 1531.163905] vhm: failed to create VM from Hypervisor !____
[ 1531.664126] vhm: failed to create VM from Hypervisor !____
[ 1532.164360] vhm: failed to create VM from Hypervisor !____
[ 1532.664589] vhm: failed to create VM from Hypervisor !____
[ 1533.164775] vhm: failed to create VM from Hypervisor !____
[ 1533.664987] vhm: failed to create VM from Hypervisor !____
[ 1534.165215] vhm: failed to create VM from Hypervisor !____
[ 1534.665435] vhm: failed to create VM from Hypervisor !____
[ 1535.165656] vhm: failed to create VM from Hypervisor !____
[ 1535.682037] vhm: freed vm____
____
Any hint on what might be going wrong and instructions on how to
debug? I followed previously the tutorial for Clear Linux and
was able to launch the RT image. I am using a NUC7i7DNH device.
Thanks!
Alfonso____
__


Re: Cannot launch hart RT UOS when running Ubuntu as SOS

Alfonso Sanchez-Beato
 

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 errors:


Version info:

$ acrn-dm -v
DM version is: 1.4-unstable-bcefd673 (daily tag:acrn-2019w47.1-140000p), build by ubuntu@2020-01-09 09:45:17

ubuntu@nuc:~$ uname -a
Linux nuc 4.19.78-98.iot-lts2018-sos #1 SMP PREEMPT Mon Nov 18 09:22:10 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

I have not been able yet to get output from the serial port, unfortunately.


I see there an hvlog error which I do not know if it is relevant or not:

$ sudo dmesg | grep -i ACRN
[    0.000000] Command line: BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98 pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000
[    0.000000] Hypervisor detected: ACRN
[    0.054541] Kernel command line: BOOT_IMAGE=/boot/acrn/org.clearlinux.iot-lts2018-sos.4.19.78-98 pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.nuclear_pageflip=1 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000
[    1.058634] acrngt found
[    1.143414] ACRNTrace: Initialized acrn trace module with 4 cpu
[    1.144809] ACRN HVLog: Failed to init last hvlog devs, errno -19
[    1.144976] ACRN HVLog: Initialized hvlog module with 4 cpu

Thanks
Alfonso


On Thu, Jan 9, 2020 at 3:37 AM Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Alfonso

Could you please share acrn.efi and acrn-dm commit info?

 

With following steps:

  1. run “acrn-dm -v” in sos
  2. run “version” in HV console

We need them to reproduce this issue.

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Liu, Fuzhong
Sent: Thursday, January 9, 2020 5:36 AM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Alfonso

Please share your acrn.efi and acrn-dm, will reproduce this issue on our side.

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Alfonso Sanchez-Beato
Sent: Wednesday, January 8, 2020 7:39 PM
To: acrn-users@...
Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi Liu,

 

On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...> wrote:

Hi Alfonso,

You are using default launch_hard_rt_vm.sh, right?

Maybe, it is SDC(by default) scenario for your acrn.efi,

Please refer following patch:

 

diff --git a/hypervisor/arch/x86/Kconfig b/hypervisor/arch/x86/Kconfig

index 41a78fe7..386a074b 100644

--- a/hypervisor/arch/x86/Kconfig

+++ b/hypervisor/arch/x86/Kconfig

@@ -1,6 +1,6 @@

choice

        prompt "ACRN Scenario"

-       default SDC

+       default INDUSTRY

        help

          Select the scenario name to load corresponding VM configuration.

 

Then;

 

cd ~/acrn-hypervisor

make

sudo make install

 

And try again.

 

I tried with that, but no difference in the traces :-/.

Actually I had already tried with 'make all BOARD=nuc7i7dnb SCENARIO=industry', which I guess i the same.

 

 

Thanks!

 

BR.

Fuzhong

 

Thanks

Alfonso

 

 

From: acrn-users@... <acrn-users@...> On Behalf Of alfonso.sanchez-beato@...
Sent: Wednesday, January 8, 2020 5:44 PM
To: acrn-users@...
Subject: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS

 

Hi,

I have set-up Ubuntu as service OS by following the instructions in https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html. ACRN is recognized as hypervisor and all looks good in principle. However, after that I followed the instructions on how to start an RT UOS and things fail:

$ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh

cpu1 online=1

cpu2 online=1

cpu3 online=1

pm by vuart node-index = 1

SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000

vm_create: hard_rtvm

VHM api version 1.0

failed to create VM hard_rtvm


The kernel output is:

[ 1530.397790] smpboot: CPU 1 is now offline

[ 1530.398653] vhm: try to offline cpu 1 with lapicid 2

[ 1530.409744] smpboot: CPU 2 is now offline

[ 1530.410476] vhm: try to offline cpu 2 with lapicid 4

[ 1530.429694] smpboot: CPU 3 is now offline

[ 1530.430509] vhm: try to offline cpu 3 with lapicid 6

[ 1530.575078] nvme nvme0: failed to set APST feature (-19)

[ 1530.579387] pci-stub 0000:02:00.0: claimed by stub

[ 1530.661794] vhm_dev_open: opening device node

[ 1530.663654] vhm: failed to create VM from Hypervisor !

[ 1531.163905] vhm: failed to create VM from Hypervisor !

[ 1531.664126] vhm: failed to create VM from Hypervisor !

[ 1532.164360] vhm: failed to create VM from Hypervisor !

[ 1532.664589] vhm: failed to create VM from Hypervisor !

[ 1533.164775] vhm: failed to create VM from Hypervisor !

[ 1533.664987] vhm: failed to create VM from Hypervisor !

[ 1534.165215] vhm: failed to create VM from Hypervisor !

[ 1534.665435] vhm: failed to create VM from Hypervisor !

[ 1535.165656] vhm: failed to create VM from Hypervisor !

[ 1535.682037] vhm: freed vm

 

Any hint on what might be going wrong and instructions on how to debug? I followed previously the tutorial for Clear Linux and was able to launch the RT image. I am using a NUC7i7DNH device.

Thanks!
Alfonso

741 - 760 of 1237