Wayland proxying implemention?

[C Liu]

https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3054321

vm_tools/sommelier: feature-complete virtgpu based Wayland proxying This implements Wayland proxying via the technique described here:

  goto.google.com/virtio-gpu-wayland-context 

 The kernel tree is found here: 

  https://gitlab.freedesktop.org/virgl/drm-misc-next/-/commits/context-init

could any one tell me how to donwload the following technique document?

goto.google.com/virtio-gpu-wayland-context

It seems that only google employees have access to this link

[Hakatit]

This is the best resource i can find. https://chromium.googlesource.com/chromium/src/+/master/docs/ozone_overview.md

I know tht for the most part the move was to stack Aura on ozone which then communicated directly to the DRM/KVM hardware module. This was the push for hardware acceleration while moving away from X. 

[Gurchetan Singh]

Hi!

It's actually a bit difficult to share documents with non-Googlers.  However, the implementation of wayland proxying is indeed open-source and you can find details on how to run it on standard Linux distro at:

https://crosvm.dev/book/

https://crosvm.dev/book/devices/wayland.html

 

It seems that only google employees have access to this link

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss

[Cong Liu]

thanks for your reponse,

following the crosvm document, I run it with ubuntu22.04 Host + ubuntu 22.04 guest, it success to run gedit/weston-terminal
(sommelier --virtgpu-channel gedit)in guest, but failed when run 3d app such as glmark2-wayland.

my setup:

on host,  build crosvm and run with the exist qcow2 images, on the guest, I only upgrade the ubuntu guest kernel to  5.18.19 and compile sommelier.

cargo build --features "gpu,virgl_renderer,virgl_renderer_next,x"

sudo ./target/debug/crosvm run --cpus 4 --mem 4096 -disable-sandbox -rwdisk ubuntu22.04.qcow2 --initrd initrd.img-5.18.19-051819-generic     --tap-name crosvm_tap     --gpu backend=virglrenderer,egl=true,glx=true,gles=false,udmabuf=true,context-types=virgl:virgl2:cross-domain --wayland-sock $XDG_RUNTIME_DIR/wayland-0  --display-window-keyboard  --display-window-mouse -p "root=/dev/vda2" vmlinuz-5.18.19-051819-generic
---------------


liucong@liucong:~$ sudo dmesg | grep drm
[sudo] password for liucong:
[    6.039605] systemd[1]: Starting Load Kernel Module drm...
[    6.692246] ACPI: bus type drm_connector registered
[   11.923927] [drm] pci: virtio-gpu-pci detected at 0000:00:04.0
[   11.924215] [drm] Host memory window: 0x400000000 +0x200000000
[   11.924216] [drm] features: +virgl +edid +resource_blob +host_visible
[   11.924217] [drm] features: +context_init
[   11.926370] [drm] number of scanouts: 1
[   11.926380] [drm] number of cap sets: 3
[   12.025579] [drm] cap set 0: id 1, max-version 1, max-size 308
[   12.025710] [drm] cap set 1: id 2, max-version 2, max-size 1376
[   12.025902] [drm] cap set 2: id 5, max-version 0, max-size 16
[   12.026472] [drm] Initialized virtio_gpu 0.1.0 0 for virtio3 on minor 0
[   12.028106] virtio_gpu virtio3: [drm] drm_plane_enable_fb_damage_clips() not called
[   12.031302] virtio_gpu virtio3: [drm] fb0: virtio_gpudrmfb frame buffer device

....
$ sommelier --virtgpu-channel glmark2-wayland
=======================================================
    glmark2 2021.02
=======================================================
    OpenGL Information
    GL_VENDOR:     Mesa/X.org
    GL_RENDERER:   virgl (Mesa Intel(R) UHD Graphics 630 (CFL GT2))
    GL_VERSION:    4.5 (Compatibility Profile) Mesa 22.3.0-devel (git-647773a094)
=======================================================
[build] use-vbo=false:
[   36.885360] [drm:virtio_gpu_dequeue_ctrl_func [virtio_gpu]] *ERROR* response 0x1200 (command 0x207)
wl_display@1: error 1: invalid arguments for wl_di...@1.sync
 FPS: 506 FrameTime: 1.976 ms