From: "Lars Böckel" <listdump@larf.space>
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: libvirt with modified QEMU and OVMF
Date: Sat, 8 Sep 2018 23:56:34 +0200 [thread overview]
Message-ID: <9de89b41-b522-3c40-a879-432801325b88@larf.space> (raw)
In-Reply-To: <87in3fem46.fsf@gnu.org>
Thanks for sharing your idea about it. I cannot pull right now but i
think ...nvram = " ovmf "/F... would not work since you would have to
call the complete path of the package. Though something like "nvram =
/run/current-system/profile/share/firmware/ovmf_x64.bin" COULD work. I
don't know how it would react to the massive wall of symlinks. That is
probably the reason why NixOS calls it with ${pkgs.OVMF}. The produced
file in NixOS (/var/lib/libvirt/qemu.conf) points to /nix/store/....
For usability something you can just put in libvirt-service-type with #t
would be good for usability. As well as the user variable.
Configurations like these are probably more common than changing
tls-ports and would simplify the migration of people running different
systems since they could more easily configure VMs with UEFI support.
When my internet is running again i will pull and try this config. But
since its saturday that might take some time... You can easily check for
UEFI support in libvirt with either virt-install --boot uefi or in
virt-manager when you create a vm and edit it beforehand you have a
dropdown menu for BIOS/UEFI. If someone could test it out and report
back that would be great!
>> 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’.
next prev parent reply other threads:[~2018-09-09 11:39 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
2018-09-08 21:56 ` Lars Böckel [this message]
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=9de89b41-b522-3c40-a879-432801325b88@larf.space \
--to=listdump@larf.space \
--cc=ludo@gnu.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 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).