From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48710) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBKKR-0000C7-Q3 for qemu-devel@nongnu.org; Thu, 06 Feb 2014 03:29:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBKKL-0001uW-Rz for qemu-devel@nongnu.org; Thu, 06 Feb 2014 03:28:59 -0500 Received: from isrv.corpit.ru ([86.62.121.231]:39659) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBKKL-0001uL-LC for qemu-devel@nongnu.org; Thu, 06 Feb 2014 03:28:53 -0500 Message-ID: <52F347C3.9030600@msgid.tls.msk.ru> Date: Thu, 06 Feb 2014 12:28:51 +0400 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] 128Kb bios size and older machines? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: Gerd Hoffmann 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