From: Mick Jordan <mick.jordan@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Help with 3.4.x compilation problem
Date: Thu, 29 Apr 2010 19:58:44 -0700 [thread overview]
Message-ID: <4BDA4764.2070808@oracle.com> (raw)
In-Reply-To: <C7FEC902.11726%keir.fraser@eu.citrix.com>
On 04/29/10 05:26 AM, Keir Fraser wrote:
> You need -I/import/xen/xen-3.4.2/tools/include in your CFLAGS, and at some
> point previously you need to have done 'make' inside that directory, in
> order to have set up the necessary symlinks.
>
Thanks, that fixed the problem.
Now I have a follow-on question. Is there any support for privileged
domUs in Xen 3.4.0, in the sense of writing to another domain's xenstore
tree? The tool I want to use (a cross-domain Java VM debugger) needs to
be 64-bit, so it can't run in my current dom0, which is 32-bit. In my
previous Solaris xVM dom0/Linux domU world, I used to hack Xen and
remove the xenstore permission checks, but I'd really rather not do that
again.
Mick
prev parent reply other threads:[~2010-04-30 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 1:11 Help with 3.4.x compilation problem Mick Jordan
2010-04-29 12:26 ` Keir Fraser
2010-04-30 2:58 ` Mick Jordan [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=4BDA4764.2070808@oracle.com \
--to=mick.jordan@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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).