From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, Cyrill Gorcunov <gorcunov@gmail.com>,
John Floren <john@jfloren.net>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH 3/3] kvm tools, ui: Add support for SDL framebuffer output target
Date: Fri, 3 Jun 2011 18:54:47 +0200 [thread overview]
Message-ID: <20110603165447.GB18795@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.1106031946000.807@tiger>
so, i still don't have a GUI. What happens is that once the
framebuffer initializes in the guest the bootup gets *real* slow,
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 suspend
[ 20.040000] registered taskstats version 1
[ 20.040000] Magic number: 15:707:842
[ 41.601000] md: Waiting for all devices to be available before autodetect
[ 41.601000] md: If you don't use raid, use raid=noautodetect
not much CPU used after this point - just the SIGALRM hitting the kvm
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=0x4f00, err=-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=2560, pages=0
[ 0.682000] vesafb: scrolling: redraw
[ 0.682000] vesafb: Truecolor: size=8:8:8:8, shift=24:0:8:16
[ 0.683000] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90000900000, 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)
�[ 4.269000] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 4.535000] serial8250: ttyS0 at I/O 0x3f8 (irq = 0) is a 16550A
�[ 7.270000] serial8250: ttyS1 at I/O 0x2f8 (irq = 0) is a 16550A
�[ 8.190000] serial8250: ttyS2 at I/O 0x3e8 (irq = 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 intel_agp module!
so the badness starts after the 'framebuffer mapped' message.
Thanks,
Ingo
next prev parent reply other threads:[~2011-06-03 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 15:59 [PATCH 1/3] kvm tools, ui: Add framebuffer infrastructure Pekka Enberg
2011-06-03 15:59 ` [PATCH 2/3] kvm tools, ui: Move VNC specific framebuffer code to ui/vnc.c Pekka Enberg
2011-06-03 15:59 ` [PATCH 3/3] kvm tools, ui: Add support for SDL framebuffer output target Pekka Enberg
2011-06-03 16:26 ` Ingo Molnar
2011-06-03 16:28 ` Ingo Molnar
2011-06-03 16:33 ` Ingo Molnar
2011-06-03 16:37 ` Pekka Enberg
2011-06-03 16:40 ` Ingo Molnar
2011-06-03 16:44 ` Pekka Enberg
2011-06-03 16:45 ` Ingo Molnar
2011-06-03 16:46 ` Pekka Enberg
2011-06-03 16:52 ` Ingo Molnar
2011-06-03 16:54 ` Pekka Enberg
2011-06-03 16:58 ` Ingo Molnar
2011-06-03 16:54 ` Ingo Molnar [this message]
2011-06-03 16:56 ` Ingo Molnar
2011-06-03 16:30 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110603165447.GB18795@elte.hu \
--to=mingo@elte.hu \
--cc=gorcunov@gmail.com \
--cc=john@jfloren.net \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=penberg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox