From: Alyssa Ross <hi@alyssa.is>
To: Jamie McClymont <jamie@kwiius.com>, devel@spectrum-os.org
Subject: Re: virtio-wl on AMD graphics
Date: Thu, 01 Apr 2021 22:56:35 +0000 [thread overview]
Message-ID: <87y2e1mx5o.fsf@alyssa.is> (raw)
In-Reply-To: <a170c3ca-f95d-4e27-b250-f7f3b282c586@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
"Jamie McClymont" <jamie@kwiius.com> writes:
> Hello
>
> If anyone else has struggled with sepectrum-vm on AMD graphics, where
> the "child virtio-pci (virtio-wl)" process dies without a descriptive
> error, I believe the issue is fixed here:
> https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2570453/2/seccomp/x86_64/video_device.policy
>
> It doesn't cleanly apply (I assume the seccomp policies have been shuffled between files), but --disable-sandbox is there as a functioning workaround :)
Thanks for the tip. :) I haven't tested with AMD graphics -- not sure if
anybody else will have.
> Does anyone have a branch where the chromium-os upstream-info is more
> up to date? I can have a go myself, but didn't want to duplicate
> effort :)
I don't think so. Somebody was interested in updating to a more recent
Nixpkgs a few weeks ago but I don't think they got anywhere. I was
planning on doing it once I got some stuff I have locally cleaned up and
committed. If you wanted to have a go that'd be great, and I'll happily
provide any help you need. :)
In particular, if you were to run into any failures due to versions of
dependencies being too old or something, we might need to sync with
upstream Nixpkgs first. If that's the case I can prioritise getting
that done unless you'd like to try that as well -- I'd expect it to be
easier than updating chromiumOSPackages because we don't heavily modify
Nixpkgs, just add to it.
> Thanks
> - Jamie McClymont
>
> --
>
> P.S. an introduction: Hi everyone!
>
> I have just started a new job where VM isolation is necessary, and
> have been hoping for a way to get integrated window management across
> VM boundaries - it looks like this is clearly the ideal approach, and
> I'm already a NixOS user, so am keen to contribute :)
Nice to make your acquaintance! I'm Alyssa, and I'm the main person
behind Spectrum at the moment. I hope you stick around. :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2021-04-01 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 10:46 virtio-wl on AMD graphics Jamie McClymont
2021-04-01 22:56 ` Alyssa Ross [this message]
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=87y2e1mx5o.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=devel@spectrum-os.org \
--cc=jamie@kwiius.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).