From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: libxc linux privcmd bugs
Date: Mon, 13 Jan 2014 16:53:35 +0000 [thread overview]
Message-ID: <52D41A0F.5030707@citrix.com> (raw)
Hello,
More bugs for tracking:
1) PERROR("Could not obtain handle on privileged command interface");
doesn't indicate which path(s) were tried.
2) xc_linux_osdep.c:linux_privcmd_open() only tries to open
"/proc/xen/privcmd" which is the classic-xen location, whereas the
expected location under PVops is "/dev/xen/privcmd". The other open
functions (evtchn, gnttab, gntshr) exclusivly use "/dev/xen/$FOO".
~Andrew
next reply other threads:[~2014-01-13 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:53 Andrew Cooper [this message]
2014-01-13 17:06 ` libxc linux privcmd bugs Ian Campbell
2014-01-13 17:06 ` Ian Campbell
2014-01-13 17:15 ` Processed: " xen
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=52D41A0F.5030707@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.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.