From: ludo@gnu.org (Ludovic Courtès)
To: "Lars Böckel" <listdump@larf.space>
Cc: guix-devel@gnu.org
Subject: Re: libvirt with modified QEMU and OVMF
Date: Sat, 08 Sep 2018 13:22:37 +0200 [thread overview]
Message-ID: <87efe4grnm.fsf@gnu.org> (raw)
In-Reply-To: <129c5140-eb4c-27df-fe43-6f7cbd423edd@larf.space> ("Lars \=\?utf-8\?Q\?B\=C3\=B6ckel\=22's\?\= message of "Sun, 2 Sep 2018 01:16:39 +0200")
Hi Lars,
Lars Böckel <listdump@larf.space> skribis:
> 2) Using a modified QEMU with libvirt. A modified QEMU could help
> sometimes. A way to specify which QEMU package to use would be helpful
> to resolve issues with newer qemu versions or patches which are not
> upstream. While in NixOS you could add patches like this
>
> nixpkgs.config.packageOverrides = pkgs: rec {
> qemu = pkgs.qemu.overrideAttrs (attrs:{
> patches = (lib.filter (x: ! (lib.hasSuffix
> "fix-hda-recording.patch" (builtins.toString x))) attrs.patches) ++ [
> /path/to/qemu.patch ];
> }
> );
> };
>
> to the QEMU package, i don't think this is possible in GuixSD.
As Gábor suggested, you would do it along these lines:
(define qemu-patched
(package
(inherit qemu)
…))
(define custom-libvirt
(package
(inherit libvirt)
(inputs `(("qemu" ,qemu-patched)
,@(alist-delete "qemu" (package-inputs libvirt))))))
(operating-system
;; …
(services (cons (service libvirt-service-type
(libvirt-configuration
(libvirt custom-libvirt)))
%base-services)))
It’s not equivalent to the above Nix snippet because it only affects the
libvirt service, but it addresses this particular need.
HTH,
Ludo’.
next prev parent reply other threads:[~2018-09-08 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 23:16 libvirt with modified QEMU and OVMF Lars Böckel
2018-09-02 5:18 ` Gábor Boskovits
2018-09-02 8:16 ` Ricardo Wurmus
2018-09-08 11:22 ` Ludovic Courtès [this message]
[not found] ` <b86074ab-f530-670a-550b-0b0b21b5cbe2@larf.space>
2018-09-08 21:05 ` Ludovic Courtès
2018-09-08 21:56 ` Lars Böckel
2018-09-13 21:03 ` Ricardo Wurmus
2018-11-17 22:34 ` Lars Böckel
-- strict thread matches above, loose matches on Subject: below --
2018-11-17 22:48 Lars Böckel
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=87efe4grnm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=listdump@larf.space \
/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.