Displaying 14 results from an estimated 14 matches for "code_debug".
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
2017 Jun 21
0
[PATCH v8 07/42] common/utils: Move ‘uefi.c’ to ‘lib/’.
...h
@@ -102,18 +102,6 @@ extern void guestfs_int_fadvise_noreuse (int fd);
//extern void guestfs_int_fadvise_willneed (int fd);
extern char *guestfs_int_shell_unquote (const char *str);
-/* uefi.c */
-struct uefi_firmware {
- const char *code; /* code file (NULL = end of list) */
- const char *code_debug; /* code file with debugging msgs (may be NULL)*/
- const char *vars; /* vars template file */
- int flags; /* various flags, see below */
-#define UEFI_FLAG_SECURE_BOOT_REQUIRED 1 /* secure boot (see RHBZ#1367615) */
-};
-extern struct uefi_firmware guestfs_int_uefi_i386_firm...
2019 Oct 15
4
Splitting the large libguestfs repo
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
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.
2019 Feb 25
0
[PATCH 3/3] v2v: add -o json output mode
...ref [
+ "code", JSON.String uefi_firmware.Uefi.code;
+ "vars", JSON.String uefi_firmware.Uefi.vars;
+ "flags", JSON.List (json_list_of_string_list flags);
+ ] in
+
+ push_optional_string uefi "code-debug" uefi_firmware.Uefi.code_debug;
+
+ List.push_back fw ("uefi", JSON.Dict !uefi)
+ );
+
+ !fw in
+ List.push_back doc ("firmware", JSON.Dict firmware);
+
+ List.push_back doc ("features",
+ JSON.List (json_list_of_string_list source.s_features));
+
+ let machine =...
2019 Mar 29
0
[PATCH v2 3/3] v2v: add -o json output mode
...ref [
+ "code", JSON.String uefi_firmware.Uefi.code;
+ "vars", JSON.String uefi_firmware.Uefi.vars;
+ "flags", JSON.List (json_list_of_string_list flags);
+ ] in
+
+ push_optional_string uefi "code-debug" uefi_firmware.Uefi.code_debug;
+
+ List.push_back fw ("uefi", JSON.Dict !uefi)
+ );
+
+ !fw in
+ List.push_back doc ("firmware", JSON.Dict firmware);
+
+ List.push_back doc ("features",
+ JSON.List (json_list_of_string_list source.s_features));
+
+ let machine =...
2019 Mar 29
5
[PATCH v2 0/3] v2v: add -o json output mode
This series adds a new output mode for virt-v2v, called -o json.
It produces local files, just like -o local, although the metadata
produced is a JSON file with data that v2v collected in the conversion
process. This can be useful for converting to unsupported destinations,
still based on QEMU/KVM.
In addition to a simple different metadata, it offers a way to relocate
the disks, with
2019 Feb 25
7
[PATCH 0/3] RFC: v2v: add -o json output mode
This series adds a new output mode for virt-v2v, called -o json.
It produces local files, just like -o local, although the metadata
produced is a JSON file with data that v2v collected in the conversion
process. This can be useful for converting to unsupported destinations,
still based on QEMU/KVM.
In addition to a simple different metadata, it offers a way to relocate
the disks, with
2017 Jun 19
16
[PATCH v7 00/13] Refactor utilities
This is just the utilities part of the patch series from:
https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html
I believe this addresses everything raised in comments on that
patch series.
Rich.
2017 Jun 09
12
[PATCH 00/12] Refactor utility functions.
This turned out to be rather more involved than I thought.
We have lots of utility functions, spread all over the repository,
with not a lot of structure. This moves many of them under common/
and structures them so there are clear dependencies.
This doesn't complete the job by any means. Other items I had on my
to-do list for this change were:
- Split up mllib/common_utils into:
-
2017 Jun 12
32
[PATCH v5 00/32] Refactor utilities, implement some APIs in OCaml.
This is a combination of:
https://www.redhat.com/archives/libguestfs/2017-June/msg00046.html
[PATCH 00/12] Refactor utility functions.
plus:
https://www.redhat.com/archives/libguestfs/2017-June/msg00023.html
[PATCH v3 00/19] Allow APIs to be implemented in OCaml.
with the second patches rebased on top of the utility refactoring, and
some other adjustments and extensions.
This passes
2017 Jun 21
45
[PATCH v8 00/42] Refactor utilities and reimplement inspection.
v7 was:
https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html
https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html
I believe this addresses all comments received so far.
Also it now passes a test where I compared about 100 disk images
processed with old and new virt-inspector binaries. The output is
identical in all cases except one which is caused by a bug in blkid
2017 Jun 15
45
[PATCH v6 00/41] Refactor utilities, reimplement inspection in the daemon.
v5:
https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html
Since v5, this now implements inspection almost completely for Linux
and Windows guests.
Rich.