search for: aavmf_firmware

Displaying 4 results from an estimated 4 matches for "aavmf_firmware".

2016 Feb 04
0
[PATCH] aarch64: Use a common table of AAVMF paths.
...{ NULL }; - -#endif - int guestfs_int_get_uefi (guestfs_h *g, char **code, char **vars) { +#ifdef __aarch64__ size_t i; - for (i = 0; uefi_firmware[i] != NULL; i += 2) { - const char *codefile = uefi_firmware[i]; - const char *varsfile = uefi_firmware[i+1]; + for (i = 0; guestfs_int_aavmf_firmware[i] != NULL; i += 2) { + const char *codefile = guestfs_int_aavmf_firmware[i]; + const char *varsfile = guestfs_int_aavmf_firmware[i+1]; if (access (codefile, R_OK) == 0 && access (varsfile, R_OK) == 0) { CLEANUP_CMD_CLOSE struct command *copycmd = guestfs_int_new_command...
2016 Aug 18
3
[PATCH v2 0/2] v2v: Use OVMF secure boot file (RHBZ#1367615).
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
2016 May 22
3
[PATCH 0/2] uefi: Add new locations for UEFI files on Fedora.
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.
2016 Aug 17
1
[PATCH] v2v: Use OVMF secure boot file (RHBZ#1367615).
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.