[133672.221112] kvm: 28400: cpu0 unhandled wrmsr: 0xc0010117 data 0

Confirmed, I'm seeing the same messages.

At this point, they seem benign. I haven't seen any lockups or incorrect behavior (yet).

Also, this was reported to the KVM upstream kernel mailing list, against kvm-83 by a Fedora user, so we're not the only ones seeing this. I'll track that thread and backport a patch, should one become available upstream.

:-Dustin

It's benign. It's not indicative of an error of any sort. It is indeed fixed in kvm-83 by adding a no-op handler for it[1], basically to silence this message. IMO, it should be wishlist, but I'll leave that up to the kernel team to decide, since I'm not completely up-to-date on their bug handling policies.

[1]: http://git.kernel.org/?p=linux/kernel/git/avi/kvm.git;a=commitdiff;h=61a6bd672bda3b9468bf5895c1be085c4e481138

confirmed.
not benign

posted info to http://ubuntuforums.org/showpost.php?p=7542913&postcount=3

summary:
* fresh "upgrade" from hardy-64 to jaunty-64; fresh installatio over existing data on partitions
* unable to use old/existing images w CLI KVM; cycle of crashes & reboots
* partially able to use load old config XML's with virsh, but removes VM from catalogue/list after reboot
* when creating new client profile via virt-manager, using existing image & info found in XML-dump, again causes similar crash cycle as CLI KVM

On my old windows-based clients, I get a BSoD, indicating the non-availability of APCI

Completely removed & purged all traces of KVM & libvirt (including directories), reboot & re-installed.

Old clients are still useless, but manages to re-install a copy of xp32 (running out of activations soon...); seem to be OK for now

＠freakalad, did you confirm this issue was fixed in Jaunty? if not, can you confirm this issue exists with the Karmic Alpha 9.10 release. Images for testing are available at http://cdimage.ubuntu.com/daily-live/current/ . Please let us know your results.

If the issue remains while still running Karmic, please run the following command which will automatically gather and attach updated debug information:

apport-collect -p linux <bug #>

Thanks in advance.
-Bryan

I have the same problem on Jaunty with an XP installation and I get a black screen instead of the installation.

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.