mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-31 03:15:42 +00:00
54975e4629
ACRN 2.1 supports two virtual boot modes, deprivilege boot mode and direct boot mode. The deprivilege boot mode’s main purpose is to support booting Clear Linux Service VM with UEFI service support, but this brings scalability problems when porting ACRN to new Intel platforms. For the 2.2 release, deprivilege mode is removed, and only direct boot is supported, and with this we've removed support for Clear Linux as the service VM, which impacts over 50 ACRN documents. This PR removes documents we don't intend to update, and fixes broken links that would occur from references to these deleted docs. Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
172 lines
5.0 KiB
ReStructuredText
172 lines
5.0 KiB
ReStructuredText
.. _gpu-passthrough:
|
|
|
|
Enable GVT-d in ACRN
|
|
####################
|
|
|
|
This tutorial describes how to enable GVT-d in ACRN.
|
|
|
|
.. note:: After GVT-d is enabled, have either a serial port
|
|
or SSH session open in the Service VM to be able to
|
|
continue interact with it.
|
|
|
|
Introduction
|
|
************
|
|
|
|
Intel GVT-d is a graphics virtualization approach that is also known as
|
|
the Intel-Graphics-Device passthrough feature. Based on Intel VT-d
|
|
technology, it offers useful special graphics-related configurations.
|
|
It allows for direct assignment of an entire GPU's prowess to a single
|
|
user, passing the native driver capabilities through to the hypervisor
|
|
without any limitations.
|
|
|
|
Verified version
|
|
*****************
|
|
|
|
- ACRN-hypervisor tag: **acrn-2020w17.4-140000p**
|
|
- ACRN-Kernel (Service VM kernel): **master** branch, commit id **095509221660daf82584ebdd8c50ea0078da3c2d**
|
|
- ACRN-EDK2 (OVMF): **ovmf-acrn** branch, commit id **0ff86f6b9a3500e4c7ea0c1064e77d98e9745947**
|
|
|
|
Prerequisites
|
|
*************
|
|
|
|
Follow :ref:`these instructions <rt_industry_ubuntu_setup>` to set up
|
|
Ubuntu as the ACRN Service VM.
|
|
|
|
Supported hardware platform
|
|
***************************
|
|
|
|
Currently, ACRN has enabled GVT-d on the following platforms:
|
|
|
|
* Kaby Lake
|
|
* Whiskey Lake
|
|
* Elkhart Lake
|
|
|
|
BIOS settings
|
|
*************
|
|
|
|
Kaby Lake platform
|
|
==================
|
|
|
|
* Set **IGD Minimum Memory** to **64MB** in **Devices** →
|
|
**Video** → **IGD Minimum Memory**.
|
|
|
|
Whiskey Lake platform
|
|
=====================
|
|
|
|
* Set **PM Support** to **Enabled** in **Chipset** → **System
|
|
Agent (SA) Configuration** → **Graphics Configuration** →
|
|
**PM support**.
|
|
* Set **DVMT Pre-Allocated** to **64MB** in **Chipset** →
|
|
**System Agent (SA) Configuration**
|
|
→ **Graphics Configuration** → **DVMT Pre-Allocated**.
|
|
|
|
Elkhart Lake platform
|
|
=====================
|
|
|
|
* Set **DMVT Pre-Allocated** to **64MB** in **Intel Advanced Menu**
|
|
→ **System Agent(SA) Configuration** →
|
|
**Graphics Configuration** → **DMVT Pre-Allocated**.
|
|
|
|
Passthrough the GPU to Guest
|
|
****************************
|
|
|
|
1. Copy ``/usr/share/acrn/samples/nuc/launch_win.sh`` to ``install_win.sh``
|
|
|
|
::
|
|
|
|
cp /usr/share/acrn/samples/nuc/launch_win.sh ~/install_win.sh
|
|
|
|
2. Modify the ``install_win.sh`` script to specify the Windows image you use.
|
|
|
|
3. Modify the ``install_win.sh`` script to enable GVT-d:
|
|
|
|
Add the following commands before ``acrn-dm -A -m $mem_size -s 0:0,hostbridge \``
|
|
|
|
::
|
|
|
|
gpudevice=`cat /sys/bus/pci/devices/0000:00:02.0/device`
|
|
|
|
echo "8086 $gpudevice" > /sys/bus/pci/drivers/pci-stub/new_id
|
|
echo "0000:00:02.0" > /sys/bus/pci/devices/0000:00:02.0/driver/unbind
|
|
echo "0000:00:02.0" > /sys/bus/pci/drivers/pci-stub/bind
|
|
|
|
Replace ``-s 2,pci-gvt -G "$2" \`` with ``-s 2,passthru,0/2/0,gpu \``
|
|
|
|
4. Run ``launch_win.sh``.
|
|
|
|
.. note:: If you want to passthrough the GPU to a Clear Linux User VM, the
|
|
steps are the same as above except your script.
|
|
|
|
Enable the GVT-d GOP driver
|
|
***************************
|
|
|
|
When enabling GVT-d, the Guest OS cannot light up the physical screen
|
|
before the OS driver loads. As a result, the Guest BIOS and the Grub UI
|
|
is not visible on the physical screen. The occurs because the physical
|
|
display is initialized by the GOP driver or VBIOS before the OS driver
|
|
loads, and the Guest BIOS doesn't have them.
|
|
|
|
The solution is to integrate the GOP driver binary into the OVMF as a DXE
|
|
driver. Then the Guest OVMF can see the GOP driver and run it in the graphic
|
|
passthrough environment. The physical display can be initialized
|
|
by the GOP and used by the Guest BIOS and Guest Grub.
|
|
|
|
Steps
|
|
=====
|
|
|
|
1. Fetch the ACRN OVMF:
|
|
|
|
::
|
|
|
|
git clone https://github.com/projectacrn/acrn-edk2.git
|
|
|
|
#. Fetch the vbt and gop drivers.
|
|
|
|
Fetch the **vbt** and **gop** drivers from the board manufacturer
|
|
according to your CPU model name.
|
|
|
|
#. Add the **vbt** and **gop** drivers to the OVMF:
|
|
|
|
::
|
|
|
|
cp IntelGopDriver.efi acrn-edk2/OvmfPkg/IntelGop/IntelGopDriver.efi
|
|
cp Vbt.bin acrn-edk2/OvmfPkg/Vbt/Vbt.bin
|
|
|
|
Confirm that these binaries names match the board manufacturer names.
|
|
|
|
#. Git apply the following two patches:
|
|
|
|
* `Use-the-default-vbt-released-with-GOP-driver.patch <../_static/downloads/Use-the-default-vbt-released-with-GOP-driver.patch>`_
|
|
|
|
* `Integrate-IntelGopDriver-into-OVMF.patch <../_static/downloads/Integrate-IntelGopDriver-into-OVMF.patch>`_
|
|
|
|
#. Compile the OVMF:
|
|
|
|
::
|
|
|
|
cd acrn-edk2
|
|
git submodule update --init CryptoPkg/Library/OpensslLib/openssl
|
|
|
|
source edksetup.sh
|
|
make -C BaseTools
|
|
|
|
vim Conf/target.txt
|
|
|
|
ACTIVE_PLATFORM = OvmfPkg/OvmfPkgX64.dsc
|
|
TARGET_ARCH = X64
|
|
TOOL_CHAIN_TAG = GCC5
|
|
|
|
build -DFD_SIZE_2MB -DDEBUG_ON_SERIAL_PORT=TRUE
|
|
|
|
Keep in mind the following:
|
|
|
|
- Use a build machine that has GCC 5.X version installed.
|
|
|
|
- The ``source edksetup.sh`` step is needed for compilation every time
|
|
a shell is created.
|
|
|
|
- This will generate the binary at
|
|
``Build/OvmfX64/DEBUG_GCC5/FV/OVMF.fd``. Transfer the binary to
|
|
your target machine.
|
|
- Modify the launch script to specify the OVMF you built just now.
|