Your message dated Thu, 18 Nov 2021 10:32:18 +0800 with message-id <69b1937408d47e2921420600ad718d2795be1819.camel@debian.org> and subject line Re: RFP: virt-v2v -- Convert a guest from a foreign hypervisor to run on KVM has caused the Debian Bug report #962293, regarding RFP: virt-v2v -- Convert a guest from a foreign hypervisor to run on KVM to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 962293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962293 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: RFP: virt-v2v -- Convert a guest from a foreign hypervisor to run on KVM
- From: Kevin Locke <kevin@kevinlocke.name>
- Date: Fri, 05 Jun 2020 11:38:04 -0600
- Message-id: <159137868410.887769.5310030329871500787.reportbug@kevinolos.locke.internal>
Package: wnpp Severity: wishlist * Package name : virt-v2v Version : 1.42.0 Upstream Author : Richard W.M. Jones, Red Hat Inc. * URL : http://libguestfs.org/ * License : GPL-2+ Programming Lang: OCaml Description : Convert a guest from a foreign hypervisor to run on KVM Virt-v2v converts a single guest from a foreign hypervisor to run on KVM. It can read Linux and Windows guests running on VMware, Xen, Hyper-V and some other hypervisors, and convert them to KVM managed by libvirt, OpenStack, oVirt, Red Hat Virtualisation (RHV) or several other targets. It can modify the guest to make it bootable on KVM and install virtio drivers so it will run quickly. It was developed as part of libguestfs from 1.28 up to 1.41.7, and has since been split into its own repository.[1][2][3] It was shipped in buster and it would be great to see it return to sid. I whipped up a package for my own use.[4] It is functional, but I'm still following up on a few issues with upstream. Deficiencies I'm aware of are noted in debian/TODO.md. Let me know if there's anything else I can do to help. Thanks, Kevin [1]: https://www.redhat.com/archives/libguestfs/2019-July/msg00102.html [2]: https://www.redhat.com/archives/libguestfs/2019-October/msg00085.html [3]: https://www.redhat.com/archives/libguestfs/2020-March/msg00053.html [4]: https://salsa.debian.org/kevinoid/virt-v2v
--- End Message ---
--- Begin Message ---
- To: 962293-done@bugs.debian.org, Kevin Locke <kevin@kevinlocke.name>, Ryan Pavlik <ryan@ryanpavlik.com>
- Subject: Re: RFP: virt-v2v -- Convert a guest from a foreign hypervisor to run on KVM
- From: Paul Wise <pabs@debian.org>
- Date: Thu, 18 Nov 2021 10:32:18 +0800
- Message-id: <69b1937408d47e2921420600ad718d2795be1819.camel@debian.org>
- In-reply-to: <159137868410.887769.5310030329871500787.reportbug@kevinolos.locke.internal>
- References: <159137868410.887769.5310030329871500787.reportbug@kevinolos.locke.internal>
Source: virt-v2v Source-Version: 1.44.0-1 On Fri, 05 Jun 2020 11:38:04 -0600 Kevin Locke wrote: > * Package name : virt-v2v virt-v2v has been available in Debian since 2021-08-17: https://tracker.debian.org/pkg/virt-v2v Looks like the libvirt team could use some assistance with it though, there is one release-critical bug to solve in Debian bookworm, otherwise it will get auto-removed on 2021-11-21 (this Sunday). -- bye, pabs https://wiki.debian.org/PaulWiseAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---