Kais Belgaied wrote: > Nicolas Droux wrote: > >> Folks, >> >> I posted a first draft of the Crossbow virtualization architecture >> document. It can be found at: >> >> http://opensolaris.org/os/project/crossbow/Docs/crossbow-virt.pdf >> >> > > good job Nicolas. > > Quick comments/questions after a first skimming: > > . About the Random MAC addresses for vnic. What was the rationale for > having the local > bit set?
We need to have a OUI used by the VNIC to avoid conflicts with other nodes on the network. Using an existing Sun OUI with the local bit set was a quick way to get this. If we had a OUI reserved for VNICs, we wouldn't have to turn the local bit on, but the allocation of new OUIs is not free. > > . There could be a bit of inconcistency in the expected behavior between > create-vnic and > move-vnic: create-vnic without -m attempts to allocates a factory MAC > address, and, in > case of unavailability generates a random one. The user doesn't need > any extra option > for the right thing to succees. On the other hand, if the user is > moving a > vnic that was using a factory MAC address (even without the user's > explicitly asking for it), > to a NIC that doesn't has MAC address slots left, then he/she needs to > pass an overriding > option, -F, to force the move. > The user didn't care in the first time whether hardware resource must > be used for > the vnic, and shouldn't care when the vnic is relocated neither. Yes, moving VNICs that have a factory MAC address assigned to it needs to be done with care. The user still needs to be informed in this case, since the VNIC MAC address shouldn't be changed automatically during a move, and the factory MAC address cannot be simply moved along with the VNIC without warning, since it is still associated with the hardware that was underneath. That's why the option needs to be specified. > . Any example of what down-vnic is needed for? For symmetry with 'up-vnic', and for consistency with the other pseudo devices managed with dladm, and because it is useful to be able to quickly bring down all VNICs to be able to unload the VNIC driver. Nicolas. > > > Kais > -- Nicolas Droux - Solaris Networking - Sun Microsystems, Inc. droux at sun.com - http://blogs.sun.com/droux
