From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 198205] infinite loop in vmx_vcpu_run on x86_64
Date: Thu, 11 Jan 2018 21:16:05 +0000 [thread overview]
Message-ID: <bug-198205-28872-gsXaWmgaSC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198205-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198205
Mike Marshall (hubcap@omnibond.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubcap@omnibond.com
--- Comment #4 from Mike Marshall (hubcap@omnibond.com) ---
I have a 3rd generation X1 Carbon. It had Fedora 25 on
it until the other day, I figured I better upgrade to
26 or 27 since those are the ones with the Meltdown updates.
I had been using qemu-kvm VMs on it, now when I try to
virt-install one, virt-viewer is unresponsive when it turns on.
When I turn on Virtual Machine Manager, I can see that
CPU is pegged at 100% in the not-yet-installed running VM.
Anywho... it seems the same with Fedora 27. I've been looking
around for what to do with no luck, and then I found this infinite
loop thread.
I have a 1st generation thinkpad as well, it has Fedora 26 on it,
and VMs work great there... perhaps there some combination of
hardware on the 3rd generation one that is the problem...
-Mike
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-01-11 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 18:37 [Bug 198205] New: infinite loop in vmx_vcpu_run on x86_64 bugzilla-daemon
2017-12-19 20:05 ` [Bug 198205] " bugzilla-daemon
2018-01-07 13:54 ` bugzilla-daemon
2018-01-07 14:13 ` bugzilla-daemon
2018-01-11 21:16 ` bugzilla-daemon [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=bug-198205-28872-gsXaWmgaSC@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