From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org,
Glauber de Oliveira Costa <gcosta@redhat.com>,
Mark McLoughlin <markmc@redhat.com>
Subject: Re: qemu: kvm: avoid harmless unhandled wrmsr 0xc0010117 messages
Date: Sun, 31 May 2009 17:26:46 +0300 [thread overview]
Message-ID: <4A2293A6.3000306@redhat.com> (raw)
In-Reply-To: <20090507184848.GA32150@amt.cnet>
Marcelo Tosatti wrote:
> Olders kernel which don't contain kvm.git commit
> 61a6bd672bda3b9468bf5895c1be085c4e481138 display the following message:
>
> kvm: 32301: cpu0 unhandled wrmsr: 0xc0010117 data 0
>
> When kvm_arch_load_regs is called. This is confusing in bug reports.
>
> Avoid it by checking whether the host advertises the MSR, similarly to
> how MSR_STAR is handled.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-05-31 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 18:48 qemu: kvm: avoid harmless unhandled wrmsr 0xc0010117 messages Marcelo Tosatti
2009-05-31 14:26 ` Avi Kivity [this message]
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=4A2293A6.3000306@redhat.com \
--to=avi@redhat.com \
--cc=gcosta@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mtosatti@redhat.com \
/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