From: Vadim Likholetov <vadim.likholetov@unikie.com>
To: Alyssa Ross <alyssa.ross@unikie.com>
Cc: devel@spectrum-os.org
Subject: Re: Enabling forwarding Wayland from appVM to host with waypipe
Date: Wed, 30 Nov 2022 12:32:28 +0200 [thread overview]
Message-ID: <CALSVioAF00-0eapCuCFFUhpMgcrosmf8Hc39Qt5cb3ai02P3ZQ@mail.gmail.com> (raw)
In-Reply-To: <20221130102415.w5bctfyzlkx5m6yy@x220>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Wed, Nov 30, 2022 at 12:24 PM Alyssa Ross <alyssa.ross@unikie.com> wrote:
> On Wed, Nov 30, 2022 at 12:14:28PM +0200, Vadim Likholetov wrote:
> > Thank you for the feedback!
> > I managed to make foot terminal working in my setup -- the issue was in
> > lack of compositor ( weston in my case) on the guest, looks like it's the
> > common issue for wayland programs, so now I have competitive advantage
> over
> > virtio-gpu setup :)
>
> Interesting — why does it need there to be a compositor in the guest?
> Doesn't Waypipe act as the compositor?
>
> No, why should it?
Also wayland-info shows the screen says the display has no compositor.
>
> > I also think that having socket-only approach in Spectrum is not a bad
> idea
> > cause it is enabling remote access and networking easy for virtual
> > machines and applications.
>
> You mean remote access to Spectrum VMs?
>
> Yes, and may be some distributed configurations.
[-- Attachment #2: Type: text/html, Size: 1533 bytes --]
next prev parent reply other threads:[~2022-11-30 10:32 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
2022-11-30 10:14 ` Vadim Likholetov
2022-11-30 10:24 ` Alyssa Ross
2022-11-30 10:32 ` Vadim Likholetov [this message]
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=CALSVioAF00-0eapCuCFFUhpMgcrosmf8Hc39Qt5cb3ai02P3ZQ@mail.gmail.com \
--to=vadim.likholetov@unikie.com \
--cc=alyssa.ross@unikie.com \
--cc=devel@spectrum-os.org \
/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).