KR> For Net: KR> -Set address - get a default mac address I think we've had this discussion in the past, and decided it was better to not offer generated mac addresses in the template instances. Since resolving the association is the act of allocation (or pre-allocation), there's no easy way to say "I need three NICs" and get back unique MACs for each. Because of this lack of a formal allocation step, I think it's likely that clients would grab a template RASD and offer it multiple times in the DefineSystem() call, which wouldn't result in a valid domain configuration. The concession was that we would let the client leave out the MAC and assign one for it during DefineSystem(). That way if they want to specify a MAC, they can, but we don't have to deal with the other issues. So, I definitely think that the fields you're adding for the other templates are good, but I'd rather leave this one out of it, if possible. Thoughts? -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com