- similar to what is done for XenSource's Linux, create a "vifname"
node
inside XenStore, which contains the vifnames (doh!) for the domain
just
created. In our case, for dom0, that would be "xvifX-Y", or anything
that avoid using dots in the name (X being domU ID and Y the
frontend
interface ID).
- modify the vif-ip and vif-bridge scripts: introduce a
"xenstore_read_default" function, like done for Linux:
# xenstore_read_default <path> <default>
#
# Read the given path, returning the value there or the given
default
# if the path is not present.
#
xenstore_read_default() {
xenstore-read "$1" 2>/dev/null || echo "$2"
}
- use it to query the "vifname" keys; obviously, keep the "xvifX.Y"
as
default syntax.
- wait for an arbitrary amount of time (TBD), so that Xen scripts
get
eventually replaced by their newer versions.
- finally, modify the syntax in kernel. Consequence: vifname will
change
its syntax within xenstore for each new domU, and the newer scripts
will
take that into account "automagically."
Opinions?