Date   

Re: acrn.efi not booting correctly

Geoffroy Van Cutsem
 

Thanks

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Kaige Fu
Sent: Wednesday, October 17, 2018 3:11 AM
To: acrn-users@...
Subject: Re: [acrn-users] acrn.efi not booting correctly

Hi Geoffroy,

Seems it is a bug, we'll follow up and let you know the result.

--
Thanks
Kaige Fu


-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Geoffroy Van
Cutsem
Sent: Wednesday, October 17, 2018 8:02 AM
To: acrn-users@...
Subject: [acrn-users] acrn.efi not booting correctly

Hi folks,

I have tried to compile the ACRN hypervisor for uefi on three
different development systems, namely Ubuntu 16.04 (with gcc 7.3.0),
Fedora 27 and Clear Linux 25620. None of them generate an 'acrn.efi'
file that can boot correctly. I focused on Clear Linux as the build machine
and ran 'git bisect'
which indicated this commit as the culprit:
https://github.com/projectacrn/acrn-hypervisor/commit/1d725c89c03025e
0823a6a76276e3155ce854879

The symptom if I use that commit (or any newer one) is that I never
see the Service OS bootloader. I'm testing this on a NUC7i7DNHE.

Is this a known issue?

Thanks,
Geoffroy



Re: acrn.efi not booting correctly

Kaige Fu
 

Hi Geoffroy,

Seems it is a bug, we'll follow up and let you know the result.

--
Thanks
Kaige Fu

-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Wednesday, October 17, 2018 8:02 AM
To: acrn-users@...
Subject: [acrn-users] acrn.efi not booting correctly

Hi folks,

I have tried to compile the ACRN hypervisor for uefi on three different
development systems, namely Ubuntu 16.04 (with gcc 7.3.0), Fedora 27 and
Clear Linux 25620. None of them generate an 'acrn.efi' file that can boot
correctly. I focused on Clear Linux as the build machine and ran 'git bisect'
which indicated this commit as the culprit:
https://github.com/projectacrn/acrn-hypervisor/commit/1d725c89c03025e
0823a6a76276e3155ce854879

The symptom if I use that commit (or any newer one) is that I never see the
Service OS bootloader. I'm testing this on a NUC7i7DNHE.

Is this a known issue?

Thanks,
Geoffroy


acrn.efi not booting correctly

Geoffroy Van Cutsem
 

Hi folks,

I have tried to compile the ACRN hypervisor for uefi on three different development systems, namely Ubuntu 16.04 (with gcc 7.3.0), Fedora 27 and Clear Linux 25620. None of them generate an 'acrn.efi' file that can boot correctly. I focused on Clear Linux as the build machine and ran 'git bisect' which indicated this commit as the culprit: https://github.com/projectacrn/acrn-hypervisor/commit/1d725c89c03025e0823a6a76276e3155ce854879

The symptom if I use that commit (or any newer one) is that I never see the Service OS bootloader. I'm testing this on a NUC7i7DNHE.

Is this a known issue?

Thanks,
Geoffroy


Re: Clear Linux iot kernel LTS2018

Geoffroy Van Cutsem
 

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 11:43 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

On Thu, Oct 11, 2018 at 08:10:29AM +0000, Geoffroy Van Cutsem wrote:
I see some mix-up in this thread between bundles and packages. The
service-os bundle [1] includes a number of packages, such as the acrn-
hypervisor (hypervisor, devicemodel, tools), the kernels we use for the
Service OS and other useful things.

The change that's coming is that at the moment the kernels (SOS and UOS)
are coming from the linux-pk414 package (which included in the service-os
bundle) and the 'linux-pk' bundle respectively. Soon the service-os bundle
will be updated to include the linux-iot-lts2018-sos package that provides the
kernel for the Service OS. The 'kernel-iot-lts2018' should be used instead of
the 'linux-pk' one to install the Guest OS kernel. And we'll also need to adjust
all kernel names/versions throughout the Getting Started Guide document.

By the way, I think there was a small mistake that sneaked in below:
iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.
Should read:
linux-iot-lts2018-sos is shipped with service-os bundle.
linux-iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.
Thanks for the clarification ;-)

Currently service-os bundle contains linux-pk414-sos and linux-iot-lts2018.
I guess you meant linux-iot-lts2018-sos here: https://github.com/clearlinux/clr-bundles/blob/master/bundles/service-os#L12 ;)



[1]
https://github.com/clearlinux/clr-bundles/blob/master/bundles/service-
os

Geoffroy

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of
bounce+13723+88+767563+1700423@...
Sent: Thursday, October 11, 2018 9:41 AM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

This is obvious! No.

pk414-sos/iot-lts20180-sos, which contains Clear Linux SOS kernel, acrn-
hypervisor, acrn-dm and related Guest OS launch scripts. It is targeting
for
Clear Linux as the SOS on ACRN hypervisor. This bundle needs to
install with "swupd " manually if people want to enable ACRN.
pk414-standard/iot-lts2018, which is targeting for Native Clear
Linux or Linux as the Guest. It Is installed with bare metal system
installation.

From the procedure to install ACRN point of view, Miguel said there
is no changes. Just need to be updating kernel name with
iot-lts2018-sos replacing pk414-sos.
And standard kernel with iot-lts2018 replacing pk414-standard.

I think this change is for upgrading current 4.14 kernel to 4.19
named kernel
LTS2018 purpose only.

Again, that would be nice if acrn.efi can be deployed into EFI
partition and acrn boot entry be added into EFI firmware boot menu
by default after install "service-os" bundle with this upgrade opportunity.


Thanks
Ailin
-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Tzeng, Tonny
Sent: Thursday, October 11, 2018 2:46 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

The service-os bundle will also install acrn-hypervisor package, but
it seems the kernel-iot-lts2018 bundle only does part of what the
service-os bundle is doing currently. Will the kernel-iot-lts2018
bundle brings in the acrn- hypervisor package in future releases to reuse
the same setup procedure?

Regards,
Tonny

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 2:26 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

this change means we don't need to install a "service_os" bundle
and copy
acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-
lts2018 "
package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need
to setup
manually to boot up one of them?
Any plan, please let me know. We may need to update documentation
per
your change.

the procedure to install ACRN is the same, we (ACRN team & CLR team)
need to improve it to setup easily.

Only changes the kernel, instead of choose pk414-sos you can choose
iot- lts2018-sos, and instead of pk414-standard as Guest you can
choose
iot-lts2018 (note: no extra/post name (-standard) in it).

And in the next weeks pk414 will be removed (I'll send an email when
we plan to remove it).

iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.



Thanks
Ailin
-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Miguel
Bernal Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant
list of back-
ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on
bare
metal systems as well as running as a "normal" guest in various
hypervisors. It is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN
hypervisor
setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.
--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation









--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: Clear Linux iot kernel LTS2018

Miguel Bernal Marin
 

On Thu, Oct 11, 2018 at 08:10:29AM +0000, Geoffroy Van Cutsem wrote:
I see some mix-up in this thread between bundles and packages. The service-os bundle [1] includes a number of packages, such as the acrn-hypervisor (hypervisor, devicemodel, tools), the kernels we use for the Service OS and other useful things.

The change that's coming is that at the moment the kernels (SOS and UOS) are coming from the linux-pk414 package (which included in the service-os bundle) and the 'linux-pk' bundle respectively. Soon the service-os bundle will be updated to include the linux-iot-lts2018-sos package that provides the kernel for the Service OS. The 'kernel-iot-lts2018' should be used instead of the 'linux-pk' one to install the Guest OS kernel. And we'll also need to adjust all kernel names/versions throughout the Getting Started Guide document.

By the way, I think there was a small mistake that sneaked in below:
iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.
Should read:
linux-iot-lts2018-sos is shipped with service-os bundle.
linux-iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.
Thanks for the clarification ;-)

Currently service-os bundle contains linux-pk414-sos and linux-iot-lts2018.


[1] https://github.com/clearlinux/clr-bundles/blob/master/bundles/service-os

Geoffroy

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of
bounce+13723+88+767563+1700423@...
Sent: Thursday, October 11, 2018 9:41 AM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

This is obvious! No.

pk414-sos/iot-lts20180-sos, which contains Clear Linux SOS kernel, acrn-
hypervisor, acrn-dm and related Guest OS launch scripts. It is targeting for
Clear Linux as the SOS on ACRN hypervisor. This bundle needs to install with
"swupd " manually if people want to enable ACRN.
pk414-standard/iot-lts2018, which is targeting for Native Clear Linux or Linux
as the Guest. It Is installed with bare metal system installation.

From the procedure to install ACRN point of view, Miguel said there is no
changes. Just need to be updating kernel name with iot-lts2018-sos replacing
pk414-sos.
And standard kernel with iot-lts2018 replacing pk414-standard.

I think this change is for upgrading current 4.14 kernel to 4.19 named kernel
LTS2018 purpose only.

Again, that would be nice if acrn.efi can be deployed into EFI partition and
acrn boot entry be added into EFI firmware boot menu by default after install
"service-os" bundle with this upgrade opportunity.


Thanks
Ailin
-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Tzeng, Tonny
Sent: Thursday, October 11, 2018 2:46 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

The service-os bundle will also install acrn-hypervisor package, but it seems
the kernel-iot-lts2018 bundle only does part of what the service-os bundle is
doing currently. Will the kernel-iot-lts2018 bundle brings in the acrn-
hypervisor package in future releases to reuse the same setup procedure?

Regards,
Tonny

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 2:26 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

this change means we don't need to install a "service_os" bundle and copy
acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-lts2018 "
package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need to setup
manually to boot up one of them?
Any plan, please let me know. We may need to update documentation per
your change.

the procedure to install ACRN is the same, we (ACRN team & CLR team) need
to improve it to setup easily.

Only changes the kernel, instead of choose pk414-sos you can choose iot-
lts2018-sos, and instead of pk414-standard as Guest you can choose
iot-lts2018 (note: no extra/post name (-standard) in it).

And in the next weeks pk414 will be removed (I'll send an email when we
plan to remove it).

iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.



Thanks
Ailin
-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Miguel Bernal
Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant list of back-
ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on bare
metal systems as well as running as a "normal" guest in various hypervisors. It
is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN hypervisor
setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.
--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation









--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: Clear Linux iot kernel LTS2018

Geoffroy Van Cutsem
 

I see some mix-up in this thread between bundles and packages. The service-os bundle [1] includes a number of packages, such as the acrn-hypervisor (hypervisor, devicemodel, tools), the kernels we use for the Service OS and other useful things.

The change that's coming is that at the moment the kernels (SOS and UOS) are coming from the linux-pk414 package (which included in the service-os bundle) and the 'linux-pk' bundle respectively. Soon the service-os bundle will be updated to include the linux-iot-lts2018-sos package that provides the kernel for the Service OS. The 'kernel-iot-lts2018' should be used instead of the 'linux-pk' one to install the Guest OS kernel. And we'll also need to adjust all kernel names/versions throughout the Getting Started Guide document.

By the way, I think there was a small mistake that sneaked in below:
iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.
Should read:
linux-iot-lts2018-sos is shipped with service-os bundle.
linux-iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.
[1] https://github.com/clearlinux/clr-bundles/blob/master/bundles/service-os

Geoffroy

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of
bounce+13723+88+767563+1700423@...
Sent: Thursday, October 11, 2018 9:41 AM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

This is obvious! No.

pk414-sos/iot-lts20180-sos, which contains Clear Linux SOS kernel, acrn-
hypervisor, acrn-dm and related Guest OS launch scripts. It is targeting for
Clear Linux as the SOS on ACRN hypervisor. This bundle needs to install with
"swupd " manually if people want to enable ACRN.
pk414-standard/iot-lts2018, which is targeting for Native Clear Linux or Linux
as the Guest. It Is installed with bare metal system installation.

From the procedure to install ACRN point of view, Miguel said there is no
changes. Just need to be updating kernel name with iot-lts2018-sos replacing
pk414-sos.
And standard kernel with iot-lts2018 replacing pk414-standard.

I think this change is for upgrading current 4.14 kernel to 4.19 named kernel
LTS2018 purpose only.

Again, that would be nice if acrn.efi can be deployed into EFI partition and
acrn boot entry be added into EFI firmware boot menu by default after install
"service-os" bundle with this upgrade opportunity.


Thanks
Ailin
-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Tzeng, Tonny
Sent: Thursday, October 11, 2018 2:46 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

The service-os bundle will also install acrn-hypervisor package, but it seems
the kernel-iot-lts2018 bundle only does part of what the service-os bundle is
doing currently. Will the kernel-iot-lts2018 bundle brings in the acrn-
hypervisor package in future releases to reuse the same setup procedure?

Regards,
Tonny

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 2:26 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

this change means we don't need to install a "service_os" bundle and copy
acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-lts2018 "
package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need to setup
manually to boot up one of them?
Any plan, please let me know. We may need to update documentation per
your change.

the procedure to install ACRN is the same, we (ACRN team & CLR team) need
to improve it to setup easily.

Only changes the kernel, instead of choose pk414-sos you can choose iot-
lts2018-sos, and instead of pk414-standard as Guest you can choose
iot-lts2018 (note: no extra/post name (-standard) in it).

And in the next weeks pk414 will be removed (I'll send an email when we
plan to remove it).

iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.



Thanks
Ailin
-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Miguel Bernal
Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant list of back-
ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on bare
metal systems as well as running as a "normal" guest in various hypervisors. It
is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN hypervisor
setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.
--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation








Re: Clear Linux iot kernel LTS2018

Yang, Ailin
 

This is obvious! No.

pk414-sos/iot-lts20180-sos, which contains Clear Linux SOS kernel, acrn-hypervisor, acrn-dm and related Guest OS launch scripts. It is targeting for Clear Linux as the SOS on ACRN hypervisor. This bundle needs to install with "swupd " manually if people want to enable ACRN.
pk414-standard/iot-lts2018, which is targeting for Native Clear Linux or Linux as the Guest. It Is installed with bare metal system installation.

From the procedure to install ACRN point of view, Miguel said there is no changes. Just need to be updating kernel name with iot-lts2018-sos replacing pk414-sos.
And standard kernel with iot-lts2018 replacing pk414-standard.

I think this change is for upgrading current 4.14 kernel to 4.19 named kernel LTS2018 purpose only.

Again, that would be nice if acrn.efi can be deployed into EFI partition and acrn boot entry be added into EFI firmware boot menu by default after install "service-os" bundle with this upgrade opportunity.


Thanks
Ailin

-----Original Message-----
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
Sent: Thursday, October 11, 2018 2:46 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

The service-os bundle will also install acrn-hypervisor package, but it seems the kernel-iot-lts2018 bundle only does part of what the service-os bundle is doing currently. Will the kernel-iot-lts2018 bundle brings in the acrn-hypervisor package in future releases to reuse the same setup procedure?

Regards,
Tonny

-----Original Message-----
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 2:26 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

this change means we don't need to install a "service_os" bundle and copy acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-lts2018 " package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need to setup manually to boot up one of them?
Any plan, please let me know. We may need to update documentation per your change.
the procedure to install ACRN is the same, we (ACRN team & CLR team) need to improve it to setup easily.

Only changes the kernel, instead of choose pk414-sos you can choose iot-lts2018-sos, and instead of pk414-standard as Guest you can choose
iot-lts2018 (note: no extra/post name (-standard) in it).

And in the next weeks pk414 will be removed (I'll send an email when we plan to remove it).

iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.



Thanks
Ailin
-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Miguel Bernal
Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant list of back-ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on bare metal systems as well as running as a "normal" guest in various hypervisors. It is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN hypervisor setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.
--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: Clear Linux iot kernel LTS2018

Tzeng, Tonny <tonny.tzeng@...>
 

Hi Miguel,

The service-os bundle will also install acrn-hypervisor package, but it seems the kernel-iot-lts2018 bundle only does part of what the service-os bundle is doing currently. Will the kernel-iot-lts2018 bundle brings in the acrn-hypervisor package in future releases to reuse the same setup procedure?

Regards,
Tonny

-----Original Message-----
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 2:26 PM
To: acrn-users@...
Subject: Re: [acrn-users] Clear Linux iot kernel LTS2018

Hi Miguel,

this change means we don't need to install a "service_os" bundle and copy acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-lts2018 " package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need to setup manually to boot up one of them?
Any plan, please let me know. We may need to update documentation per your change.
the procedure to install ACRN is the same, we (ACRN team & CLR team) need to improve it to setup easily.

Only changes the kernel, instead of choose pk414-sos you can choose iot-lts2018-sos, and instead of pk414-standard as Guest you can choose
iot-lts2018 (note: no extra/post name (-standard) in it).

And in the next weeks pk414 will be removed (I'll send an email when we plan to remove it).

iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.



Thanks
Ailin
-----Original Message-----
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Miguel Bernal
Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant list of back-ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on bare metal systems as well as running as a "normal" guest in various hypervisors. It is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN hypervisor setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.
--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: Clear Linux iot kernel LTS2018

Miguel Bernal Marin <miguel.bernal.marin@...>
 

Hi Miguel,

this change means we don't need to install a "service_os" bundle and copy acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-lts2018 " package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need to setup manually to boot up one of them?
Any plan, please let me know. We may need to update documentation per your change.
the procedure to install ACRN is the same, we (ACRN team & CLR team)
need to improve it to setup easily.

Only changes the kernel, instead of choose pk414-sos you can choose
iot-lts2018-sos, and instead of pk414-standard as Guest you can choose
iot-lts2018 (note: no extra/post name (-standard) in it).

And in the next weeks pk414 will be removed (I'll send an email when we
plan to remove it).

iot-lts2018-sos is shipped with service-os bundle.
iot-lts2018 (standard) is shipped with kernel-iot-lts2018 bundle.



Thanks
Ailin
-----Original Message-----
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant list of back-ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on bare metal systems as well as running as a "normal" guest in various hypervisors. It is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN hypervisor setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.
--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: Clear Linux iot kernel LTS2018

Yang, Ailin
 

Hi Miguel,

this change means we don't need to install a "service_os" bundle and copy acrn.efi to EFI partition manually to boot ACRN hypervisor after " iot-lts2018 " package installed with bare metal system. right?
if so, how to boot up system to "standard" and "sos"? still need to setup manually to boot up one of them?
Any plan, please let me know. We may need to update documentation per your change.

Thanks
Ailin

-----Original Message-----
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 1:26 PM
To: acrn-users@...
Subject: [acrn-users] Clear Linux iot kernel LTS2018

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant list of back-ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on bare metal systems as well as running as a "normal" guest in various hypervisors. It is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an ACRN hypervisor setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.

--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: When is github.com/projectacrn/acrn-kernel updated?

Yang, Ailin
 

there will be 2 branches under acrn-kernl. 4.14 current branch and 4.9 branch(based on LTS2018)

Thanks
Ailin

-----Original Message-----
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Miguel Bernal Marin
Sent: Thursday, October 11, 2018 1:05 PM
To: acrn-users@...
Subject: Re: [acrn-users] When is github.com/projectacrn/acrn-kernel updated?

I'm doing some experimentation and wanted to generate my own kernel
for my SOS and UOS. I cloned the kernel hosted on
https://github.com/projectacrn/acrn-kernel but noticed that it was
last updated on September 29th and its version is 4.14.69. Looking at
the latest SOS kernel provided by Clear Linux [1], it's at version
4.14.73. Are we missing some patches/updates on https://github.com/projectacrn/acrn-kernel?
Thanks for the pointing out the issue.
Generally speaking, the acrn-kernel will be synchronized with
github.com/intel-linux-lts.git Weekly.
Now we are preparing the switch of kernel version.
So this is not updated.
And, Are you going to switch to LTS2018 (mainline-tracking) kernel in the next weeks?


Clear Linux iot kernel LTS2018

Miguel Bernal Marin
 

Hi,

Since 25540 Clear Linux* OS has added a new kernel called

IOT LTS2018

This kernel is an "enterprise style" kernel with a significant
list of back-ported features.

This package has a main package "standard" and a sub-package "sos".

The "standard" kernel (the main package) is meant for running on
bare metal systems as well as running as a "normal" guest in
various hypervisors. It is available in the kernel-iot-lts2018 bundle.

The "sos" kernel is specifically meant to run as DOM0 in an
ACRN hypervisor setup. It is available in the service-os bundle.

Currently service-os bundle keep pk414 but will be removed when
iot-lts2018 be adopted.

--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation


Re: When is github.com/projectacrn/acrn-kernel updated?

miguel.bernal.marin@...
 

I'm doing some experimentation and wanted to generate my own kernel for
my SOS and UOS. I cloned the kernel hosted on
https://github.com/projectacrn/acrn-kernel but noticed that it was last
updated on September 29th and its version is 4.14.69. Looking at the latest
SOS kernel provided by Clear Linux [1], it's at version 4.14.73. Are we missing
some patches/updates on https://github.com/projectacrn/acrn-kernel?
Thanks for the pointing out the issue.
Generally speaking, the acrn-kernel will be synchronized with github.com/intel-linux-lts.git
Weekly.
Now we are preparing the switch of kernel version.
So this is not updated.
And, Are you going to switch to LTS2018 (mainline-tracking) kernel in
the next weeks?


Re: When is github.com/projectacrn/acrn-kernel updated?

Zhao, Yakui
 

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Wednesday, October 10, 2018 5:55 PM
To: acrn-users@...
Subject: [acrn-users] When is github.com/projectacrn/acrn-kernel updated?

Hi folks,

I'm doing some experimentation and wanted to generate my own kernel for
my SOS and UOS. I cloned the kernel hosted on
https://github.com/projectacrn/acrn-kernel but noticed that it was last
updated on September 29th and its version is 4.14.69. Looking at the latest
SOS kernel provided by Clear Linux [1], it's at version 4.14.73. Are we missing
some patches/updates on https://github.com/projectacrn/acrn-kernel?
Thanks for the pointing out the issue.
Generally speaking, the acrn-kernel will be synchronized with github.com/intel-linux-lts.git
Weekly.
Now we are preparing the switch of kernel version.
So this is not updated.

Thanks,
Geoffroy

[1]
https://download.clearlinux.org/releases/current/clear/x86_64/os/Packages/l
inux-pk414-sos-4.14.73-114.x86_64.rpm



ACRN Project Technical Community Meeting Minutes - 10/10

Wang, Hongbo
 

ACRN Project TCM - 10th October 2018
Location
Agenda
 
  1. ACRN project update
ACRN + Open Source version Android is working, will publish guide later.
 
  1. Cao, Minggui:  Interrupt Storm Mitigation
Download foil from ACRN Presentation->ACRN_TCM->WW41’18.
  1. All: Community open discussion.
Q: Does Intel hardware also has hardware limitation of interrupts? for e.g. if in case of level edge triggered the interrupts are generated until the level is changed.. in this case would Intel hardware limit interrupt?   A: Yes, for some device, it can reduce.
Q: Can this capability be a statically configured as part of VM DM configuration info?  A: Is a good suggestion, per VM interrupt rate setting by using command line. For different VM, setting different threshold.
Q:Once the device is passed through it means only that VM will handle that device ...then what is the need to make a hypercall and inject an interrupt ..back to UOS again.  A: No, the hypercall is not used to inject interrupt.
Q: how is interrupt storm affecting SOS? (2) why is interrupt injection enabled for SOS? may be we can turn it off after UOS is boot up? The concerpt of passthrough only applies to UOS.  A: Even device passed through to UOS, the interrupt sill needs go through hypervisor.
Q: Can post-interrupt solve the interrupt storm by bypassing the hypervisor?  A: for APL platform, it doesn’t support post-interrupt.  And VT-d device will go through hypervisor too.
One comment: One problem you have is that once you start throttling a particular interrupt you will not know when the storm has ended because your data is now skewed since many devices cannot inject a new interrupt until the previous interrupt has been serviced.   Throttling will need a timeout.
 
 
  1. Next meeting agenda proposal:
 
WW Topic Presenter Status
WW21 ACRN roadmap introduction Ren, Jack Done
WW22 Patch submission process
ACRN feature list introduction
Wang, Hongbo
Ren, Jack
Done
WW23 Memory Management Chen, Jascon Done
WW24 Boot flow and fast boot Wu, Binbin Done
WW25 Memory Management Chen, Jason C Done
WW26 Audio virtualization Li, Jocelyn Done
WW27 Trusty Security on ACRN Zhu, Bing’s team Done
WW28 Clear Linux and use on ACRN Du, Alek Done
WW29 GVT-g for ACRN (a.k.a AcrnGT) Gong, Zhipeng Done
WW30 Device pass-through Zhai, Edwin Done
WW31 ACRN logical partition Ren, Jack/Xu, Anthony Done
WW32 ACRN interrupt management Chen, Jason Done
WW33 ACRN ACPI virtualization Edwin Zhai Done
WW34 ACRN S3/S5 management Fengwei Yin Done
WW35 ACRN P-state/C-state management Victor Sun Done
WW36 CPU Virtualization Jason Chen Done
WW37 Joint Design: VM Configuration Options Discussion Fengwei Yin Done
WW38 Joint Design: Remove dynamic memory allocation from ACRN memory management Li, Fei Done
WW39 USB virtualization Wang, Yu Done
WW41 Interrupt Storm Mitigation Cao, Minggui Today
 
Marketing/Events
  1. 2018 IoT solution world Congress
  1. Oct’18
  2. One talk and one demo accepted
  1. 2019 Embedded World Exhibition & Conference
  1. Feb. 26-28, 2019
  2. CFP deadline: Aug. 31, 2018
  3. Nuremberg, Germany
Resources
  1. Project URL:
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@...g
  4. Technical Mailing list: acrn-dev@...g
=============================
 
 
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 


When is github.com/projectacrn/acrn-kernel updated?

Geoffroy Van Cutsem
 

Hi folks,

I'm doing some experimentation and wanted to generate my own kernel for my SOS and UOS. I cloned the kernel hosted on https://github.com/projectacrn/acrn-kernel but noticed that it was last updated on September 29th and its version is 4.14.69. Looking at the latest SOS kernel provided by Clear Linux [1], it's at version 4.14.73. Are we missing some patches/updates on https://github.com/projectacrn/acrn-kernel?

Thanks,
Geoffroy

[1] https://download.clearlinux.org/releases/current/clear/x86_64/os/Packages/linux-pk414-sos-4.14.73-114.x86_64.rpm


Re: How to pass through off-chip USB controller

Wu, Binbin
 

Great to hear it!

--
Best wishes,
Binbin

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Tzeng, Tonny
Sent: Monday, October 8, 2018 2:55 PM
To: VanCutsem, Geoffroy <geoffroy.vancutsem@...>; acrn-
users@...
Subject: Re: [acrn-users] How to pass through off-chip USB controller

Thanks Binbin, the Movidius UP AI Core [1] now can be passed through to the
User OS. Thanks for the great help!!

[1] https://up-shop.org/featured/204-up-ai-core.html

Regards,
Tonny

-----Original Message-----
From: VanCutsem, Geoffroy
Sent: Tuesday, September 11, 2018 2:19 PM
To: acrn-users@...
Cc: Tzeng, Tonny <tonny.tzeng@...>
Subject: RE: [acrn-users] How to pass through off-chip USB controller

Thanks Binbin!

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Wu, Binbin
Sent: Tuesday, September 11, 2018 7:47 AM
To: acrn-users@...
Cc: Tzeng, Tonny <tonny.tzeng@...>
Subject: Re: [acrn-users] How to pass through off-chip USB controller

Hi Geoffroy,

Yes, and the PR has been sent out.
https://github.com/projectacrn/acrn-hypervisor/pull/1210


On 9/10/2018 6:36 PM, Geoffroy Van Cutsem wrote:

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Wu, Binbin
Sent: Sunday, September 9, 2018 11:57 AM
To: acrn-users@...
Cc: Tzeng, Tonny <tonny.tzeng@...>
Subject: Re: [acrn-users] How to pass through off-chip USB
controller

Hi Geoffroy,

Thanks for providing the info.
After checking the code, I did found a logic error when handling
msix table read/write in passthrough.
I have sent out a patch to fix the issue to
acrn-dev@... for review.
Thanks Binbin! I guess that's the one:
https://lists.projectacrn.org/g/acrn-
dev/message/11368?

We will keep an eye on it (to see when it gets merged) and perhaps
even
test it beforehand on our side if we get a chance!

Thanks,
Geoffroy

On 9/7/2018 9:50 PM, Geoffroy Van Cutsem wrote:
Hi Binbin, Edwin,

The error Tonny got at the time was with this combination (so not
the latest as of today):

- HV/DM: f815415

- SOS: Clear 24030 w/ 4.14.57-69 kernel

Looking it up on Github, this is the line you’re asking for:
https://github.com/projectacrn/acrn-hypervisor/blob/acrn-2018w30.4
-1
40
000p/devicemodel/hw/pci/passthrough.c#L560

And yes, that’s the one you have below J

Thanks,

Geoffroy

*From:*acrn-users@...
[mailto:acrn-users@...] *On Behalf Of *Wu,
Binbin
*Sent:* Friday, September 7, 2018 9:16 AM
*To:* acrn-users@...
*Subject:* Re: [acrn-users] How to pass through off-chip USB
controller

Hi Tonny,
Which version of your clearlinux SOS?
Is there any chance that can you confirm that whether
hw/pci/passthrough.c:560 is the line of code in bold?

static void

msix_table_write(struct vmctx *ctx, int vcpu, struct passthru_dev
*ptdev,

uint64_t offset, int size, uint64_t data)

{

struct pci_vdev *dev;

struct msix_table_entry *entry;

uint8_t *dest8;

uint16_t *dest16;

uint32_t *dest32;

uint64_t *dest64;

size_t entry_offset;

uint32_t vector_control;

int index;

dev = ptdev->dev;

if (offset >= dev->msix.pba_offset &&

    offset < dev->msix.pba_offset + dev->msix.pba_size) {

switch (size) {

case 1:

dest8 = (uint8_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

*dest8 = data;

break;

case 2:

dest16 = (uint16_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

*dest16 = data;

break;

case 4:

dest32 = (uint32_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

**dest32 = data; *//is hw/pci/passthrough.c:560 this line of code?

break;

case 8:

dest64 = (uint64_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

*dest64 = data;

break;

default:

break;

}

return;

}





Re: How to pass through off-chip USB controller

Tzeng, Tonny <tonny.tzeng@...>
 

Thanks Binbin, the Movidius UP AI Core [1] now can be passed through to the User OS. Thanks for the great help!!

[1] https://up-shop.org/featured/204-up-ai-core.html

Regards,
Tonny

-----Original Message-----
From: VanCutsem, Geoffroy
Sent: Tuesday, September 11, 2018 2:19 PM
To: acrn-users@...
Cc: Tzeng, Tonny <tonny.tzeng@...>
Subject: RE: [acrn-users] How to pass through off-chip USB controller

Thanks Binbin!

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Wu, Binbin
Sent: Tuesday, September 11, 2018 7:47 AM
To: acrn-users@...
Cc: Tzeng, Tonny <tonny.tzeng@...>
Subject: Re: [acrn-users] How to pass through off-chip USB controller

Hi Geoffroy,

Yes, and the PR has been sent out.
https://github.com/projectacrn/acrn-hypervisor/pull/1210


On 9/10/2018 6:36 PM, Geoffroy Van Cutsem wrote:

-----Original Message-----
From: acrn-users@... [mailto:acrn-
users@...] On Behalf Of Wu, Binbin
Sent: Sunday, September 9, 2018 11:57 AM
To: acrn-users@...
Cc: Tzeng, Tonny <tonny.tzeng@...>
Subject: Re: [acrn-users] How to pass through off-chip USB
controller

Hi Geoffroy,

Thanks for providing the info.
After checking the code, I did found a logic error when handling
msix table read/write in passthrough.
I have sent out a patch to fix the issue to
acrn-dev@... for review.
Thanks Binbin! I guess that's the one:
https://lists.projectacrn.org/g/acrn-
dev/message/11368?

We will keep an eye on it (to see when it gets merged) and perhaps
even
test it beforehand on our side if we get a chance!

Thanks,
Geoffroy

On 9/7/2018 9:50 PM, Geoffroy Van Cutsem wrote:
Hi Binbin, Edwin,

The error Tonny got at the time was with this combination (so not
the latest as of today):

- HV/DM: f815415

- SOS: Clear 24030 w/ 4.14.57-69 kernel

Looking it up on Github, this is the line you’re asking for:
https://github.com/projectacrn/acrn-hypervisor/blob/acrn-2018w30.4
-1
40
000p/devicemodel/hw/pci/passthrough.c#L560

And yes, that’s the one you have below J

Thanks,

Geoffroy

*From:*acrn-users@...
[mailto:acrn-users@...] *On Behalf Of *Wu,
Binbin
*Sent:* Friday, September 7, 2018 9:16 AM
*To:* acrn-users@...
*Subject:* Re: [acrn-users] How to pass through off-chip USB
controller

Hi Tonny,
Which version of your clearlinux SOS?
Is there any chance that can you confirm that whether
hw/pci/passthrough.c:560 is the line of code in bold?

static void

msix_table_write(struct vmctx *ctx, int vcpu, struct passthru_dev
*ptdev,

uint64_t offset, int size, uint64_t data)

{

struct pci_vdev *dev;

struct msix_table_entry *entry;

uint8_t *dest8;

uint16_t *dest16;

uint32_t *dest32;

uint64_t *dest64;

size_t entry_offset;

uint32_t vector_control;

int index;

dev = ptdev->dev;

if (offset >= dev->msix.pba_offset &&

    offset < dev->msix.pba_offset + dev->msix.pba_size) {

switch (size) {

case 1:

dest8 = (uint8_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

*dest8 = data;

break;

case 2:

dest16 = (uint16_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

*dest16 = data;

break;

case 4:

dest32 = (uint32_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

**dest32 = data; *//is hw/pci/passthrough.c:560 this line of code?

break;

case 8:

dest64 = (uint64_t *)(dev->msix.pba_page + offset -

    dev->msix.pba_page_offset);

*dest64 = data;

break;

default:

break;

}

return;

}




Re: Questions about ACRN's dependency and Other Linux Distro Supports

Shin, Jun-Sik
 

ClearLinux SOS and Ubuntu SOS still have the same issue, even though I removed "i915.enable_initial_modeset=1 i915.avail_planes_per_pipe=0x000C00" from grub entry configuration file. (acrn.conf, 40_custom)
At below, I attached the grub configuration files used for my test.

/etc/grub.d/40_custom (Ubuntu as SOS)
menuentry 'ACRN ubuntu SOS' {
        recordfail
        insmod gzio
        insmod part_gpt
        insmod ext2
        linux  /boot/acrn/org.clearlinux.pk414-sos.4.14.71-110 pci_devices_ignore=(0:18:1)  console=tty0 console=ttyS0 i915.nuclear_pageflip=1 root=PARTUUID=a3bd9401-910c-4256-9150-6da0687d6a89 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.tsd_init=7 i915.tsd_delay=2000 i915.domain_plane_owners=0x011111110000 i915.enable_guc_loading=0 i915.enable_guc_submission=0 i915.enable_preemption=1 i915.context_priority_mode=2 i915.enable_gvt=1 hvlog=2M@0x1FE00000
}
 
/boot/loader/entries/acrn.conf (ClearLinux as SOS)
title The ACRN Service OS
linux   /EFI/org.clearlinux/kernel-org.clearlinux.pk414-sos.4.14.71-110
options pci_devices_ignore=(0:18:1) console=tty0 console=ttyS0 i915.nuclear_pageflip=1 root=/dev/sda3 rw rootwait ignore_loglevel no_timer_check consoleblank=0 i915.tsd_init=7 i915.tsd_delay=2000 i915.domain_plane_owners=0x011111110000 i915.enable_guc_loading=0 i915.enable_guc_submission=0 i915.enable_preemption=1 i915.context_priority_mode=2 i915.enable_gvt=1 i915.enable_guc=0 hvlog=2M@0x1FE00000 hugepagesz=1G hugepages=2


Re: Questions about ACRN's dependency and Other Linux Distro Supports

Miguel Bernal Marin
 

According to your comment, I tried removing a line "load_video" from "/etc/grub.d/40_custom", run "sudo update-grub", and reboot. But, my hardware still showed a black screen.
As another try, I tried installing Clear Linux as the Service OS. Clear Linux as host OS was working without any problems. But, booting ACRN hypervisor showed the same problem. ACRN hypervisor appeared in grub list, but after selecting it, my hardware didn't show anything.
If I can get detailed log messages regarding this issue, then those are very helpful to locate the cause of this problem. Are there any methods to get log messages or debugging messages in this situation?
Looks like a video issue, try removing

i915.enable_initial_modeset=1 i915.avail_planes_per_pipe=0x000C00

from kernel cmdline.

--
Regards,

Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation

1141 - 1160 of 1234