RE: [Xen-devel] Is it possible to disable vif completely?

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> If you comment out the vif line, but don't set nics=0 then 
> you will get the default nics value, which is 1.  This means 
> that it will try to create a nic with default configuration, 
> which will fail.  If you need no nics, you need to explicitly 
> say so, with nics=0.
> 
> This is confusing, and a mess, but I don't want to alter 
> configuration file behaviour this close to release, if I can help it.

Conversely, I'd much rather change the config file format before the
3.0.0 release rather than changing it before 3.1.0 -- there'll be a lot
more configuration files out there to break. I see changes to
configuration parsing code as fairly low risk -- you're certainly not
likely to get 'complex' breakage. If its going to happen, it would have
to be in the next week, though.

I think after the last email discussion we have a clear idea of what the
syntax should be, and it would only require most people to ubdate their
vbd specifiers. I'd really like to sort out the kernel command line
generation at the same time, though...

Ian


vbd = [ 'device=hda1, source=phy:/dev/vg/myroot, options=rw',
        'device=hda2, source=file:"/root/dumb, name!", options=ro' ]

vif = [ 'device=eth0, mac=aa:00:00:00:00:11, bridge=xen-br0',
        'device=eth1, mac=aa:00:00:00:00:12, bridge=xen-br1' ]

(for vif, the device= can be optional for backward compatibility.
'nics=' must die!)






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel