From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: libxc linux privcmd bugs
Date: Mon, 13 Jan 2014 16:53:35 +0000
Message-ID: <52D41A0F.5030707@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Xen-devel List <xen-devel@lists.xen.org>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

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