From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34567) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMbKa-0007ML-Li for qemu-devel@nongnu.org; Wed, 06 Dec 2017 10:09:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMbKW-0004tc-JQ for qemu-devel@nongnu.org; Wed, 06 Dec 2017 10:09:52 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53928) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eMbKW-0004sW-9m for qemu-devel@nongnu.org; Wed, 06 Dec 2017 10:09:48 -0500 Date: Wed, 6 Dec 2017 15:09:44 +0000 From: Stefan Hajnoczi Message-ID: <20171206150943.GB22757@stefanha-x1.localdomain> References: <20171205063313.GB4102@yangzhon-Virtual> <20171205120623.GB31150@stefanha-x1.localdomain> <5f9f2835-5811-3ee0-9049-0d2cddc08958@redhat.com> <876e5376-d729-72d7-3c04-3c6f52b745de@redhat.com> <20171205163109.GC6712@stefanha-x1.localdomain> <33183CC9F5247A488A2544077AF19020DA4CA201@DGGEMA505-MBS.china.huawei.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rS8CxjVDS/+yyDmU" Content-Disposition: inline In-Reply-To: <33183CC9F5247A488A2544077AF19020DA4CA201@DGGEMA505-MBS.china.huawei.com> Subject: Re: [Qemu-devel] About the light VM solution! List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Gonglei (Arei)" Cc: Paolo Bonzini , Yang Zhong , Stefan Hajnoczi , qemu-devel --rS8CxjVDS/+yyDmU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 06, 2017 at 09:21:55AM +0000, Gonglei (Arei) wrote: >=20 > > -----Original Message----- > > From: Qemu-devel > > [mailto:qemu-devel-bounces+arei.gonglei=3Dhuawei.com@nongnu.org] On > > Behalf Of Stefan Hajnoczi > > Sent: Wednesday, December 06, 2017 12:31 AM > > To: Paolo Bonzini > > Cc: Yang Zhong; Stefan Hajnoczi; qemu-devel > > Subject: Re: [Qemu-devel] About the light VM solution! > >=20 > > On Tue, Dec 05, 2017 at 03:00:10PM +0100, Paolo Bonzini wrote: > > > On 05/12/2017 14:47, Stefan Hajnoczi wrote: > > > > On Tue, Dec 5, 2017 at 1:35 PM, Paolo Bonzini > > wrote: > > > >> On 05/12/2017 13:06, Stefan Hajnoczi wrote: > > > >>> On Tue, Dec 05, 2017 at 02:33:13PM +0800, Yang Zhong wrote: > > > >>>> As you know, AWS has decided to switch to KVM in their clouds. T= his > > news make almost all > > > >>>> china CSPs(clouds service provider) pay more attention on KVM/Qe= mu, > > especially light VM > > > >>>> solution. > > > >>>> > > > >>>> Below are intel solution for light VM, qemu-lite. > > > >>>> > > http://events.linuxfoundation.org/sites/events/files/slides/Light%20wei= ght%2 > > 0virtualization%20with%20QEMU%26KVM_0.pdf > > > >>>> > > > >>>> My question is whether community has some plan to implement light > > VM or alternative solutions? If no, whether our > > > >>>> qemu-lite solution is suitable for upstream again? Many thanks! > > > >>> > > > >>> What caused a lot of discussion and held back progress was the ap= proach > > > >>> that was taken. The basic philosophy seems to be bypassing or > > > >>> special-casing components in order to avoid slow operations. This > > > >>> requires special QEMU, firmware, and/or guest kernel binaries and > > causes > > > >>> extra work for the management stack, distributions, and testers. > > > >> > > > >> I think having a special firmware (be it qboot or a special-purpose > > > >> SeaBIOS) is acceptable. > > > > > > > > The work Marc Mari Barcelo did in 2015 showed that SeaBIOS can boot > > > > guests quickly. The guest kernel was entered in <35 milliseconds > > > > IIRC. Why is special firmware necessary? > > > > > > I thought that wasn't the "conventional" SeaBIOS, but rather one with > > > reduced configuration options, but I may be remembering wrong. > >=20 > > Marc didn't spend much time on optimizing SeaBIOS, he used the build > > options that were suggested. An extra flag can be added in > > qemu_preinit() to skip slow init that's unnecessary on optimized > > machines. That would allow a single SeaBIOS binary to run both full and > > lite systems. > >=20 > What's options do you remember? Stefan. Or any links about that > thread? I'm Interesting with this topic. Here is what I found: Marc Mari's fastest SeaBIOS build took 8 ms from the first guest CPU instruction to entering the guest kernel. CBFS was used instead of a normal boot device (e.g. virtio-blk). Most hardware support was disabled. https://mail.coreboot.org/pipermail/seabios/2015-July/009554.html The SeaBIOS configuration file is here: https://mail.coreboot.org/pipermail/seabios/2015-July/009548.html Stefan --rS8CxjVDS/+yyDmU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJaKAg3AAoJEJykq7OBq3PILVUH/RpAAoXg3DzcdrYz28G6i7bJ oF1LNFd+F9+KORK9z8EZZS1OpCm9WfYUaQLBTRwbQJ0S+cN08tAOj/kidS+5Tu+c 0GdDxpAq1oqj+JYWu/A9dEmuiXIJBq0utibw7j/bfAgADUomwHEvTUbfVxaLjcJ0 f8OvhMZEctQTl2AFnbK+FE8m25nDiWQ+MbnOVDH4iu1nAolB9J3Yp/dfDns4fQrx kMIL92oJBVI3mgOHd81TPwcf9pOvC6juVQ5mYU8CgQwjcKOJ4tcNVpYFUUa3gt7H kpyNVcFC57CuhZR1SwCWFcOgQ7ff+9a3b0MphvgKnQm0aSRxql9mLu+wMBHtRDk= =Nb/M -----END PGP SIGNATURE----- --rS8CxjVDS/+yyDmU--