[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: [Xen-users] Overcoming loopback device limitation - revisited


  • To: "Steve Kemp" <steve@xxxxxxxxxxxx>
  • From: "john maclean" <jayeola@xxxxxxxxx>
  • Date: Tue, 1 Aug 2006 14:35:10 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 01 Aug 2006 06:35:51 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p7NAMfd2u33gYgM3ixUWnpKiPWlsOuYB5pLWpnZ75tNaGPav9892yYrPOxl0UkK6Rq9JYz4dLzk3MBUJo6sX2/ou7fWp4boYtqabkuO3EqJh5oeLQvmU9Q1F9qLhMvYBxeDeSNjb60a/urSFySUVPWJJ0lJBCpkTnfmbhbPp3WI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

 xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      512     1 r-----  6956.8
centos0                            7       32     1 ------    15.2
centos1                            9       32     1 ------    15.2
centos2                           12       32     1 ------    15.5
centos3                           13       32     1 ------    21.4
centos4                           14       32     1 ------    15.2
centos5                           15       32     1 ------    15.0
centos6                           16       32     1 ------ 28452.9
centos7                           17       32     1 ------    14.4


I finally got there at about 05:10 this morning.
rmmod loop
modprobe loop max_loop=64
That did it. Had a look in the source code and
/usr/src/xen-3.0.2-2/pristine-linux-2.6.16/drivers/block/loop.c gave
me the clue.
"...
* Maximum number of loop devices when compiled-in now selectable by passing
* max_loop=<1-255> to the kernel on boot.
...static int max_loop = 8;"
That final line threw me as I thought I'd have to change that value
from 8 to something like 32. It finally occurred to me what everyone
was talking about.

Thanks chaps for your patience and time.

On 01/08/06, Steve Kemp <steve@xxxxxxxxxxxx> wrote:
On Tue, Aug 01, 2006 at 01:06:04AM +0100, john maclean wrote:
> still no joy. Managed to bring some domUs back to life though. Only
> had one, now I got four.

> acid:~# losetup -f
> losetup: could not find any free loop device

  Remove the max_loop setting from the boot line.

  Instead run:

  echo 'options loop max_loop=255' > /etc/modprobe.d/loop.local

  Now if you have no domains running you should be able to do:

    rmmod loop
    modprobe loop
    dmesg | grep loop

  The last line should show you that you have >8 loaded.

Steve
--



--
John Maclean  - 07739 171 531
MSc (DIC)

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.