On Wed, Sep 10, 2014 at 03:11:37PM +0300, Itamar Heim wrote:
On 09/10/2014 02:55 PM, Richard W.M. Jones wrote:
>On Wed, Sep 10, 2014 at 01:36:59PM +0300, Itamar Heim wrote:
>>- Windows VMs - v2v would need to make sure relevant iso is in the iso
>> domain probably with the drivers expected by v2v?
>I'm not 100% sure how this works, but I'll tell you what virt-v2v does
>(which is the same as old virt-v2v). It installs RHEV-APT (.exe) in
>the guest and ensures it runs at first boot. Does RHEV-APT need an
>ISO to work? I was under the impression that the executable contained
>the drivers needed in itself.
rhev-apt (can't remember the upstream name of the top of my head) is
just a utility that automatically installs/updates the tools based
- detecting there is an ISO
- detecting the ISO is a rhev-tools iso
- detecting the ISO is properly signed
- run the various installers
so yes, we need to make sure if the converted VM is a windows VM,
there is an ISO (and attach it to the VM).
how/where does v2v get rhev-apt from btw?
Very good question! Both old and current virt-v2v use a binary (added
to the RHEL build) which Matt extracted from rhev-apt, probably an old
version. I have no idea where it comes from, and I doubt it is up to
$ grep RHEV-App libguestfs.spec
(not sure the newly introduced ovirt windows guest driver iso has
Something we can build from source using the mingw-* chain would be
useful, otherwise we can never add this to Fedora.
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch