| |
|
 |
|
 |
|
|
|
| |
|
|
xen-api
RE: [Xen-API] xapi toolstack
> Its my understanding that virtual interfaces(vif, vbd...) are created by
> xapi toolstack when a vm is installed i.e basically xapi toolstack
> controls creation/deletion of interfaces in dom0 when VM's come and go. Is
> it true that xapi toolstack runs in domU as well since interfaces are
> created there for netfront drivers? If I were to create a temp device
> under /sys/bus/xen-backend/devices/(this is where I see vif, vbd and other
> devices are present in dom0), I believe I have to modify xapi toolstack is
> that correct?
[from Ian Campbell]
The vif hotplug script is probably the closest that currently exists. It is
called via udev from /etc/udev/rules.d/xen-backend.rules.
The parameters are the action (online, add, remove, etc) and "vif" or "tap"
depending on which type of virtual device. The domid and devid are then
obtained from $XENBUS_PATH (vif) or $INTERFACE (tap) both of which are part of
the hotplug environment.
Other relevant info is retrieved from xenstore where it was stashed by xapi.
The info in xenstore includes e.g. the vif-uuid so someone could implement a
/etc/xensource/scripts/vif.d/<uuid> type mechanism or something else along
those lines.
Cheers,
Ian
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
|
|
|
| |
|
Home