Re: [Libguestfs] Virtualbox vdi Input Format and man pages

It's good that you mention ‘qemu-img convert’, because the significant difference between virt-v2v & plain qemu-img conversion is that virt-v2v will try to install virtio drivers. Installing virtio drivers in a Windows guest post-conversion is a PITA which is why virt-v2v may be better if you require virtio. So ... to the topic: We don't specifically test conversion from VirtualBox or .vdi. But it ought to work. You will need the virtio drivers from:   https://fedoraproject.org/wiki/Windows_Virtio_Drivers You can either install that package so it appears under /usr/share/virtio-win, or you can use the .iso file from that package and set the VIRTIO_WIN environment variable to point to it:   http://libguestfs.org/virt-v2v.1.html#environment-variables Do you have metadata from VirtualBox (number of CPUs, RAM, etc) in some format? If not, then you should probably use the ‘-i libvirtxml’ input method. You will have to write or modify the metadata, as documented here:   http://libguestfs.org/virt-v2v.1.html#minimal-xml-for--i-libvirtxml-option I believe that virt-v2v should be able to transparently convert the .vdi source file. You might or might not need to use the ‘-if vdi‘ option. It's safe to run virt-v2v on the guest disk image (or a copy, if you want to be extra cautious), just to see if it can be converted. If it fails or gives warnings or errors, then please post the full output of ‘virt-v2v -v -x ....’ Rich.