* [email protected] [2009-07-20 09:50:08] > I want to how could domU know the vnic have been added in the dom0 > with the scripts /usr/lib/xen/scripts/vif-vnic ,
The domU has no way of knowing how the IO domain is providing connectivity. It doesn't know that there is a VNIC. Also consider that if you migrate a domain from a Solaris dom0 to a Linux dom0 the mechanism used in dom0 will change (Solaris uses VNICs, Linux uses a bridge). Why do you need to know this from within the domU? > and Could I add two or more xnf in the same domU? How could I add two > or more vnics used by the same domU? You can add network interfaces to a guest domain using 'virsh attach-interface'. > And when the vnic has been created by /usr/lib/xen/scripts/vif-vnic, > whether it needs the Backend Driver for this vnic or not, if yes, how > it loads in to the system. The script writes the name of the nic to be used by the backend driver into xenstore. The backend driver reads xenstore to discover which nic to open. See usr/src/uts/common/xen/io/xnbo.c. Backend devices are created by monitoring xenstore for the creation of nodes. When a domain is created the tools add entries indicating that a network device (vif) should be made available. The kernel notices this and creates a new backend device instance to handle it. See usr/src/uts/common/xen/os/xvdi.c. dme. -- David Edmondson, Sun Microsystems, http://dme.org _______________________________________________ xen-discuss mailing list [email protected]
