Re: [win-pv-devel] Windows 10 domU is unstable with PV Bus Driver

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: win-pv-devel [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On
> Behalf Of Michel D'HOOGE
> Sent: 15 December 2017 09:01
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [win-pv-devel] Windows 10 domU is unstable with PV Bus Driver
> 
> Hi Paul,
> 
> Me again :'-(
> After what seemed a Windows10 update, the problem is back...
> 
> > Setting to 128 should give you enough head-room for a few multi-page
> storage rings and multi-queue networks.
> 
> Is it possible that 128 isn't enough, or does-it mean that there is a
> *real* problem?

Michel,

  The log below shows you are still running out of space, even with 128 grant 
frames so you're going to either need more or scale back some of your PV 
interfaces.

> 
> Note that after first time the problem re-appeared, I upgraded to
> version 2017-12-05 of xenbus and version 2017-12-07 of xenvbd. But
> with no changes.
> 
> I'm considering uninstalling xenvbd and live without it. But if you
> want me to do some tests before...
> 

  The problem is not necessarily xenvbd per se; it is trying to make full use 
of your backend's capability. I can only assume things worked for you before 
the frontend update because you were getting close to the limit but not quite 
exceeding it (because of timing or the frontends not trying to fill the rings 
so much). There is the possibility of a reference leak though so could you try 
increasing your grant frame limit again and see if things stabilise?

  Cheers,

    Paul

> Thanks for your help
> Michel
> 
> 
> I you wish I can provide you with full (zipped) logs -- I don't think
> there is something to anonymise in them.
> 
> 
> Here is the content of xl-win10.log
> ----
> Waiting for domain win10 (domid 1) to die [pid 21203]
> Domain 1 has shut down, reason code 1 0x1
> Action for shutdown reason code 1 is preserve
> Done. Exiting now
> ---
> 
> And an excerpt of qemu-dm-win10.log
> ---
> GNTTAB: MAP XENMAPSPACE_grant_table[124] @ 00000000.f207d000
> XENBUS|GnttabExpand: added references [0000f800 - 0000f9ff]
> XENBUS|RangeSetPop: fail2
> XENBUS|RangeSetPop: fail1 (c000009a)
> GNTTAB: MAP XENMAPSPACE_grant_table[125] @ 00000000.f207e000
> XENBUS|GnttabExpand: added references [0000fa00 - 0000fbff]
> XENBUS|RangeSetPop: fail2
> XENBUS|RangeSetPop: fail1 (c000009a)
> GNTTAB: MAP XENMAPSPACE_grant_table[126] @ 00000000.f207f000
> XENBUS|GnttabExpand: added references [0000fc00 - 0000fdff]
> XENBUS|RangeSetPop: fail2
> XENBUS|RangeSetPop: fail1 (c000009a)
> GNTTAB: MAP XENMAPSPACE_grant_table[127] @ 00000000.f2080000
> XENBUS|GnttabExpand: added references [0000fe00 - 0000ffff]
> XENBUS|RangeSetPop: fail2
> XENBUS|RangeSetPop: fail1 (c000009a)
> XENBUS|GnttabExpand: fail1 (c000009a)
> XENBUS|GnttabEntryCtor: fail1 (c000009a)
> XENBUS|CacheCreateObject: fail2
> XENBUS|CacheCreateObject: fail1 (c000009a)
> XENBUS|GnttabPermitForeignAccess: fail1 (c000009a)
> XENVBD|GranterGet:fail2
> XENVBD|GranterGet:fail1 c000009a
> XENBUS|RangeSetPop: fail2
> XENBUS|RangeSetPop: fail1 (c000009a)
> XENBUS|GnttabExpand: fail1 (c000009a)
> XENBUS|GnttabEntryCtor: fail1 (c000009a)
> XENBUS|CacheCreateObject: fail2
> XENBUS|CacheCreateObject: fail1 (c000009a)
> XENBUS|GnttabPermitForeignAccess: fail1 (c000009a)
> XENVBD|GranterGet:fail2
> ---
> 
> And I see nothing special in xenstored-access.log.
> 
> _______________________________________________
> win-pv-devel mailing list
> win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/win-pv-devel
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/win-pv-devel