qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>, Gleb Natapov <gleb@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Slow kernel/initrd loading via fw_cfg; Was Re: Hack integrating SeaBios / LinuxBoot option rom with QEMU trace backends
Date: Sat, 15 Oct 2011 17:16:48 +0100	[thread overview]
Message-ID: <20111015161648.GC8872@amd.home.annexia.org> (raw)
In-Reply-To: <CAAu8pHv-5vVqUmx_tETk_AO3g8r9mYTdCyyaQqS3diQCntyoxQ@mail.gmail.com>

On Sat, Oct 15, 2011 at 10:00:02AM +0000, Blue Swirl wrote:
> I don't understand why PC can't use the same way of loading initrd by
> QEMU to guest memory before boot as Sparc32 uses. It should even be
> possible to deduplicate the kernel and initrd images: improve the
> loader to use mmap() for loading so that several guests would use the
> same pages. Preloaded kernel and initrd are paravirtual anyway, there
> could be even guest visible changes if ever needed (e.g. map
> kernel/initrd pages outside of normal RAM areas).

+1!

Even better if we extended Linux so it worked more like OS-9 (circa
1990): At boot, scan memory for modules and insmod them.  That way we
wouldn't even need an initrd since we could just supply the correct
list of modules that the guest needs to mount its root disk.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

  reply	other threads:[~2011-10-15 16:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 17:08 [Qemu-devel] Hack integrating SeaBios / LinuxBoot option rom with QEMU trace backends Daniel P. Berrange
2011-10-10 18:53 ` Anthony Liguori
2011-10-10 19:01   ` Alexander Graf
2011-10-11  8:23     ` [Qemu-devel] Slow kernel/initrd loading via fw_cfg; Was " Daniel P. Berrange
2011-10-11  8:43       ` Richard W.M. Jones
2011-10-11  9:15       ` Avi Kivity
2011-10-11  9:19         ` Alexander Graf
2011-10-11  9:26           ` Avi Kivity
2011-10-11  9:38             ` Alexander Graf
2011-10-11  9:49               ` Avi Kivity
2011-10-11  9:56                 ` Gleb Natapov
2011-10-11  9:59                   ` Avi Kivity
2011-10-11 10:28                     ` Gleb Natapov
2011-10-11 13:12               ` Anthony Liguori
2011-10-11 13:14                 ` Alexander Graf
2011-10-11 13:17                   ` Gleb Natapov
2011-10-11 13:19                   ` Anthony Liguori
2011-10-11 13:23                     ` Avi Kivity
2011-10-11 13:24                       ` Gleb Natapov
2011-10-11 13:29                       ` Anthony Liguori
2011-10-11 13:45                         ` Avi Kivity
2011-10-11 13:58                           ` Anthony Liguori
2011-10-11 14:01                     ` Daniel P. Berrange
2011-10-11 14:33                       ` Anthony Liguori
2011-10-11 14:34                         ` Alexander Graf
2011-10-11 14:36                         ` Daniel P. Berrange
2011-10-11  9:50             ` Gleb Natapov
2011-10-11  9:55               ` Avi Kivity
2011-10-11 13:17                 ` Anthony Liguori
2011-10-11 13:22                   ` Gleb Natapov
2011-10-15 14:19                   ` Kevin O'Connor
2011-10-11  9:27         ` Daniel P. Berrange
2011-10-11  9:39           ` Avi Kivity
2011-10-11  9:49             ` Daniel P. Berrange
2011-10-11  9:50               ` Avi Kivity
2011-10-11 10:09                 ` Daniel P. Berrange
2011-10-15 10:00       ` Blue Swirl
2011-10-15 16:16         ` Richard W.M. Jones [this message]
2011-10-16 17:20           ` Lluís Vilanova
2011-10-11  9:08     ` [Qemu-devel] " Avi Kivity
2011-10-11  9:18       ` Daniel P. Berrange
2011-10-11  9:35         ` Avi Kivity
2011-10-10 23:57 ` Kevin O'Connor

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=20111015161648.GC8872@amd.home.annexia.org \
    --to=rjones@redhat.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).