we emulate x2apic in software */
entry->ecx |= F(*X2APIC*);
QEMU will get this feature through kvm_ioctl().
On 2013-07-24 8:48, Peter Huang(Peng) wrote:
> Hi,Jiri
>
> Thanks for replying.
>
> So why VM identified different features from host is due to the hypervi
:48 +0800, Peter Huang(Peng) wrote:
>>> libvirt's "host-passthrough" uses "-cpu host', and it "-cpu host"
>>> enables every feature that can be enabled on the host.
>> From my test results, I found that even when use host-passthrough mode, V
> libvirt's "host-passthrough" uses "-cpu host', and it "-cpu host"
> enables every feature that can be enabled on the host.
>From my test results, I found that even when use host-passthrough mode, VM's
cpu features are very different from host, this doesn't match what
host-passthrough
mode's expl
ul 22, 2013 at 08:36:05PM +0800, Peter Huang(Peng) wrote:
>> I traced the qemu process, and find out that host cpuid doesn't support
>> x2apic,
>> but VM interception seems enabled x2apic.
>>
>> with function=1(bit 21 indicates x2apic)
>> host_cpuid:ecx=0x009
I traced the qemu process, and find out that host cpuid doesn't support x2apic,
but VM interception seems enabled x2apic.
with function=1(bit 21 indicates x2apic)
host_cpuid:ecx=0x009ce3bd
guest_cpuid:ecx=0x00b82201
On 2013-07-22 19:24, Peter Huang(Peng) wrote:
> Hi, Everyone
>
&g
Hi, Everyone
I have been encountered a problem recently.
My box uses Nehalem E5520 CPU, and this model doesn't support x2apic feature.
I created a VM on KVM, and uses cpu mode=pass-through, I can get the right cpu
model from the VM, but I can also see that the CPU in the vm supports x2apic.
This
Hi,Wanlong
>From the patch discription below, seems that qemu numa only support
>cpu/memory node binding.
As we know, binding is not the common usage due to VM migration may happen or
the load balance
would be disabled.
So, do we have any plan of generating virtual numa automatically?
For exam
