All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mick Jordan <Mick.Jordan@Sun.COM>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Size limit on extra argument to xm create
Date: Mon, 12 Oct 2009 10:05:24 -0700	[thread overview]
Message-ID: <4AD361D4.8010500@Sun.COM> (raw)
In-Reply-To: <C6F5E8A9.171BD%keir.fraser@eu.citrix.com>

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

  reply	other threads:[~2009-10-12 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10  3:49 Size limit on extra argument to xm create Mick Jordan
2009-09-10  4:00 ` Size limit on extra argument to xm create; RETRACT Mick Jordan
2009-10-09 19:57 ` Size limit on extra argument to xm create Mick Jordan
2009-10-09 20:31   ` Keir Fraser
2009-10-09 22:32     ` Mick Jordan
2009-10-10  6:30       ` Keir Fraser
2009-10-12 17:05         ` Mick Jordan [this message]
2009-10-12 17:15           ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD361D4.8010500@Sun.COM \
    --to=mick.jordan@sun.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.