similar to: How to mask an event channel?

Hi: I wanna write code about sharing memory between dom0 and domU, and I decide to use void *xc_map_foreign_range(int xc_handle, unint32_t dom, int size, int port, unsigned long mfn) (this is a function in xenctl.h). My question is : If I wanna map a range of memory in dom0 to domU, how can I　get the value of mfn? and I do not know the port here. Can anybody help me ? Thanks .

Hi: I wanna domU to map dom0''s page, so that these two domain can receive/send data between them in the future. But when I run my code , it told me that "Could not open grant table interface(22=invalid argument)". Can anybody know what the problem is ? Thanks . Danius Wu. ====== The Result of running my codes: [root@vm1 program]# gcc -g -Wall

Hi, Could anybody send me some code samples about how to use event channel (Dom0 and DomU, xenstore) and shared memory(grant table)? thanks a lot. Danius ========================================================================= _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi: There is a code sample in <The Definite Guide to the Xen Hypervisor>, chapter 4, "Using Grant Tables". The code sample is as following: #include <public/xen.h> extern void * shared_page; extern grant_entry_t * grant_table; void offer_page() { uint16_t flags; /* create the grant table*/ gnttab_setup_table_t setup_op;

Hi: I am now using shared memory( through xenstore) and event channel to communicate and send/receive data between Dom0 and DomU in my work. Though I read the Xen Developer''s Interface Manual so many times, I still do not know how to write the code. Can anybody show me the sample code or teach how to write it? Thanks a lot!

# HG changeset patch # User Brendan Cully <brendan@cs.ubc.ca> # Date 1220640849 25200 # Node ID 6e53036deb06fdbaa55489610ea8fc9c9b67ca64 # Parent 0eab1869ef6649878e7f2f5f5af534122aca3a4c Janitorial work on xc_save.c Remove an unused variable. Replace errx by warnx when cleanup code follows. diff --git a/tools/xcutils/xc_save.c b/tools/xcutils/xc_save.c --- a/tools/xcutils/xc_save.c +++

The original implementation utilies select(). In Linux select() typically supports up to 1024 file descriptors. This can be a problem when user tries to boot up many guests. Switching to poll() has minimum impact on existing code and has better scalibility. Up to 8192 file descriptors are supported in the current implementation. Signed-off-by: Wei Liu <wei.liu2@citrix.com> ---

Changes to libxc to enable easy access to the grant table device. Signed-off-by: Derek Murray <Derek.Murray@cl.cam.ac.uk> --- diff -r 809f36b1b685 tools/libxc/xc_linux.c --- a/tools/libxc/xc_linux.c Thu Mar 15 10:43:13 2007 +0000 +++ b/tools/libxc/xc_linux.c Thu Mar 15 17:46:06 2007 +0000 @@ -13,6 +13,7 @@ #include <xen/memory.h> #include <xen/sys/evtchn.h> +#include

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

To allow xenguest consumers to also make use of the extra protection added as a result of xsa-25. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> diff -r 5af4f2ab06f3 -r daec50a41570 tools/libxc/xenguest.h --- a/tools/libxc/xenguest.h +++ b/tools/libxc/xenguest.h @@ -177,6 +177,13 @@ int xc_dom_linux_build(xc_interface *xch unsigned int console_evtchn, unsigned

Hi, All Intel QA conducted a full validation for xen 4.1 rc1, it includes VT-x, VT-d, SRIOV, RAS, TXT and xl tools testing. 24 issues were exposed. Refer the bug list, please. We already assigned 14 bugs to Intel developers (which has an ''Intel'' tag in the bug title), most of the rest 10 bugs are related xl command. For the these bugs, need community''s help to fix

Where is the code that maps the kernel of a DomU into memory? i.e, when you do a xm create <config file> what code is called to actually map the kernel into memory? Is it a python script or is it re-directed to Dom0 to do? Thanks. -Brian --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

Where is the code that maps the kernel of a DomU into memory? i.e, when you do a xm create <config file> what code is called to actually map the kernel into memory? Is it a python script or is it re-directed to Dom0 to do? Thanks. -Brian --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

This patch series introduces the shared ring used by the front-end to pass request descriptors to tapdisk, as well as responses from tapdisk to the front-end. Requests from this ring end up in tapdisk''s standard request queue. When the tapback daemon detects that the front-end tries to connect to the back-end, it spawns a tapdisk and tells it to connect to the shared ring. The shared

Hi all, this is the long awaited patch series to add xen device model support in qemu; the main author is Anthony Perard. Developing this series we tried to come up with the cleanest possible solution from the qemu point of view, limiting the amount of changes to common code as much as possible. The end result still requires a couple of hooks in piix_pci but overall the impact should be very

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

Signed-off-by: Scott Seago <sseago at redhat.com> --- AUTHORS | 17 ++++++ README | 10 +++ conf/ovirt-agent | 12 ++++ conf/ovirt-db-omatic | 12 ++++ conf/ovirt-host-browser | 12 ++++