patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <alyssa.ross@unikie.com>
To: Vadim Likholetov <vadim.likholetov@unikie.com>
Cc: devel@spectrum-os.org
Subject: Re: Enabling forwarding Wayland from appVM to host with waypipe
Date: Wed, 30 Nov 2022 08:51:09 +0000	[thread overview]
Message-ID: <20221130085109.wkcwpr54roqvhe4l@x220> (raw)
In-Reply-To: <CALSVioDK-azWsHZ1fkjUSR08KCrpsiCcLni9FFf8_bMTbwOXKA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]

On Wed, Nov 30, 2022 at 09:12:50AM +0200, Vadim Likholetov wrote:
> This patchset enables forwarding Wayland connections from appVM to the host
> with the help of waypipe tool.
>
> It doesn't reqire major changes in Spectrum and tries to utilise existing
> packages and solutions.
> Main idea is to create VSOCK virtual device on the start of appVM and use
> this virtual socket to connect host and guest.
>
> On the host side I implement vm-start-way tool that is based on vm-start,
> but does necessary preparations for wayland forwarfing.
>
> The guest VM is appvm-hello-waypipe and described in  hello-waypipe.nix
> file.
>
> To test it boot the Spectrum and do 'vm-start-way appvm-hello-waypipe'.
> Be patient and in couple of seconds will appear a terminal window from
> appVM.
>
> This patches are for test the concept, so possibly redisign is needed for
> production use.

Thanks for sharing these!

You've done a great job fitting it into the Spectrum codebase.

Since you mentioned in your previous email that the same applications
are broken with Waypipe and virtio-gpu, I think that virtio-gpu still
looks like the way to go, since it would allow optimisations like shared
memory between guest and host that wouldn't be possible with a pure
socket-based approach like Waypipe.

But lots of people come to Spectrum looking for advice and inspiration for
their own custom Wayland-in-VM setups, and often they're more interested in
Waypipe, so it'll be great to be able to point them here.

> ps sorry for mess in the mailing list

No worries. :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-30  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  7:12 Enabling forwarding Wayland from appVM to host with waypipe Vadim Likholetov
2022-11-30  8:51 ` Alyssa Ross [this message]
2022-11-30 10:14   ` Vadim Likholetov
2022-11-30 10:24     ` Alyssa Ross
2022-11-30 10:32       ` Vadim Likholetov
2022-11-30 11:29         ` Alyssa Ross
2022-11-30 13:12           ` Vadim Likholetov
2022-11-30 14:21             ` Alyssa Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221130085109.wkcwpr54roqvhe4l@x220 \
    --to=alyssa.ross@unikie.com \
    --cc=devel@spectrum-os.org \
    --cc=vadim.likholetov@unikie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).