From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: "i8042.c: No controller found" -> no keyboard when I type in BIOS
Date: Thu, 14 May 2009 13:03:26 +0200 [thread overview]
Message-ID: <4A0BFA7E.9070402@wpkg.org> (raw)
Sometimes, when I type any keys in BIOS, my Linux guests boot without
keyboard - I'm not able to type in VNC console, guest's dmesg says:
i8042.c: No controller found.
Rebooting the guest doesn't fix the problem; only stopping/starting the
guest helps (i.e. new kvm process is started).
Which is a bit strange - usually, the keyboard is there when I boot:
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
The keyboard is not present after I reboot the guest and usually type
before Linux is started. It does not happen always.
Observed with kvm-83, kvm-84, kvm-85 on multiple KVM hosts (different
hardware).
Anyone else seeing this? If you're not sure, do something like:
grep i8042 /var/log/kern*
(or grep "i8042.c: No controller found" /var/log/kern*)
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2009-05-14 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 11:03 Tomasz Chmielewski [this message]
2009-05-14 12:37 ` "i8042.c: No controller found" -> no keyboard when I type in BIOS Tomasz Chmielewski
2009-05-14 13:41 ` Tomasz Chmielewski
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=4A0BFA7E.9070402@wpkg.org \
--to=mangoo@wpkg.org \
--cc=kvm@vger.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