[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Problems with VM after kernel commit b18d5431acc7a2fd22
|
From: |
Paolo Bonzini |
|
Subject: |
Re: [Qemu-devel] Problems with VM after kernel commit b18d5431acc7a2fd22767925f3a6f597aa4bd29e |
|
Date: |
Fri, 13 Nov 2015 16:04:35 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
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 address@hidden :)
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
>>
>
>