From: phrdina <phrdina@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu: using incorrect datadir /usr/lib when build qemu package
Date: Wed, 22 Jul 2020 15:05:17 +0200 [thread overview]
Message-ID: <20200722130517.R5X5Y2WMYTWSn1TSbtPXbuxDpBdIMaXX_Cr5w8ol_GM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23495@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
New comment by phrdina on void-packages repository
https://github.com/void-linux/void-packages/issues/23495#issuecomment-662440938
Comment:
@pandom79 No it doesn't depend on the ISO file. It depends on the selected or detected OS that you are installing inside the VM.
If you pick windows or it is detected it will pick Q35 as default machine type using osinfo project and virt-manager will get domain capabilities only for Q35 machine type which will contain secure boot firmware and non-secure boot firmware.
If the selected or detected OS will lead to i440FX it will contain only non-secure boot firmware.
The situation that you describe is not working correctly because if you change the machine type into i440FX the secure boot firmware should disappear as it will not work with i440FX.
next prev parent reply other threads:[~2020-07-22 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 12:24 [ISSUE] " phrdina
2020-07-11 15:25 ` sgn
2020-07-11 15:27 ` sgn
2020-07-12 23:21 ` phrdina
2020-07-19 10:57 ` pandom79
2020-07-20 9:27 ` phrdina
2020-07-20 9:32 ` pandom79
2020-07-20 14:00 ` pandom79
2020-07-21 7:44 ` pandom79
2020-07-22 13:05 ` phrdina [this message]
2020-07-22 13:11 ` pandom79
2020-09-14 7:11 ` [ISSUE] [CLOSED] " Hoshpak
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=20200722130517.R5X5Y2WMYTWSn1TSbtPXbuxDpBdIMaXX_Cr5w8ol_GM@z \
--to=phrdina@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).