On Wed, Feb 03, Wei Liu wrote:
> If it is to be removed, why don't you just filter it out and not have it
> in JSON at all? This is provided libxl won't rely on that to do proper
> clean-up I don't see the value of retaining them, and if libxl is
> relying on the JSON file to do clean-up the desig
On Wed, Feb 03, 2016 at 02:36:03PM +, Wei Liu wrote:
> (Note that I'm not very familiar with this, so what I'm talking might be
> non-sense, and please bear with me if I ask stupid questions.)
>
> On Wed, Jan 27, 2016 at 11:00:12AM +0100, Olaf Hering wrote:
> > On Fri, Nov 13, Olaf Hering wrot
(Note that I'm not very familiar with this, so what I'm talking might be
non-sense, and please bear with me if I ask stupid questions.)
On Wed, Jan 27, 2016 at 11:00:12AM +0100, Olaf Hering wrote:
> On Fri, Nov 13, Olaf Hering wrote:
>
> > Port pvscsi support from xend to libxl:
>
> How should c
On Fri, Nov 13, Olaf Hering wrote:
> Port pvscsi support from xend to libxl:
How should code which converts devices from xenstore to json handle
devices which got marked as "to be removed"?
In my pvscsi code I set XenbusStateClosing in the vscsidev, then
XenbusStateReconfiguring in vscsictrl. Th
Port pvscsi support from xend to libxl:
vscsi=['pdev,vdev{,options}']
xl scsi-attach
xl scsi-detach
xl scsi-list
Signed-off-by: Olaf Hering
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
docs/man/xl.cfg.pod.5| 55 +++
docs/man/xl.pod.1
