From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58446) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qobnv-0005gH-Q5 for qemu-devel@nongnu.org; Wed, 03 Aug 2011 09:48:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qobnu-0002Jh-CP for qemu-devel@nongnu.org; Wed, 03 Aug 2011 09:48:11 -0400 Received: from canardo.mork.no ([148.122.252.1]:54816) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qobnu-0002J7-1a for qemu-devel@nongnu.org; Wed, 03 Aug 2011 09:48:10 -0400 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= References: <87ochmmhma.fsf@nemi.mork.no> <87sjqi9jsx.fsf@nemi.mork.no> <20110707235009.GB12991@morn.localdomain> <87fwmh9puv.fsf@nemi.mork.no> <20110710204100.GA25495@morn.localdomain> <0895461378D74EC49BD787BDBFF8C934@FSCPC> <8739hlb5t4.fsf@nemi.mork.no> <20110802003637.GA3046@morn.localdomain> <87y5zc9mzu.fsf@nemi.mork.no> <20110802124114.GA29924@morn.localdomain> <87pqkm7jko.fsf@nemi.mork.no> <4E394DAF.8030700@redhat.com> Date: Wed, 03 Aug 2011 15:48:06 +0200 In-Reply-To: <4E394DAF.8030700@redhat.com> (Avi Kivity's message of "Wed, 03 Aug 2011 16:31:27 +0300") Message-ID: <87hb5y7gix.fsf@nemi.mork.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [SeaBIOS] SeaBIOS error with Juniper FreeBSD kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Brandon Bennett , Kevin O'Connor , seabios@seabios.org, qemu-devel@nongnu.org, Sebastian Herbszt Avi Kivity writes: > On 08/03/2011 03:42 PM, Bj=C3=B8rn Mork wrote: >> Anyway, I would appreciate if some solution was found which allowed >> JUNOS to boot with an unmodified SeaBIOS with SMBIOS enabled, as long as >> the number of CPUs is limited. >> >> > > Is fixing JUNOS out of the question? Yes, I would say so. The ability to run it on non-Juniper hardware is undocumented and unsupported to the degree that the functionality probably rather would be removed than fixed to support something like SeaBIOS. > AFAICT, Seabios complies with all relevant standards. Yes, I have no reason to believe otherwise. But still it does behave sufficiently different from other BIOSes for low CPU count machines to fail in this particular case. I see this as another end of the discussion about whether Linux should try to configure PC hardware in the same manner as Windows, as that is the configuration which will be tested by hardware vendors. Most OS vendors will test their systems with the big proprietary BIOSes and not with SeaBIOS. Does that make sense? Bj=C3=B8rn