search for: gnttab_max_frames

...rote: > > According to that link, the fix seems to be configuration rather than > > code. > > Does this mean this bug against the kernel should be closed? > > Yes, the problem seems to be in the Xen hypervisor and not the Linux > kernel itself. The default value for the gnttab_max_frames parameter > needs to be increased to avoid domU disk IO hangs, for example: > > GRUB_CMDLINE_XEN="dom0_mem=10240M gnttab_max_frames=256" > > So either close the bug or reassign it to xen-hypervisor package so > they can increase the default value for this parameter i...

...why +deb9u11 is affected while +deb9u10 is not. I'm afraid increasing the gnttab max size to 32 might just defer filling it up. > -# ./xen-diag gnttab_query_size 5 > domid=5: nr_frames=11, max_nr_frames=32 The current value is 31 over max 32 indeed. > With Xen 4.8, you can add gnttab_max_frames=64 (or another number, but > higher than the default 32) to the xen hypervisor command line and reboot. admin@: I made the modification in the grub config. We can probably try to reboot with the newer hypervisor, and monitor that value. Samuel

...ying and recreating them (far from ideal!). After a bit of research and digging around, we eventually found these 2 nuggets: https://wiki.gentoo.org/wiki/Xen#Xen_domU_hanging_with_kernel_4.3.2B https://www.novell.com/support/kb/doc.php?id=7018590 They both advise adding the command line argument: gnttab_max_frames=256(the default is 32). We applied this change and all hypervisors rand stable for around a week until DomU's started freezing again (we've since tried even higher values, to no avail). More research later led me to https://bugs.centos.org/view.php?id=14258 and https://bugs.centos.org/view....

...fected by the > lack of grant entry. I suspect that 31 measurement was taken when the domU was not hanging yet. > If to increase the max frame to 64 takes effect, it is weird why the I/O would > hang when there are still 512 entries available. > >>> With Xen 4.8, you can add gnttab_max_frames=64 (or another number, but >>> higher than the default 32) to the xen hypervisor command line and reboot. >> >> admin@: I made the modification in the grub config. We can probably try >> to reboot with the newer hypervisor, and monitor that value. K

Hi, On 10/23/18 7:34 PM, Ian Jackson wrote: > Control: retitle -1 max grant frames problem (domu freeze with linux-image-4.9.0-4-amd64) > Control: severity -1 important > Control: reassign -1 src:xen 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 my last comment in this bts bug was about: