libxc linux privcmd bugs

libxc linux privcmd bugs

[Andrew Cooper]

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

Re: libxc linux privcmd bugs

[Ian Campbell]

create ^
title it libxc should use /dev/xen/privcmd on Linux
severity it wishlist
thanks

On Mon, 2014-01-13 at 16:53 +0000, Andrew Cooper wrote:
> 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".

Nothing has ever used /dev/xen/privcmd since it was reimplemented to
replace xenfs, so describing it as expected is a bit strong. At best
there is a wishlist issue here for someone to finish implementing this
transition, which I've now created.

http://lists.xen.org/archives/html/xen-devel/2011-12/msg01344.html
http://lists.xen.org/archives/html/xen-devel/2011-12/msg01345.html
looks to be related patches, not sure why thay didn't go in back then.
Lack of a S-o-b perhaps.

>   The other open
> functions (evtchn, gnttab, gntshr) exclusivly use "/dev/xen/$FOO".

These have only ever been driver rather than proc based so there was
never a transition.

Ian.

Re: libxc linux privcmd bugs

[Ian Campbell]

create ^
title it libxc should use /dev/xen/privcmd on Linux
severity it wishlist
thanks

On Mon, 2014-01-13 at 16:53 +0000, Andrew Cooper wrote:
> 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".

Nothing has ever used /dev/xen/privcmd since it was reimplemented to
replace xenfs, so describing it as expected is a bit strong. At best
there is a wishlist issue here for someone to finish implementing this
transition, which I've now created.

http://lists.xen.org/archives/html/xen-devel/2011-12/msg01344.html
http://lists.xen.org/archives/html/xen-devel/2011-12/msg01345.html
looks to be related patches, not sure why thay didn't go in back then.
Lack of a S-o-b perhaps.

>   The other open
> functions (evtchn, gnttab, gntshr) exclusivly use "/dev/xen/$FOO".

These have only ever been driver rather than proc based so there was
never a transition.

Ian.

Processed: Re: libxc linux privcmd bugs

[xen]

Processing commands for xen@bugs.xenproject.org:

> create ^
Created new bug #34 rooted at `<52D41A0F.5030707@citrix.com>'
Title: `Re: libxc linux privcmd bugs'
> title it libxc should use /dev/xen/privcmd on Linux
Set title for #34 to `libxc should use /dev/xen/privcmd on Linux'
> severity it wishlist
Change severity for #34 to `wishlist'
> thanks
Finished processing.

Modified/created Bugs:
 - 34: http://bugs.xenproject.org/xen/bug/34 (new)

---
Xen Hypervisor Bug Tracker
See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs
Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues