[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v3 3/4] docs: Document xenstore paths for domain hotplug features
Without some indication from a domain it is not possible for a toolstack to know whether instantiation of a new vbd or vif should result in a new PV device of the appropriate type being instantiated in a guest. (In other words whether PV drivers are present and functioning). This patch documents two paths which vif and vbd frontend drivers can use to advertise their ability to respond to new vif or vbd instantiations. Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Cc: Ian Campbell <ian.campbell@xxxxxxxxxx> Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Cc: Jan Beulich <jbeulich@xxxxxxxx> Cc: Keir Fraser <keir@xxxxxxx> Cc: Tim Deegan <tim@xxxxxxx> --- v2: - Drop HVM restriction --- docs/misc/xenstore-paths.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/misc/xenstore-paths.markdown b/docs/misc/xenstore-paths.markdown index cae5115..6fecdf3 100644 --- a/docs/misc/xenstore-paths.markdown +++ b/docs/misc/xenstore-paths.markdown @@ -389,6 +389,18 @@ A domain writable path. Available for arbitrary domain use. A domain may write version information for PV driver $NAME using this path. +#### ~/feature/hotplug/vif = ("0"|"1") [w] + +An HVM domain can indicate to a toolstack that it is capable +of responding to instantiation of a new vif by bringing online a +new PV network device without the need for a reboot. + +#### ~/feature/hotplug/vbd = ("0"|"1") [w] + +An HVM domain can indicate to a toolstack that it is capable +of responding to instantiation of a new vbd by bringing online a +new PV block device without the need for a reboot. + ### Paths private to the toolstack #### ~/device-model/$DOMID/state [w] -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |