Hi Fuzhong,
    The windows uos is works normally after enable "multi-user.target". The reason of this issue is I didn't change the Ubuntu sos to text mode. Thanks.
About the GVT parameter, do you mean "-s 2,pci-gvt -G "$2" \"? I attached the scripts, please help to confirm.
I have checked the BIOS setting, it's same like the GSG.  The ACRN version is V2.3,  Industry Scenario.
Other questions:
1. How to make VGA and USB controller works again on Ubuntu sos after the windows uos poweroff?
2. launch_xenomai.sh script make the WHL stuck. It didn't happen on the KBL platform.
Command :  "sudo ./launch_xenomai.sh -f ./preempt-rt-32030.img -k ./linux-4.19.59-xenomai-3.1-acrn+-x86.tar.gz"

Best Regards,
ZhangShuai

Hi ZhangShuai

Which codebase are you using for WhiskyLake Platform?

Do you follow the GSG to set BIOS: https://projectacrn.github.io/latest/getting-started/rt_industry_ubuntu.html#additional-settings-in-the-service-vm

Item 1, please ignore the waring message;

Item 2, Do you add GVT parameter in your launch script? GVT-g doesn’t work since v2.1. Please share it to us.

Item3, Please enable “multi-user.target” with systemctl set-default multi-user.target in Ubuntu sos.

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of ZhangShuai
Sent: Friday, March 26, 2021 10:55 AM
To: acrn-users@...
Cc: hudongjiang@...; ligang@...; wumengkui@...; lijia@...; hujunke@...
Subject: Re: [acrn-users] some issues when launch debian and windows uos

 

updates

Change to a WhiskyLake Platform, still have these issues.
I enabled the serial port of the WHL, got some debug messages of ACRN when launch sos and uos.
1. at acrn startup, the uart output:
[11007973us][cpu=0][vm0:vcpu0][sev=2][seq=37]:vpci_write_cfg 0:1c.1 not found! off: 0xdb, val: 0xbf
[11018799us][cpu=0][vm0:vcpu0][sev=2][seq=38]:vpci_write_cfg 0:1c.2 not found! off: 0xdb, val: 0xbf
[11029675us][cpu=0][vm0:vcpu0][sev=2][seq=39]:vpci_write_cfg 0:1c.3 not found! off: 0xdb, val: 0xbf
......

2. when launch a uos (debian, ubuntu or clr linux), the uart output :

[721704238us][cpu=0][vm0:vcpu0][sev=3][seq=224]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[721716301us][cpu=0][vm0:vcpu0][sev=3][seq=225]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[721727986us][cpu=0][vm0:vcpu0][sev=3][seq=226]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[721739730us][cpu=0][vm0:vcpu0][sev=3][seq=227]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[733552988us][cpu=0][vm1:vcpu0][sev=3][seq=230]:vlapic: Start Secondary VCPU1 for VM[1]...

 

3. at the first time of running install_win.sh, got the message like below. I saw the UEFI shell on the HDMI screen, then the WHL restarted.

[758442306us][cpu=0][vm0:vcpu0][sev=1][seq=224]:vpci_assign_pcidev 0:14.0 not support FLR or not support PM reset
[758549509us][cpu=0][vm0:vcpu0][sev=3][seq=225]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[758575283us][cpu=0][vm0:vcpu0][sev=3][seq=226]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[758602622us][cpu=0][vm0:vcpu0][sev=3][seq=227]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
[758629819us][cpu=0][vm0:vcpu0][sev=3][seq=228]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler

After this time, the system always restarted directly when running  install_win.sh. Nothing output on the uart.

 

Best Regards,
ZhangShuai

 

 

 

On 2021/3/19 10:57, zhangshuai wrote:

Hi all,
    I build a Ubuntu18.04 SOS on our 7300U board.  SCENARIO = industry
$ uname -a
Linux acrn-Kabylake 5.4.72-PKT-200203T060100Z #2 SMP PREEMPT Mon Mar 8 10:59:26 CST 2021 x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep ACRN
[    0.000000] Hypervisor detected: ACRN
[   65.293721] ACRNTrace: Initialized acrn trace module with 4 cpu
[   65.293722] ACRN HVLog: no fixed memory reserve for hvlog.
$ acrn-dm -v
DM version is: 2.3-b6e24ea4-dirty (daily tag:acrn-2020w48.5-180000p), build by acrn@2021-03-08 10:28:57

There are some issues when launch UOS:
issue1: The SOS freezes for 60s at startup after the i915.enable_gvt=1 added in 40_customer.

the dmesg file is in attachment.

issue2: launch Debian as UOS,  warning messages(as follows) keep printing but the UOS works fine.
Failed to emulate instruction [mmio address 0xdf57e000, size 4Unhandled memory access to 0xdf57e004
Failed to emulate instruction [mmio address 0xdf57e004, size 4Unhandled memory access to 0xdf57e008
Failed to emulate instruction [mmio address 0xdf57e008, size 4Unhandled memory access to 0xdf57e00c
....

issue3: follow the latest document to using_windows_as_uos,  Enable the GVT-d GOP Driver.
The board often restarts after running the install_win.sh script. 
have tried 10 times, see UEFI shell only twice, and the rest are restarted directly.
finished the windows installation by GVT-d, but never launch WaaG successfully
because the board always restart when running launch_win.sh

the attachment is the tar of the dmesg files and scripts.
Any information, or thoughts would be greatly appreciated.

Thanks and Best Regards,
ZhangShuai

-- 

Xi'an R&D Center Computerized Numerical Control R&D Dept.  Shuai Zhang 
Tel : 029-84503040-8360 
E-mail :  zhangshuai@...     Web :  www.jingdiao.com