xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dagaen Golomb <dgolomb@seas.upenn.edu>
To: xen-devel@lists.xen.org
Subject: Problem Reading from XenStore in DomU
Date: Sun, 15 May 2016 12:40:47 -0400	[thread overview]
Message-ID: <CALcuvTi9vOE7EZafGicNy-G4FX7O9X406bMBgzwJwDMN__0OTQ@mail.gmail.com> (raw)

Hi All,

I'm having an interesting issue. I am working on a project that
requires me to share memory between dom0 and domUs. I have this
successfully working using the grant table and the XenStore to
communicate grefs.

My issue is this. I have one domU running Ubuntu 12.04 with a default
3.8.x kernel that has no issue reading or writing from the XenStore.
My work also requires some kernel modifications, and we have made
these changes in the 4.1.0 kernel. In particular, we've only added a
simple hypercall. This modified kernel is what dom0 is running, on top
of Xen 4.7 rc1.

The guest I mentioned before with the default kernel can still read
and write the XenStore just fine when on Xen 4.7 rc1 and with dom0
running our kernel.

The issue I'm having is with another newly created guest (i.e., it is
not a copy of the working one, this is because I needed more space and
couldn't expand the original disk image). It is also running Ubuntu
12.04 but has been upgraded to our modified kernel. On this guest I
can write to the XenStore, and see that the writes were indeed
successful using xenstore-ls in dom0. However, when this same guest
attempts to read from the XenStore, it doesn't return an error code
but instead just blocks indefinitely. I've waiting many minutes to
make sure its not just blocking for a while, it appears like it will
block forever. The block is happening when I start the transaction.
I've also tried not using a transaction, in which case it blocks on
the read itself.

I have an inkling this may be something as simple as a configuration
issue, but I can't seem to find anything. Also, the fact that writes
work fine but reads do not is perplexing me.

Any help would be appreciated!

Regards,
Dagaen Golomb
Ph.D. Student, University of Pennsylvania

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2016-05-15 16:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15 16:40 Dagaen Golomb [this message]
2016-05-15 17:04 ` Problem Reading from XenStore in DomU 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
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=CALcuvTi9vOE7EZafGicNy-G4FX7O9X406bMBgzwJwDMN__0OTQ@mail.gmail.com \
    --to=dgolomb@seas.upenn.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).