On Thu, 10 Nov 2011, Ian Campbell wrote:
> > I think it would be very useful as a manpage.
> > If we really want to keep it in markdown rather than pod, we could still
> > find a way to convert it into a manpage (using ronn, pandoc, etc.).
>
> If there is a good markdown->man converter I'm all for using it.
well, I am not sure if any of them are good, but a badly formatted
manpage is still better than no manpage at all
> > > +
> > > +## Devices
> > > +
> > > +The following options define the paravirtual, emulated and physical
> > > +devices which the guest will contain.
> > > +
> > > + * `disk=[ "DISK_SPEC_STRING", "DISK_SPEC_STRING", ...]`: Specifies
> > > + the disks (both emulated disks and Xen virtual block devices) which
> > > + are to be provided to the guest, and what objects on the they
> > > + should map to. See `docs/misc/xl-disk-configuration.txt`.
> > > +
> > > + * `vif=[ "NET_SPEC_STRING", "NET_SPEC_STRING", ...]`: Specifies the
> > > + networking provision (both emulated network adapters, and Xen
> > > + virtual interfaces) to provided to the guest. See
> > > + `docs/misc/xl-network-configuration.markdown`.
> > > +
> > > + * `vfb=[ "VFB_SPEC_STRING", "VFB_SPEC_STRING", ...]`: Specifies the
> > > + paravirtual framebuffer devices which should be supplied to the
> > > domain.
> > > +
> > > + This options does not control the emulated graphics card presented
> > > + to an HVM guest. See "Emulated VGA Graphics Device" below for how
> > > + to configure the emulated device.
> >
> > and it is only relevant for PV guests.
>
> Really, I thought that it was possible for a PVHVM to have a PV FB too?
> Perhaps only in theory?
Only in theory, there is no support for it at the moment and I don't
think there will be anytime soon.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|