|
Re: Intel NUC APL gets powered off when launching uos with gpu passthrough
Could you be hitting something similar as this: https://github.com/projectacrn/acrn-hypervisor/issues/5811
Can you try to boot with with “uart=disabled” and see what happens? Add this to your /etc/grub.d/40_custom file: multiboot2 /boot/acrn/acrn.bin uart=disabled root=PARTUUID="PARTUUID"
Then run “sudo update-grub” and reboot.
Geoffroy
From: acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Sent: Thursday, January 27, 2022 6:13 am To: acrn-users@... Subject: Re: [acrn-users] Intel NUC APL gets powered off when launching uos with gpu passthrough
[Edited Message Follows]
Intel NUC apollo lake: NUC6CAYH
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Intel NUC APL gets powered off when launching uos with gpu passthrough
Hello Geoffroy, Please find the details Intel NUC apollo lake: NUC6CAYH ACRN Version 2.6 ACRN kernel: 2.6 Launch Script: Already attached
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Canceled: 2021 ACRN Project Technical Community Meeting (2021/1~2021/12): @ Monthly 3rd Wednesday 4PM (China-Shanghai), Wednesday 10AM (Europe-Munich), Tuesday 1AM (US-West Coast)
Zou, Terry
Cancel this time, and we will start 2022 TCM from ww13 after Chinese New Year, draft agenda as below, thanks.
Special Notes: If you have Zoom connection issue by using
web browser, please install & launch Zoom application, manually input the meeting ID (320664063)
to join the Zoom meeting.
Agenda & Archives:
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
We invite you to attend a monthly "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:
Or visit Github wiki if you can’t access Google doc: https://github.com/projectacrn/acrn-hypervisor/wiki/ACRN-Committee-and-Working-Group-Meetings#technical-community-meetings
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Intel NUC APL gets powered off when launching uos with gpu passthrough
Can you share more details about your set-up? More specifically: - Hardware platform (inc. lspci output) - ACRN version - Launch script
Thanks, Geoffroy
From: acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Sent: Monday, January 10, 2022 2:30 pm To: acrn-users@... Subject: Re: [acrn-users] Intel NUC APL gets powered off when launching uos with gpu passthrough
Could someone please help me get through this
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Intel NUC APL gets powered off when launching uos with gpu passthrough
shibi590268@...
Could someone please help me get through this
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Is it possible to boot Ubuntu-RT as pre-launched vm
Liu, Fuzhong
Hi The pre-condition to access pre-launched vm: there is serial port on your board.
The function should be ok for RTVM using ubuntu rootfs; but RT performance may be impacted by some services of ubuntu OS. You can refer following xml: <pci_devs> <pci_dev>00:17.0 SATA controller: Intel Corporation Device 9dd3 (rev 30)</pci_dev> <pci_dev>03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)</pci_dev> </pci_devs>
Please update the bdf info to match your setup.
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Sent: Friday, December 24, 2021 12:14 PM To: acrn-users@... Subject: [acrn-users] Is it possible to boot Ubuntu-RT as pre-launched vm
Hello,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Intel NUC APL gets powered off when launching uos with gpu passthrough
shibi590268@...
Hello,
The intel nuc apollo lake board NUC6CAYH gets powered off when launching the ubuntu uos script with gpu passthrough. I want to assign a display to the user vm which is ubuntu. This board has two display ports 1. VGA and 2. HDMI. User vm runs successfully when the gpu passthrough is removed. is it possible to assign a display to a pre-launched ubuntu-RT vm. ACRN version: 2.6 Kernel Version: 2.6 SOS: Ubuntu 18.04
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Is it possible to boot Ubuntu-RT as pre-launched vm
shibi590268@...
Hello,
I would like to use ubuntu with a kernel patched with RT as pre launched vm in a hybrid scenario. Is this case applicable? If so, is there any reference link for that? ACRN-hypervisor: 2.6 ACRN-kernel:2.6 SOS: ubuntu
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[Announce] ACRN Open Source Ver2.7 Release Notes
Zou, Terry
Hi all, We are very pleased to announce Version 2.7 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_2.7.html What’s New in v2.7· API and Documentation Updates for User VM and Service VM Terminology More often than not, the terms “UOS” and “SOS” referred to the User VM and Service VM components of an ACRN Hypervisor system and not to the VM’s OS. We’ve updated the hypervisor APIs and documentation to properly reflect these names and removed uses of UOS and SOS. In the code, uses of uos and sos in names were changed to user_vm and service_vm respectively. When specifically referring to the OS of these VMs, we now use user_vm_os and service_vm_os. These changes appear throughout the C files, as well as in the .xml configuration files. For example, here are examples of old and new names:
· Update Scenario Names The pre-defined scenario names were changed to be indicative of their properties instead of an example use. The “industry” scenario is now called “shared”, the “logical partitioning” scenario is now called “partitioned”, and the “hybrid” scenario name remains the same. Here are the three configuration scenarios: § Shared: The physical hardware resources can be shared among post-launched User VMs. The Service VM (Device Model) provides device emulation for the shared virtual devices. § Partitioned: The physical resources are strictly dedicated to individual pre-launched User VMs and there is no Service VM needed. § Hybrid: The physical resource are dedicated to pre-launched User VMs and the Service VM provides resource emulation and sharing for post-launched User VMs, all in the same system configuration. · User-Friendly VM names Instead of using a UUID as the User VM identifier, we’re now using a user-friendly VM name. · Extend Use of CAT Cache Tuning to VMs In previous releases, Cache Allocation Technology (CAT) was available only at the hypervisor level and with per-pCPU granularity. In this v2.7 release, each VM with exclusive cache resources can partition them with per-thread granularity and allocate cache resources to prioritized tasks. · Expand Passthrough Device Use Cases We now allow pre-launched VMs (in partitioned or hybrid scenarios) to use graphics device passthrough for improved performance, a feature previously available to only post-launched VMs. Trusted Platform Module (TPM) 2.0 and its associated resource can now be passthrough to post-launched VMs, a feature previously available to only pre-launched VMs. · Document Updates: We’ve updated references throughout the documentation to use “Service VM” and “User VM” instead of “SOS” and “UOS” respectively. We’ve also made edits throughout the documentation to improve clarity, formatting, and presentation: ² VT-d ² Configuration and Development Overview ² Enable Inter-VM Communication Based on Ivshmem ² Getting Started Guide for ACRN Partitioned Mode See the v2.7 full release notes and documentation for more information about this release including fixed and known issues. Upgrading to v2.7 From Previous ReleasesAll project ACRN source code is maintained in the https://github.com/projectacrn/acrn-hypervisor repository and includes folders for the ACRN hypervisor, the ACRN device model, tools, and documentation. You can download this source code either as a zip or tar.gz file (see the ACRN v2.7 GitHub release page) or use Git clone and checkout commands: git clone https://github.com/projectacrn/acrn-hypervisor cd acrn-hypervisor
git checkout v2.7
The project’s online technical documentation is also tagged to correspond with a specific release: generated v2.7 documents can be found at https://projectacrn.github.io/2.7/. Documentation for the latest development branch is found at https://projectacrn.github.io/latest/. ACRN v2.7 requires Ubuntu 18.04. Follow the instructions in the Getting Started Guide to get started with ACRN.
Best & Regards Terry
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: is ACRN v2.6 supported on intel NUC apollo lake
shibi590268@...
Hello Xiangyang Wu,
Great Thank you for the timely help. Now my user VM runs without any issue. Thank you.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: is ACRN v2.6 supported on intel NUC apollo lake
Wu, Xiangyang
Hi Shibin,
I see error message “vm_get_config: IOCTL first time failed” in your log. In acrn-kernel v2.7, get platform information IOCTL is removed, please use acrn-kernel v2.6, thanks!
BRs, Xiangyang Wu.
From: acrn-users@... <acrn-users@...>
On Behalf Of Liu, Fuzhong
Sent: Wednesday, December 22, 2021 1:29 PM To: acrn-users@... Subject: Re: [acrn-users] is ACRN v2.6 supported on intel NUC apollo lake
TGLNUC is the preferred platform for v2.6.
Anyway, do you refer following guide to update iASL: Install the iASL compiler/disassembler used for advanced power management, device discovery, and configuration (ACPI) within the host OS: 1. mkdir ~/acrn-work 2. cd ~/acrn-work 3. wget https://acpica.org/sites/acpica/files/acpica-unix-20210105.tar.gz 4. tar zxvf acpica-unix-20210105.tar.gz 5. cd acpica-unix-20210105 6. make clean && make iasl sudo cp ./generate/unix/bin/iasl /usr/sbin
BR. Fuzhong From:
acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Hello ACRN, sudo ./launch_uos_id2.sh logger: name=console, level=4 logger: name=kmsg, level=3 logger: name=disk, level=5
SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000 vm_create: post_vm_id2 vm_setup_memory: size=0x20000000 open hugetlbfs file /run/hugepage/acrn/huge_lv1/post_vm_id2/615DB82AE1894B4F8DBBD321343E4AB3 open hugetlbfs file /run/hugepage/acrn/huge_lv2/post_vm_id2/615DB82AE1894B4F8DBBD321343E4AB3 level 0 free/need pages:0/257 page size:0x200000 level 1 free/need pages:4/0 page size:0x40000000 to reserve more free pages: to reserve pages (+orig 0): echo 257 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages now enough free pages are reserved!
try to setup hugepage with: level 0 - lowmem 0x20000000, biosmem 0x200000, highmem 0x0 level 1 - lowmem 0x0, biosmem 0x0, highmem 0x0 total_size 0x100200000
mmap ptr 0x0x7fec2a706000 -> baseaddr 0x0x7fec2a800000 mmap 0x20000000@0x7fec2a800000 touch 256 pages with pagesz 0x200000 mmap 0x200000@0x7fed2a600000 touch 1 pages with pagesz 0x200000
really setup hugepage with: level 0 - lowmem 0x20000000, biosmem 0x200000, highmem 0x0 level 1 - lowmem 0x0, biosmem 0x0, highmem 0x0 vm_init_vdevs No pm notify channel given Listening 0... polling 0... init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR pci init hostbridge pci init lpc pci init virtio-net pci init virtio-console pci init virtio-blk tpm: init_vtpm2:Invalid socket path! vm_get_config: IOCTL first time failed! basl_fwrite_madt, get VM configuration fail. acpi_build failed, error=-1 pci deinit hostbridge pci deinit lpc pci deinit virtio-net vtnet tx thread closing... pci deinit virtio-console pci deinit virtio-blk mngr_client_new: Failed to accept from fd 37, err: Invalid argument Stop listening 37... Stop polling 37... No correct pm notify channel given
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: is ACRN v2.6 supported on intel NUC apollo lake
Liu, Fuzhong
TGLNUC is the preferred platform for v2.6.
Anyway, do you refer following guide to update iASL: Install the iASL compiler/disassembler used for advanced power management, device discovery, and configuration (ACPI) within the host OS: 1. mkdir ~/acrn-work 2. cd ~/acrn-work 3. wget https://acpica.org/sites/acpica/files/acpica-unix-20210105.tar.gz 4. tar zxvf acpica-unix-20210105.tar.gz 5. cd acpica-unix-20210105 6. make clean && make iasl sudo cp ./generate/unix/bin/iasl /usr/sbin
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Sent: Tuesday, December 21, 2021 2:20 PM To: acrn-users@... Subject: [acrn-users] is ACRN v2.6 supported on intel NUC apollo lake
Hello ACRN, sudo ./launch_uos_id2.sh logger: name=console, level=4 logger: name=kmsg, level=3 logger: name=disk, level=5
SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000 vm_create: post_vm_id2 vm_setup_memory: size=0x20000000 open hugetlbfs file /run/hugepage/acrn/huge_lv1/post_vm_id2/615DB82AE1894B4F8DBBD321343E4AB3 open hugetlbfs file /run/hugepage/acrn/huge_lv2/post_vm_id2/615DB82AE1894B4F8DBBD321343E4AB3 level 0 free/need pages:0/257 page size:0x200000 level 1 free/need pages:4/0 page size:0x40000000 to reserve more free pages: to reserve pages (+orig 0): echo 257 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages now enough free pages are reserved!
try to setup hugepage with: level 0 - lowmem 0x20000000, biosmem 0x200000, highmem 0x0 level 1 - lowmem 0x0, biosmem 0x0, highmem 0x0 total_size 0x100200000
mmap ptr 0x0x7fec2a706000 -> baseaddr 0x0x7fec2a800000 mmap 0x20000000@0x7fec2a800000 touch 256 pages with pagesz 0x200000 mmap 0x200000@0x7fed2a600000 touch 1 pages with pagesz 0x200000
really setup hugepage with: level 0 - lowmem 0x20000000, biosmem 0x200000, highmem 0x0 level 1 - lowmem 0x0, biosmem 0x0, highmem 0x0 vm_init_vdevs No pm notify channel given Listening 0... polling 0... init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR init passthru first to reserve PIO BAR pci init hostbridge pci init lpc pci init virtio-net pci init virtio-console pci init virtio-blk tpm: init_vtpm2:Invalid socket path! vm_get_config: IOCTL first time failed! basl_fwrite_madt, get VM configuration fail. acpi_build failed, error=-1 pci deinit hostbridge pci deinit lpc pci deinit virtio-net vtnet tx thread closing... pci deinit virtio-console pci deinit virtio-blk mngr_client_new: Failed to accept from fd 37, err: Invalid argument Stop listening 37... Stop polling 37... No correct pm notify channel given
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Florian Arnold
Hi David,
Yes, it works by padding the ELF image to 1 MB. I tested it yesterday with a clean Ubuntu 20.04 installation without updating GRUB. Best regards Florian
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
is ACRN v2.6 supported on intel NUC apollo lake
shibi590268@...
Hello ACRN,
I am looking for some details regarding using ACRN on intel nuc apollo lake or similar custom hardware which uses intel celeron J series processors. 1. Is the latest version v2.6 supported on this platform? 2. Is hybrid-rt supported on this hardware? 3. My use case is one Ubuntu SOS and ubuntu with RT as pre-launched RT VM. Does it work on this hardware or have to choose latest hardware with i5 core? 4. I tried to build the hypervisor with latest v2.6 version. ACRN ubuntu service OS was running. But while launching the uos i get "vm get config fail error". sudo ./launch_uos_id2.sh
logger: name=console, level=4
logger: name=kmsg, level=3
logger: name=disk, level=5
SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000
vm_create: post_vm_id2
vm_setup_memory: size=0x20000000
open hugetlbfs file /run/hugepage/acrn/huge_lv1/post_vm_id2/615DB82AE1894B4F8DBBD321343E4AB3
open hugetlbfs file /run/hugepage/acrn/huge_lv2/post_vm_id2/615DB82AE1894B4F8DBBD321343E4AB3
level 0 free/need pages:0/257 page size:0x200000
level 1 free/need pages:4/0 page size:0x40000000
to reserve more free pages:
to reserve pages (+orig 0): echo 257 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
now enough free pages are reserved!
try to setup hugepage with:
level 0 - lowmem 0x20000000, biosmem 0x200000, highmem 0x0
level 1 - lowmem 0x0, biosmem 0x0, highmem 0x0
total_size 0x100200000
mmap ptr 0x0x7fec2a706000 -> baseaddr 0x0x7fec2a800000
mmap 0x20000000@0x7fec2a800000
touch 256 pages with pagesz 0x200000
mmap 0x200000@0x7fed2a600000
touch 1 pages with pagesz 0x200000
really setup hugepage with:
level 0 - lowmem 0x20000000, biosmem 0x200000, highmem 0x0
level 1 - lowmem 0x0, biosmem 0x0, highmem 0x0
vm_init_vdevs
No pm notify channel given
Listening 0...
polling 0...
init passthru first to reserve PIO BAR
init passthru first to reserve PIO BAR
init passthru first to reserve PIO BAR
init passthru first to reserve PIO BAR
init passthru first to reserve PIO BAR
pci init hostbridge
pci init lpc
pci init virtio-net
pci init virtio-console
pci init virtio-blk
tpm: init_vtpm2:Invalid socket path!
vm_get_config: IOCTL first time failed!
basl_fwrite_madt, get VM configuration fail.
acpi_build failed, error=-1
pci deinit hostbridge
pci deinit lpc
pci deinit virtio-net
vtnet tx thread closing...
pci deinit virtio-console
pci deinit virtio-blk
mngr_client_new: Failed to accept from fd 37, err: Invalid argument
Stop listening 37...
Stop polling 37...
No correct pm notify channel given
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Thanks for your help with this issue Florian. To confirm, by padding your Zephyr elf image you had no issue using the GRUB that came with Ubuntu 20.04? I want to update the documentation about this but wanted to make sure the instructions we said to build your own GRUB were unnecessary if you just padded the image to 1MB.
Thanks. -- david
From: acrn-users@... <acrn-users@...>
On Behalf Of florian.arnold@...
Sent: Monday, December 20, 2021 6:26 AM To: acrn-users@... Subject: Re: [acrn-users] Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Hi Victor,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Victor Sun
Good to know that.
BR, Victor
From: acrn-users@... <acrn-users@...>
On Behalf Of florian.arnold@...
Sent: Monday, December 20, 2021 10:26 PM To: acrn-users@... Subject: Re: [acrn-users] Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Hi Victor,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Florian Arnold
Hi Victor,
Thanks for your help. With an image larger than 1 MB and Ubuntu 20.04 everything works fine. Best regards, Florian
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Florian Arnold
Hi Fuzhong,
Thanks for your quick response. I rebuilt grub. I tested Version 2.06 and 2.11 but I got the same error as before for both versions. I checked that the mentioned commit is included in both versions. However, if I use a zephyr image that is larger than 1 MB I can boot without any problems. So for a real-world example that contains more code than 'Hello World' it shouldn't be an issue. Best regards Florian
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Victor Sun
Hi Florian, Besides rebuilding GRUB, you also need padding your Zephyr elf file to 1MB as we don’t support pre-launched VM OS image less than 1MB. You can use below method: dd if=zephyr.elf ibs=1M count=1 of=zephyr_new.elf conv=sync
With the new GRUB and the new zephyr_new.elf, you should be able run Zephyr as pre-launched ACRN VM. Please let us know your test result, thanks!
BR, Victor
From: acrn-users@... <acrn-users@...>
On Behalf Of Liu, Fuzhong
Sent: Friday, December 17, 2021 9:56 AM To: acrn-users@... Subject: Re: [acrn-users] Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Hi Florian, As Victor mentioned; please refer following guide to rebuild grub: https://projectacrn.github.io/latest/tutorials/using_grub.html#installing-self-built-grub
And make sure below commit is included:
Thanks!
BR. Fuzhong From:
acrn-users@... <acrn-users@...>
On Behalf Of Victor Sun
Hi Florian,
The log shows your GRUB put the module at HPA 0, which ACRN doesn’t support. Please try GRUB of Ubuntu 20.04, or rebuild a new GRUB by yourself.
[21602370us][cpu=3][(null)][sev=3][seq=27]:Unsupported module: start at HPA 0, size 0x7e998
You can refer source code at acrn-hypervisor/hypervisor/boot/guest/vboot_info.c: /* GRUB might put module at address 0 or under 1MB in the case that the module size is less then 1MB * ACRN will not support these cases */ if ((mod != NULL) && (mod->start == NULL)) { pr_err("Unsupported module: start at HPA 0, size 0x%x .", mod->size); mod = NULL; }
BR, Victor
From:
acrn-users@... <acrn-users@...>
On Behalf Of florian.arnold@...
Hi everyone,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Liu, Fuzhong
Hi Florian, As Victor mentioned; please refer following guide to rebuild grub: https://projectacrn.github.io/latest/tutorials/using_grub.html#installing-self-built-grub
And make sure below commit is included:
Thanks!
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of Victor Sun
Sent: Thursday, December 16, 2021 11:31 PM To: acrn-users@... Subject: Re: [acrn-users] Hybrid-Scenario: Pre-launched Zephyr-VM failed to load kernel module
Hi Florian,
The log shows your GRUB put the module at HPA 0, which ACRN doesn’t support. Please try GRUB of Ubuntu 20.04, or rebuild a new GRUB by yourself.
[21602370us][cpu=3][(null)][sev=3][seq=27]:Unsupported module: start at HPA 0, size 0x7e998
You can refer source code at acrn-hypervisor/hypervisor/boot/guest/vboot_info.c: /* GRUB might put module at address 0 or under 1MB in the case that the module size is less then 1MB * ACRN will not support these cases */ if ((mod != NULL) && (mod->start == NULL)) { pr_err("Unsupported module: start at HPA 0, size 0x%x .", mod->size); mod = NULL; }
BR, Victor
From:
acrn-users@... <acrn-users@...>
On Behalf Of florian.arnold@...
Hi everyone,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|