Description of problem:
In a qemu-kvm virtual guest running F17 or F18, the syslog fills with the following messages:
--------------------------------
Dec 23 09:27:20 btrfs2 kernel: [  441.567162] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
Dec 23 09:27:20 btrfs2 kernel: [  441.567174] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.
Dec 23 09:27:20 btrfs2 kernel: [  441.567287] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
Dec 23 09:27:20 btrfs2 kernel: [  441.567293] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.
Dec 23 09:27:21 btrfs2 kernel: [  442.863174] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
Dec 23 09:27:21 btrfs2 kernel: [  442.863186] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.
Dec 23 09:27:21 btrfs2 kernel: [  442.863299] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
Dec 23 09:27:21 btrfs2 kernel: [  442.863305] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.
Dec 23 09:27:21 btrfs2 kernel: [  442.995886] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
Dec 23 09:27:21 btrfs2 kernel: [  442.995897] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.
--------------------------------------

This does not happen on F17 with qemu-kvm-1.0.1-2