Re: [win-pv-devel] [Xen-devel] PVL XenNet inf

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: win-pv-devel [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On
> Behalf Of Dominic Russell
> Sent: 11 May 2016 14:53
> To: Paul Durrant
> Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [win-pv-devel] [Xen-devel] PVL XenNet inf
> 
> The PDO that Windows shows is the one I mentioned, therefore it does not
> bind automatically.  How can I make the PDO appeared the first time as
> it should?
> 
> xenvif does not load, Windows returns an error 10.

Ok, so that's your problem. Messing with INF files is never the answer.

Did you build all the drivers yourself? The usual reason for XENVIF failing to 
load is that it's not compatible with the version of XENBUS you have installed.

> 
> How can I get QEMU logs?
> 

What QEMU are you running in dom0? Did you build your Xen installation yourself?

  Paul

> Cordialement,
> Dominic Russell
> MSI Bureautique inc.
> 
> Le 2016-05-11 à 05:41, Paul Durrant a écrit :
> > De-htmling... Please send emails in plain text.
> >
> > ---
> > From: Dominic Russell [mailto:dominic@xxxxxxxxxxxxxxxxx]
> > Sent: 10 May 2016 20:35
> > To: Paul Durrant
> > Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [win-pv-devel] [Xen-devel] PVL XenNet inf
> >
> > Hello,
> > For the device IDs, it is only by modifying the IDs in the inf file that
> Windows was assigning the xennet drivers to the network card automatically,
> otherwise they have to be assigned manually.
> > ---
> >
> > As I tried to explain. The PDO to which you are trying to attach XENNET is
> the wrong one. By modifying the IDs in the INF file you may be able to get
> the driver to bind, but there's no way it's going to function. The PDO you are
> looking at (XENBUS\VEN_XP0001&DEV_VIF&REV_08000009) is the one that
> the XENVIF driver should bind to. It will then create PDOs of the form
> XENVIF\VEN_XP0001&DEV_NET&REV_08000009 whicn XENNET will then bind
> to.
> >
> > ----
> > I did clean the GPLPV drivers, but the xenpci is hard to remove, because
> Windows treats it as a critical, boot needed, driver, so not all the keys are
> accessible to be deleted in the registry.
> > The new xenbus driver is active, and xenpci does not appear in the files 
> > list
> of the loaded files in the driver of the peripherals (at first, I was not 
> cleaning
> properly xenpci, and it was appearing as a loaded file for the xenbus and
> xennet drivers).  To be sure, I deleted the xenpci.sys and rebooted, it
> rebooted properly, otherwise it would give a blue screen with error 7B.
> > On the virtual computer, every new drivers are loaded, not reporting errors
> except for xennet, that returns an error 10.  I discovered in Windows logs a
> generic error (but not tagged as an error) which mentions
> PnpDeviceProblemCode, which by googling did not reveal much.
> > ----
> >
> > Is XENVIF loaded and functioning? Do you have a log from QEMU?
> >
> >    Paul
> 
> 
> _______________________________________________
> 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