From: Mike Gerwitz <mtg@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 31365@debbugs.gnu.org
Subject: bug#31365: libvirt/virt-manager: Embeds full path to qemu-system in saved .xml files
Date: Fri, 04 May 2018 21:24:59 -0400 [thread overview]
Message-ID: <87r2mqopw4.fsf@gnu.org> (raw)
In-Reply-To: <87in83ots0.fsf@aikidev.net> (Vagrant Cascadian's message of "Fri, 04 May 2018 17:01:03 -0700")
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
On Fri, May 04, 2018 at 17:01:03 -0700, Vagrant Cascadian wrote:
> When i create a new libvirt instance with virt-manager, it embeds the
> full path to the qemu binary used at the time. For the machine named
> "networkboot":
>
> # grep qemu-system /etc/libvirt/qemu/networkboot.xml
> <emulator>/gnu/store/0rzb7rjri2kb258j58asndw2pnp0xv9p-qemu-2.11.1/bin/qemu-system-x86_64:</emulator>
>
> If I later run "guix gc" and it happens to remove this particular qemu
> version, the system no longer runs, of course:
>
> # virsh start networkboot
> error: Failed to start domain networkboot
> error: Cannot check QEMU binary
> /gnu/store/0rzb7rjri2kb258j58asndw2pnp0xv9p-qemu-2.11.1/bin/qemu-system-x86_64:
> No such file or directory
Thanks for looking into this; I hit this problem last night but hadn't
had the time to research.
I encountered this issue the same way (after a `guix gc').
> It also means each virtual machine may be running on an older version of
> qemu, for better or worse.
Yes, I was concerned by that as well. :X VMs would not benefit from
security fixes, which is to me is the more important issue here.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2018-05-05 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:01 bug#31365: libvirt/virt-manager: Embeds full path to qemu-system in saved .xml files Vagrant Cascadian
2018-05-05 1:24 ` Mike Gerwitz [this message]
2019-09-11 11:21 ` 宋文武
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=87r2mqopw4.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=31365@debbugs.gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.