Displaying 20 results from an estimated 1000 matches similar to: "[PATCH] v2v: ovf: add firmware and machine type element"
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 ++--
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.
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
2018 Jul 19
0
Re: [PATCH] v2v: ovf: add firmware and machine type element
On Thursday, 19 July 2018 15:51:04 CEST Tomáš Golembiovský wrote:
> Add oVirt 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
2015 Oct 20
1
[PATCH v3 06/13] v2v: factor out determining the guest firmware
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---
v2v/v2v.ml | 45 +++++++++++++++++++++++++--------------------
1 file changed, 25 insertions(+), 20 deletions(-)
diff --git a/v2v/v2v.ml b/v2v/v2v.ml
index 633c29f..afffde2 100644
--- a/v2v/v2v.ml
+++ b/v2v/v2v.ml
@@ -103,26 +103,7 @@ let rec main () =
g#shutdown ();
g#close ();
- (* Does the guest require UEFI on the target?
2018 Feb 22
5
[PATCH v2 0/3] Make generated OVF more conforming to standard
The main reason for creating different OVF is that it can be used to create VM
by oVirt REST API. The RHV export domain flavor cannot be used that way.
v1 -> v2:
- introduced flavour types instead of booleans
- instead of referring to the new flavour as "standard OVF" or "fixed OVF" I
refer to it as oVirt flavour. While it is more conforming than the one used
in export
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
2018 Feb 18
6
[PATCH 0/3] Make generated OVF more conforming to standard
The main reason for creating different OVF is that it can be used to create VM
by oVirt REST API. The RHV export domain flavor cannot be used that way.
Tomáš Golembiovský (3):
v2v: tests: check generated OVF
v2v: ovf: Create OVF more aligned with the standard
v2v: vdsm: add --vdsm-fixed-ovf option
v2v/cmdline.ml | 5 ++
v2v/create_ovf.ml
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
2017 Apr 26
2
[PATCH 1/2] v2v: -o glance: add property for UEFI firmware (RHBZ#1445659)
When converting a guest with UEFI firmware, set the also
hw_firmware_type=uefi property for all the disks of the guest, so Nova
can properly boot the guest.
---
v2v/output_glance.ml | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/v2v/output_glance.ml b/v2v/output_glance.ml
index b712d68..cfb19b4 100644
--- a/v2v/output_glance.ml
+++ b/v2v/output_glance.ml
@@ -41,7
2017 Apr 05
2
[PATCH] v2v: Rename OVF module to Create_ovf.
This is just a bit of preparatory refactoring ...
Rich.
2018 Jun 19
2
[PATCH] v2v: Set machine type explicitly for outputs which support it (RHBZ#1581428).
QEMU for x86 supports two machine types, "pc" (emulating the ancient
Intel i440FX chipset originally used by the Pentium Pro), and "q35"
(https://wiki.qemu.org/Features/Q35).
Currently virt-v2v does not set any machine type, so libvirt or the
target hypervisor will choose some default, probably i440fx. Newer
versions of libvirt and QEMU will probably switch over to defaulting
2018 Jul 19
0
[PATCH] v2v: Model machine type explicitly.
QEMU for x86 supports two machine types, "pc" (emulating the ancient
Intel i440FX chipset originally used by the Pentium Pro), and "q35"
(https://wiki.qemu.org/Features/Q35).
Currently virt-v2v does not set any machine type, so libvirt or the
target hypervisor will choose some default, probably i440fx. The
latest advice from the QEMU and libvirt communities is not to rely on
2015 Aug 11
41
[PATCH v2 00/17] v2v: add --in-place mode
This series is a second attempt to add a mode of virt-v2v operation
where it leaves the config and disk image conversion, rollback on
errors, registering with the destination hypervisor, etc. to a
third-party toolset, and performs only tuning of the guest OS to run in
the KVM-based hypervisor.
The first 14 patches are just refactoring and rearrangement of the code,
factoring the implementation
2016 Jun 13
1
[PATCH] v2v: Fix get_firmware_bootable_device.
I'm going to push this because it's a test blocker, but FYI.
Rich.
2023 Mar 10
1
[V2V PATCH v3 1/6] Revert "Remove guestcaps_block_type Virtio_SCSI"
This code is needed to check whether virtio-scsi driver was installed.
This reverts commit f0afc439524853508938b2bfc758896f053462e3.
---
convert/convert.ml | 2 +-
convert/convert_linux.ml | 9 +++++++--
convert/target_bus_assignment.ml | 1 +
lib/create_ovf.ml | 1 +
lib/types.ml | 3 ++-
lib/types.mli
2023 Mar 07
1
[V2V PATCH v2 1/5] Revert "Remove guestcaps_block_type Virtio_SCSI"
This code is needed to check whether virtio-scsi driver was installed.
This reverts commit f0afc439524853508938b2bfc758896f053462e3.
---
convert/convert.ml | 2 +-
convert/convert_linux.ml | 9 +++++++--
convert/target_bus_assignment.ml | 1 +
lib/create_ovf.ml | 1 +
lib/types.ml | 3 ++-
lib/types.mli
2023 Mar 13
1
[V2V PATCH v2 1/5] Revert "Remove guestcaps_block_type Virtio_SCSI"
On 3/7/23 20:40, Andrey Drobyshev wrote:
> This code is needed to check whether virtio-scsi driver was installed.
>
> This reverts commit f0afc439524853508938b2bfc758896f053462e3.
> ---
> convert/convert.ml | 2 +-
> convert/convert_linux.ml | 9 +++++++--
> convert/target_bus_assignment.ml | 1 +
> lib/create_ovf.ml |
2016 Jun 09
1
[PATCH] v2v: OVF: Set <Origin/> field correctly based on source hypervisor.
https://bugzilla.redhat.com/show_bug.cgi?id=1342398#c6
---
v2v/OVF.ml | 138 ++++++++++++++++++++++++++++++++++---------------------------
1 file changed, 76 insertions(+), 62 deletions(-)
diff --git a/v2v/OVF.ml b/v2v/OVF.ml
index 8a6f13e..0599306 100644
--- a/v2v/OVF.ml
+++ b/v2v/OVF.ml
@@ -184,6 +184,15 @@ and get_ostype = function
typ distro major minor arch product;
2023 Mar 13
1
[V2V PATCH v2 1/5] Revert "Remove guestcaps_block_type Virtio_SCSI"
On 3/13/23 10:13, Laszlo Ersek wrote:
> On 3/7/23 20:40, Andrey Drobyshev wrote:
>> This code is needed to check whether virtio-scsi driver was installed.
>>
>> This reverts commit f0afc439524853508938b2bfc758896f053462e3.
>> ---
>> convert/convert.ml | 2 +-
>> convert/convert_linux.ml | 9 +++++++--
>>