similar to: virt-v2v adding support for Debian/Ubuntu guest?

Enable testing of Debian and Ubuntu guest conversion. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/Makefile.am | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/v2v/Makefile.am b/v2v/Makefile.am index a2f6969..1c06277 100644 --- a/v2v/Makefile.am +++ b/v2v/Makefile.am @@ -311,12 +311,19 @@ check-slow: real_guests_scripts = \

Hi, this series adds a couple bits more in v2v to convert Debian/Ubuntu (and derived) guests. The series does not complete the support (see known issues below), but all the patches here should be fit for review and inclusion. The series does not enable the conversion, yet. Known issues: * currently tested with simple local guest images, hence needs testing with real guests on

Hi Is virt-v2v able to import a debian guest from an OVA archive ? According to the "true" in convert_linux.ml, I would have said yes let matching = function | { i_type = "linux"; i_distro = ("fedora" | "rhel" | "centos" | "scientificlinux" | "redhat-based" |

20:35 < user333> Hello libguestfs ! Is this : virt-v2v: error: virt-v2v is unable to convert this guest type (linux/ubuntu) really a thing ? 20:37 < user333> I got this error with the latest dev. Yes it is. Full support for Debian-based distros is possible, but could be a bit of work. However there are some baby-steps that someone could take towards that goal. I would start by

From matt : Osier, Comments inline below. On 18/12/09 07:39, Osier Yang wrote: > and another point. > > the messages printed to stdout or stderr are not with "message level". > such as > [root at dhcp-66-70-131 image]# virt-v2v -i libvirtxml demo1.xml > virt-v2v: The connected hypervisor does not support a machine type of pc. > virt-v2v: demo1 configured with

--- v2v/virt-v2v.pod | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index 4c7204b..ba91851 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -227,6 +227,10 @@ And hence L<virsh(1)>, L<virt-manager(1)>, and similar tools. =item OpenSUSE 10 and up +=item Debian 6 and up + +=item Ubuntu 10.04, 12.04, 14.04, 16.04,

Hi, this series implements the first bits in v2v to convert Debian/Ubuntu (and derived) guests. The series does not complete the support (see known issues below), but all the patches here should be fit for review and inclusion. The series does not enable the conversion, yet. Known issues: * there is no grubby nor Bootloader::Tools Perl module available in Debian, so there is no way to know

Hi, this series adds a couple bits more in v2v to convert Debian/Ubuntu (and derived) guests. The series does not complete the support (see known issues below), but all the patches here should be fit for review and inclusion. The series does not enable the conversion, yet. Known issues: * currently tested with simple local guest images, hence needs testing with real guests on

Hi, this series implements the first bits in v2v to convert Debian/Ubuntu (and derived) guests. The series does not complete the support (see known issues below), but all the patches here should be fit for review and inclusion. The series does not enable the conversion, yet. Known issues: * there is no grubby nor Bootloader::Tools Perl module available in Debian, so there is no way to know

This message got caught in moderation because the attachment was large. I put the attachment here: http://oirase.annexia.org/tmp/2023-lgarrett-virt-v2v-debug-output.txt ----- Forwarded message from Lee Garrett <lgarrett at rocketjump.eu> ----- Date: Sun, 10 Sep 2023 00:09:17 +0200 From: Lee Garrett <lgarrett at rocketjump.eu> To: libguestfs at redhat.com Subject: virt-v2v creating

Hi list, Is it possible to import Ubuntu (or Debian) VM with virt-p2v or virt-v2v to oVirt ? Thanks Kevin C

Hello List, i have Debian ESXi Guest VMs. Can i use virt-v2v to convert and import them in oVirt? I have read that this is possible for RedHat guest and i was wondering if this also works for Debian Guest VMs, too. Thanks, Mario

Hi Mike, in 2013 you added the support for SUSE guests in the old virt-v2v (the one written in Perl); the commit doing it is attached, since the old virt-v2v was hosted on fedorahosted.org, which is no more. As part of that change, the default graphics driver was changed to be cirrus for SUSE guests, and qxl (as before) for any other. When Rich Jones rewrote virt-v2v in 2014 in OCaml, he kept

Hi Pino, On 2/26/19 5:52 PM, Mike Latimer wrote: > On 2/21/19 3:07 AM, Pino Toscano wrote: >> My question is: is using cirrus still the best choice for SUSE guests? >> If not, what about using qxl as well, as done for any non-SUSE guest? >> (We can also do that depending on the version of the guest, in case >> only newer SUSE versions work fine with qxl). > At the

Run with LIBGUESTFS_ATTACH_METHOD=appliance Fails with: inspect_os: mount_ro: /dev/sda on / (options: 'ro'): mount: /dev/sda is already mounted or /sysroot busy at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 194. virt-inspector works as expected libguestfs-test-tool.log: http://pastebin.ca/2317900 virt-v2v.log: http://iaindb.pastebin.ca/2317938 Any

On 02/23/2017 05:06 PM, Pino Toscano wrote: > On Thursday, 23 February 2017 16:47:57 CET Emmanuel Kasper wrote: >> Is virt-v2v able to import a debian guest from an OVA archive ? >> >> According to the "true" in convert_linux.ml, I would have said yes >> >> let matching = function >> | { i_type = "linux"; >> i_distro =

Keir: This is to to make the IDE device model multithreading so that the VMX domain IO access completion (triggering DMA operation) can be asynchronize with the completion of DMA operation. With this patch we get 8%--14% performance gain for kernel build. Thanks, eddie Yang, Xiaowei wrote: > Originally in qemu when a IDE dma transfer is started which is > triggered by access to 0xc000

Test the newer versions of these distros. --- v2v/Makefile.am | 2 ++ 1 file changed, 2 insertions(+) diff --git a/v2v/Makefile.am b/v2v/Makefile.am index 53c137fc6..39511022e 100644 --- a/v2v/Makefile.am +++ b/v2v/Makefile.am @@ -530,8 +530,10 @@ real_guests_scripts = \ test-v2v-conversion-of-debian-6.sh \ test-v2v-conversion-of-debian-7.sh \ test-v2v-conversion-of-debian-8.sh \ +

There were two related bugs in the virt-v2v error messages when source inspection failed. Firstly it would print the message about running 'virt-v2v -v -x' twice: virt-v2v: error: inspection could not detect the source guest (or physical machine). Assuming that you are running virt-v2v/virt-p2v on a source which is supported (and not, for example, a blank disk), then this should

Allows virt-v2v to be compiled against the libguestfs build directory. --- v2v/Makefile.am | 2 ++ 1 file changed, 2 insertions(+) diff --git a/v2v/Makefile.am b/v2v/Makefile.am index 2a196d45d..104420d13 100644 --- a/v2v/Makefile.am +++ b/v2v/Makefile.am @@ -197,6 +197,7 @@ virt_v2v_CPPFLAGS = \ -I$(top_srcdir)/lib virt_v2v_CFLAGS = \ $(WARN_CFLAGS) $(WERROR_CFLAGS) \ +