From: iyzsong@member.fsf.org (宋文武)
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 31365-done@debbugs.gnu.org
Subject: bug#31365: libvirt/virt-manager: Embeds full path to qemu-system in saved .xml files
Date: Wed, 11 Sep 2019 19:21:18 +0800 [thread overview]
Message-ID: <871rwnxemp.fsf@member.fsf.org> (raw)
In-Reply-To: <87in83ots0.fsf@aikidev.net> (Vagrant Cascadian's message of "Fri, 04 May 2018 17:01:03 -0700")
Vagrant Cascadian <vagrant@debian.org> writes:
> 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
>
> It also means each virtual machine may be running on an older version of
> qemu, for better or worse.
>
> Manaully replacing the emulator entry in the .xml file with
> /run/current-system/profie/bin/qemu-system-x86_64 works around the
> issue, and might be the easiest fix.
>
Hello, I believe my commit 'ef640db2f509f51ebfe3a6a66ba837ef3103bbb7'
fix this, now it use '/run/current-system/profie/bin/qemu-system-x86_64'
in the xml files. Close now.. Thank you!
prev parent reply other threads:[~2019-09-11 11:22 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
2019-09-11 11:21 ` 宋文武 [this message]
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=871rwnxemp.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=31365-done@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.