From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: cooldharma06 <cooldharma06@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: XEN: Interdomain communication.
Date: Tue, 20 Aug 2013 09:49:01 -0400 [thread overview]
Message-ID: <521373CD.1070907@tycho.nsa.gov> (raw)
In-Reply-To: <CAJ4UyV36U2_6EdYf-Txxr1nwnuwKGWTkq5R4TMpH7MEB0+jhQg@mail.gmail.com>
On 08/20/2013 06:44 AM, cooldharma06 wrote:
> hi all,
>
> i am experimenting interdomain communication between dom0 and domU in
> xen-4.2.1.
>
> in domU i copied required libraries and also xenfs is mounted.
>
> but in /dev/xen i have only gntdev file. but we have evtchn, gntalloc files
> for communication. how i can make(create) those files for domU.
Load the kernel modules for these files (xen-evtchn and xen-gntalloc).
You may also need to select a xenstore path with the proper permissions, as Ian
suggested in his emails. You could also use xenstore-mkdir and xenstore-chmod
in dom0 if you have a need to use a specific xenstore path.
The vchan-node2 tool may be more friendly to testing since it is bidirectional
while vchan-node1 forces you to specify read/write on each end.
> Information regarding to the communication as follows:
> 1. In ldd vchan-node1 shows following outputs:
[...]
> and when running that one it shows:
> libxenvchan_*_init: No such file or directory
>
> 2. The files under /dev/xen/ folder in domU is : gntdev
>
> 3. The files under /proc/xen/ folder in domU is : capabilities xenbus
>
> Please guide me to achieve the communication.
>
> regards,
> cooldharma06.
--
Daniel De Graaf
National Security Agency
prev parent reply other threads:[~2013-08-20 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 10:44 XEN: Interdomain communication cooldharma06
2013-08-20 13:07 ` Ian Campbell
[not found] ` <CAJ4UyV0TLBqx8y5Gat3_iMA1Oar1wL-fxUyXAHTDHYqh99ziLg@mail.gmail.com>
2013-08-20 13:26 ` Fwd: " cooldharma06
2013-08-20 13:37 ` Ian Campbell
2013-08-20 13:49 ` Daniel De Graaf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521373CD.1070907@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=Ian.Campbell@citrix.com \
--cc=cooldharma06@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.