On Thu, Jan 4, 2024 at 4:02 AM Juergen Gross <[email protected]> wrote: > > Add support for the new 9pfs backend "xen-9pfsd". For this backend type > the tag defaults to "Xen" and the host side path to > "/var/log/xen/guests/<dom-name>". > > Signed-off-by: Juergen Gross <[email protected]> > Reviewed-by: Jason Andryuk <[email protected]> > --- > V2: > - test max_files and max_open_files, too (Jason Andryuk) > --- > docs/man/xl.cfg.5.pod.in | 36 ++++++++++++++++++++++++++++++++++-- > tools/xl/xl_parse.c | 36 ++++++++++++++++++++++++++++++++++++ > 2 files changed, 70 insertions(+), 2 deletions(-) > > diff --git a/docs/man/xl.cfg.5.pod.in b/docs/man/xl.cfg.5.pod.in > index 2e234b450e..80011adbf3 100644 > --- a/docs/man/xl.cfg.5.pod.in > +++ b/docs/man/xl.cfg.5.pod.in > @@ -772,10 +772,16 @@ settings, from the following list: > > =over 4 > > +=item B<type=TYPE> > + > +The backendtype for the PV device. Supported values are B<qemu> and > +B<xen-9pfsd>. The default is B<qemu>. > + > =item B<tag=STRING> > > 9pfs tag to identify the filesystem share. The tag is needed on the > -guest side to mount it. > +guest side to mount it. For the backendtype of B<xen-9pfsd> the tag defaults > to > +"Xen".
Here and below it's "xen_9pfsd" as the type. I tried mounting a xen-9pfsd export in Linux, but mount failed: mount: /mnt/9p-b: mount(2) system call failed: Remove I/O error. dmesg(1) may have more information after failed mount system call. dmesg doesn't have any other details. /sys/bus/xen/devices/9pfs-2/state shows Connected. Regards, Jason
