On Tue, Feb 09, 2016 at 01:50:37PM -0800, Joshua Pincus wrote:> Hi Rich, > > Thanks, again, for the pointer. I'm still slowly going through the > registry making my changes. > > I noticed what may be a small bug in your code. Please look at > https://github.com/libguestfs/libguestfs/blob/master/v2v/windows_virtio.ml#L230-L231. > I think you meant to have those two compat ids be: > > "PCI\\CC_010000"; > "PCI\\CC_0100";Yes - you are quite correct. I went back to the original Windows guest that I used for getting the registry changes, and found that I had transcribed these two strings incorrectly. Here is the fix: https://github.com/libguestfs/libguestfs/commit/938f48f08a37791e8ebd6245d19b53f9660b30d2 Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
Hi Richard, Thanks for all your help. Turns out that I needed to get a handle on the StartOverride rubbish that MSFT pushed into Win8 and Win10. It was preventing my viostor service from starting at boot, much like what many poor souls found when they tried to enable/disable AHCI in the BIOS of their machines. Do you know which entity is responsible for modifying the registry at boot to disable/enable these boot services with StartOverride registry updates? Thanks, JP On Mon, Feb 15, 2016 at 2:44 AM, Richard W.M. Jones <rjones@redhat.com> wrote:> On Tue, Feb 09, 2016 at 01:50:37PM -0800, Joshua Pincus wrote: > > Hi Rich, > > > > Thanks, again, for the pointer. I'm still slowly going through the > > registry making my changes. > > > > I noticed what may be a small bug in your code. Please look at > > > https://github.com/libguestfs/libguestfs/blob/master/v2v/windows_virtio.ml#L230-L231 > . > > I think you meant to have those two compat ids be: > > > > "PCI\\CC_010000"; > > "PCI\\CC_0100"; > > Yes - you are quite correct. I went back to the original Windows > guest that I used for getting the registry changes, and found that I > had transcribed these two strings incorrectly. > > Here is the fix: > > > https://github.com/libguestfs/libguestfs/commit/938f48f08a37791e8ebd6245d19b53f9660b30d2 > > Thanks, > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-df lists disk usage of guests without needing to install any > software inside the virtual machine. Supports Linux and Windows. > http://people.redhat.com/~rjones/virt-df/ >
On Mon, Feb 15, 2016 at 09:59:47AM -0800, Joshua Pincus wrote:> Hi Richard, > > Thanks for all your help. Turns out that I needed to get a handle on the > StartOverride rubbish that MSFT pushed into Win8 and Win10. It was > preventing my viostor service from starting at boot, much like what many > poor souls found when they tried to enable/disable AHCI in the BIOS of > their machines. Do you know which entity is responsible for modifying the > registry at boot to disable/enable these boot services with StartOverride > registry updates?virt-v2v doesn't touch StartOverride. The only thing we have found which prevents viostor from being installed is Group Policy. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top