On Thu, Jan 31, 2008 at 07:58:56AM -0800, Gary Leong wrote: > I had a question about Crossbow and Xen VNICs. In Linux, VNICs are > available for Xen, but I don't know if there is a way to > limit/control the traffic to the NICs.
The architecture of networking for Xen is quite different in Solaris from that in Linux. Linux doesn't have "vnics" in the same sense as Solaris. > So Crossbow provides the same Xen framework, but integrates more > controlled for VNIC? The entirety of Crossbow is not yet integrated into Nevada, just an early cut of the basic VNIC functionality. In particular, resource control is not available in Nevada, only in the Crossbow project bits. > Prior to Crossbox, Solaris Zones had virtual nics, but I guess it's > similar to the current Xen releases with a limitation of resource > allocation? No. Zones generally (pre IP Instances) used logical interfaces, which are a feature of IP (at layer 3). VNICs provide a different abstraction (at layer 2). > Please free to chime in. I'm undecided whether I really need > crossbow, but if I do I will have use at least snv_83. It's a bit > of a pain since I have to include the Dell Perc 5 driver into both > the installer rootfs and the final rootfs on the system. Nevada build 83 includes only the basic VNIC functionality required for xVM - it doesn't have resource control.
