On Mon, Feb 06, 2006 at 01:54:20PM +0100, Molle Bestefich wrote:
> Ewan Mellor wrote:
> > This change was made on Dec 13. Previously, the nics= option and the
> > vif option interacted in unexpected ways (nics=0 did not necessarily
> > mean 0 vifs, for example). This way vif and vbd configuration behaves
> > the same, and there are no concealed defaults to confuse people.
> It seems that the options:
> still work, but now they can also be specified within the vif=['']
> list as vif=['ip=blah, etc'].
> Is this a bug, or is there just supposed to be two ways to apply an IP
> address etc. now?
Those ip, netmask, and gateway parameters specify options for the Linux
kernel command line. With these, you can persuade the guest to use the
specified details, without having the guest preconfigured, but in
general it's not a good way to work -- you can't specify addresses for
multiple interfaces this way, in particular. The vif options specify
the details given to the hotplug scripts when the devices come up.
These details are used to configure DHCP, routing, or whatever inside
dom 0 -- they don't necessarily affect the guest. You still need the
guest to configure itself appropriately.
The best thing to do is probably to use vif=, have a DHCP server inside
dom0 (dhcp=yes in a couple of places) and then preconfigure the guest to
expect their addresses via DHCP.
The kernel command line options are probably most useful for developers, who
just want to get things up and running quickly without configuring their guest
Xen-devel mailing list