unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Lars Böckel" <listdump@larf.space>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: libvirt with modified QEMU and OVMF
Date: Sat, 08 Sep 2018 23:05:13 +0200	[thread overview]
Message-ID: <87in3fem46.fsf@gnu.org> (raw)
In-Reply-To: <b86074ab-f530-670a-550b-0b0b21b5cbe2@larf.space> ("Lars \=\?utf-8\?Q\?B\=C3\=B6ckel\=22's\?\= message of "Sat, 8 Sep 2018 20:01:07 +0200")

Hello,

(+Cc: guix-devel.)

Lars Böckel <listdump@larf.space> skribis:

> thanks for the suggestion. I had success with a snipplet similiar to
> yours. So i would call that issue "fixed" even though its not pretty.

Cool.

> i would like to push the issue with OVMF in libvirt again:
>
> I would like to have OVMF(UEFI) capability with QEMU. In NixOS you can
> achieve this with
>
>   virtualisation.libvirtd.enable = true;
>   virtualisation.libvirtd.qemuOvmf = true;
>    virtualisation.libvirtd.qemuVerbatimConfig = ''
>      nvram = [ "${pkgs.OVMF}/FV/OVMF.fd:${pkgs.OVMF}/FV/OVMF_VARS.fd" ]
>      user = "1000"
>    '';
>
> the "user" part is not necessary but is required for system VMs in
> combination with qemu's pulseaudio driver. qemuVerbatimConfig is the
> config that is at /etc/libvirt/qemu.conf in traditional GNU/Linux
> distributions.

I don’t know about OVMF but IIUC, what you need here is to create
/etc/libvirt/qemu.conf.  To do that, you can something along these
lines:

  (simple-service 'qemu-conf etc-service-type
                  `(("libvirt/qemu.conf"
                     ,(mixed-text-file "qemu.conf"
                                        "nvarm = "
                                        ovmf "/FV/OVMF.fd:…'))))

Would that work?

(Actually the “libvirt/” bit is only possible since commit
5dec93bb8ba89605bce2f9a5ee9c4dbadeee3b58, a few minutes ago…)

We could provide a proper abstraction on top of that if needed, but I’m
not familiar with libvirt.  If you have ideas on how to improve this,
that’d be great!

Thanks,
Ludo’.

  parent reply	other threads:[~2018-09-08 21:05 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
     [not found]   ` <b86074ab-f530-670a-550b-0b0b21b5cbe2@larf.space>
2018-09-08 21:05     ` Ludovic Courtès [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87in3fem46.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).