All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: bugzilla-daemon@bugzilla.kernel.org, kvm@vger.kernel.org
Subject: Re: [Bug 104091] New: [bisected] Starting a VM causes the host to halt and create Machine Check Exceptions
Date: Sun, 6 Sep 2015 18:28:38 +0800	[thread overview]
Message-ID: <55EC1556.4020003@linux.intel.com> (raw)
In-Reply-To: <bug-104091-28872@https.bugzilla.kernel.org/>



On 09/06/2015 06:03 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=104091
>
>              Bug ID: 104091
>             Summary: [bisected] Starting a VM causes the host to halt and
>                      create Machine Check Exceptions
>             Product: Virtualization
>             Version: unspecified
>      Kernel Version: 4.2
>            Hardware: All
>                  OS: Linux
>                Tree: Mainline
>              Status: NEW
>            Severity: normal
>            Priority: P1
>           Component: kvm
>            Assignee: virtualization_kvm@kernel-bugs.osdl.org
>            Reporter: harn-solo@gmx.de
>          Regression: No
>
> Created attachment 186851
>    --> https://bugzilla.kernel.org/attachment.cgi?id=186851&action=edit
> dmesg output after starting the VM
>
> With kernel 4.2, starting one of my VMs instantly freezes the host system and
> creates Machine Check Exceptions on CPUs dedicated to that particula VM:
>
> [12316.171917] mce: [Hardware Error]: CPU 3: Machine Check Exception: 5 Bank
> 17: be2000000003110a
> [12316.171917] mce: [Hardware Error]: RIP !INEXACT! 10:<ffffffff813217fd>
> {intel_idle+0xbd/0x120}
> [12316.171917] mce: [Hardware Error]: TSC 76fd7352bf6 ADDR fa137140 MISC
> 30f0083884509086
> [12316.171917] mce: [Hardware Error]: PROCESSOR 0:306f2 TIME 1441130705 SOCKET
> 0 APIC 6 microcode 2d
> [12316.171917] mce: [Hardware Error]: Run the above through 'mcelog --ascii'
> ...
>

Could you please decode it by mcelog?

> A bisection revealed that commit fd717f11015f673487ffc826e59b2bad69d20fe5
> introduced the problem:
>
> KVM: x86: apply guest MTRR virtualization on host reserved pages
>
> Currently guest MTRR is avoided if kvm_is_reserved_pfn returns true.
> However, the guest could prefer a different page type than UC for
> such pages. A good example is that pass-throughed VGA frame buffer is
> not always UC as host expected.
>
> This patch enables full use of virtual guest MTRRs.
>
> One could argue that the following warning is an obvious hint
> [12311.584431] pmd_set_huge: Cannot satisfy [mem 0x383fe0000000-0x383fe0200000]
> with a huge-page mapping due to MTRR override.

Just confirm: it happened on host, right?

>
> but I'm able to run another VM without problems despite that warning.
>
> Please let me know I you need additional information.
>

  parent reply	other threads:[~2015-09-06 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 10:03 [Bug 104091] New: [bisected] Starting a VM causes the host to halt and create Machine Check Exceptions bugzilla-daemon
2015-09-06 10:05 ` [Bug 104091] " bugzilla-daemon
2015-09-06 10:08 ` bugzilla-daemon
2015-09-06 10:28 ` Xiao Guangrong [this message]
2015-09-08  4:13 ` bugzilla-daemon
2015-10-01 11:03 ` 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=55EC1556.4020003@linux.intel.com \
    --to=guangrong.xiao@linux.intel.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.