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

Re: [Xen-users] DomU kernel parameters

  • To: "Christian Wittmer" <chris@xxxxxxxxxxxxxxxx>
  • From: "Henning Sprang" <henning_sprang@xxxxxx>
  • Date: Wed, 7 Feb 2007 19:07:50 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 07 Feb 2007 10:07:50 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Mrux82k1ZBpwZWk2KqMZc2OQ/IknWZGn5crBD0Q+ZVKbi84lsBUR++qjNJPOzzDrPHQ74/R6RUeXBJ8tRSQ7hjEYRXpoomTxegtQnXH5e92zTLFPvz8BJ50lnP1a/YxUNTSudF3tUHr60JH8FXBsy2K5BuxpsN5gdRrkMULaXDs=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 2/7/07, Christian Wittmer <chris@xxxxxxxxxxxxxxxx> wrote:
It's a module: (on Dom0 and DomU)
srv-ux-0014:/etc/xen/vm # zcat /proc/config.gz | grep BLK_DEV_LOOP

for dom0 "max_loop=64" works
for domU "extra = "3 TERM=xterm max_loop=64"" this does not work.

When it's a module you need to make sure it's loaded with this param.
The module doesn't use the parameter from the kernel command line.
You have to load the module for example like
modprobe loop max_loop=64
or add sometthing like that in your module config.

The tap:aio itamar wrote about might also work - but on some settings
we had problems with the stability of this, and not sure if all
distribution packages already support this.


Xen-users mailing list



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