Xen devel - Dec 2005 - DomU networking not working with changeset 8333 in xen-unstable

I am testing with changeset 8333 from xen-unstable, and networking on
any on my domUs is not working. Yesterday, with changeset 8320,
everything was normal. 


-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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

On Tue, Dec 13, 2005 at 09:31:53AM -0600, David F Barrera wrote:
> I am testing with changeset 8333 from xen-unstable, and networking on
> any on my domUs is not working. Yesterday, with changeset 8320,
> everything was normal. 
The nics= option in the configuration file was deprecated yesterday.  If
previously you just had nics=1, then you now need vif=['''']. 
If you are still
having trouble, please post your xm create configuration files.

There were also changes to the netfront driver, the vif-nat script,
vif-common.sh yesterday, so networking may be affected by those changes also.

If this is a migration-specific networking issue, there was a change yesterday
to increase security on the migration socket, also.

Ewan.

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

On 13 Dec 2005, at 15:31, David F Barrera wrote:
> I am testing with changeset 8333 from xen-unstable, and networking on
> any on my domUs is not working. Yesterday, with changeset 8320,
> everything was normal.
Maybe you need to add a line ''vif = [ '''' ]''
to your domain config files?

  -- Keir


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

How do you specify nics=0 now?

Thanks,
Dan

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

On Tue, Dec 13, 2005 at 03:24:37PM -0800, Magenheimer, Dan (HP Labs Fort
Collins) wrote:
> How do you specify nics=0 now?
Just leave out the vif line (or vif = [], if you prefer).

Ewan.

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

Thanks.  Does leaving a nics=0 line in cause a failure
or is it gracefully ignored?
> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xensource.com] 
> Sent: Tuesday, December 13, 2005 4:32 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] DomU networking not working with 
> changeset 8333 in xen-unstable
> 
> On Tue, Dec 13, 2005 at 03:24:37PM -0800, Magenheimer, Dan 
> (HP Labs Fort Collins) wrote:
> 
> > How do you specify nics=0 now?
> 
> Just leave out the vif line (or vif = [], if you prefer).
> 
> Ewan.
> 
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Tue, Dec 13, 2005 at 03:33:48PM -0800, Magenheimer, Dan (HP Labs Fort
Collins) wrote:
> Thanks.  Does leaving a nics=0 line in cause a failure
> or is it gracefully ignored?
You get "Warning: The nics option is deprecated.  Please remove it."
and then
domain creation proceeds as you would expect.

If you have a nics=1 entry, then you get

Warning: The nics option is deprecated.  Please use an empty vif entry instead:

  vif = [ '''' ]

and then the domain creation continues with 1 vif, just as it would have done
last week.

The only incompatibility is if you have specified neither a nics option nor a
vif line.  In this case, last week you would have got 1 random vif -- now you
get no vifs.

Ewan. 

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