[PATCH wiki] Some updates for GVTg_Setup_guide.md.
Terrence Xu
terrence.xu at intel.com
Mon Apr 10 13:29:49 UTC 2017
1. update the latest Windows GFX driver version.
2. update the vgpu type descriptions.
3. update the known issue for secondary GFX card in Windows VM.
4. fix some typos.
Signed-off-by: Terrence Xu <terrence.xu at intel.com>
---
GVTg_Setup_Guide.md | 37 +++++++++++++++++++++----------------
1 file changed, 21 insertions(+), 16 deletions(-)
diff --git a/GVTg_Setup_Guide.md b/GVTg_Setup_Guide.md
index 8ee10f4..ade9356 100644
--- a/GVTg_Setup_Guide.md
+++ b/GVTg_Setup_Guide.md
@@ -194,7 +194,7 @@ BTW: The PCI ID was chose by the "lspci".
> 00:04.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 0a)
-NOTICE: after you changed the display card to Intel GFX card, Qemu will comes to black screen, you only can see guest desktop by remote protocal.
+NOTICE: After you changed the display card to Intel GFX card, Qemu will comes to black screen, you only can see guest desktop by remote protocal.
### 4.1.3 Linux Remote Protocol Support ###
We suggest to use the X11VNC as the remote protocol to validation.
@@ -225,27 +225,28 @@ After you completed the lightdm configuration, you can run the X11VNC service in
Then connect guest by host with guest X support by:
-> vncviewer <guestIP>
+> vncviewer $guestIP
-NOTICE: after you changed the display card to Intel GFX card, Qemu will comes to black screen, you only can see guest desktop by remote protocol.
+NOTICE: After you changed the display card to Intel GFX card, Qemu will comes to black screen, you only can see guest desktop by remote protocol.
## 4.2 Windows Guest Setup ##
### 4.2.1 Windows Version Support
Win7-32 / Win7-64 / Win8.1-64 /Win10-RS1-64 are validated.
### 4.2.2 Windows GFX Driver Support ###
-After you boot up Windows guest, you can see 2 GFX card in "Device manager" (One is the virtual GFX card "QXL" or "Cirrus", the other is Intel GFX card), then you must install the Intel GFX Windows for the Intel GFX card to support OpenCL / OpenGL / DirectX9 / DirectX10/ DirectX11 / DirectX12 hardware acceleration .
+After you boot up Windows guest, you can see 2 GFX card in "Device manager" (One is the virtual GFX card "QXL" or "Cirrus", the other is Intel GFX card), then you must install the Intel GFX driver for the Intel GFX card to support OpenCL / OpenGL / DirectX9 / DirectX10/ DirectX11 / DirectX12 hardware acceleration .
You can get the Windows driver from Intel website: https://downloadcenter.intel.com/product/80939/Graphics-Drivers
- Skylake: >= 15.45.14.4590
- Broadwell: The driver has been published, will coming soon.
-NOTICE: after you installed Windows GFX driver, you can see guest desktop by both QEMU and remote protocal.
+ Skylake: 15.45.16.4627
+ Broadwell: 15.40.34.4624
+
+NOTICE: After you installed Windows GFX driver, you can see guest desktop by both QEMU and remote protocol. QEMU display the emulated driver and the remote protocol display the Intel GFX driver. BTW, There is a known issue that some 3D workload cannot run with hardware acceleration while both GFX card is available, so suggest to disable the emulated GFX card in "Device Manager" after you make sure the Intel GFX card is working.
### 4.2.3 Windows Remote Protocol Support ###
All Windows Remote protocol are supported, such as TightVNC, HP RGS, RDP.
-"Tightvnc" is validated, so you can install the "Tightvnc" in Windows guest, and you can connect guest by host with guest X support by:
+"Tightvnc" is validated, so you can install the "Tightvnc" in Windows guest, and you can connect guest by host with guest X support by:
-> vncviewer <guestIP>
+> vncviewer $guestIP
# 5 Basic usage #
## 5.1 Check mdev Module ##
@@ -254,15 +255,17 @@ After you boot up you host to GVT-g menuentry, you make sure the "mdev_supported
> total 0
-> drwxr-xr-x 5 root root 0 Apr 16 21:24 ./
+> drwxr-xr-x 5 root root 0 Apr 10 21:24 ./
+
+> drwxr-xr-x 12 root root 0 Apr 10 20:04 ../
-> drwxr-xr-x 12 root root 0 Apr 16 20:04 ../
+> drwxr-xr-x 3 root root 0 Apr 10 21:24 i915-GVTg_V4_1/ $ This node with low_gm_size=512MB, high_gm_size=2048MB, fense=4, resolution=1920x1200
-> drwxr-xr-x 3 root root 0 Apr 16 21:24 i915-GVTg_V4_1/ # This node max support 1 VM
+> drwxr-xr-x 3 root root 0 Apr 10 21:24 i915-GVTg_V4_2/ # This node with low_gm_size=256MB, high_gm_size=1024MB, fense=4, resolution=1920x1200
-> drwxr-xr-x 3 root root 0 Apr 16 21:24 i915-GVTg_V4_2/ # This node max support 2 VMs
+> drwxr-xr-x 3 root root 0 Apr 10 21:24 i915-GVTg_V4_4/ # This node with low_gm_size=128MB, high_gm_size=512MB, fense=4, resolution=1920x1200
-> drwxr-xr-x 3 root root 0 Apr 16 21:24 i915-GVTg_V4_4/ # This node max support 4 VMs
+> drwxr-xr-x 3 root root 0 Apr 10 21:24 i915-GVTg_V4_8/ # This node with low_gm_size=64MB, high_gm_size=512MB, fense=4, resolution=1024x768
And you can check the detail description for each vgpu type,
@@ -274,6 +277,8 @@ And you can check the detail description for each vgpu type,
> fence: 4
+> resolution: 1920x1200
+
## 5.2 Generate the uuid for create VGPU ##
Use Ubuntu as example, you can use the third-party tool to generate uuid like "uuid", "uuidgen", if we need to create 3 VM, we must create 3 uuid for 3 VGPU, like below:
> root at gvtg-host:~# uuid -n 3
@@ -326,7 +331,7 @@ We sugguest to use the secondary gfx card mode (virtual "qxl" or "cirrus" gfx ca
-machine kernel_irqchip=on \
-global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 \
-cpu host -usb -usbdevice tablet \
- -device vfio-pci,sysfsdev=/sys/bus/pci/devices/0000:00:02.0/a297db4a-f4c2-11e6-90f6-d3b88d6c9525
+ -device vfio-pci,sysfsdev=/sys/bus/pci/devices/0000:00:02.0/a297db4a-f4c2-11e6-90f6-d3b88d6c9525,rombar=0
# 6 Features Supported #
@@ -355,4 +360,4 @@ We sugguest to use the secondary gfx card mode (virtual "qxl" or "cirrus" gfx ca
- Media:
* Multiple thread decode/transcode for JPEG, MPEG2, H264, HEVC, VC1, VP8, etc
- OpenCL:
- * LuxMark, Beignet
+ * LuxMark, Beignet
\ No newline at end of file
--
2.7.4
More information about the intel-gvt-dev
mailing list