From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:56394) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRldJ-00047e-1i for qemu-devel@nongnu.org; Tue, 08 May 2012 10:43:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRldG-00037o-P5 for qemu-devel@nongnu.org; Tue, 08 May 2012 10:43:20 -0400 Received: from e06smtp15.uk.ibm.com ([195.75.94.111]:44888) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRldG-00037H-FM for qemu-devel@nongnu.org; Tue, 08 May 2012 10:43:18 -0400 Received: from /spool/local by e06smtp15.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 8 May 2012 15:43:15 +0100 Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1407.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q48Eh82e2646094 for ; Tue, 8 May 2012 15:43:08 +0100 Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q48Eh7fv029376 for ; Tue, 8 May 2012 08:43:07 -0600 Message-ID: <4FA930FA.4000305@de.ibm.com> Date: Tue, 08 May 2012 16:43:06 +0200 From: Christian Borntraeger MIME-Version: 1.0 References: <1336139040-16628-1-git-send-email-borntraeger@de.ibm.com> <1336139040-16628-2-git-send-email-borntraeger@de.ibm.com> <16456C5E-6C77-4976-8F09-A122C0FE0943@suse.de> <4FA3E108.9040204@de.ibm.com> <4FA3E15D.20804@de.ibm.com> <72DBB625-871D-4B0F-8139-A8F941448905@suse.de> <4FA91267.5050306@de.ibm.com> <9A5D5218-5E01-4D3D-B06E-25F83522E703@suse.de> In-Reply-To: <9A5D5218-5E01-4D3D-B06E-25F83522E703@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] s390: IPL device for s390 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Cornelia Huck , Anthony Liguori , Heinz Graalfs , Jens Freimann , qemu-devel Developers >> Anthony, this is the prototype of the IPL device that we have talked about some weeks >> ago. Is an external device to do the IPL process for s390 still ok with you? > > Even with an external IPL, we should still be able to detect that a guest provides > its own virtio-zipl code that contains a boot menu and execute that instead of directly > booting into the first entry, right? This is something that we can argue about to find a way to cover all our use cases Some of my goals are - make it possible to install the boot loader in lpar/vm and boot in kvm and vice versa - follow the real HW ipl process (which I do for FCP, but not for dasd/eckd) - be able to choose a boot device (-boot is not the right thing for s390) - be able to choose an program (loadparm) - get a disk booted no matter if FCP, ECKD CDL, ECKD LDL, block size etc as long as this configuration can exist with the current tool sets (that includes ipling disks prepared with the sles11 tools) - have some code that can be extended to non-disk boot devices (s390-ipl takes a qdev id as parameter) Can you clarify what you need? the code should be modular enough to add a detection, a switch or something else to make that possible. Christian PS: long term we probably also want to have real ECKD dasd passthrough as an alternative to virtio for dasds. Then the IPL process will also include interpretation of ipl ccws, but this is something that wont be ready anytime soon