Kusanaginoturugi: /* QXL ビデオドライバーと SPICE クライアント表示 */ 空白追加

2024-06-04T00:53:11Z

QXL ビデオドライバーと SPICE クライアント表示: 空白追加

← 古い版		2024年6月4日 (火) 09:53時点における版
10行目:		10行目:
	== QXL ビデオドライバーと SPICE クライアント表示 ==		== QXL ビデオドライバーと SPICE クライアント表示 ==

	[[QEMU#qxl\|QXL/SPICE]]は高性能な表示方法です。しかし、ベアメタルに近い性能を提供するようには設計されていません。		[[QEMU#qxl\|QXL/SPICE]] は高性能な表示方法です。しかし、ベアメタルに近い性能を提供するようには設計されていません。

	== PCI GPU passthrough ==		== PCI GPU passthrough ==

Kusanaginoturugi: /* QXL ビデオドライバーと SPICE クライアント表示 */ [ 抜け

2024-06-04T00:52:32Z

QXL ビデオドライバーと SPICE クライアント表示: [ 抜け

← 古い版		2024年6月4日 (火) 09:52時点における版
10行目:		10行目:
	== QXL ビデオドライバーと SPICE クライアント表示 ==		== QXL ビデオドライバーと SPICE クライアント表示 ==

	[QEMU#qxl\|QXL/SPICE]]は高性能な表示方法です。しかし、ベアメタルに近い性能を提供するようには設計されていません。		[[QEMU#qxl\|QXL/SPICE]]は高性能な表示方法です。しかし、ベアメタルに近い性能を提供するようには設計されていません。

	== PCI GPU passthrough ==		== PCI GPU passthrough ==

Kusanaginoturugi: 一部飜訳

2024-06-04T00:52:07Z

一部飜訳

← 古い版		2024年6月4日 (火) 09:52時点における版
6行目:		6行目:
	{{Related\|KVM}}		{{Related\|KVM}}
	{{Related articles end}}		{{Related articles end}}
			仮想マシンのグラフィックス表示には、大幅に高速化された、あるいはベアメタルに近いパフォーマンスを実現する複数の方法があります。
	There are multiple methods for virtual machine graphics display which yield greatly accelerated or near bare metal performance.

	== QXL ~~video driver and~~ SPICE ~~client for display~~ ==		== QXL ビデオドライバーと SPICE クライアント表示 ==

			[QEMU#qxl\|QXL/SPICE]]は高性能な表示方法です。しかし、ベアメタルに近い性能を提供するようには設計されていません。
	[[QEMU#qxl\|QXL/SPICE]] is a high-performance display method. However, it is not designed to offer near-bare metal performance.

	== PCI GPU passthrough ==		== PCI GPU passthrough ==

Kusanaginoturugi: 英語版より転載

2024-05-30T11:50:11Z

英語版より転載

新規ページ

[[Category:仮想化]]
[[Category:エミュレーション]]
{{Related articles start}}
{{Related|OVMF による PCI パススルー}}
{{Related|QEMU}}
{{Related|KVM}}
{{Related articles end}}
There are multiple methods for virtual machine graphics display which yield greatly accelerated or near bare metal performance.

== QXL video driver and SPICE client for display ==

[[QEMU#qxl|QXL/SPICE]] is a high-performance display method. However, it is not designed to offer near-bare metal performance.

== PCI GPU passthrough ==

=== PCI VGA/GPU passthrough via OVMF ===

[[OVMF による PCI パススルー|PCI passthrough]] currently seems to be the most popular method for optimal performance. [https://bbs.archlinux.org/viewtopic.php?id=162768&p=1 This forum thread] (now closed, and may be outdated) may be of interest for problem solving. You can use kvm switch to control desktops.

=== Single GPU passthrough ===

Currently, [[OVMF による PCI パススルー|PCI passthrough]] works for dual-graphic cards only. However, there is a [https://gitlab.com/risingprismtv/single-gpu-passthrough/-/wikis/1)-Preparations workaround] for passing a single graphic card. The problem with this approach is that you have to detach the graphics card from the host and use ssh to control the host from the guest.

When you start the virtual machine, all your GUI apps will be force terminated. However, as a workaround, you can use [[Xpra]] to detach to another Display before starting the virtual machine and reattach the Apps to display after shutting down the virtual machine.

If you have [[NVIDIA]] GPU, you may need to dump your GPU's vBIOS using {{AUR|nvflash}} and patch it using [https://github.com/Matoking/NVIDIA-vBIOS-VFIO-Patcher vBIOS Patcher].

=== Looking Glass ===

There is a fairly recent passthrough method called [https://looking-glass.hostfission.com/ Looking Glass]. See [https://forum.level1techs.com/t/looking-glass-guides-help-and-support/122387 this guide to getting started] which provides some problem solving and user support. Looking Glass uses DXGI (MS DirectX Graphics Infrastructure) to pass complete frames captured from the virtual machine's passed-through video card via shared memory to the host system where they are read (scraped) by a display client running on the bare-metal host.

== GPU virtualization ==

=== LIBVF.IO ===

[https://github.com/Arc-Compute/libvf.io LibVF.IO] is a Virtualization Framework (Libvirt's alternative) for simplifying the GPU Virtualization. It supports Intel (Intel GVT-g, SR-IOV), NVIDIA (NVIDIA vGPU, SR-IOV) and AMD (AMD SR-IOV). You have to create YAML configurations for each virtual machine. Currently, Intel and NVIDIA GPUs are tested, with limited support for AMD. You can follow this [https://arccompute.com/blog/libvfio-commodity-gpu-multiplexing/ setup guide]. You can also check their [https://open-iov.org/index.php/Articles Wiki]. For NVIDIA GPU, you need to unlock vGPU which can be done by installing {{AUR|nvidia-merged-dkms}}{{Broken package link|package not found}} or [https://github.com/rupansh/vgpu_unlock_5.12#merged-driver-notes building it yourself] and putting it in LIBVF.IO's Optional Folder.

There is also LIME (''L''IME ''I''s ''M''ediated ''E''mulation) for executing Windows programs in Linux.

This framework was [https://www.youtube.com/watch?v=wqUjukaTqEg tested for gaming]. By default, LibVF.IO uses Looking Glass as Virtual Display but you can change that through YAML configuration.

{{Tip|In case you have Ryzen CPU, You have to enable ignore_msrs to avoid Windows BSOD. Always double check your guest driver version. For Nvidia GPU, make sure nvidia-vgpud and nvidia-vgpu-mgr services are running!}}

=== NVIDIA vGPU ===

By default, NVIDIA disabled the vGPU for consumer series (if you own an enterprise card [https://documentation.suse.com/sles/15-SP3/html/SLES-all/article-nvidia-vgpu.html go ahead]). However, you can [https://krutavshah.github.io/GPU_Virtualization-Wiki/overview.html unlock vGPU] for your consumer card.

You will also need a [https://www.nvidia.com/en-us/data-center/resources/vgpu-evaluation/ vGPU license], though there are some [https://github.com/DualCoder/vgpu_unlock/issues/94#issuecomment-1072870857 workarounds].

Follow [https://github.com/tuh8888/libvirt_win10_vm this guide] to manually setup a Windows 10 guest with NVIDIA vGPU.

=== SR-IOV ===

''S''ingle ''R''oot ''I/O'' ''V''irtualization is under development by Intel and NVIDIA New GPU Series. There are some AMD GPUs that support this technology such as [https://forum.level1techs.com/t/how-to-sr-iov-mod-the-w7100-gpu the W7100].

Intel GPUs based on [[Wikipedia:Intel Xe|Xe architecture]] and newer also support SR-IOV. However, the mainline Linux kernel does not yet support the feature, and you will have to install a [https://github.com/intel/linux-intel-lts/tree/lts-v5.15.49-adl-linux-220826T092047Z custom kernel] from Intel. There is also an i915 [[DKMS]] kernel module {{AUR|i915-sriov-dkms-git}} to simplify the process.

* For Linux guests you will have to have the supporting i915 module installed using either the [https://github.com/intel/linux-intel-lts/tree/6.1/linux intel-lts] kernel or i915-sriov-dkms-git.
* For Windows guests you must install the latest drivers and set the hypervisor's vendor ID to {{ic|GenuineIntel}}.

=== Intel-specific iGVT-g extension ===

iGVT-g is limited to integrated Intel graphics on past Intel CPUs (starting from Broadwell and ending with Comet Lake). This is a "software workaround" for older iGPUs that do not support SR-IOV [https://www.reddit.com/r/VFIO/comments/q9noan/comment/hgxlqch/?utm_source=share&utm_medium=web2x&context=3]. Newer Intel iGPUs can use SR-IOV instead. For more information, see [[Intel GVT-g]].

== Virgil3d virtio-gpu paravirtualized device driver ==

[https://docs.mesa3d.org/drivers/virgl.html] virtio-gpu is a paravirtualized 3d accelerated graphics driver, similar to [[QEMU#Installing virtio drivers|non-graphics virtio drivers]] (see [https://www.linux-kvm.org/page/Virtio virtio driver information] and [https://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers virtio Windows guest drivers]). For Linux guests, [[QEMU#virtio|virtio-gpu]] is fairly mature, having been available since Linux kernel version 4.4 and QEMU version 2.6. See [https://www.reddit.com/r/archlinux/comments/7nmceg/kvmqemu_with_virtiogpu_virgl_support_enabled/ this Reddit Arch thread] and [https://www.kraxel.org/blog/2016/09/using-virtio-gpu-with-libvirt-and-spice/ Gerd Hoffmann's blog for using this with libvirt and spice].

For Windows guests, there's currently an active work in progress on [https://github.com/virtio-win/kvm-guest-drivers-windows/pull/943 a fully functional OpenGL and Direct3D10 driver] on the main GitHub repo's pull request. There's also [https://lists.freedesktop.org/archives/virglrenderer-devel/2021-January/001897.html a report that Red Hat also previously worked on the OpenGL driver], including [https://gist.github.com/Keenuts/199184f9a6d7a68d9a62cf0011147c0b the project summary] but abandoned it soon after. Other drivers include [https://gitlab.com/spice/win32/virtio-gpu-wddm-dod the DOD (Windows kernel) driver] and [https://github.com/Keenuts/virtio-gpu-win-icd the ICD (Windows userland) driver] are available. In addition, see [https://www.phoronix.com/scan.php?page=news_item&px=QEMU-3D-Windows-Guests this Phoronix article] and its comments.

QEMU/ゲストグラフィックアクセラレーション - 版の履歴

Kusanaginoturugi: /* QXL ビデオドライバーと SPICE クライアント表示 */ 空白追加

Kusanaginoturugi: /* QXL ビデオドライバーと SPICE クライアント表示 */ [ 抜け

Kusanaginoturugi: 一部飜訳

Kusanaginoturugi: 英語版より転載