The FAQ says to use loopback.nloopbacks to limit the number of vif''s and veth''s that show up in dom0. This no longer appears to work. Has this been remove with no replacement or has this just changed and the FAQ hasn''t kept up? -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 30 Mar 2006, at 05:13, Jason wrote:> The FAQ says to use loopback.nloopbacks to limit the number of vif''s > and veth''s that show up in dom0. This no longer appears to work. Has > this been remove > with no replacement or has this just changed and the FAQ hasn''t kept > up?Try netloop.nloopbacks -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
That''s the one. Thank you very much! -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet On Thu, 30 Mar 2006, Keir Fraser wrote:> > On 30 Mar 2006, at 05:13, Jason wrote: > >> The FAQ says to use loopback.nloopbacks to limit the number of vif''s and >> veth''s that show up in dom0. This no longer appears to work. Has this been >> remove >> with no replacement or has this just changed and the FAQ hasn''t kept up? > > Try netloop.nloopbacks > > -- Keir > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Maybe Matching Threads
- Bug#388486: xen-utils-common: upgrade new 2.6.17-2-xen breaks create domU until modprobe netloop nloopbacks=n
- options netloop nloopbacks=<n> ignored
- Bug#388352: xen-hypervisor-3.0-unstable-1-amd64: veth0 is missing
- xen 3.2 network problems
- [PATCH linux-2.6.18-xen] make netloop permanent