From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 155211] vcpu0, guest rIP: 0xffffffff81064496 unhandled rdmsr: 0x34
Date: Tue, 14 Nov 2017 11:14:00 +0000 [thread overview]
Message-ID: <bug-155211-28872-MnNvmMoYYX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-155211-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=155211
--- Comment #3 from Stid (stidofficiel@gmail.com) ---
(In reply to Stid from comment #2)
> Same problem for me, i use libvirt on debian 9 (stretch) and i lose graphic
> view and mouse/keyboard.
> If i don't close window while kvm bug, sometime i keep full control on VM.
>
> dmesg:
> [86817.636548] kvm: zapping shadow pages for mmio generation wraparound
> [87418.274144] kvm [2856]: vcpu0, guest rIP: 0xffffffff8a0595e2 unhandled
> rdmsr: 0x34
> [87422.306238] kvm [2856]: vcpu0, guest rIP: 0xffffffff8a0595e2 unhandled
> rdmsr: 0x606
> [87422.686053] kvm [2856]: vcpu0, guest rIP: 0xffffffff8a0595e2 unhandled
> rdmsr: 0x611
> [87422.686207] kvm [2856]: vcpu0, guest rIP: 0xffffffff8a0595e2 unhandled
> rdmsr: 0x639
> [87422.686342] kvm [2856]: vcpu0, guest rIP: 0xffffffff8a0595e2 unhandled
> rdmsr: 0x641
> [87422.686474] kvm [2856]: vcpu0, guest rIP: 0xffffffff8a0595e2 unhandled
> rdmsr: 0x619
My spice bug issue is not linked to kvm module :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-11-14 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 20:15 [Bug 155211] New: vcpu0, guest rIP: 0xffffffff81064496 unhandled rdmsr: 0x34 bugzilla-daemon
2016-08-28 20:15 ` [Bug 155211] " bugzilla-daemon
2016-08-28 20:27 ` bugzilla-daemon
2017-11-14 9:00 ` bugzilla-daemon
2017-11-14 11:14 ` bugzilla-daemon [this message]
2020-03-17 11:43 ` bugzilla-daemon
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=bug-155211-28872-MnNvmMoYYX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).