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: Mon, 20 Jul 2020 11:32:28 +0200 [thread overview]
Message-ID: <20200720093228.OyGPsIsiXoNTebfkC3hJMjnnJnJxXI2OONy3WwIiE5U@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: 1064 bytes --]
New comment by pandom79 on void-packages repository
https://github.com/void-linux/void-packages/issues/23495#issuecomment-660916774
Comment:
> Hi @pandom79 so there is a bug in virt-manager GUI.
>
> If you start creating new VM in the Step 2 at the bottom page you can select operating system that will be installed inside the VM. Based on the selected OS virt-manager picks q35 or i440fx. If it defaults to i440fx virt-manager gets domain capabilities from libvirt for i440fx only.
>
> Later in the customize window if you switch chipset to q35 virt-manager will not refresh domain capabilities so it will not update the list of firmwares which is the bug here. The same happens the other way around. We need to fix it to refresh domain capabilities correctly when user switches chipset in the UI.
>
> So there is an issue how QEMU is installed in Void Linux and there is a bug in virt-manager to not show correct firmwares if chipset is changed. I'll fix the virt-manager bug.
Hi @phrdina ,
I'll waiting your notice
thank you so much.
regards
next prev parent reply other threads:[~2020-07-20 9:32 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 [this message]
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=20200720093228.OyGPsIsiXoNTebfkC3hJMjnnJnJxXI2OONy3WwIiE5U@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).