Re: [win-pv-devel] No matching device was found when trying to install PV drivers

[Nick Craig-Wood <nick@xxxxxxxxxxxxxx>]

On 28/09/16 18:07, Nick Craig-Wood wrote:
> On 28 September 2016 17:37:49 Paul Durrant <Paul.Durrant@xxxxxxxxxx> wrote:
> 
>>> -----Original Message-----
>>> From: Nick Craig-Wood [mailto:nick@xxxxxxxxxxxxxx]
>>> Sent: 28 September 2016 17:25
>>> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>; win-pv-
>>> devel@xxxxxxxxxxxxxxxxxxxx
>>> Subject: Re: [win-pv-devel] No matching device was found when trying to
>>> install PV drivers
>>>
>>> On 28/09/16 15:36, Paul Durrant wrote:
>>> >> -----Original Message-----
>>> >> From: win-pv-devel [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx]
>>> >> On Behalf Of Nick Craig-Wood
>>> >> Sent: 28 September 2016 14:53
>>> >> To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
>>> >> Subject: [win-pv-devel] No matching device was found when trying to
>>> >> install PV drivers
>>> >>
>>> >> We've been trying to make the new PV drivers work under Xen 4.6.3
>>> >> (compiled from source) with Windows 2012R2
>>> >>
>>> >> When we try to install them the drivers can't find the device they
>>> >> are supposed to be attached to.  The Xen platform PCI device is
>>> >> visible in device manager.
>>> >>
>>> >
>>> > Ok, good :-)
>>> >
>>> >> This is trying with the 8.1 Release.
>>> >>
>>> >> C:\users\root\Downloads\xennet\x64> dir
>>> >>
>>> >>     Directory: C:\users\root\Downloads\xennet\x64
>>> >>
>>> >> Mode                LastWriteTime     Length Name
>>> >> ----                -------------     ------ ----
>>> >> -a---        22/07/2016     15:57     679840 dpinst.exe
>>> >> -a---        22/07/2016     15:57      10760 xennet.cat
>>> >> -a---        22/07/2016     13:35       9557 xennet.inf
>>> >> -a---        22/07/2016     13:35     544768 xennet.pdb
>>> >> -a---        22/07/2016     15:56      44448 xennet.sys
>>> >> -a---        22/07/2016     15:57     207776 xennet_coinst.dll
>>> >> -a---        22/07/2016     13:36    1789952 xennet_coinst.pdb
>>> >>
>>> >> C:\users\root\Downloads\xennet\x64> .\dpinst.exe /C
>>> >> INFO:   Option set: dumping log info to console.
>>> >> INFO:   Current working directory:
>>> 'C:\users\root\Downloads\xennet\x64'
>>> >> INFO:   Running on path 'C:\users\root\Downloads\xennet\x64'
>>> >> INFO:   No valid 'dpinst.xml' file provided.
>>> >> INFO:   Found driver package:
>>> >> 'C:\users\root\Downloads\xennet\x64\xennet.inf'.
>>> >> INFO:   Preinstalling
>>> 'c:\users\root\downloads\xennet\x64\xennet.inf' ...
>>> >> INFO:   ENTER:  DriverPackagePreinstallW
>>> >> SUCCESS:c:\users\root\downloads\xennet\x64\xennet.inf is
>>> preinstalled.
>>> >> INFO:   RETURN: DriverPackagePreinstallW  (0x0)
>>> >> INFO:   ENTER:  DriverPackageGetPathW
>>> >> INFO:   RETURN: DriverPackageGetPathW  (0x0)
>>> >> INFO:   ENTER:  DriverPackageInstallW
>>> >> INFO:   Installing INF file
>>> >> 'c:\users\root\downloads\xennet\x64\xennet.inf' (Plug and Play).
>>> >> INFO:   Looking for Model Section [Inst.NTamd64]...
>>> >> INFO:   No matching devices found in INF
>>> >>
>>> "C:\Windows\System32\DriverStore\FileRepository\xennet.inf_amd64_3d1
>>> >> 357c296dde9
>>> >> ff\xennet.inf" on the Machine.
>>> >> INFO:   No drivers installed. No devices found that match driver(s)
>>> >> contained in 'C:\Windows\System32\DriverStore\FileRe
>>> >> pository\xennet.inf_amd64_3d1357c296dde9ff\xennet.inf'.
>>> >> INFO:   RETURN: DriverPackageInstallW  (0xE000020B)
>>> >> INFO:   No matching device was found for
>>> >> 'c:\users\root\downloads\xennet\x64\xennet.inf'. Driver will be
>>> >> installed when plugged in.
>>> >> INFO:   Created entry in Add or Remove Programs for
>>> >>
>>> 'C:\Windows\System32\DriverStore\FileRepository\xennet.inf_amd64_3d1
>>> >> 357c296dde9ff\xennet.inf'.
>>> >>
>>> >
>>> > Have you installed XENBUS and XENVIF? XENBUS is the driver that
>>> binds to
>>> the platform PCI device and creates the virtual device for XENVIF to
>>> bind to
>>> which, in turn, creates the virtual device which XENNET binds to.
>>>
>>> Ah, I didn't realise there were dependencies between the drivers - I
>>> expect
>>> that is the problem :-)
>>>
>>> Is there a recommended order to load the drivers in?
>>>
>>
>> Not really, Windows should sort things out. If you just install XENBUS
>> and XENVIF in either order then XENNET should spring to life. Be aware
>> that you'll need a reboot after driver installation though, to allow
>> the emulated network device to be unplugged.
> 
> Thanks, that is very helpful.
> 
> I'll try that over the next couple of days and report back.

I just wanted to report back success!

Our image build process needed a bit of tweaking but loading XENBUS
first seemed to be the most important thing.

Thank you very much for your help

Nick
-- 
Nick Craig-Wood <nick@xxxxxxxxxxxxxx> -- http://www.craig-wood.com/nick

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel