On Wed 11/21/07 at 09:38 AM, John.Plocher at Sun.COM wrote: > Nils Nieuwejaar wrote: > >Unfortunately, it's not that simple. > > >Within the domU, we don't have enough information to draw any inferences > >about network topology. Any guesses we made about a sensible renaming > >scheme would likely go wrong under all but the simplest scenarios. > > So if I do a sys-unconfig and reboot, I get presented with a bunch > of questions (which network do you want to use...) that /I/ don't have > any clue about which to choose either...
I'm not sure I understand why you wouldn't. This is exactly the same as if you swap out your Broadcom NIC for an Intel NIC in a physical system. > I'm not saying to automate this completely, but to provide tools that > the user can use to manage the complexity. I understand this request, but I believe it is beyond the scope of this project. From some of the other messages in this thread, it sounds like this is one of the goals of the vanity naming project. > In the simple case, where I have a domU with a single iface, a tool > that could do > > change_network_device --from rtls0 --to xnf34 > > is what I'm thinking of. My question above is how the user would figure > out that xfn34 would be the right new device name. Both before and after the change, the domain will only have a single network device. Initially it will have rtls0. After the domain is halted, reconfigured, and rebooted, it will have xnf0. If you are using DHCP and NWAM, then I'm pretty sure the transition from HVM to PV devices should be seamless. As soon as I can find an HVM-capable system on a network with DHCP, I'll verify this. Nils
