This has possibilities. I just did yum install virt-v2v on a handy Fedora 14 VM here. The path is a little different:
[root@p2v32bit Converter]# [root@p2v32bit Converter]# pwd /usr/share/perl5/Sys/VirtConvert/Converter [root@p2v32bit Converter]# ls RedHat.pm Windows.pm [root@p2v32bit Converter]#
Looking over Windows.pm, it looks like it spells out the registry keys nicely. Maybe I can put something together to put the files where they belong and insert those registry keys. Let me see what I can come up with and I'll post the results here.
- Greg
-----Original Message----- From: Matthew Booth [mailto:mbooth@redhat.com] Sent: Thursday, October 06, 2011 10:50 AM To: Greg Scott Cc: virt@lists.fedoraproject.org Subject: Re: [fedora-virt] Restored Windows Server 2003 VM goes black
On 06/10/11 16:10, Greg Scott wrote:
Thanks. I don't know anything about perl, but how tough can it be?
Is
there a handy download link?
Have at look in /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/Windows.pm on a machine with virt-v2v installed.
Matt
-----Original Message----- From: Matthew Booth [mailto:mbooth@redhat.com] Sent: Thursday, October 06, 2011 9:55 AM To: Greg Scott Cc: virt@lists.fedoraproject.org Subject: Re: [fedora-virt] Restored Windows Server 2003 VM goes black
On 06/10/11 15:46, Greg Scott wrote:
In the meantime - does anyone have guidance on how to install the
virtio
block driver onto the physical host proactively - with the idea being the migrated virtual server will use it when it boots?
It's more than a little awkward! If you can read perl, have a look in Windows.pm from virt-v2v. It opens the guest image with libguestfs, copies the driver file over and pokes some keys into the registry for the driver and its entry in the CDD.
Everything else it does you can do manually after the guest boots.
Matt