From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-4.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=3.4.4 Received: by atuin.qyliss.net (Postfix, from userid 496) id 81AB418F0B; Thu, 1 Apr 2021 10:46:58 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id CAFF118ED4; Thu, 1 Apr 2021 10:46:51 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 496) id 7AE2618E53; Thu, 1 Apr 2021 10:46:49 +0000 (UTC) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by atuin.qyliss.net (Postfix) with ESMTPS id D355018E52 for ; Thu, 1 Apr 2021 10:46:45 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3F5C95C0088 for ; Thu, 1 Apr 2021 06:46:45 -0400 (EDT) Received: from imap22 ([10.202.2.72]) by compute4.internal (MEProxy); Thu, 01 Apr 2021 06:46:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kwiius.com; h= mime-version:message-id:date:from:to:subject:content-type; s= fm2; bh=VzFKHb/HTxdDUHS8fMZNnCb0AlcCNHVbU49rexnYGFs=; b=ThZPUcuH qkcUdsoJnagtAaDL8QdFIUoHlVnQtbkDzwX2E5S08T0CFPpxvmCef0WIrdRb6IZ1 SAwrrt0azTjkAf6bsh1TIgGAYNuz9g27TWSlFnuc6W5L/zfc2JlvUc/FoSCjUsTq 8lJNJo0xUdUBeVvUqqB+SgvuJVlkJTV8on0W/us70JlznQWFoccRr83uvg+tkwCP V3kACywvMmUmfQ0OdAwO3eogA5IqVIMMjxzes+WawGohGeueEfguz2QeCsmWMYJE TRdOuDwh+pejuxZWK0NDct/cgNsZCxHoWJq0/vpFTGgmCBNoKH5AxodTXs/zvJqA 5nEOoXbMey8cVw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=VzFKHb/HTxdDUHS8fMZNnCb0AlcCN HVbU49rexnYGFs=; b=ZlAIld1kyqmtj0f668CpimWJMk+J+p+4H37T6DXR/Sv4Z iU1dF+c8NP/3foW2zhEeyjO1VEjDhvgIi1DBoe/GC8k4G0a4jdEO3KoAIaafBc7D 91a447J9H+lZaFKJeW8dEUeQh0ao2YwwrgkfaxCl+AIrrBTO7oGgyn0qhpOAXf7L ZEVEjj6Yd/+QppfmEbYeEkBkpVCTY8G+IVIQkmQ78j/7+qArQDmm+XB+aQkqUDO0 +eTnZN+rk+udKZLCSjFkWYTfOuisKrPJkGsiP6m9OPFrXzq1v9LcC0sulTwr5qQ5 SgBQYDltHlFd8o0wHe445+vYomyfclDbulLWV2hSQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeigedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsehttdertd erredtnecuhfhrohhmpedflfgrmhhivgcuofgtvehlhihmohhnthdfuceojhgrmhhivges khifihhiuhhsrdgtohhmqeenucggtffrrghtthgvrhhnpeeftdffiefgteetudegieffhe fhvdeiteehfefhheelgfegueekgefftdetvdettdenucffohhmrghinhepghhoohhglhgv shhouhhrtggvrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepjhgrmhhivgeskhifihhiuhhsrdgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9FD4D62C0064; Thu, 1 Apr 2021 06:46:44 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249 Mime-Version: 1.0 Message-Id: Date: Thu, 01 Apr 2021 23:46:09 +1300 From: "Jamie McClymont" To: devel@spectrum-os.org Subject: virtio-wl on AMD graphics Content-Type: text/plain Message-ID-Hash: PAUE7IZOD3AJ2YSGNHC6EUWOZ5YUVIWL X-Message-ID-Hash: PAUE7IZOD3AJ2YSGNHC6EUWOZ5YUVIWL X-MailFrom: jamie@kwiius.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.1 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: 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 :) 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 :) 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 :)