From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, kvm ML <kvm@vger.kernel.org>
Subject: Re: Major KVM issues with kernel 4.5 on the host
Date: Thu, 14 Apr 2016 03:16:29 +0200 [thread overview]
Message-ID: <570EEF6D.40307@redhat.com> (raw)
In-Reply-To: <20160413222942.GD7600@torres.zugschlus.de>
On 14/04/2016 00:29, Marc Haber wrote:
> On Wed, Apr 13, 2016 at 10:36:34PM +0200, Paolo Bonzini wrote:
>> Didn't help, but a fresh look at the list of 4.5 patches helped.
>> What the hell was I thinking, I missed write_rdtscp_aux who
>> obviously uses MSR_TSC_AUX.
>
> I applied this patch to 4.5, which didn't go cleanly, I had to do it
> manually, and there is no change in behavior. Sometimes, the Vm just
> crashes, but most times the filesystem is remounted ro.
Ok, then I guess bisection is needed. Please first try commit
45bdbcfdf241. If it fails, then the bug come together with KVM's merge
window changes for 4.5-rc1. Please apply the patch I sent here when
bisection is past 46896c73c1a4dde527c3a3cc43379deeb41985a1 (which means
that probably that should be the commit you try second; the bisection
then becomes much easier).
Thanks,
Paolo
> [ 84.658968] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27903
> [ 84.664877] Aborting journal on device dm-0-8.
> [ 84.667992] EXT4-fs (dm-0): Remounting filesystem read-only
> [ 84.670972] EXT4-fs error (device dm-0): ext4_journal_check_start:56: Detected aborted journal
> [ 84.763331] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27898
> [ 84.825412] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27895
> [ 84.907959] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27893
> [ 84.915187] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27900
> [ 84.961062] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27889
> [ 84.983700] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #7669: comm aide: deleted inode referenced: 27891
> [ 98.315538] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #23567: comm aide: deleted inode referenced: 27897
> [ 98.323606] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #23567: comm aide: deleted inode referenced: 27904
> [ 99.889927] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #4650: comm aide: deleted inode referenced: 27892
> [ 99.893823] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #4650: comm aide: deleted inode referenced: 27901
> [ 99.901140] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #4650: comm aide: deleted inode referenced: 27890
> [ 99.904898] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #4650: comm aide: deleted inode referenced: 27896
> [ 99.909758] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #4650: comm aide: deleted inode referenced: 27899
> [ 99.914394] EXT4-fs error (device dm-0): ext4_lookup:1602: inode #4650: comm aide: deleted inode referenced: 27894
> [ 207.132045] serial8250: too much work for irq4
> [ 207.220043] serial8250: too much work for irq4
> [ 207.312028] serial8250: too much work for irq4
>
>
> Greetings
> Marc
>
next prev parent reply other threads:[~2016-04-14 1:16 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 [this message]
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
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=570EEF6D.40307@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
/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).