From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: loop devices - Xen 3.0.3 problem? Date: Fri, 27 Oct 2006 16:56:06 +0200 Message-ID: <45421E06.4060601@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com, Keir.Fraser@cl.cam.ac.uk, padmashree.k.apparao@intel.com List-Id: xen-devel@lists.xenproject.org >> When I try to create bridge 4 >> >> /etc/xen/scripts/network-bridge vifnum=4 start >> >> >> >> Link veth4 is missing. >> >> I tried increasing the loopback devices in the kernel boot command line using netloop.nloopbacks=64 >> And also with max_loop=64, but neither worked. > > > The former should work if the driver is built into your kernel. If it's not I'm not sure if module loading picks up options from the boot-time command line. You might need to add a line to your modules.conf or to the line that manually loads netloop. I also have this problem, it started with an upgrade to 3.0.3. Trying to bring up a vifnum 4 or bigger results in that error (Link veth4 is missing). It doesn't work when loop is in the kernel, and when is built as a module. In fact, I tried to build it as a module, and then do: # modprobe loop max_loop=256 # dmesg|grep loop loop: loaded (max 256 devices) # /etc/init.d/xend start But it will always say that "Link veth4 is missing" if I start something like "/etc/xen/scripts/network-bridge vifnum=4 start". -- Tomasz Chmielewski http://wpkg.org