On Fri, Aug 04, 2017 at 05:36:29PM +0800, Dongli Zhang wrote:
>
>
> On 08/04/2017 05:13 PM, Roger Pau Monné wrote:
> > On Fri, Aug 04, 2017 at 10:00:09AM +0200, Valentin Vidic wrote:
> >> On Mon, Jul 31, 2017 at 09:09:19AM +0800, Dongli Zhang wrote:
> >>> To verify whether the above patch would
On 08/04/2017 05:13 PM, Roger Pau Monné wrote:
> On Fri, Aug 04, 2017 at 10:00:09AM +0200, Valentin Vidic wrote:
>> On Mon, Jul 31, 2017 at 09:09:19AM +0800, Dongli Zhang wrote:
>>> To verify whether the above patch would help, please check the
>>> nr_grant_frames
>>> value in guest domU. If
On Fri, Aug 04, 2017 at 10:00:09AM +0200, Valentin Vidic wrote:
> On Mon, Jul 31, 2017 at 09:09:19AM +0800, Dongli Zhang wrote:
> > To verify whether the above patch would help, please check the
> > nr_grant_frames
> > value in guest domU. If this value is exactly the same of maximum grant
> >
On Mon, Jul 31, 2017 at 09:09:19AM +0800, Dongli Zhang wrote:
> To verify whether the above patch would help, please check the nr_grant_frames
> value in guest domU. If this value is exactly the same of maximum grant frames
> (by default, xen mainline uses 32) and the number of free grant
Here are the options:
1. Dump a vmcore of guest and print nr_grant_frames with crash utility.
2. Implement a kernel module in guest to dump nr_grant_frames if you still have
access to your hung guest domU.
3. There is a new utility in xen toolstack at tools/misc/xen-diag.c to dump
grant table
CCed xen-devel so that more people would be able to help.
Dongli Zhang
On 07/31/2017 09:09 AM, Dongli Zhang wrote:
> Hi Valentin,
>
> On 07/30/2017 03:42 PM, Valentin Vidic wrote:
>> I'm having a problem with a domU hang in disk IO, described here:
>>
>>
