Displaying 3 results from an estimated 3 matches for "biostyp".
Did you mean:
biostype
2018 Jul 19
5
[PATCH] v2v: ovf: add firmware and machine type element
...| 1 +
7 files changed, 28 insertions(+), 12 deletions(-)
diff --git a/v2v/create_ovf.ml b/v2v/create_ovf.ml
index 2cf610333..1cab11dfd 100644
--- a/v2v/create_ovf.ml
+++ b/v2v/create_ovf.ml
@@ -462,6 +462,22 @@ let origin_of_source_hypervisor = function
*)
| _ -> None
+let get_ovirt_biostype guestcaps target_firmware =
+ let uefi_firmware =
+ match target_firmware with
+ | TargetBIOS -> None
+ | TargetUEFI -> Some (find_uefi_firmware guestcaps.gcaps_arch) in
+ let secure_boot_required =
+ match uefi_firmware with
+ | Some { Uefi.flags = flags }
+ when L...
2018 Oct 10
4
[PATCH v2 0/2] v2v: machine type for oVirt
changes in v2:
- split patch in two
- changed as per suggestions
Tomáš Golembiovský (2):
v2v: ovf: add firmware and machine type element
v2v: enable UEFI for oVirt/RHV outputs
v2v/create_ovf.ml | 12 +++++++++++-
v2v/create_ovf.mli | 2 +-
v2v/output_rhv.ml | 6 ++----
v2v/output_rhv_upload.ml | 4 ++--
2018 Jul 19
0
Re: [PATCH] v2v: ovf: add firmware and machine type element
...rt specific elemnt to OVF. It represents the combination of
> machine type (i440fx/q35) and firmware (BIOS/UEFI).
Other than adding a new element in the OVF, this also enables the
conversion of UEFI guests to oVirt. It is tested? Does it require other
changes?
I'd split the addition of <BiosType> to the OVF in an own patch, and
the enablement of UEFI for oVirt in a different one.
> +let get_ovirt_biostype guestcaps target_firmware =
> + let uefi_firmware =
> + match target_firmware with
> + | TargetBIOS -> None
> + | TargetUEFI -> Some (find_uefi_firmwa...