On Tue, 2015-03-24 at 03:34 +0000, Hu, Robert wrote: > > Make it an option to the function which creates the configuration in the > > first place. Quoting myself from earlier in this very thread:
> Then we still need to designate to use e1000 device somewhere; say, in > ts-nested-setup, we store this designation in runvar. > Then when creating the config, according to your proposal, we plumbing > such designation through $xopts, since we see it in runvar. Are you OK > with such implementation? I'm not sure if this should be a runvar or just something which ts-nested-setup knows. That's one for Ian J to decide. > But if like above, I would prefer to altering/manipulating guest configation > directly in ts-nested-setup after normal guest is setup. Since this is more > simple and constrained to nested case only. IMHO, this should be properly integrated into the configuration creation, not fixed up later as an adhoc step. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
