From: Aleksander Alekseev <afiskon@devzen.ru>
To: KVM devel mailing list <kvm@vger.kernel.org>
Subject: User question: does KVM work better with latest Linux kernel?
Date: Thu, 17 Mar 2016 13:10:14 +0300 [thread overview]
Message-ID: <20160317131014.7dc42d4f@fujitsu> (raw)
Hello
I'm currently using Linux kernel 3.13.0 (Ubuntu Linux 14.04 with
latest updates). KVM works in general but I noticed a number of small
bugs. E.g. after suspending/resuming a system time is different on host
and guest systems (FreeBSD 10.2). Also when guest system consumes 100%
of its CPU, htop on host system shows that utilization is 100%, but in
guest system it shows only about 33%. Etc.
Is it worth trying to upgrade Linux kernel to say 4.5? Does an upgrade
usually solve some problems with KVM or more likely I will just waste my
time? So basically I'm asking what is considered rule of thumb here.
--
Best regards,
Aleksander Alekseev
http://eax.me/
next reply other threads:[~2016-03-17 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 10:10 Aleksander Alekseev [this message]
2016-03-17 13:32 ` User question: does KVM work better with latest Linux kernel? 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=20160317131014.7dc42d4f@fujitsu \
--to=afiskon@devzen.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox