From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: Borislav Petkov <bp@alien8.de>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm ML <kvm@vger.kernel.org>
Subject: Re: Major KVM issues with kernel 4.5 on the host
Date: Sat, 23 Apr 2016 19:52:46 +0100 [thread overview]
Message-ID: <20160423185246.GC8376@gallifrey> (raw)
In-Reply-To: <20160423184341.GA21755@torres.zugschlus.de>
* Marc Haber (mh+linux-kernel@zugschlus.de) wrote:
> On Sat, Apr 23, 2016 at 06:04:29PM +0200, Borislav Petkov wrote:
> > On Thu, Apr 21, 2016 at 10:04:33PM +0200, Marc Haber wrote:
> > > Yes, but there are two symptoms. The VM either suffers file system
> > > issues (garbage read from files, or an aborted ext4 journal and
> > > following ro remount) or it stops dead in its tracks.
> >
> > Stops dead? What does that mean exactly? Box is wedged solid and it
> > doesn't react to any key presses?
>
> No ping, no reaction on serial console, no reaction on virtual
> console, no syslog entries.
>
> > Because if so, this could really be a DRAM going bad and a correctable
> > error turning into an uncorrectable. How old is the DRAM in that box?
> > Judging by your CPU, it should be a couple of years...
>
> Uncorrectable errors would still be identified by the ECC hardware,
> and the box wouldn't be perfectly fine with an "old" kernel.
Hmm, your problem does sound like bad hardware, but....
If you've got a nice reliable crash, can you try turning transparent huge pages
off on the host;
echo never > /sys/kernel/mm/transparent_hugepage/enabled
Dave
> > > The box reports about one correctable error per week, so I probably
> > > have a faulty DIMM, but since the issue only surfaces in VMs while the
> > > host system is in perfect working order...
> >
> > So it could be that correctable error turns into an uncorrectable one at
> > some point. But then you should be getting an exception...
>
> Yes, that would be in the logs.
>
> > > And yes, I am pondering to simply replace the box with an Intel CPU.
> >
> > Your CPU is fine, from what I've seen so far.
>
> But we still postulate that the issue does only show on older AMD
> CPUs. Otherwise, I wouldn't be the only one making this experience.
>
> > > I go the way of Debian packages since it is easier to handle the
> > > crypto file systems when the machine is booting up.
> >
> > As long as you're testing the correct bisection kernels...
>
> I am reasonably sure about that, yes.
>
> > > And yes, I think about doing a test reinstall on unencrypted disk to
> > > find out whether encryption plays a role, but I currently need the
> > > machine to urgently to take it out of serice for half a month, and,
> > > again, the host system is in perfect working order, it is just VMs
> > > that barf.
> >
> > Yeah, I can't reproduce it here and I have a very similar box to yours
> > which is otherwise idle, more or less.
> >
> > Another fact which points to potentially DIMM going bad...
>
> Do you want me to memtest for 24 hours?
>
> Greetings
> Marc
>
> --
> -----------------------------------------------------------------------------
> Marc Haber | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2016-04-23 19:12 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 16:54 Major KVM issues with kernel 4.5 on the host Marc Haber
2016-03-17 18:11 ` Borislav Petkov
2016-03-18 10:01 ` Paolo Bonzini
2016-04-13 18:37 ` Marc Haber
2016-04-13 20:36 ` Paolo Bonzini
2016-04-13 20:52 ` Marc Haber
2016-04-13 22:29 ` Marc Haber
2016-04-14 1:16 ` Paolo Bonzini
2016-04-14 5:22 ` Marc Haber
2016-04-21 8:39 ` Marc Haber
2016-04-21 12:37 ` Borislav Petkov
2016-04-21 14:50 ` Marc Haber
2016-04-21 16:51 ` Borislav Petkov
2016-04-21 20:04 ` Marc Haber
2016-04-23 16:04 ` Borislav Petkov
2016-04-23 18:43 ` Marc Haber
2016-04-23 18:52 ` Dr. David Alan Gilbert [this message]
2016-05-12 20:20 ` transparent huge pages breaks KVM on AMD Marc Haber
2016-05-12 20:24 ` Kirill A. Shutemov
2016-05-12 20:34 ` Marc Haber
2016-05-12 20:42 ` Kirill A. Shutemov
2016-05-13 5:23 ` Marc Haber
2016-05-13 8:07 ` Borislav Petkov
2016-05-13 8:09 ` Borislav Petkov
2016-05-13 13:21 ` Marc Haber
2016-05-13 16:08 ` Borislav Petkov
2016-05-14 6:19 ` Marc Haber
2016-05-13 9:08 ` Marc Haber
2016-05-13 9:19 ` Borislav Petkov
2016-05-13 14:59 ` Marc Haber
2016-05-13 8:35 ` Dr. David Alan Gilbert
2016-05-13 14:03 ` Marc Haber
2016-04-23 23:57 ` Major KVM issues with kernel 4.5 on the host Borislav Petkov
2016-04-14 6:07 ` Marc Haber
2016-04-14 16:47 ` Marc Haber
2016-04-14 17:30 ` Paolo Bonzini
2016-04-14 17:47 ` Marc Haber
2016-03-18 18:49 ` Marc Haber
2016-03-18 22:04 ` Borislav Petkov
2016-03-19 0:08 ` Marc Haber
2016-03-20 13:31 ` Borislav Petkov
2016-03-20 17:14 ` Andrey Korolyov
2016-03-20 18:25 ` Borislav Petkov
2016-03-20 18:42 ` Andrey Korolyov
2016-03-20 18:58 ` Borislav Petkov
2016-04-13 18:22 ` Marc Haber
2016-04-13 20:37 ` Paolo Bonzini
2016-04-13 18:20 ` Marc Haber
2016-03-21 9:08 ` Paolo Bonzini
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=20160423185246.GC8376@gallifrey \
--to=dave@treblig.org \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
--cc=pbonzini@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 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.