From: Francisco Rocha <f.e.liberal-rocha@newcastle.ac.uk>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen-unstable libvchan not working
Date: Wed, 25 Apr 2012 15:26:45 +0100 [thread overview]
Message-ID: <4F9809A5.9010309@newcastle.ac.uk> (raw)
In-Reply-To: <4F9803BB.8060106@newcastle.ac.uk>
On 04/25/2012 03:01 PM, Francisco Rocha wrote:
> Hi everyone,
>
> I have a machine that have built earlier this year and
> libvchan works correctly.
> Now, I am trying to build a new one but it doesn't work.
>
> I have used the latest xen-unstable.
> When I try the vchan-node2 test application I get:
>
> (guest 1 is the server and guest 2 the client)
>
> # ./vchan-node2 server 1 /local/domain/1/data/vchan-1-2
> libxenvchan_*_init: No such file or directory
>
> I thought it could be the directory in xenstored so I created it
> manually but the error persists.
>
> Anyone has came across this problem?
I have added some tracing to see which part of the init was
failing. It looks like it is xc_evtchn_open. What can cause
this to fail?
>
> I have all the required modules and libraries running in
> the guests:
> # lsmod | grep xen
> xen_gntalloc 5536 0
> xen_gntdev 9019 0
> xen_evtchn 5032 0
> xen_kbdfront 4149 0
> xen_netfront 16358 0
> xenfs 9621 1
> xen_blkfront 12741 3
> # mount | grep xen
> none on /proc/xen type xenfs (rw,relatime)
>
> # ls /usr/lib64/ | grep xen
> libxenctrl.a
> libxenctrl.so
> libxenctrl.so.4.2
> libxenctrl.so.4.2.0
> libxenstore.a
> libxenstore.so
> libxenstore.so.3.0
> libxenstore.so.3.0.0
> libxenvchan.a
> libxenvchan.so
> libxenvchan.so.1.0
> libxenvchan.so.1.0.0
>
> Cheers,
> Francisco
prev parent reply other threads:[~2012-04-25 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:01 xen-unstable libvchan not working Francisco Rocha
2012-04-25 14:26 ` Francisco Rocha [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=4F9809A5.9010309@newcastle.ac.uk \
--to=f.e.liberal-rocha@newcastle.ac.uk \
--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.