[gnome-boxes.wiki] Create 3daccel
- From: Felipe Borges <felipeborges src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-boxes.wiki] Create 3daccel
- Date: Mon, 15 Apr 2019 09:21:46 +0000 (UTC)
commit 42671dc99324349f1d2645800d25657df3281039
Author: Felipe Borges <felipeborges gnome org>
Date: Mon Apr 15 09:21:41 2019 +0000
Create 3daccel
3daccel.md | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
---
diff --git a/3daccel.md b/3daccel.md
new file mode 100644
index 0000000..9033a79
--- /dev/null
+++ b/3daccel.md
@@ -0,0 +1,16 @@
+# 3D Acceleration
+
+The Boxes 3D acceleration feature for guest is powered by [virlgrenderer](https://virgil3d.github.io/).
+
+We have gotten a few bug reports after auto-enabling 3D acceleration for all guests that libosinfo reports
to support virtio-gpu.
+
+https://github.com/flathub/org.gnome.Boxes/issues/22
+https://gitlab.gnome.org/GNOME/gnome-boxes/issues/324
+https://gitlab.gnome.org/GNOME/gnome-boxes/issues/341
+
+The way it is implemented NOW is that we try to enable 3D acceleration by default for all guests that
support virtio-gpu and we offer a toggle option in the VM properties to disable that in case of issues. This
setting is saved in the VM's keyfile, under the **3daccel** property.
+
+The UX logic is:
+* If the "3daccel" flag is not set, we throw a notification offering the user to disable 3D acceleration in
case they are having issues. Once the user interacts with the notification, the keyfile is written:
+ - if the notification is dismissed, 3daccel = true
+ - if the user clicks "Disable", 3daccel = false
\ No newline at end of file
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]