Date   

Re: Zephyr as UOS slows down when SOS is busy

Geoffroy Van Cutsem
 

Hi Alfonso,

 

My best guess as to what’s happening is that there is some contention between the Service VM and the Zephyr VM to use the cache, Zephyr would typically stay in cache but now that there is some heavy load in the Service VM, it may get evicted at times. This is where Cache Allocation Technology (CAT) can help further isolate the VMs, especially against so-called “noisy neighbours. Unfortunately, Kaby Lake does not support CAT. Here is more about CAT and how to use it with ACRN: https://projectacrn.github.io/latest/getting-started/rt_industry.html?#configure-cat

 

Geoffroy

 

From: acrn-users@... <acrn-users@...> On Behalf Of Alfonso Sanchez-Beato
Sent: Tuesday, January 21, 2020 1:09 PM
To: acrn-users@...
Subject: Re: [acrn-users] Zephyr as UOS slows down when SOS is busy

 

 

 

On Tue, Jan 21, 2020 at 1:07 PM Alfonso Sanchez-Beato <alfonso.sanchez-beato@...> wrote:

Hello,

 

I have been playing with using Zephyr as UOS on top of Ubuntu as SOS, using the Industry scenario and launching the UOS with launch_zephyr.sh.

 

I created this small program to prove that Zephyr was not affected by what happened in the SOS: https://paste.ubuntu.com/p/c3j9XwvrT6/ (with config https://paste.ubuntu.com/p/sPhwTRrRTZ/). The program simply calculates the number of primes below a number and prints the time spent.

 

Although the problem runs and I get output from the serial port, I found two problems:

 

1. gettimeofday is not returning good times, the elapsed time is ~20 times more than the real one. I see the same problem when using k_uptime_get and k_uptime_delta. It looks related to handling of the HW clock, but the pre-defined frequency (100) seems correct.

 

2. More importantly, I see that the time spent in the calculation varies when I do something CPU intensive on the SOS. For instance, if I run the same calculation on the SOS, I see that Zephyr is expending 5% more time in the calculation, which should not happen and defeats the purpose of this set-up.

 

ACRN version is:

HV version 1.4-unstable-2020-01-09 09:45:06-bcefd673 DBG (daily tag: acrn-2019w47.1-140000p) build by ubuntu
API version 1.0

 

Any ideas on what might be going on?

 

I forgot to mention that I am testing on a NUC7i7DNH.

 

 

Thanks

Alfonso

 


Re: Zephyr as UOS slows down when SOS is busy

Alfonso Sanchez-Beato
 



On Tue, Jan 21, 2020 at 1:07 PM Alfonso Sanchez-Beato <alfonso.sanchez-beato@...> wrote:
Hello,

I have been playing with using Zephyr as UOS on top of Ubuntu as SOS, using the Industry scenario and launching the UOS with launch_zephyr.sh.

I created this small program to prove that Zephyr was not affected by what happened in the SOS: https://paste.ubuntu.com/p/c3j9XwvrT6/ (with config https://paste.ubuntu.com/p/sPhwTRrRTZ/). The program simply calculates the number of primes below a number and prints the time spent.

Although the problem runs and I get output from the serial port, I found two problems:

1. gettimeofday is not returning good times, the elapsed time is ~20 times more than the real one. I see the same problem when using k_uptime_get and k_uptime_delta. It looks related to handling of the HW clock, but the pre-defined frequency (100) seems correct.

2. More importantly, I see that the time spent in the calculation varies when I do something CPU intensive on the SOS. For instance, if I run the same calculation on the SOS, I see that Zephyr is expending 5% more time in the calculation, which should not happen and defeats the purpose of this set-up.

ACRN version is:
HV version 1.4-unstable-2020-01-09 09:45:06-bcefd673 DBG (daily tag: acrn-2019w47.1-140000p) build by ubuntu
API version 1.0

Any ideas on what might be going on?

I forgot to mention that I am testing on a NUC7i7DNH.
 

Thanks
Alfonso


Zephyr as UOS slows down when SOS is busy

Alfonso Sanchez-Beato
 

Hello,

I have been playing with using Zephyr as UOS on top of Ubuntu as SOS, using the Industry scenario and launching the UOS with launch_zephyr.sh.

I created this small program to prove that Zephyr was not affected by what happened in the SOS: https://paste.ubuntu.com/p/c3j9XwvrT6/ (with config https://paste.ubuntu.com/p/sPhwTRrRTZ/). The program simply calculates the number of primes below a number and prints the time spent.

Although the problem runs and I get output from the serial port, I found two problems:

1. gettimeofday is not returning good times, the elapsed time is ~20 times more than the real one. I see the same problem when using k_uptime_get and k_uptime_delta. It looks related to handling of the HW clock, but the pre-defined frequency (100) seems correct.

2. More importantly, I see that the time spent in the calculation varies when I do something CPU intensive on the SOS. For instance, if I run the same calculation on the SOS, I see that Zephyr is expending 5% more time in the calculation, which should not happen and defeats the purpose of this set-up.

ACRN version is:
HV version 1.4-unstable-2020-01-09 09:45:06-bcefd673 DBG (daily tag: acrn-2019w47.1-140000p) build by ubuntu
API version 1.0

Any ideas on what might be going on?

Thanks
Alfonso


Canceled: 2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)

Wang, Hongbo
 

Cancel meeting this week. Happy Chinese New Year Holiday~
 
<Detailed calendar will be published 1 week before meeting>
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "Technical Community" meeting where we'll meet community members and talk about the ACRN project and plans. As we explore community interest and involvement opportunities, we'll (re)schedule these meetings at a time convenient to most attendees:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.us/j/457171121
  • Zoom Meeting ID: 457-171-121
  • Online conference phone:
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • Additional international phone numbers
  • Meeting Notes:
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 
 
 
 
 
 


Canceled: 2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)

Wang, Hongbo
 

Cancel meeting this week. Happy Chinese New Year Holiday~
 
<Detailed calendar will be published 1 week before meeting>
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "Technical Community" meeting where we'll meet community members and talk about the ACRN project and plans. As we explore community interest and involvement opportunities, we'll (re)schedule these meetings at a time convenient to most attendees:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.us/j/457171121
  • Zoom Meeting ID: 457-171-121
  • Online conference phone:
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • Additional international phone numbers
  • Meeting Notes:
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 
 
 
 
 
 


Re: Problem with Industry Scenario on a NUC7i7DNH

Geoffroy Van Cutsem
 

-----Original Message-----
From: acrn-users@... <acrn-users@...> On
Behalf Of Yin, Fengwei
Sent: Monday, January 13, 2020 3:28 AM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

On 1/13/2020 9:44 AM, Yin, Fengwei wrote:
On 1/10/2020 8:38 PM, Geoffroy Van Cutsem wrote:
I found this article that suggests Ubuntu 19.10 specifically enabled
this flag for the first time by default:
https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-19.10-
GCC-Hardening.


I guess this is not the case in Clear Linux at this point, although I
have not dug yet into where these things are set to really understand
if that’s the cause of this problem.
The kernel also hit same issue and it disabled the -fcf-protection if
the -mindirect-branch is enabled (for retpoline):
https://lkml.org/lkml/2019/7/9/641

I will submit a patch accordingly.
Fixing patch was sent to acrn-dev mail list:
https://lists.projectacrn.org/g/acrn-
dev/topic/patch_makefile_disable/69659519?p=,,,20,0,0,0::recentpostdate%
2Fsticky,,,20,2,0,69659519
Thanks!
Geoffroy


Regards
Yin, Fengwei


Regards
Yin, Fengwei


Cheers,

Geoffroy

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

Thanks Geoffroy. Odd that the same version of the compiler works with
Clear Linux ?

Cheers Steve.

On Fri, 10 Jan 2020 at 12:23, Geoffroy Van Cutsem
<geoffroy.vancutsem@... <mailto:geoffroy.vancutsem@...>>
wrote:

    Thanks Steve, I can confirm that I see the problem too using
Ubuntu
    19.10 (gcc 9.2.1). Ubuntu 19.04 compiles ACRN correctly (uses gcc
    8.3.0). I have filed an issue to track this:
    https://github.com/projectacrn/acrn-hypervisor/issues/4358.

    Geoffroy

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

    Hi Geoffroy,

    Build from a clean checkout on 19.10 (not 19.04) with:

    make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0

    Default gcc is 9.2.1

    Cheers Steve.

    On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem
    <geoffroy.vancutsem@...
<mailto:geoffroy.vancutsem@...>>
    wrote:

        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@...
        <mailto:acrn-users@...>
        <acrn-users@...
        <mailto:acrn-users@...>> *On Behalf Of
*Steve
        Osselton
        *Sent:* Friday, January 10, 2020 11:03 AM
        *To:* acrn-users@...
        <mailto: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@... <mailto: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-sourc
e.html


            BR.

            Fuzhong

            *From:* acrn-users@...
            <mailto:acrn-users@...>
            <acrn-users@...
            <mailto:acrn-users@...>> *On Behalf Of
            *Steve Osselton
            *Sent:* Friday, January 10, 2020 5:33 PM
            *To:* acrn-users@...
            <mailto: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_che
cks.o

            -MMD -MT

/home/steve/git/acrn-hypervisor/build/hypervisor/pre_build/static_che
cks.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@... <mailto: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@...>
                 > <mailto: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@...>>
                 >      > <mailto: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@...>>>
                 >      >      > <mailto: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@...>>>
                 >      >      >
 <mailto: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@...>>>
                 >      >      >
 <mailto: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@...>>>
                 >      >      >
 <mailto: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@...>>>
                 >      >      >     <mailto: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@...>>>
                 >      >      >
 <mailto: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@...>>>
                 >      >      >
 <mailto: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@...>>>
                 >      >      >
 <mailto: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.


    --
    Engineering Director

    IOTech Systems Ltd.


--

Engineering Director

IOTech Systems Ltd.





Re: Problem with Industry Scenario on a NUC7i7DNH

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

On 1/13/2020 9:44 AM, Yin, Fengwei wrote:
On 1/10/2020 8:38 PM, Geoffroy Van Cutsem wrote:
I found this article that suggests Ubuntu 19.10 specifically enabled this flag for the first time by default: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-19.10-GCC-Hardening.

I guess this is not the case in Clear Linux at this point, although I have not dug yet into where these things are set to really understand if that’s the cause of this problem.
The kernel also hit same issue and it disabled the -fcf-protection if
the -mindirect-branch is enabled (for retpoline):
https://lkml.org/lkml/2019/7/9/641
I will submit a patch accordingly.
Fixing patch was sent to acrn-dev mail list:
https://lists.projectacrn.org/g/acrn-dev/topic/patch_makefile_disable/69659519?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,69659519

Regards
Yin, Fengwei

Regards
Yin, Fengwei


Cheers,

Geoffroy

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

Thanks Geoffroy. Odd that the same version of the compiler works with Clear Linux ?

Cheers Steve.

On Fri, 10 Jan 2020 at 12:23, Geoffroy Van Cutsem <geoffroy.vancutsem@... <mailto:geoffroy.vancutsem@...>> wrote:

    Thanks Steve, I can confirm that I see the problem too using Ubuntu
    19.10 (gcc 9.2.1). Ubuntu 19.04 compiles ACRN correctly (uses gcc
    8.3.0). I have filed an issue to track this:
    https://github.com/projectacrn/acrn-hypervisor/issues/4358.

    Geoffroy

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

    Hi Geoffroy,

    Build from a clean checkout on 19.10 (not 19.04) with:

    make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0

    Default gcc is 9.2.1

    Cheers Steve.

    On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem
    <geoffroy.vancutsem@... <mailto:geoffroy.vancutsem@...>>
    wrote:

        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@...
        <mailto:acrn-users@...>
        <acrn-users@...
        <mailto:acrn-users@...>> *On Behalf Of *Steve
        Osselton
        *Sent:* Friday, January 10, 2020 11:03 AM
        *To:* acrn-users@...
        <mailto: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@... <mailto: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@...
            <mailto:acrn-users@...>
            <acrn-users@...
            <mailto:acrn-users@...>> *On Behalf Of
            *Steve Osselton
            *Sent:* Friday, January 10, 2020 5:33 PM
            *To:* acrn-users@...
            <mailto: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@... <mailto: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@...>
                 > <mailto: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@...>>
                 >      > <mailto: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@...>>>
                 >      >      > <mailto: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@...>>>
                 >      >      >  <mailto: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@...>>>
                 >      >      >  <mailto: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@...>>>
                 >      >      >  <mailto: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@...>>>
                 >      >      >     <mailto: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@...>>>
                 >      >      >  <mailto: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@...>>>
                 >      >      >  <mailto: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@...>>>
                 >      >      >  <mailto: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.


    --
    Engineering Director

    IOTech Systems Ltd.


--

Engineering Director

IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

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

On 1/10/2020 8:38 PM, Geoffroy Van Cutsem wrote:
I found this article that suggests Ubuntu 19.10 specifically enabled this flag for the first time by default: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-19.10-GCC-Hardening.
I guess this is not the case in Clear Linux at this point, although I have not dug yet into where these things are set to really understand if that’s the cause of this problem.
The kernel also hit same issue and it disabled the -fcf-protection if
the -mindirect-branch is enabled (for retpoline):
https://lkml.org/lkml/2019/7/9/641

I will submit a patch accordingly.

Regards
Yin, Fengwei

Cheers,
Geoffroy
*From:* acrn-users@... <acrn-users@...> *On Behalf Of *Steve Osselton
*Sent:* Friday, January 10, 2020 1:27 PM
*To:* acrn-users@...
*Subject:* Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH
Thanks Geoffroy. Odd that the same version of the compiler works with Clear Linux ?
Cheers Steve.
On Fri, 10 Jan 2020 at 12:23, Geoffroy Van Cutsem <geoffroy.vancutsem@... <mailto:geoffroy.vancutsem@...>> wrote:
Thanks Steve, I can confirm that I see the problem too using Ubuntu
19.10 (gcc 9.2.1). Ubuntu 19.04 compiles ACRN correctly (uses gcc
8.3.0). I have filed an issue to track this:
https://github.com/projectacrn/acrn-hypervisor/issues/4358.
Geoffroy
*From:* acrn-users@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Steve Osselton
*Sent:* Friday, January 10, 2020 11:33 AM
*To:* acrn-users@...
<mailto:acrn-users@...>
*Subject:* Re: [acrn-users] Problem with Industry Scenario on a
NUC7i7DNH
Hi Geoffroy,
Build from a clean checkout on 19.10 (not 19.04) with:
make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0
Default gcc is 9.2.1
Cheers Steve.
On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem
<geoffroy.vancutsem@... <mailto:geoffroy.vancutsem@...>>
wrote:
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@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of *Steve
Osselton
*Sent:* Friday, January 10, 2020 11:03 AM
*To:* acrn-users@...
<mailto: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@... <mailto: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@...
<mailto:acrn-users@...>
<acrn-users@...
<mailto:acrn-users@...>> *On Behalf Of
*Steve Osselton
*Sent:* Friday, January 10, 2020 5:33 PM
*To:* acrn-users@...
<mailto: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@... <mailto: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@...>
> <mailto: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@...>>
>      > <mailto: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@...>>>
>      >      > <mailto: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@...>>>
>      >      >
 <mailto: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@...>>>
>      >      >
 <mailto: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@...>>>
>      >      >
 <mailto: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@...>>>
>      >      >     <mailto: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@...>>>
>      >      >
 <mailto: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@...>>>
>      >      >
 <mailto: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@...>>>
>      >      >
 <mailto: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.
--
Engineering Director
IOTech Systems Ltd.
--
Engineering Director
IOTech Systems Ltd.


2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)

Wang, Hongbo
 

Topic (1/15): Expose and pass through platform hidden PCIs devices to SOS
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "Technical Community" meeting where we'll meet community members and talk about the ACRN project and plans. As we explore community interest and involvement opportunities, we'll (re)schedule these meetings at a time convenient to most attendees:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.us/j/457171121
  • Zoom Meeting ID: 457-171-121
  • Online conference phone:
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • Additional international phone numbers
  • Meeting Notes:
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 
 
 
 
 
 


2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)

Wang, Hongbo
 

Topic (1/5): Expose and pass through platform hidden PCIs devices to SOS
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "Technical Community" meeting where we'll meet community members and talk about the ACRN project and plans. As we explore community interest and involvement opportunities, we'll (re)schedule these meetings at a time convenient to most attendees:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.us/j/457171121
  • Zoom Meeting ID: 457-171-121
  • Online conference phone:
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • Additional international phone numbers
  • Meeting Notes:
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 
 
 
 
 
 


[Announce] ACRN Open Source Ver1.5 Release Notes

Wang, Hongbo
 

Hi all,

 

We are very pleased to announce Version 1.5 release of ACRN. You can see the release blog from https://projectacrn.org/blog/ and detailed Release Notes in website https://projectacrn.github.io/latest/release_notes/release_notes_1.5.html .

Version 1.5 features:

  • Basic CPU sharing: Fairness Round-Robin CPU Scheduling has been added to support basic CPU sharing (the Service VM and WaaG share one CPU core).
  • 8th Gen Intel® Core ™ Processors (code name Whiskey Lake) are now supported and validated.
  • Overall stability and performance have been improved.
  • An offline configuration tool has been created to help developers port ACRN to different hardware boards.

Besides new features, in this release, there’re several reference documents available, including “Run Kata Container on Service VM”, “Supported Hardware”, “CPU Sharing”, “Using Windows as Guest VM”, etc.

 

To learn more about ACRN: ACRN is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open source platform. Check out the ACRN project portal (https://projectacrn.org/) for more information.

 

 

 

 

Best regards.

Hongbo

Tel: +86-21-6116 7445

MP: +86-1364 1793 689

Mail: hongbo.wang@...

 


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

Hi Liu,

Just to confirm that the suggested fix works. Can now boot the sos from ACRN.
Thanks for all the help.

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
 

I found this article that suggests Ubuntu 19.10 specifically enabled this flag for the first time by default: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-19.10-GCC-Hardening.

 

I guess this is not the case in Clear Linux at this point, although I have not dug yet into where these things are set to really understand if that’s the cause of this problem.

 

Cheers,

Geoffroy

 

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

 

Thanks Geoffroy. Odd that the same version of the compiler works with Clear Linux ?

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 12:23, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

Thanks Steve, I can confirm that I see the problem too using Ubuntu 19.10 (gcc 9.2.1). Ubuntu 19.04 compiles ACRN correctly (uses gcc 8.3.0). I have filed an issue to track this: https://github.com/projectacrn/acrn-hypervisor/issues/4358.

 

Geoffroy

 

 

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

 

Hi Geoffroy,

 

Build from a clean checkout on 19.10 (not 19.04) with:

 

make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0

 

Default gcc is 9.2.1

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

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.


 

--

Engineering Director

IOTech Systems Ltd.


 

--

Engineering Director

IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

Thanks Geoffroy. Odd that the same version of the compiler works with Clear Linux ?

Cheers Steve.

On Fri, 10 Jan 2020 at 12:23, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

Thanks Steve, I can confirm that I see the problem too using Ubuntu 19.10 (gcc 9.2.1). Ubuntu 19.04 compiles ACRN correctly (uses gcc 8.3.0). I have filed an issue to track this: https://github.com/projectacrn/acrn-hypervisor/issues/4358.

 

Geoffroy

 

 

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

 

Hi Geoffroy,

 

Build from a clean checkout on 19.10 (not 19.04) with:

 

make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0

 

Default gcc is 9.2.1

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

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.


 

--

Engineering Director

IOTech Systems Ltd.



--
Engineering Director
IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Geoffroy Van Cutsem
 

Thanks Steve, I can confirm that I see the problem too using Ubuntu 19.10 (gcc 9.2.1). Ubuntu 19.04 compiles ACRN correctly (uses gcc 8.3.0). I have filed an issue to track this: https://github.com/projectacrn/acrn-hypervisor/issues/4358.

 

Geoffroy

 

 

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

 

Hi Geoffroy,

 

Build from a clean checkout on 19.10 (not 19.04) with:

 

make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0

 

Default gcc is 9.2.1

 

Cheers Steve.

 

On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

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.


 

--

Engineering Director

IOTech Systems Ltd.


Re: Problem with Industry Scenario on a NUC7i7DNH

Steve Osselton
 

Hi Geoffroy,

Build from a clean checkout on 19.10 (not 19.04) with:

make all BOARD=nuc7i7dnb  SCENARIO=industry RELEASE=0

Default gcc is 9.2.1

Cheers Steve.

On Fri, 10 Jan 2020 at 10:24, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote:

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.



--
Engineering Director
IOTech Systems Ltd.


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.

721 - 740 of 1233