search for: libvchan

Hi, Header says: /* * Unmaps the @count pages starting at @start_address, which were mapped by a * call to xc_gntshr_share_*. Never logs. */ int xc_gntshr_munmap(xc_gntshr *xcg, void *start_address, uint32_t count); But implementation calls: static int linux_gntshr_munmap(xc_gntshr *xcg, xc_osdep_handle h, void *start_address, uint32_t count) { return

Hi, I am trying to run libvchan on ARM Fast Model for VExpress platform for using inter domain communication. But there are some errors. I am attaching the strace outputs for vchan-node1 run in dom0 and domU. Has anybody faced these issues before. Xl console 1The command is Usage: vchan-node1 [client|server] [write|read] domid...

Can the XenStore database be accessed by domU''s? If so, could it be used to pass small amounts of data back and forth between dom0 and domU''s using XenStore key entries? If this is possible, it would seem that this could eliminate the need to create a "device" driver for a simple communication path. Also, what type of Guest Fedora Kernel would be needed to

...in vhd_journal_write_entry tools/blktap2: fix out of bounds access in block-log.c tools/blktap2: fix build errors caused by Werror in tdqcow_get_parent_id tools/blktap2: remove unneeded pointer dereferencing from img2qcow.c tools/blktap2: remove unneeded pointer dereferencing from qcow2raw.c tools/libvchan: fix function prototypes in node-select.c tools/memshr: fix build errors caused by Werror tools/xenpaging: fix build errors caused by -Werror tools/libvchan: fix build errors caused by Werror in io.c tools/blktap2: remove static string table from header file tools/blktap2: fix build errors caused b...

Added two new sets of compile flags, and pass them to the check scripts, so libraries and includes are searched there also. Resend this patches because they suffered some modifications and where scattered along the mailing list. Please review, thanks Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am new to Xen and want to provide simple communication between my DomU and Dom0 environments. I just need to be able to pass a few bytes of information back and forth between DomU and Dom0 while using some form of event management to know when an update occurs so I can act on it. At first, it appeared that using XenBus and XenStore might be the right solution for this. However, after looking

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

Hey Keir, I committed the last of the big outstanding tools blockers for 4.2 yesterday. Currently they are still in staging because they added some new xenstore paths which tickled the leak detector in the test system What do you think of doing an rc0 release next week? There''s still some smaller issues remaining but I think they can wait until rc1. Ian.

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *