All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] 128Kb bios size and older machines?
Date: Thu, 06 Feb 2014 12:28:51 +0400	[thread overview]
Message-ID: <52F347C3.9030600@msgid.tls.msk.ru> (raw)

Since the "small" (128Kb) seabios is now built without
support of xen, does that mean that xen will be unable
to use qemu with -M 1.7 and before?  Does it _ever_ use
-M option like this?

I'm asking because I don't really understand how this works.
 We updated seabios in debian to 1.7.4 (with qemu 1.7), it
grew past 128Kb, and now I'm trying to understand what
exactly is broken and how to fix it.  I should either
build it w/o xen support for it to fit in 128Kb again,
or keep it at larger size and live with (migration) breakage
caused by different bios size.

BTW, recompiling seabios-1.7.4 without xchi and a few other
recently added stuff (pvscsi boot et al) with gcc-4.7.2 on
debian does not produce 128Kb binary, it is larger than 128k,
so I can't produce 128kb bios on debian anymore.. ;)

Thanks,

/mjt

             reply	other threads:[~2014-02-06  8:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06  8:28 Michael Tokarev [this message]
2014-02-06  8:50 ` [Qemu-devel] 128Kb bios size and older machines? Gerd Hoffmann
2014-02-06 13:08   ` Michael Tokarev
2014-02-06 13:15     ` Ian Campbell
2014-02-06 13:30       ` Michael Tokarev
2014-02-06 13:52         ` Ian Campbell
2014-02-06 14:31           ` Gerd Hoffmann
2014-02-06 14:48             ` Ian Campbell
2014-02-06 23:55               ` Paolo Bonzini
2014-02-06 23:56       ` Paolo Bonzini
2014-02-07  7:11         ` Michael Tokarev

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=52F347C3.9030600@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=kraxel@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 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.