Hi,

You can download the RPMs (both precompiled binaries and source) and use ‘rpm2cpio’ to extract the content and re-use it. We have an example of how to use the pre-compiled binaries in this tutorial section: https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html#install-the-service-os-kernel (you will need to adapt the instructions to the kernel name and version below).

Links to the RPMs:

Precompiled binary:

linux-iot-lts2018-4.19.0-19.x86_64.rpm             10-Nov-2018 14:53            25970178

linux-iot-lts2018-extra-4.19.0-19.x86_64.rpm       10-Nov-2018 14:53           304973245

linux-iot-lts2018-sos-4.19.0-19.x86_64.rpm         10-Nov-2018 14:53            71975780

Source RPM:

linux-iot-lts2018-4.19.0-19.src.rpm                10-Nov-2018 14:53           119125797

HTH,

Geoffroy

Ailin is correct the ACRN hypervisor is not running (for some reason).

There are three possibilities for the ‘uart=’ parameter:

- uart=disabled

- uart=mmio@0x9141e000

- uart=port@0x3F8

https://github.com/projectacrn/acrn-hypervisor/blob/master/hypervisor/bsp/uefi/cmdline.c#L18-L20

The best is to boot a standard OS off a USB stick (Clear, Ubuntu, …), check from dmesg the serial port settings: “dmesg | grep ttyS”, and use those.

HTH,

Geoffroy

drivers/acrn/hvlog.c

174         if (x86_hyper_type != X86_HYPER_ACRN)

175                 return -ENODEV;

Thanks

Ailin

Check kernel command line to see which kernel loaded?

cat /proc/cmdline

Below log shows ACRN hypervisor isn’t launched successfully, and no hv log，

Thanks

Ailin

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of tk.kim@...
Sent: Tuesday, November 27, 2018 4:17 PM
To: acrn-users@...
Subject: Re: [acrn-users] Questions about ACRN's dependency and Other Linux Distro Supports

Hi 
I'm using a mmio for the uart setting and I show shell prompt.  
However, I'm not sure this is the SOS or the host clear linux. 

dmesg | grep ACRN  gives me below logs...

ACRNTrace : acrn_trace : not support acrn hypervisor!
ACRN HVLog : acrn_hvlog_init
ACRN HVLog : Failed to setup acrn_hvlog_cur_0, errno -19

What is error number 19, and do you have any idea to clarify root cause?
(I couldn't find this messages from the hypervisor source codes)

Thanks 
Taekyoung Kim

drivers/acrn/hvlog.c

174         if (x86_hyper_type != X86_HYPER_ACRN)

175                 return -ENODEV;

Thanks

Ailin

Check kernel command line to see which kernel loaded?

cat /proc/cmdline

Below log shows ACRN hypervisor isn’t launched successfully, and no hv log，

Thanks

Ailin

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of tk.kim@...
Sent: Tuesday, November 27, 2018 4:17 PM
To: acrn-users@...
Subject: Re: [acrn-users] Questions about ACRN's dependency and Other Linux Distro Supports

Hi 
I'm using a mmio for the uart setting and I show shell prompt.  
However, I'm not sure this is the SOS or the host clear linux. 

dmesg | grep ACRN  gives me below logs...

ACRNTrace : acrn_trace : not support acrn hypervisor!
ACRN HVLog : acrn_hvlog_init
ACRN HVLog : Failed to setup acrn_hvlog_cur_0, errno -19

What is error number 19, and do you have any idea to clarify root cause?
(I couldn't find this messages from the hypervisor source codes)

Thanks 
Taekyoung Kim

Check kernel command line to see which kernel loaded?

cat /proc/cmdline

Below log shows ACRN hypervisor isn’t launched successfully, and no hv log，

Thanks

Ailin

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of tk.kim@...
Sent: Tuesday, November 27, 2018 4:17 PM
To: acrn-users@...
Subject: Re: [acrn-users] Questions about ACRN's dependency and Other Linux Distro Supports

Hi 
I'm using a mmio for the uart setting and I show shell prompt.  
However, I'm not sure this is the SOS or the host clear linux. 

dmesg | grep ACRN  gives me below logs...

ACRNTrace : acrn_trace : not support acrn hypervisor!
ACRN HVLog : acrn_hvlog_init
ACRN HVLog : Failed to setup acrn_hvlog_cur_0, errno -19

What is error number 19, and do you have any idea to clarify root cause?
(I couldn't find this messages from the hypervisor source codes)

Thanks 
Taekyoung Kim

Sounds great, good luck and do let us know if you are successful!

If possible, I would advice that you set up ACRN on another platform that is supported, to make sure you are very familiar and comfortable with the process. Please note that it will be hard to debug problems if you don’t have a serial port (as it’s the only way you can get debug info from the hypervisor).

Thanks,

Geoffroy

Hi Taekyoung,

With the latest release (v0.3), you should be using org.clearlinux.iot-lts2018-sos.4.19.0-19, we’re in the process of updating the Getting Started Guide to reflect these changes – see https://github.com/projectacrn/acrn-hypervisor/pull/1859. We will also need to update our tutorial on how to use Ubuntu as the Service OS as it is, as you’ve noted, out of date in a few places. I have filed a ticket to track that task: https://github.com/projectacrn/acrn-hypervisor/issues/1878

You’re absolutely right about the discrepancy about the kernel location. Ultimately, you can put it pretty much where you want on the ESP (/dev/sda1, the EFI System Partition), the key being to use the right path in your grub conf file. IMHO, the most logical location for that kernel would be under /EFI/Ubuntu

Thanks,

Geoffroy

Are you sure you have the kernel in the right place, your grub entry indicated: /boot/acrn/org.clearlinux.pk414-sos.4.14.74-115 but the kernel is usually placed in a different folder (and under a slightly different name), e.g. /EFI/org.clearlinux/kernel-org.clearlinux.pk414-sos.4.14.57-69

The normal boot flow is:

EFI BIOS-> acrn.efi->grub->SOS kernel -> user land

“ACRN ubuntu SOS appeared in boot list” doesn’t mean the grub must be loaded by acrn.efi.

This is why I asked you to check #1 point to make sure you first boot stage is correct.

By the way, you need to change org.clearlinux.pk414-sos.4.14.74-115 to org.clearlinux.iot-lts2018-sos.4.19.0-19

We have update kernel to 4.19 already if you are using ACRN v0.3 or latest.

Thanks

Ailin

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of tk.kim@...
Sent: Wednesday, November 21, 2018 4:17 PM
To: acrn-users@...
Subject: Re: [acrn-users] Questions about ACRN's dependency and Other Linux Distro Supports

Hello, Yang.
Thank you for the reply.

1,  is your acrn.efi loaded by EFI firmware correctly?

     You can run “ sudo efibootmgr –v” to check if the “ACRN Hypervisor” is first boot option,

    Also you can enter the EFI firmware at boot (using F10) to select “ACRN Hypervisor”

  -> [TK] ACRN ubuntu SOS appeared in boot list, but after selecting it, my hardware didn't show anything and rebooted in few seconds. 

    because of that I couldn't go further step 2 or 3 as you mentioned. 

I was wondering if the SOS kernel that I'm using(org.clearlinux.pk414-sos.4.14.74-115) has device dependency (might be CPU, graphic card and so on)

I think knowing which component or options are dependent on device would be helpful to porting ACRN hypervisor and Service OS

Showing “Black screen” only is hard to know your issue exactly.

Also NUC6i5SYH is not official supported hardware,  we didn’t run test with it.

But can you check below 3 points to narrow down your issue first:

1,  is your acrn.efi loaded by EFI firmware correctly?

     You can run “ sudo efibootmgr –v” to check if the “ACRN Hypervisor” is first boot option,

    Also you can enter the EFI firmware at boot (using F10) to select “ACRN Hypervisor”

2, check you SOS booted up successfully with right kernel and kernel command line?

You should able to login from remote ssh Client if the OS boot up successfully

3, check if ACRN hypervisor is running properly with “$ dmesg | grep ACRN”

     The right output is:

     $ dmesg | grep ACRN

   [    0.000000] Hypervisor detected: ACRN

   [    1.687128] ACRNTrace: acrn_trace_init, cpu_num 4

   [    1.693129] ACRN HVLog: acrn_hvlog_init

Thanks

ailin

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of tk.kim@...
Sent: Wednesday, November 21, 2018 2:51 PM
To: acrn-users@...
Subject: Re: [acrn-users] Questions about ACRN's dependency and Other Linux Distro Supports

Hello. This is Taekyoung Kim. 
I have same problem with booting both Clear Linux SOS and Ubuntu SOS. 
My machine shows black screen and reboots automatically.

I have a question regarding this issue.
- Is there H/W dependency in the grub command? What are they? How can I get rid of dependency to boot SOS?

The environment I am using is below (Ubuntu as SOS)
H/W : NUC6i5SYH 
Hypervisor : ACRN Hypervisor v0.3
SOS Kernel : org.clearlinux.pk414-sos.4.14.74-115