libvirt still embeds full path to qemu-system in saved .xml files

  • Done
  • quality assurance status badge
Details
4 participants
  • divoplade
  • Leo Famulari
  • Maxime Devos
  • Pierre Langlois
Owner
unassigned
Submitted by
divoplade
Severity
normal
Merged with
D
D
divoplade wrote on 2 Apr 2021 22:41
(address . bug-guix@gnu.org)
39438626b14fc0dfc1de53aae8269d2d23597924.camel@divoplade.fr
Hello,

I tried to add my comment to issue 31365, but it has been archived and
made read-only.

This issue is not fully fixed. I’m using gnome-boxes to create virtual
machines, and I noticed something similar to what is experienced in
this issue.

The hard-coded path is in /gnu/store/xxx-profile/, so I think it has
been found in /run/current-system/profile/bin, but the symlink has been
resolved too early.

I have recently gc’ed my system, and that’s when I noticed I could not
run my VMs anymore.

My workaround is to replace the hard-coded paths in the XML files.

Best regards,

divoplade

M
M
Maxime Devos wrote on 3 Apr 2021 15:27
3fdc1b625071a61ab8b2b0d778608fa8034b6601.camel@telenet.be
On Fri, 2021-04-02 at 22:41 +0200, divoplade wrote:
Toggle quote (6 lines)
> Hello,
>
> I tried to add my comment to issue 31365, but it has been archived and
> made read-only.
> [...]

For future reference:
it is possible to unarchive and reopen issues. I don't recall the exact
procedure, but when sending a mail to 31365@debbugs.gnu.org, debbugs should
respond with instructions on how to unarchive or re-open the issue.

The ‘archived’ status is mostly for avoiding typos in NNN@debbugs.gnu.org
mail addresses in my experience.

Greetings,
Maxime.
-----BEGIN PGP SIGNATURE-----

iI0EABYIADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYGhtSRccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7pScAP9sxPdeVH/A0mhfruhOPkcD1dnA
y063kmec8HVXbNuszAEA9GIBUVby1kW18OK2VTPlCZbDqNE91MdUnJ223cM0Ngk=
=V/Er
-----END PGP SIGNATURE-----


L
L
Leo Famulari wrote on 3 Apr 2021 21:26
(no subject)
(address . control@debbugs.gnu.org)
YGjBgnzfCVsAw2go@jasmine.lan
unarchive 31365
reopen 31365
merge 47570 31365
P
P
Pierre Langlois wrote on 5 Apr 2021 20:45
Re: bug#47570: libvirt still embeds full path to qemu-system in saved .xml files
(name . divoplade)(address . d@divoplade.fr)
87r1jozi2v.fsf@gmx.com
Hello,

divoplade writes:

Toggle quote (18 lines)
> Hello,
>
> I tried to add my comment to issue 31365, but it has been archived and
> made read-only.
>
> This issue is not fully fixed. I’m using gnome-boxes to create virtual
> machines, and I noticed something similar to what is experienced in
> this issue.
>
> The hard-coded path is in /gnu/store/xxx-profile/, so I think it has
> been found in /run/current-system/profile/bin, but the symlink has been
> resolved too early.
>
> I have recently gc’ed my system, and that’s when I noticed I could not
> run my VMs anymore.
>
> My workaround is to replace the hard-coded paths in the XML files.

Ouch :-/.

Do you know at which guix commit this happened? I'm wondering which
version of libvirt triggered this. AFAICT, right now, if you create a
fresh VM using gnome-boxes, it initializes the xml config with the qemu
in /run/current-system/profile, which looks like the right thing to do.
I've just tested this downloading a fedora image via gnome-boxes, using
either libvirt 5.8 or 7.2 under the hood (updated just now).

Could it be that you created a VM before the bug was fixed? Which would
have left a xml config that refers to GC-able qemu in .config/libvirt,
which a guix update cannot automatically migrate (although one day it might!).

Let me know if I've got this wrong.

Thanks,
Pierre
-----BEGIN PGP SIGNATURE-----

iQFMBAEBCgA2FiEEctU9gYy29KFyWDdMqPyeRH9PfVQFAmBrWrkYHHBpZXJyZS5s
YW5nbG9pc0BnbXguY29tAAoJEKj8nkR/T31UyxsH/iHF8/kagZYN6dQRnTmXQMrV
zjvsIA2+qQ9R++517Ch7OJUW3Eovnk6L3VHc+dPlnTga0CdsSTFxRx/qz3xnYKQ1
/Zqk1tfTq/sA27Zz/RzWVB8gBzLSN2fw4gUS5cUspuUkbVjivrxVZUsFSEPm+TO3
DIcHn1Si8NVnEOJHMZH7iPbmT/4R+Qqz4LDUjhcOsH0GMR/WyIoMnZXGO8Dsqu9F
cWsKw8q++0S6AbviPRPhGZxFDPEnS3Q1wcJ8X48gbQdfMagdazWaN6p17CpcIalp
fV/SZM0hPOfs4Ej5ISotR6AsHle5THlvm6I/jJj39O6/e9OUsMOcngsLZmkWSnE=
=ODOe
-----END PGP SIGNATURE-----

D
D
divoplade wrote on 6 Apr 2021 08:48
(name . Pierre Langlois)(address . pierre.langlois@gmx.com)
93f528bfc35f533761637067f375db3ab09e6eb5.camel@divoplade.fr
Le lundi 05 avril 2021 à 19:45 +0100, Pierre Langlois a écrit :
Toggle quote (8 lines)
> Do you know at which guix commit this happened? I'm wondering which
> version of libvirt triggered this. AFAICT, right now, if you create
> a
> fresh VM using gnome-boxes, it initializes the xml config with the
> qemu
> in /run/current-system/profile, which looks like the right thing to
> do.

I think my system did not auto-upgrade for some time because of a bug
in org-html-export-to-html that broke one of my packages (the bug is,
there’s an explicit comment to indicate a license for a script and that
comment is not XHTML). I don’t know which commit did that, but the
faulty system was between that commit and 24h before. Or there was
another earlier problem, and I can’t help, sorry.

You’re right, now that I upgraded it’s fixed.
P
P
Pierre Langlois wrote on 6 Apr 2021 15:56
(name . divoplade)(address . d@divoplade.fr)
87mtub7bzn.fsf@gmx.com
divoplade writes:

Toggle quote (18 lines)
> Le lundi 05 avril 2021 à 19:45 +0100, Pierre Langlois a écrit :
>> Do you know at which guix commit this happened? I'm wondering which
>> version of libvirt triggered this. AFAICT, right now, if you create
>> a
>> fresh VM using gnome-boxes, it initializes the xml config with the
>> qemu
>> in /run/current-system/profile, which looks like the right thing to
>> do.
>
> I think my system did not auto-upgrade for some time because of a bug
> in org-html-export-to-html that broke one of my packages (the bug is,
> there’s an explicit comment to indicate a license for a script and that
> comment is not XHTML). I don’t know which commit did that, but the
> faulty system was between that commit and 24h before. Or there was
> another earlier problem, and I can’t help, sorry.
>
> You’re right, now that I upgraded it’s fixed.

Cool :-), closing the bug then!

Thanks,
Pierre
-----BEGIN PGP SIGNATURE-----

iQFMBAEBCAA2FiEEctU9gYy29KFyWDdMqPyeRH9PfVQFAmBsaIwYHHBpZXJyZS5s
YW5nbG9pc0BnbXguY29tAAoJEKj8nkR/T31UCHcIAI3jAWg6Pvul2z3iPZQZuDfg
ZUAeWj2mW6CYJ49T3RVPS1LBt1tnC/MjS1BsnLx65Rz0LrhWF2Bs3ECjmT4XWaM2
1FnIz+eAk0FGlrLRpXzhxVdBQMM89Q6GFgNfbKXg3curCxKpjg8F5Vb9SVDKvGuz
cA95l9zTMcKY9vbQJa8WssUvEqjqKyZX/h2rdpllZlwhvSTr3QzmtEvNmqWYSlxg
ZhEWCbL1TXLyAYOBJPzCI5wPo5lTHgmNKJC3OpgwjVY4cA4ateTVxlRkPBM0fx9N
Fh0z5AVGIan6D5VeKBZ5pqUrNslooRy7jvN5q7F3oVzGQ7YNo7pgV8SIvIyA7EE=
=1vPT
-----END PGP SIGNATURE-----

?