From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 3/3] kvm tools, ui: Add support for SDL framebuffer output target Date: Fri, 3 Jun 2011 18:54:47 +0200 Message-ID: <20110603165447.GB18795@elte.hu> References: <1307116779-572-1-git-send-email-penberg@kernel.org> <1307116779-572-3-git-send-email-penberg@kernel.org> <20110603162631.GA17203@elte.hu> <20110603162856.GA17415@elte.hu> <20110603163346.GB17415@elte.hu> <20110603164500.GB17964@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org, Cyrill Gorcunov , John Floren , Sasha Levin To: Pekka Enberg Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:38494 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754719Ab1FCQy4 (ORCPT ); Fri, 3 Jun 2011 12:54:56 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: so, i still don't have a GUI. What happens is that once the=20 framebuffer initializes in the guest the bootup gets *real* slow,=20 like only printk-ing two lines per second. Then it gets even slower and stops around here: [ 20.040000] No RTC device found, ALARM timers will not wake from sus= pend [ 20.040000] registered taskstats version 1 [ 20.040000] Magic number: 15:707:842 [ 41.601000] md: Waiting for all devices to be available before autod= etect [ 41.601000] md: If you don't use raid, use raid=3Dnoautodetect not much CPU used after this point - just the SIGALRM hitting the kvm=20 thread every now and then. here is how the slowdown looks like with printk timestamps: [ 0.677000] uvesafb: failed to execute /sbin/v86d [ 0.678000] uvesafb: make sure that the v86d helper is installed and= executable [ 0.679000] uvesafb: Getting VBE info block failed (eax=3D0x4f00, er= r=3D-2) [ 0.680000] uvesafb: vbe_init() failed with -22 [ 0.680000] uvesafb: probe of uvesafb.0 failed with error -22 [ 0.681000] vesafb: mode is 640x480x32, linelength=3D2560, pages=3D0 [ 0.682000] vesafb: scrolling: redraw [ 0.682000] vesafb: Truecolor: size=3D8:8:8:8, shift=3D24:0:8:16 [ 0.683000] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc9000= 0900000, using 1200k, total 1200k [ 1.855000] Console: switching to colour frame buffer device 80x30 [ 3.635000] fb0: VESA VGA frame buffer device [ 4.268000] virtio-pci 0000:00:01.0: enabling device (0000 -> 0001) =EF=BF=BD[ 4.269000] Serial: 8250/16550 driver, 4 ports, IRQ sharing= enabled [ 4.535000] serial8250: ttyS0 at I/O 0x3f8 (irq =3D 0) is a 16550A =EF=BF=BD[ 7.270000] serial8250: ttyS1 at I/O 0x2f8 (irq =3D 0) is a= 16550A =EF=BF=BD[ 8.190000] serial8250: ttyS2 at I/O 0x3e8 (irq =3D 0) is a= 16550A [ 8.818000] Non-volatile memory driver v1.3 [ 9.419000] Linux agpgart interface v0.103 [ 9.420000] [drm] Initialized drm 1.1.0 20060810 [ 9.420000] [drm:i915_init] *ERROR* drm/i915 can't work without inte= l_agp module! so the badness starts after the 'framebuffer mapped' message. Thanks, Ingo