From: Jonathan Creekmore <jonathan.creekmore@gmail.com>
To: Dagaen Golomb <dgolomb@seas.upenn.edu>
Cc: Doug Goldstein <cardoe@cardoe.com>,
Meng Xu <xumengpanda@gmail.com>,
xen-devel@lists.xen.org
Subject: Re: Problem Reading from XenStore in DomU
Date: Mon, 16 May 2016 08:12:59 -0500 [thread overview]
Message-ID: <m28tzadu3o.fsf@Nebula.lan> (raw)
In-Reply-To: <CALcuvThiSjwARNQS=wb8Y3EvYbOVohC8yoi-CSXd8ZyDvpHAXw@mail.gmail.com>
Dagaen Golomb writes:
> It does, being the custom kernel on version 4.1.0. But Dom0 uses this same
> exact kernel and reads/writes just fine! The only solution if this is
> indeed the problem appears to be changing the kernel source we build on or
> some hacky method such as symlinking /proc/.. to /dev/.., there has to be
> an elegant real solution to this...
When I was chasing down a similar problem back in August, I discovered
that Dom0 accesses XenStore through a unix domain socket and not through
the kernel interface, so hitting it through xenstore-ls always seemed to
work. That is why Dom0 reads/writes to XenStore ok with the same kernel
that fails for your DomU. When I moved XenStore to a stubdomain, I /did/
see the problem in Dom0 with new enough kernels, which is why the
XenStore access library was changed to prefer the dev device instead of
the proc file.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-16 13:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 16:40 Problem Reading from XenStore in DomU Dagaen Golomb
2016-05-15 17:04 ` Andrew Cooper
2016-05-15 19:54 ` Dagaen Golomb
2016-05-15 19:59 ` Dagaen Golomb
2016-05-15 20:35 ` Meng Xu
2016-05-15 21:11 ` Dagaen Golomb
2016-05-15 23:47 ` Dagaen Golomb
2016-05-16 1:21 ` Doug Goldstein
2016-05-16 1:28 ` Dagaen Golomb
2016-05-16 1:31 ` Doug Goldstein
2016-05-16 1:41 ` Dagaen Golomb
2016-05-16 3:15 ` Meng Xu
[not found] ` <CALcuvTjPpPQs5=i5uWvO2x_Krm-3j7u867yw4y1iWDNV7J83NA@mail.gmail.com>
[not found] ` <CALcuvTjfh4J8y0B_4GaajcgYQKvUJA3VFBrLFSq0HOVdWSyf0w@mail.gmail.com>
2016-05-16 3:30 ` Dagaen Golomb
2016-05-16 3:57 ` Meng Xu
2016-05-16 9:52 ` Andrew Cooper
2016-05-16 13:12 ` Jonathan Creekmore [this message]
2016-05-16 13:16 ` Dagaen Golomb
2016-05-16 15:55 ` Doug Goldstein
2016-05-16 16:03 ` Dagaen Golomb
2016-05-16 16:11 ` Dagaen Golomb
2016-05-16 16:20 ` Dagaen Golomb
2016-05-16 19:12 ` Doug Goldstein
2016-05-16 19:52 ` Dagaen Golomb
2016-05-16 19:56 ` Dagaen Golomb
2016-05-16 20:18 ` Dagaen Golomb
2016-05-16 22:25 ` Doug Goldstein
2016-05-16 22:29 ` Dagaen Golomb
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=m28tzadu3o.fsf@Nebula.lan \
--to=jonathan.creekmore@gmail.com \
--cc=cardoe@cardoe.com \
--cc=dgolomb@seas.upenn.edu \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.com \
/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.