Re: [win-pv-devel] xen net/vif (signed 8.2.0.6) "code 10" / win7

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Martin Cerveny [mailto:martin@xxxxxxxxx]
> Sent: 08 January 2018 17:30
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [win-pv-devel] xen net/vif (signed 8.2.0.6) "code 10" / win7
> 
> Hello.
> 
> Captured/attached "boot" debugview:
> - when OK
> - when "xen-network dialog popup say restart needed"
> - when failed
> 

Thanks Martin. Much more useful...

From the failure case I can see that your guest is running out of grant 
references. I suspect that, what has happened is you've upgraded your backend 
OS and suddenly multi-page storage rings have become available in blkback. Your 
XENVBD driver is then making use of those and stealing most of your VM's grant 
references. XENVIF is then starting up and finding it doesn't have sufficient 
grant references to operate correctly and is therefore failing to start.

You have a couple of choices... Either increase your VM's grant frame limit 
(see man xl.cfg for new per-vm parameters in Xen 4.10) or limit your storage 
backend's rings to a lower number of pages (see modinfo xen-blkback and look 
for max_ring_page_order... I suggest setting to 0).

  Cheers,

    Paul

> On Mon, 8 Jan 2018, Paul Durrant wrote:
> >> -----Original Message-----
> >> Any more log to check ?
> >> Is it known bug ?
> >> Is there any workaround (besides uninstalling pv-net drivers) ?
> >> Is it related to pv-bus driver discussion ?
> >
> >  There's no apparent failure in any of the logs that I can see. Does the
> debugview.log cover the failed driver install? I only see one successful 
> start in
> there so, if it does cover the failure, then it suggest that Windows actually
> made no attempt to start XENNET. Is there anything interesting in
> setupapi.dev.log?
> 
> I think that it is not install related (I tried 2x uninstall/install pv
> drives) and tied +-3 different VMs.
> Found many logs in setupapi.dev.log but does not seems to be failed (or
> timestamped with correlation to boot with failed drivers (unchanged from
> last install)).
> 
> >> When will new/next/repaired signed drivers be released ?
> >
> >  I'm chasing a weird issue with timer in Windows at the moment (which
> may be a Xen bug) and I'd like to understand that before signing 8.2.1. We
> also do not yet have a fully clean WHQL run on 8.2.1 XENNET.
> >  Another thing to try, if you can, would be an older dom0 kernel (or at 
> > least
> an older netback). It sounds like a bug has crept in so you may be falling
> victim to that.
> 
> Hmm, it may be possible. I am not sure but the problem could be appearing
> after upgrade from Xen4.8.0 + 4.7.9-200.fc24 to Xen4.10.0 + 4.13.9-300.fc27.
> But unable to rollback now.
> 
> Thanks, Martin

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