Github messages for voidlinux
 help / color / mirror / Atom feed
From: pandom79 <pandom79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu: using incorrect datadir /usr/lib when build qemu package
Date: Sun, 19 Jul 2020 12:57:36 +0200	[thread overview]
Message-ID: <20200719105736.fQ4inja5x8wjxUDZ0m59FEi1TxodtQhsNec4q_8cy6c@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: 873 bytes --]

New comment by pandom79 on void-packages repository

https://github.com/void-linux/void-packages/issues/23495#issuecomment-660625814

Comment:
> Symlink would work for libvirt but I'm not sure if it's correct for void linux distribution as I'm not familiar with it.

hi phrdina,
few days ago, you have answered at my email.
i built qemu as you suggested and now libvirt finds the firmware correctly.
Thare are two problems again:
1) i had to patch makefile to resolve build error caused by pkglint-elf-in-usrshare. I think that it is wrong but i only wanted to do a test for libvirt, therefore , i'll try to create a symbolic link.
2) The virt manager gui shows only firware uefi but it doesn't show uefi secure boot firmware again. I tried to set q35 machine type and storage format  raw and disk bus sata. Now , the paths are right, why does it not show?
regards

  parent reply	other threads:[~2020-07-19 10:57 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 [this message]
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
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=20200719105736.fQ4inja5x8wjxUDZ0m59FEi1TxodtQhsNec4q_8cy6c@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).