search for: map_frontend_pages

I''m having problems starting more than three domains. It sometimes works fine, but more often than not the 4th domain''s root block device times out and so the domU kernel panics as there''s no /dev/root: XENBUS: Timeout connecting to device: device/vbd/2057 (state 6) XENBUS: Timeout connecting to device: device/vif/0 (state 6) XENBUS: Timeout connecting to device:

This is a cherry pick of two patches that add support for guest paged out frames in the XCP 2.6.32 dom0 patch queue. First patch propagates the ENOENT returned by the hypervisor in the case of a paged out page, all the way up the call chain to the MMAPBATCH_V2 ioctl. The ioctl is mainly used to harvest those return values and retry. The second patch adds retry loops to all backend grant

...ool.h> #include <linux/rtnetlink.h> #include <linux/delay.h> +#include <linux/vmalloc.h> +#include <xen/evtchn.h> /* * Module parameter ''queue_length'': @@ -298,65 +300,11 @@ netif_t *netif_alloc(struct device *pare return netif; } -static int map_frontend_pages( - netif_t *netif, grant_ref_t tx_ring_ref, grant_ref_t rx_ring_ref) -{ - struct gnttab_map_grant_ref op; - - gnttab_set_map_op(&op, (unsigned long)netif->tx_comms_area->addr, - GNTMAP_host_map, tx_ring_ref, netif->domid); - gnttab_check_GNTST_eagain_do_while(GNTTABOP_map_grant_ref...

Patrick, there following patches fix xenpaging for me. Granttable handling is incomplete. If a page is gone, a GNTST_eagain should be returned to the caller to inidcate the hypercall has to be retried after a while, until the page is available again. Please review. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

We have found a critical problem with the XEN 3.1 release (for those who are running 15-20 VMs on a single server). We are using the official XEN 3.1 release on a rackable server (Dual-Core AMD Opteron, 8GB RAM). The problem we are seeing is that intermittently vifs fail to work properly in VMs after we create around 15-17 VMs on our server (all running at the same time, created one by

When I read the blkfront.c and blkback.c, I noticed that in some places (e.g, map_frontend_page()) it uses alloc_vm_area() to allocate memory for foreign page mapping. However, in some other places, it used balloon_alloc_empty_page_range() to allocate memory for mapping. What''s the difference between these two functions? Why not just use one function like alloc_vm_area() or

pvSCSI backend driver Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel