From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53083) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuYvS-0005MG-R5 for qemu-devel@nongnu.org; Tue, 10 Jun 2014 23:10:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WuYvO-0005tw-O3 for qemu-devel@nongnu.org; Tue, 10 Jun 2014 23:10:10 -0400 Received: from soto.provo.novell.com ([137.65.250.214]:34548) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuYvO-0005n5-GV for qemu-devel@nongnu.org; Tue, 10 Jun 2014 23:10:06 -0400 Message-Id: <539839040200006600036D54@soto.provo.novell.com> Date: Tue, 10 Jun 2014 21:09:56 -0600 From: "Chun Yan Liu" References: <1401867299-7715-1-git-send-email-cyliu@suse.com> In-Reply-To: <1401867299-7715-1-git-send-email-cyliu@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [Qemu-devel] [Xen-devel] [RFC PATCH V2 0/2] support xen HVM direct kernel boot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ian.Campbell@citrix.com, Ian Jackson , stefano.stabellini@eu.citrix.com Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org >>> On 6/4/2014 at 03:34 PM, in message <1401867299-7715-1-git-send-email-cyliu@suse.com>, Chunyan Liu wrote:=20 > After your valuable suggestions, I'll continue the work to support=20 > stubdom. But since stubdom currently uses qemu-xen-traditional and=20 > will switch to qemu upstream in future, in a period of time, stubdom=20 > HVM direct kernel boot won't be in working status. So, before=20 > continuing the stubdom support work, I updated existing patch series,=20 > adding proper error messages for rombios and stubdom limitation,=20 > adding man page descriptions and other trival updates to make it a=20 > complete working patch series. For those using seabios and non = stubdom,=20 > they can use now.=20 Hi, Stefan, Ian J. & Ian C., I don't know if it's proper but could we merge current patch series first = and stubdom compatible work continued next? We do have some customers they want to use it in guest installation. And considering: a) current patch = series and future stubdom compatible version will keep same user interface. b) = stubdom HVM direct kernel boot won't really work until stubdom-dm switches to qemu upstream, maybe not soon? (I didn't see it in xen 4.5 development). c) how = many users will actually use stubdom and at the same time using direct kernel = boot? Regards, Chunyan > xen side patch: pass kernel/initrd/append parameters to qemu-dm=20 > qemu side patch: reuse load_linux() for xen hvm direct kernel boot.=20 > Different from pc_memory_init which does lots of ram alloc work=20 > and rom/bios loading work, for xen, we only need to init a basic=20 > fw_cfg device used by load_linux() to store ADDRs and=20 > linuxboot.bin/multiboot.bin to retrive ADDRs, then load_linux(),=20 > after that, do real add option rom work to add=20 > linuxboot.bin/multiboot.bin to system option rom. Other things=20 > would be done by seabios smoothly.=20 > =20 > v1 is here:=20 > http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06233.html=20 > =20 > Chunyan Liu (2):=20 > xen: pass kernel initrd to qemu=20 > qemu: support xen hvm direct kernel boot=20 > =20 > _______________________________________________=20 > Xen-devel mailing list=20 > Xen-devel@lists.xen.org=20 > http://lists.xen.org/xen-devel=20 > =20 > =20 From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chun Yan Liu" Subject: Re: [Xen-devel] [RFC PATCH V2 0/2] support xen HVM direct kernel boot Date: Tue, 10 Jun 2014 21:09:56 -0600 Message-ID: <539839040200006600036D54@soto.provo.novell.com> References: <1401867299-7715-1-git-send-email-cyliu@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1401867299-7715-1-git-send-email-cyliu@suse.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Ian.Campbell@citrix.com, Ian Jackson , stefano.stabellini@eu.citrix.com Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org List-Id: xen-devel@lists.xenproject.org >>> On 6/4/2014 at 03:34 PM, in message <1401867299-7715-1-git-send-email-cyliu@suse.com>, Chunyan Liu wrote:=20 > After your valuable suggestions, I'll continue the work to support=20 > stubdom. But since stubdom currently uses qemu-xen-traditional and=20 > will switch to qemu upstream in future, in a period of time, stubdom=20 > HVM direct kernel boot won't be in working status. So, before=20 > continuing the stubdom support work, I updated existing patch series,=20 > adding proper error messages for rombios and stubdom limitation,=20 > adding man page descriptions and other trival updates to make it a=20 > complete working patch series. For those using seabios and non = stubdom,=20 > they can use now.=20 Hi, Stefan, Ian J. & Ian C., I don't know if it's proper but could we merge current patch series first = and stubdom compatible work continued next? We do have some customers they want to use it in guest installation. And considering: a) current patch = series and future stubdom compatible version will keep same user interface. b) = stubdom HVM direct kernel boot won't really work until stubdom-dm switches to qemu upstream, maybe not soon? (I didn't see it in xen 4.5 development). c) how = many users will actually use stubdom and at the same time using direct kernel = boot? Regards, Chunyan > xen side patch: pass kernel/initrd/append parameters to qemu-dm=20 > qemu side patch: reuse load_linux() for xen hvm direct kernel boot.=20 > Different from pc_memory_init which does lots of ram alloc work=20 > and rom/bios loading work, for xen, we only need to init a basic=20 > fw_cfg device used by load_linux() to store ADDRs and=20 > linuxboot.bin/multiboot.bin to retrive ADDRs, then load_linux(),=20 > after that, do real add option rom work to add=20 > linuxboot.bin/multiboot.bin to system option rom. Other things=20 > would be done by seabios smoothly.=20 > =20 > v1 is here:=20 > http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06233.html=20 > =20 > Chunyan Liu (2):=20 > xen: pass kernel initrd to qemu=20 > qemu: support xen hvm direct kernel boot=20 > =20 > _______________________________________________=20 > Xen-devel mailing list=20 > Xen-devel@lists.xen.org=20 > http://lists.xen.org/xen-devel=20 > =20 > =20