From: rekh127 <rekh127@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: incus: update to 6.4.0
Date: Wed, 28 Aug 2024 22:58:20 +0200 [thread overview]
Message-ID: <20240828205820.F33622DADC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51907@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
New comment by rekh127 on void-packages repository
https://github.com/void-linux/void-packages/pull/51907#issuecomment-2316230233
Comment:
Edit: spoke too soon
The remaining issue is no "OVMF_CODE.secboot.4m.fd" looks like we don't package this in edk2-ovmf @classabbyamp is there a specific reason not to?
But setting "security.secureboot" on a vm instance or on a profile they're attached to allows vms to be started.
edit: They're started but they're not booting up properly still. apparently hanging on loading inital ramdisk another round of debugging.
next prev parent reply other threads:[~2024-08-28 20:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 7:45 [PR PATCH] " dkwo
2024-08-22 8:26 ` [PR PATCH] [Updated] " dkwo
2024-08-23 3:25 ` classabbyamp
2024-08-27 18:23 ` rekh127
2024-08-28 20:51 ` rekh127
2024-08-28 20:55 ` classabbyamp
2024-08-28 20:58 ` rekh127 [this message]
2024-08-28 21:03 ` rekh127
2024-08-28 21:11 ` rekh127
2024-08-29 14:08 ` dkwo
2024-08-29 18:58 ` rekh127
2024-08-29 18:59 ` rekh127
2024-08-29 19:10 ` rekh127
2024-08-29 19:19 ` classabbyamp
2024-08-29 20:01 ` rekh127
2024-08-29 20:18 ` dkwo
2024-08-29 20:38 ` rekh127
2024-08-29 20:53 ` classabbyamp
2024-08-29 21:22 ` dkwo
2024-08-29 21:27 ` rekh127
2024-08-29 21:33 ` dkwo
2024-08-30 19:20 ` dkwo
2024-08-30 19:44 ` [PR PATCH] [Updated] " dkwo
2024-08-30 20:38 ` dkwo
2024-08-30 20:38 ` dkwo
2024-08-30 21:04 ` rekh127
2024-08-30 22:27 ` dkwo
2024-08-31 6:11 ` classabbyamp
2024-08-31 11:02 ` dkwo
2024-08-31 12:03 ` dkwo
2024-08-31 12:04 ` [PR PATCH] [Updated] " dkwo
2024-08-31 13:48 ` [PR REVIEW] " classabbyamp
2024-08-31 13:50 ` classabbyamp
2024-08-31 13:52 ` classabbyamp
2024-08-31 14:31 ` dkwo
2024-08-31 14:33 ` [PR REVIEW] " dkwo
2024-08-31 15:19 ` dkwo
2024-08-31 15:19 ` [PR PATCH] [Updated] " dkwo
2024-08-31 17:14 ` rekh127
2024-09-02 14:37 ` [PR PATCH] [Updated] " dkwo
2024-09-02 14:41 ` dkwo
2024-09-02 15:58 ` [PR REVIEW] " classabbyamp
2024-09-02 19:08 ` [PR PATCH] [Updated] " dkwo
2024-09-04 17:10 ` dkwo
2024-09-05 12:39 ` dkwo
2024-09-05 12:40 ` [PR PATCH] [Updated] " dkwo
2024-09-05 12:40 ` dkwo
2024-09-06 13:15 ` [PR PATCH] [Updated] " dkwo
2024-09-06 13:23 ` incus: update to 6.5 dkwo
2024-09-06 21:57 ` [PR REVIEW] " rekh127
2024-09-06 22:01 ` classabbyamp
2024-09-06 22:03 ` rekh127
2024-09-07 20:39 ` [PR PATCH] [Updated] " dkwo
2024-09-08 13:51 ` dkwo
2024-09-08 14:23 ` [PR PATCH] [Merged]: " classabbyamp
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=20240828205820.F33622DADC@inbox.vuxu.org \
--to=rekh127@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).