Hello all, I'm trying to automate the installation of the VirtIO drivers on a Windows image in the same way it is done in [1] and [2]. Registering the viostor service and adding the driver under the HKEY_LOCALE_MACHINE\SYSTEM\CurrentControlSet\CriticalDeviceDatabase registry key, makes an Windows 2008R2 image boot if the hd is under the virtio interface, but I cannot make this work for Windows 2012R2. As far as I've seen, the CDDB registry keys are deprecated in newer Windows and creating them back does not seem to make this work. Has anybody had any luck with this? Is there any other way to do it for newer Windows? If this does not work out, I'll probably try to add the driver installations process in a RunOnce registry entry, boot the image using the ide interface and reboot it using VirtIO after the drivers have been installed, but I wanted to know if there is an easier way to do this. Thank you in advanced, Nikos [1] https://github.com/libguestfs/hivex/blob/master/sh/example6 [2] https://git.fedorahosted.org/cgit/virt-v2v.git/tree/lib/Sys/VirtConvert/C...

On 13/06/14 12:51, Richard W.M. Jones wrote: > [Matt (CC'd) can probably answer this one better than anyone ...] I haven't implemented this for W2k12. Sounds like a job for Google and a couple of weeks of experimentation :( Be prepared to find many blog posts which are wrong. Matt > On Fri, Jun 13, 2014 at 11:34:08AM +0300, Nikos Skalkotos wrote: >> Hello all, >> >> I'm trying to automate the installation of the VirtIO drivers on a >> Windows image in the same way it is done in [1] and [2]. >> >> Registering the viostor service and adding the driver under the >> HKEY_LOCALE_MACHINE\SYSTEM\CurrentControlSet\CriticalDeviceDatabase >> registry key, makes an Windows 2008R2 image boot if the hd is under the >> virtio interface, but I cannot make this work for Windows 2012R2. As far >> as I've seen, the CDDB registry keys are deprecated in newer Windows and >> creating them back does not seem to make this work. >> >> Has anybody had any luck with this? Is there any other way to do it for >> newer Windows? >> >> If this does not work out, I'll probably try to add the driver >> installations process in a RunOnce registry entry, boot the image using >> the ide interface and reboot it using VirtIO after the drivers have been >> installed, but I wanted to know if there is an easier way to do this. >> >> Thank you in advanced, >> Nikos >> >> [1] https://github.com/libguestfs/hivex/blob/master/sh/example6 >> [2] >> https://git.fedorahosted.org/cgit/virt-v2v.git/tree/lib/Sys/VirtConvert/C... > Rich. >

I think the way we did this originally was to examine how other installers worked and what changes they made to the Registry. You can grab the registry content before and after running a particular installer, eg: $ virt-win-reg windows.img 'HKLM\SYSTEM' > old-system.reg # run the installer $ virt-win-reg windows.img 'HKLM\SYSTEM' > new-system.reg $ diff -ur old-system.reg new-system.reg You can also use virt-diff to show the differences between the entire disk image before and after. http://libguestfs.org/virt-win-reg.1.html#synopsis http://libguestfs.org/virt-diff.1.html Rich.