From: noarchwastaken <noarchwastaken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libvirt-7.5.0_1: [Regression] Unable to create or start VMs
Date: Thu, 07 Apr 2022 15:40:54 +0200 [thread overview]
Message-ID: <20220407134054.P0e5Cp9tW_PFJyX8fL_aRYiQBkIXOxr927JoLZqExmg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31904@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
New comment by noarchwastaken on void-packages repository
https://github.com/void-linux/void-packages/issues/31904#issuecomment-1091754469
Comment:
In #32562 (the now) ghost mentioned we could also patch `virt-aa-helper`, and I prefer it since:
First, looking at `restricted-rw[]` it's all publicly accessible files with no confidential information. /usr/share/qemu/ also doesn't contain confidential files, so even in the case of a breakout that will be stopped by apparmor, the risk is managable.
Second, the moving firmware to /usr/share/ovmf method breaks existing VM configurations (except maybe we link the firmwares back? But existing VMs still suffer from the same problem, and it requires manual intervention.)
Last, there are several closed PRs attempting to add `ovmf` so far, and I don't think we need them anymore?
next prev parent reply other threads:[~2022-04-07 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 9:43 [ISSUE] libvirt-7.5.0_1: [Regression] Unable to start any virtual machines created prior to the update noarchwastaken
2021-07-22 5:52 ` libvirt-7.5.0_1: [Regression] Unable to create or start VMs noarchwastaken
2021-07-22 5:52 ` noarchwastaken
2021-07-22 5:57 ` noarchwastaken
2021-07-22 5:58 ` noarchwastaken
2021-07-22 5:58 ` noarchwastaken
2021-07-22 9:54 ` paper42
2021-07-24 13:03 ` noarchwastaken
2021-07-24 13:05 ` noarchwastaken
2021-07-24 18:23 ` FollieHiyuki
2021-08-18 23:02 ` sernkut
2021-08-19 10:51 ` sernkut
2022-04-07 13:40 ` noarchwastaken [this message]
2022-07-07 2:13 ` github-actions
2022-07-07 23:02 ` noarchwastaken
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=20220407134054.P0e5Cp9tW_PFJyX8fL_aRYiQBkIXOxr927JoLZqExmg@z \
--to=noarchwastaken@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).