search for: gnttab_query_size

...toms of running out of "grant frames". Oh! That could be it indeed. I'm wondering what could be monopolizing them, though, and 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 con...

...t;> Oh! That could be it indeed. I'm wondering what could be monopolizing >> them, though, and 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. > > Assuming this is grant v1, there are still 4096/8=512 grant references available > (32-31=1 frame available). I do not think the I/O hang can be affected by the >...

...#39;m wondering what could be monopolizing >>>> them, though, and 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. >>> >>> Assuming this is grant v1, there are still 4096/8=512 grant references available >>> (32-31=1 frame available). I do not...

...' bus='xen'/> <input type='keyboard' bus='xen'/> <memballoon model='xen'/> </devices> <controller type='xenbus' index='0' maxGrantFrames='128'/> </domain> I dont get an error but: xen-diag gnttab_query_size 20 domid=20: nr_frames=8, max_nr_frames=32 thats wrong max_nr_frames should be 128 Am 2019-04-26 11:47, schrieb Pavel Hrdina: > On Fri, Apr 26, 2019 at 11:25:13AM +0200, Christoph wrote: > > What is the error message that you get? > > Pavel -- ------ Greetz

Hi libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). I get ever an error if I use it in the config: <domain type='xen'> <name>satan.chao5.int</name> <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory>

Hi Jeremy. According to your suggestion, I recreated patches for Ingo's x86.git tree. And this patch series includes Eddie's modification. Please review and forward them. (or push back to respin.) Recently the xen-ia64 community started to make efforts to merge xen/ia64 Linux to upstream. The first step is to merge up domU portion. This patchset is preliminary for xen/ia64 domU linux

Hi Jeremy. According to your suggestion, I recreated patches for Ingo's x86.git tree. And this patch series includes Eddie's modification. Please review and forward them. (or push back to respin.) Recently the xen-ia64 community started to make efforts to merge xen/ia64 Linux to upstream. The first step is to merge up domU portion. This patchset is preliminary for xen/ia64 domU linux

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. This patchset does the followings. - Some preparation work. Mainly importing header files to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. This patchset does the followings. - Some preparation work. Mainly importing header files to

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.