similar to: Guestconv library and python worker process

guestconv will be a new, re-usable library to perform guest OS conversions when moving between hypervisors. I've attached 3 files to this email which are relevant to the proposed API. guestconv.h is the proposed C binding. example.c is the simplest possible usage of the API. It converts the first detected root of the guest, accepting all defaults. root.xml is an example description

I've added internationalisation to guestconv, and updated HACKING with a new section. Any thoughts/comments? Matt

On Tue, 2013-09-03 at 17:10 -0600, Mike Latimer wrote: > On Tuesday, September 03, 2013 07:52:08 PM Richard W.M. Jones wrote: > > Even better, there is a repo: https://github.com/mdbooth/guestconv > > Excellent. Thanks for the pointer. > > > Matt - can you push your latest commits, or is there a more canonical > > repo that Mike can look at? > > The last

On Thu, 2013-09-05 at 09:31 -0600, Mike Latimer wrote: > On Thursday, September 05, 2013 12:00:44 PM Matthew Booth wrote: > > guestconv is not intended to completely replace virt-v2v. Broadly > > speaking, virt-v2v does 2 things: > > > > 1. Move guests between 2 hypervisors. > > 2. Make changes to the guest required for a new hypervisor. > > > > The

On Thursday, September 05, 2013 12:00:44 PM Matthew Booth wrote: > guestconv is not intended to completely replace virt-v2v. Broadly > speaking, virt-v2v does 2 things: > > 1. Move guests between 2 hypervisors. > 2. Make changes to the guest required for a new hypervisor. > > The second is unique to virt-v2v, the first has other tools out there. > guestconv will only

On Tuesday, September 03, 2013 07:52:08 PM Richard W.M. Jones wrote: > Even better, there is a repo: https://github.com/mdbooth/guestconv Excellent. Thanks for the pointer. > Matt - can you push your latest commits, or is there a more canonical > repo that Mike can look at? The last changes in the repo seem to be from back in June. Is guestconv expected to completely replace virt-v2v

On Tue, Sep 03, 2013 at 09:29:49AM -0600, Mike Latimer wrote: > Hi, I'll make some advisory comments, but you really need to talk to Matt Booth (CC'd - or mdbooth on #libguestfs). > I have recently been looking into virt-v2v, and noticed the mention > of an upcoming rewrite in a few places. Is there a roadmap or post > someplace that describes the future of this project?

On Wed, Sep 25, 2013 at 05:01:56PM +0100, Matthew Booth wrote: > Mike, > > This is great. I have a couple of minor comments inline, but this looks > good. > > I do have a major concern, though, which is this is basically a fork of > RedHat.pm. I thought your concern would be that you'd want similar functionality in guestconv. Will this SuSE code need to be rewritten

Hello everyone, referring back to https://www.redhat.com/archives/libvirt-users/2013-August/msg00107.html, in which a user discovered that there is no equivalent to "virsh -c lxc:/// lxc-enter-namespace" in the Python API. Has that ever changed? In that thread Daniel suggested that the user file a bug, but that apparently never happened. Why am I interested in this? Ansible currently

Hello everyone, referring back to https://www.redhat.com/archives/libvirt-users/2013-August/msg00107.html, in which a user discovered that there is no equivalent to "virsh -c lxc:/// lxc-enter-namespace" in the Python API. Has that ever changed? In that thread Daniel suggested that the user file a bug, but that apparently never happened. Why am I interested in this? Ansible currently

On Wednesday, September 04, 2013 07:57:25 PM Richard W.M. Jones wrote: > I'll give you a bit of background to this (mis-)feature. The "iface" > optional argument was added so that you could use qemu's IDE interface > instead of whatever the default is (virtio-scsi, falling back to > virtio-blk). Thanks for the background. That does help fill in some holes. >

On Mon, 2013-12-02 at 13:23 +0000, Richard W.M. Jones wrote: > [Continuing a discussion we had on IRC last week ...] > > How to create meaningful regression tests for the inspection code? > We'd like developers to be able to test that changes to the inspection > code don't break inspection of existing guests. We might not be able > to run these tests routinely, and we

Misters, Let me introduce myself : Guillaume FORTAINE, Engineer in Computer Science. Me and my partners are currently working on a Virtualization Firmware. After an analysis of the various solutions (Citrix, VMware and Microsoft), it seemed natural to our eyes, to enable a true bare-metal hypervisor, to go as close as possible to the hardware, hence the BIOS. That's why we are currently

On 03/31/2015 11:47 AM, Brian Kroth wrote: > Hi, I've recently been working on setting up a set of libvirt compute > nodes that will be using a ceph rbd pool for storing vm disk image > files. I've got a couple of issues I've run into. > > First, per the standard ceph documentation examples [1], the way to add > a disk is to create a block in the VM definition XML

Hi, I have recently been looking into virt-v2v, and noticed the mention of an upcoming rewrite in a few places. Is there a roadmap or post someplace that describes the future of this project? I've got a couple of patches against the current code base, and am wondering if they will still be considered for inclusion. Thanks, Mike

Matt, Thanks for the extensive comments. I'll go through them in detail, but it won't be until next week. For the time being, here's a quick take on some of the main issues: > I do have a major concern, though, which is this is basically a fork of > RedHat.pm. There are well over 1,000 identical lines of code between the > 2 modules. Many of the differences are relatively

-debug-only only works on builds with assertions enabled. Your version string says optimized build and doesn’t mention assertions. On Thu, Dec 21, 2017 at 7:15 AM Leslie Zhai via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi LLVM developers, > > llc -march=mips -debug-only=isel was able to work in Nov 8 2017 > https://reviews.llvm.org/D39723 > > But it doesn't

Mike, This is great. I have a couple of minor comments inline, but this looks good. I do have a major concern, though, which is this is basically a fork of RedHat.pm. There are well over 1,000 identical lines of code between the 2 modules. Many of the differences are relatively minor, and could be handled with additional cases. I've also fixed a couple of bits in RedHat.pm since you forked

On Tue, Sep 03, 2013 at 11:30:07PM -0600, Mike Latimer wrote: > On Tuesday, September 03, 2013 06:09:26 PM Mike Latimer wrote: > > However, as mentioned in the bug, this parameter is likely no longer > > required. Unless there is a use-case where this setting is required, it > > seems like a good idea to remove it completely (which should work in > > either libvirt or

[Continuing a discussion we had on IRC last week ...] How to create meaningful regression tests for the inspection code? We'd like developers to be able to test that changes to the inspection code don't break inspection of existing guests. We might not be able to run these tests routinely, and we might have to accept that they have to download hundreds of megabytes of test data. Idea