(CCing libvir-list)
On Thu, Nov 12, 2015 at 05:35:59PM +0100, Paolo Bonzini wrote:
> On 12/11/2015 17:27, Eduardo Habkost wrote:
> >> > > To simply remove rdtscp from all Opteron_G* models?
> > >
> > > Not sure this is the right thing to do... Real hardware has it, and
> > > going forward KVM wi
On 12/11/2015 17:27, Eduardo Habkost wrote:
>> > > To simply remove rdtscp from all Opteron_G* models?
> >
> > Not sure this is the right thing to do... Real hardware has it, and
> > going forward KVM will provide it.
>
> Do you see any alternative?
Live with the warning, and document it in t
On Thu, Nov 12, 2015 at 04:58:37PM +0100, Paolo Bonzini wrote:
> On 12/11/2015 16:25, Eduardo Habkost wrote:
> > On Thu, Nov 12, 2015 at 11:53:44AM +0100, Paolo Bonzini wrote:
> >> Eduardo,
> >>
> >> running QEMU 2.5 on SVM causes a warning because rdtscp is not supported
> >> by KVM. While I can
On 12/11/2015 16:25, Eduardo Habkost wrote:
> On Thu, Nov 12, 2015 at 11:53:44AM +0100, Paolo Bonzini wrote:
>> Eduardo,
>>
>> running QEMU 2.5 on SVM causes a warning because rdtscp is not supported
>> by KVM. While I can fix it, that leaves a warning on all existing kernels.
>
> You mean when
On Thu, Nov 12, 2015 at 11:53:44AM +0100, Paolo Bonzini wrote:
> Eduardo,
>
> running QEMU 2.5 on SVM causes a warning because rdtscp is not supported
> by KVM. While I can fix it, that leaves a warning on all existing kernels.
You mean when using Opteron_G2 or newer, right? qemu64 and kvm64
don
Eduardo,
running QEMU 2.5 on SVM causes a warning because rdtscp is not supported
by KVM. While I can fix it, that leaves a warning on all existing kernels.
What do you think is the best way forward?
Paolo
