From: pandom79 <pandom79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] qemu : fixed firmware path
Date: Mon, 20 Jul 2020 15:51:31 +0200 [thread overview]
Message-ID: <20200720135131.ClTmIoZPeZgKyNHhFw0dQVhI0SRwsNqLx3EhCJWFgQs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23651@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
There is an updated pull request by pandom79 against master on the void-packages repository
https://github.com/pandom79/void-packages qemu
https://github.com/void-linux/void-packages/pull/23651
qemu : fixed firmware path
Hi,
the actual qemu version is built wrong.
When libvirt start, it searchs firmware in **/usr/share/qemu/firmware** but the firmwares are installed in **/usr/lib/qemu/firmware** because it has been set **--data-lib=/usr/lib**.
Deleting this setting , now libvirt works correctly and i can choice uefi firmware.
Before this was not possible.
Regards
A patch file from https://github.com/void-linux/void-packages/pull/23651.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-qemu-23651.patch --]
[-- Type: text/x-diff, Size: 799 bytes --]
From fc54d2a8c6494ba3b6a1e8017cee03ebc1c9863a Mon Sep 17 00:00:00 2001
From: Domenico Panella <pandom79@gmail.com>
Date: Sun, 19 Jul 2020 11:19:22 +0200
Subject: [PATCH] qemu : fixed firmware path
---
srcpkgs/qemu/template | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/srcpkgs/qemu/template b/srcpkgs/qemu/template
index 5a32c5c1dd3..c7d5f856816 100644
--- a/srcpkgs/qemu/template
+++ b/srcpkgs/qemu/template
@@ -82,6 +82,11 @@ do_install() {
# qemu-bridge-helper must be setuid for non privileged users.
chmod u+s ${DESTDIR}/usr/libexec/qemu-bridge-helper
+ #Symbolic link /usr/share/qemu/firmware -> /usr/lib/qemu/firmware
+ #to permit libvirtd to find the firmwares
+ vmkdir usr/share/qemu
+ ln -s /usr/lib/qemu/firmware ${DESTDIR}/usr/share/qemu/firmware
+
vsv qemu-ga
}
next prev parent reply other threads:[~2020-07-20 13:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 9:33 [PR PATCH] " pandom79
2020-07-19 9:53 ` sgn
2020-07-19 9:54 ` sgn
2020-07-19 10:30 ` pandom79
2020-07-19 10:30 ` [PR PATCH] [Closed]: " pandom79
2020-07-20 11:49 ` [PR PATCH] [Updated] " pandom79
2020-07-20 11:51 ` pandom79
2020-07-20 11:53 ` pandom79
2020-07-20 11:54 ` pandom79
2020-07-20 11:55 ` pandom79
2020-07-20 13:51 ` pandom79 [this message]
2020-07-20 14:04 ` sgn
2020-07-20 14:14 ` pandom79
2020-07-20 14:15 ` pandom79
2020-09-14 8:36 ` pandom79
2020-09-14 8:36 ` [PR PATCH] [Closed]: " pandom79
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=20200720135131.ClTmIoZPeZgKyNHhFw0dQVhI0SRwsNqLx3EhCJWFgQs@z \
--to=pandom79@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).