Displaying 20 results from an estimated 1000 matches similar to: "[PATCH 1/2] v2v: -o glance: add property for UEFI firmware (RHBZ#1445659)"
2017 Apr 26
0
[PATCH 2/2] v2v: -o glance: factorize common properties
Many of the properties for disks are the same for all of them, so
collect them only once, instead of doing that for every disk.
Should be just code motion, with no behaviour change.
---
v2v/output_glance.ml | 143 ++++++++++++++++++++++++++-------------------------
1 file changed, 73 insertions(+), 70 deletions(-)
diff --git a/v2v/output_glance.ml b/v2v/output_glance.ml
index cfb19b4..3feb2e4
2017 Mar 17
7
[PATCH v2 0/6] v2v: Pass CPU vendor, model and topology from source to target.
v1 -> v2:
- Support for passing topology through -o glance.
- Support for passing topology through -o rhv.
- Use bool for acpi/apic/pae struct fields in virt-p2v.
- Write the xpath expression in error messages instead of file/line.
- Fix more memory leaks in virt-p2v cpuid.c.
- Passes make check & check-valgrind.
There may be some other minor changes. I believe that everything
2018 Aug 29
2
[PATCH 0/2] v2v: Add -o openstack target.
This patch implements output to OpenStack Cinder volumes using
OpenStack APIs.
It has only been lightly tested, but appears to work.
There are some important things to understand about how this works:
(1) You must run virt-v2v in a conversion appliance running on top of
OpenStack. And you must supply the name or UUID of this appliance to
virt-v2v using the ‘-oo server-id=NAME|UUID’ parameter.
2018 Aug 30
3
[PATCH v2 0/2] v2v: Add -o openstack target.
v1 was here:
https://www.redhat.com/archives/libguestfs/2018-August/thread.html#00287
v2:
- The -oa option now gives an error; apparently Cinder cannot
generally control sparse/preallocated behaviour, although certain
Cinder backends can.
- The -os option maps to Cinder volume type; suggested by Matt Booth.
- Add a simple test.
2017 Nov 21
2
[PATCH v3 0/2] common/mlstdutils: Extend the List module.
v2 -> v3:
- Renamed List.assoc_ -> List.assoc_lbl.
- Rebased on top of current master branch.
Rich.
2017 Mar 16
7
[PATCH 0/4] Pass CPU vendor, model and topology from source to target.
This is tangentially related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1372668
The problem in that bug is that we didn't pass the source CPU model
(Sandybridge in that case) through to the target RHV hypervisor. So
when the Windows guest booted on the target it gives an error about
CPU hardware being disconnected (although it otherwise boots and works
fine).
This patch series
2017 Oct 08
4
[PATCH 0/3] common/mlstdutils: Add Std_utils List and Option modules.
In Std_utils we already extend Char and String. These commits take it
a little further by extending List and adding a new Option submodule.
All basically simple refactoring.
Rich.
2017 Oct 08
7
[[PATCH v2 0/4] common/mlstdutils: Add Std_utils List and Option modules.
This time including the first commit ...
2023 Feb 17
3
[PATCH v2v v2 0/3] Use host-model
Version 1 was here:
https://listman.redhat.com/archives/libguestfs/2023-February/thread.html#30694
I made a few changes in v2 but overall decided to keep the now unused
gcaps_arch_min_version capability. This doesn't preclude removing it
in future if we think it's never going to be useful.
I changed patch 1 so that to remove the long comment about how the
field is used, anticipating the
2018 Apr 20
1
[PATCH] v2v: rework handling of CPU topology
Instead of storing the number of sockets, cores, and threads separately
with the possibility to have each of them optional, store them together,
so either we have a CPU topology or none. This slightly simplifies the
handling of CPU topology.
Most of the output modes/producers already considered a missing
information of a topology as "1" when any of the other was specified, so
the
2016 Nov 01
1
[PATCH] v2v: glance: Set hw_video_model property to qxl|cirrus (RHBZ#1374651).
Thanks: Vladik Romanovsky, Ming Xie.
---
v2v/output_glance.ml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/v2v/output_glance.ml b/v2v/output_glance.ml
index e38b172..179448b 100644
--- a/v2v/output_glance.ml
+++ b/v2v/output_glance.ml
@@ -92,6 +92,10 @@ object
| Virtio_net -> "virtio"
| E1000 -> "e1000"
| RTL8139 ->
2016 Sep 13
1
[PATCH] v2v: -o glance: set all properties during creation (RHBZ#1374405)
The glance client v1.0.0 defaults to the Image v2 API: this means that
an image can be referenced only by its UUID, and not anymore by the name
as well (which does not need to be unique). This caused our glance
invocation to set the properties for the newly created image to fail,
since we are using the name as identifier.
Instead of first creating the image and then setting all the properties
2016 Feb 16
3
[PATCH 0/2] v2v: glance: Allow Glance backend to import multiple disks
This patch series lifts the previous restriction that virt-v2v would
refuse to convert a guest to Glance that had more than one disk.
The first patch is just better documentation for the Glance output
mode. The second patch contains the change (best viewed with
'git diff -w' since it is mostly a whitespace change).
virt-v2v -o glance will now create multiple disks called:
- guestname
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
2015 Oct 21
2
[PATCH] v2v: use open_guestfs everywhere
Use the common open_guestfs to open Guestfs handles, so we get
debugging, tracing, and other common options set.
---
v2v/convert_windows.ml | 4 +---
v2v/input_disk.ml | 2 +-
v2v/input_libvirt_other.ml | 2 +-
v2v/input_ova.ml | 2 +-
v2v/output_glance.ml | 2 +-
v2v/output_null.ml | 2 +-
v2v/output_rhev.ml | 2 +-
v2v/output_vdsm.ml | 2 +-
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
2017 Mar 16
0
[PATCH 4/4] v2v: Pass CPU vendor, model and topology from source to target.
Where supported, pass the source CPU vendor, model and topology to the
target hypervisor.
For -i ova, we can get just cores per socket via a proprietary VMware
extension to OVF.
For -i libvirt and from virt-p2v, we can get all of these fields from
the libvirt XML.
For -o libvirt/local, we can preserve all of the information in the
target XML.
For -o glance, as far as I can tell from the
2016 Apr 12
3
[PATCH] v2v: add support for virtio-scsi
Virtio-SCSI offers a number of advantages over virtio-blk, in
particular, it supports SCSI UNMAP (aka trim) which is crucial for
keeping the virtual drive from wasting host disk space.
This patch adds support for virtio-scsi as the virtual disk connection
type both on input and on output of v2v.
Virtio-blk remains the default, so for now virtio-scsi-based guests can
only be produced in
2017 Dec 08
3
[PATCH v2 0/2] v2v: -o null: Use the qemu null device driver.
This changes the infrastructure to allow the target_file to be
a QEMU URI.
Rich.