From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ND12S-0008IV-D2 for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:27:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ND12N-0008Cl-8C for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:26:59 -0500 Received: from [199.232.76.173] (port=55785 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ND12N-0008Cb-48 for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:26:55 -0500 Received: from mail-bw0-f212.google.com ([209.85.218.212]:33573) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ND12M-0006FJ-Qm for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:26:55 -0500 Received: by bwz4 with SMTP id 4so8378887bwz.2 for ; Tue, 24 Nov 2009 11:26:53 -0800 (PST) Message-ID: <4B0C3375.4010206@codemonkey.ws> Date: Tue, 24 Nov 2009 13:26:45 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 12/13] Add zipl bootloader interpreter References: <1259083781-14642-1-git-send-email-agraf@suse.de> <1259083781-14642-13-git-send-email-agraf@suse.de> <4B0C2BB7.5010203@codemonkey.ws> <50C52B25-2CAE-43E2-A3FC-37545695086E@suse.de> In-Reply-To: <50C52B25-2CAE-43E2-A3FC-37545695086E@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Carsten Otte , qemu-devel@nongnu.org, Aurelien Jarno Alexander Graf wrote: > On 24.11.2009, at 19:53, Anthony Liguori wrote: > > >> Alexander Graf wrote: >> >>> The default bootloader on S390 is zipl. Because we don't emulate normal S390 >>> hardware we need to write our own parser for the bootloader configuration, >>> so we can boot off real hard disks. >>> >>> This patch adds a pretty simple implementation of such an interpreter. It only >>> supports 512 bytes sector sizes, always boots the default entry and doesn't >>> work with reboots yet. But it's better than nothing. >>> >>> >> This is a bit unfortunate. Wouldn't it be better to write a custom version of zipl that ran in the guest? >> > > Yeah, I've been struggling quite a bit with this myself. Writing a custom version that runs in the guest means we have to create > > 1) extboot > 2) input backdoor > > Or implement virtio in that custom version. That sounds like a pretty huge project. > > So I decided to go for the easy way for now and hopefully migrate to an in-guest version later. > Can't you just use kboot? Use a kernel loader to load the kboot module/initrd, include kboot as our firmware, then let kboot do the magic to launch the real linux kernel from disk. Regards, Anthony Liguori