Re: [Libguestfs] Virtualbox vdi Input Format and man pages
Only able to get to this now, but need additional help, if at all possible.
See comments inline below. Thanks.
19.08.2017, 10:36, "Richard W.M. Jones" <rjones(a)redhat.com>:
On Sat, Aug 19, 2017 at 08:38:31AM -0600, stef204 wrote:
> Hi,
>
> I am new to v2v/libguestfs.
> I need to convert a 30 GB virtual machine running Windows7 64 bit (a
> guest on a Linux system) from Virtualbox vdi format to qcow2 (or
> raw/img--another debate in itself) so I can use libvirt/qemu/kvm to
> run it and completely migrate away from Virtualbox.
>
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
The above is done (easy).
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
Please bear with me but I really don't have enough info as to HOW to modify the xml
template., beyond the obvious stuff, MAC address, name of VM, etc.
Might there bit a more detailed xml template in context of Windows to kvm/qemu I could
use?
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.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones