search for: aavmf

Previously the code had two places where an identical set of AAVMF paths were stored. Put this information into one place. This is just refactoring. --- src/appliance.c | 26 +++++--------------------- src/guestfs-internal-frontend.h | 1 + src/utils.c | 12 ++++++++++++ v2v/utils-c.c | 27 +++++++++++++++++...

From: "Richard W.M. Jones" <rjones@redhat.com> AAVMF is an open source UEFI implementation for aarch64 based on OVMF. As aarch64 is heading for requiring UEFI even inside guests, if the AAVMF firmware is installed on the host, use it as a hint that we should boot the guest using AAVMF instead of the default "empty machine". Note this requi...

https://bugzilla.redhat.com/show_bug.cgi?id=1338083 Now that UEFI is fully open source the UEFI firmware can be included in Fedora. The location will be slightly different. These patches do a bit of code rearrangement and add the new paths. Rich.

This is only lightly tested. In particularly I only tested that the non-secure-boot path still works. I didn't test it on RHEL 7.3 yet because I haven't got enough free disk space for these giant source *.ova files :-( Will try to give that a go later. Rich.

First version was posted here: https://www.redhat.com/archives/libguestfs/2016-August/thread.html#00100 This is semantically the same as the first version. However I've split the patch up into two parts. In the first part, I factor out the UEFI paths so now they are created by the generator and written in the library and v2v/ directory directly, instead of the complex business of having a C

I got a little way into this. The two attached patches are preliminary work. My proposed split is: libguestfs.git common -> git submodule libguestfs-common.git generator/ lib/ all language bindings C based tools (eg. virt-df, virt-edit, guestfish) guestfs-tools.git common -> git submodule libguestfs-common.git

...ppc64le guests (Maros Zatko). Inspection lists the installed applications on Archlinux guests (Nikos Skalkotos). Architectures and platforms PPC64 (POWER7) and PPC64LE (POWER8) architectures are now much better supported, and should work out of the box. For aarch64, we use AAVMF (an open source UEFI implementation based on OVMF) if available to run the appliance. For armv7, we now use the -M virt machine type by default. There is better support for compiling on non-Linux platforms (Pino Toscano, Margaret Lewicka). Libguestfs should now work on MIPS 3...

...... OK 429) QEMU XML-2-ARGV arm-vexpressa9-virtio ... OK 430) QEMU XML-2-ARGV arm-virt-virtio ... OK 431) QEMU XML-2-ARGV aarch64-virt-virtio ... OK 432) QEMU XML-2-ARGV aarch64-aavmf-virtio-mmio ... OK 433) QEMU XML-2-ARGV aarch64-virt-default-nic ... OK 434) QEMU XML-2-ARGV kvm-pit-device ... OK 435) QEMU XML-2-ARGV kvm-pit-delay ... OK 436) QEMU XML-2-ARGV k...

...s.ml b/v2v/utils.ml index 467fd9a12..91c0ed1c8 100644 --- a/v2v/utils.ml +++ b/v2v/utils.ml @@ -73,7 +73,7 @@ let find_uefi_firmware guest_arch = let rec loop = function | [] -> error (f_"cannot find firmware for UEFI guests.\n\nYou probably need to install OVMF (x86-64), or AAVMF (aarch64)") - | ({ Uefi.code = code; vars = vars_template } as ret) :: rest -> + | ({ Uefi.code; vars = vars_template } as ret) :: rest -> if Sys.file_exists code && Sys.file_exists vars_template then ret else loop rest in diff --git a/v2v/v2v.ml b/v2v/v2...

Per my previous email: https://www.redhat.com/archives/libguestfs/2017-September/msg00203.html I'd like to talk about requiring a more modern version of the OCaml compiler. These commits show some of the code changes which would be possible with OCaml >= 3.12 [which it turns out we already require by accident] and also with OCaml >= 4.02. The latter is my favoured option. Rich.