Re: [win-pv-devel] Driver initialization after installation

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-
> bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Rafal Wojdyla
> Sent: 06 August 2015 04:14
> To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [win-pv-devel] Driver initialization after installation
> 
> Hi,
> 
> I'm testing the revision schema changes and I noticed something strange
> now. I'm installing all the drivers from a single MSI. Before, xeniface
> was loaded immediately after installation. Now it requires a reboot to
> load. I didn't examine debug logs yet but it seems that xenbus doesn't
> create child devices before reboot. Is this expected? Tested my modified
> drivers and the latest official build on Win7 x64.
> 

Rafal,

Alas, this is expected. To remove use of co-installers for critical 
functionality, xenbus now relies on the presence of xenfilt to decide which PCI 
device it can become active on (there may be 2 in the system: the platform PCI 
device and a vendor device, and it needs to favour the vendor device) so if the 
query for the new XENFILT_PVDEVICE interface fails xenbus will request a reboot 
(by writing a NeedReboot DWORD into the registry under its (volatile) Status 
service subkey.

You reminded me that I really do need to write this up a.s.a.p. (I'm spending 
all my time testing at the moment).

  Cheers,

    Paul

> --
> RafaÅ WojdyÅa
> Qubes Tools for Windows developer
> https://www.qubes-os.org/
> 
> _______________________________________________
> win-pv-devel mailing list
> win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel