Hi Rich,

Thanks for the pointer.  It looks like add_viostor_to_driver_database() is the routine that I need to mimic.  I'll try that out in the morning.  I've been staring at this problem for so long that my eyes are crossing.

Thank you very much for the quick reply!
JP

On Tue, Feb 9, 2016 at 12:11 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
On Mon, Feb 08, 2016 at 04:50:09PM -0800, Joshua Pincus wrote:
> Mr Jones,
>
> I recently came across your excellent 2010 blog entry,
> https://rwmj.wordpress.com/2010/04/30/tip-install-a-device-driver-in-a-windows-vm/.
> The blog entry was incredibly useful for Win7.  I was wondering if you have
> any similar insights for Win10?  The CDDB is gone, and it's replacement, or
> partial replacement, the DeviceDriver database, doesn't seem to serve a
> similar purpose.
>
> My problem is this: I have a Win10 installation that was installed natively
> onto physical media using the standard Intel storage drivers.  In short, I
> want to do precisely that you detailed in your 2010 entry under Win10; I
> want to boot that native installation using the current RedHat viostor
> driver. Win10 keeps hitting me with an 0x7B error, and it's rather
> difficult to get into debugger mode.  If I install Win7 and then try
> booting Win7 using viostor as you detailed, it works perfectly.  Win10 does
> not.  Any insights?

See:

https://github.com/libguestfs/libguestfs/blob/master/v2v/windows_virtio.ml

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/