Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-users] Re: [Xen-devel] Re: Writing a tool for Shared Persistent

To: Jim Burnes <jvburnes@xxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] Re: Writing a tool for Shared Persistent Windows Boot Image
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Sat, 30 Jun 2007 07:21:07 +0100
Cc: Andrew Warfield <andrew.warfield@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, Anthony Liguori <anthony@xxxxxxxxxxxxx>
Delivery-date: Fri, 29 Jun 2007 23:18:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <b3ec41ba0706291207l68dfd873k7e143fafd6e7d498@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2BB087BE-D323-4D8E-82F7-794C76ED2BCD@xxxxxxxxx> <467AE21F.1020700@xxxxxxxxxxxxx> <37B43CC2-BED7-4336-9CC4-0CE1C7894458@xxxxxxxxx> <467AF0C6.5010101@xxxxxxxxxxxxx> <b3ec41ba0706281118k751e90bajf2f3095fd92d0939@xxxxxxxxxxxxxx> <20070628182736.GB12711@xxxxxxxxxx> <eacc82a40706290738r354123f3x459d1ba27b279f31@xxxxxxxxxxxxxx> <20070629144251.GC25518@xxxxxxxxxx> <eacc82a40706290918s284681fjfea2baafe53f69d2@xxxxxxxxxxxxxx> <b3ec41ba0706291200v2e81807ew7e603221342eb130@xxxxxxxxxxxxxx> <b3ec41ba0706291207l68dfd873k7e143fafd6e7d498@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2007-06-29 at 13:07 -0600, Jim Burnes wrote:
> Speaking of the XenSource 3.1.0 RPMs, I'd like to make a suggestion.
> When you build the xen-kernel for those 3.1.0 RPMs, can you make sure
> that the loop device is built as a module?  By default the loop device
> is limited to 8 instances and when you build it into the kernel it
> makes it very difficult to change max_loop. 
> 
> I tried adding it as a xen-kernel boot option in grub.conf, but as far
> as I can tell it's ignored when the loop device is compiled in the
> kernel.

When a module is builtin you often need to prefix the option on the
kernel command line with the module name. So adding loop.max_loop=<N>
may work.

Ian.




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

<Prev in Thread] Current Thread [Next in Thread>