From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mick Jordan Subject: Re: Size limit on extra argument to xm create Date: Mon, 12 Oct 2009 10:05:24 -0700 Message-ID: <4AD361D4.8010500@Sun.COM> References: Reply-To: Mick.Jordan@Sun.COM Mime-Version: 1.0 Content-Type: text/plain; CHARSET=US-ASCII; format=flowed Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 10/ 9/09 11:30 PM, Keir Fraser wrote: > Since it's baked into the guest ABI, it's not expandable. It's rather likely > you'll have to live with only 1024 characters of boot parameters: the > horror! > I realize that 1024 seems large enough for a traditional OS. In my Java Virtual Machine guest, I am faced with some applications that issue very large command lines, certainly in excess of 1024. There are workarounds, but it means I can't run certain apps out of the box. > The initial ram disk is just an 'module' you can load into guest memory for > interpretation by the guest kernel as it loads. Convention is to load it > into RAM immediately after the guest kernel, and place its address and size > into the mod_start/mod_len fields of start_info. > I assume this is specified via the "ramdisk" configuration file option? Mick