From: Paolo Bonzini <pbonzini@redhat.com>
To: Wolfgang Link <w.link@proxmox.com>, guangrong.xiao@linux.intel.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problems with VM after kernel commit b18d5431acc7a2fd22767925f3a6f597aa4bd29e
Date: Fri, 13 Nov 2015 16:04:35 +0100 [thread overview]
Message-ID: <5645FC03.7070606@redhat.com> (raw)
In-Reply-To: <5645FBD7.5020101@proxmox.com>
On 13/11/2015 16:03, Wolfgang Link wrote:
> Thanks you for the quick reply and the good news.
BTW, for kernel issues please use kvm@vger.kernel.org :)
Paolo
> Wolfgang
> On 11/13/2015 04:01 PM, Paolo Bonzini wrote:
>>
>> On 13/11/2015 15:55, Wolfgang Link wrote:
>>> Hi,
>>>
>>> We have problems with a HP ProLiant DL380 Gen9 and Vm's with large
>>> amount of memory, grater then 30GB.
>>>
>>> The problem is that the vm need about 10 sec to start to boot.
>>> and when it comes to syncing the cpu clock, it takes a long time to
>>> finish this task.
>>> What also occurs is the vcpus need at startup 100% cpu usage and take
>>> over 1 min.
>> This has been fixed already, and the fix is slowly propagating to the
>> stable kernels.
>>
>> The fixes are:
>>
>> - KVM: vmx: obey KVM_QUIRK_CD_NW_CLEARED (fixed already in 4.2)
>>
>> - KVM: x86: obey KVM_X86_QUIRK_CD_NW_CLEARED in kvm_set_cr0() (in 4.4,
>> will be backported)
>>
>> Paolo
>>
>
>
prev parent reply other threads:[~2015-11-13 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 14:55 [Qemu-devel] Problems with VM after kernel commit b18d5431acc7a2fd22767925f3a6f597aa4bd29e Wolfgang Link
2015-11-13 15:01 ` Paolo Bonzini
2015-11-13 15:03 ` Wolfgang Link
2015-11-13 15:04 ` Paolo Bonzini [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=5645FC03.7070606@redhat.com \
--to=pbonzini@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=qemu-devel@nongnu.org \
--cc=w.link@proxmox.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.