On 21/11/18 05:05, Bandan Das wrote:
>> Oh, wait. I didn't understand that. Then yeah, fixing QEMU is enough.
>> KVM is not reporting the MSR in the list on AMD, but it should (and it
>> should implement the MSR, of course!).
>>
> Until AMD implements somethinig, on the KVM side, shouldn't we
On Tue, Nov 20, 2018 at 11:28:59PM -0500, Bandan Das wrote:
> baldu...@units.it writes:
>
> > hello
> >
> >> incomplete because it can return 0 for data. Can you try this:
> >>
> >> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> >> index f524e7d929..4878ffb90b 100644
> >> ---
> Sorry Gabriele, Eduardo and Paolo pointed out that the patch was incomplete.
> I am not sure however how you are getting non zero data with the rdmsr on an
> AMD.
> Can you please try this instead ?
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index f524e7d929..cfec559aa3 100644
>
baldu...@units.it writes:
> hello
>
>> incomplete because it can return 0 for data. Can you try this:
>>
>> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
>> index f524e7d929..4878ffb90b 100644
>> --- a/target/i386/kvm.c
>> +++ b/target/i386/kvm.c
>> @@ -2002,14 +2002,9 @@ static int
Paolo Bonzini writes:
...
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index f524e7d929..4878ffb90b 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -2002,14 +2002,9 @@ static int kvm_put_msrs(X86CPU *cpu, int level)
> #endif
>
> /*
On 20/11/18 19:48, Eduardo Habkost wrote:
> On Tue, Nov 20, 2018 at 07:40:01PM +0100, Paolo Bonzini wrote:
>> On 20/11/18 00:00, Eduardo Habkost wrote:
>>> On Mon, Nov 19, 2018 at 04:55:13PM -0500, Bandan Das wrote:
baldu...@units.it writes:
> hello
>
> I'm building qemu from
On Tue, Nov 20, 2018 at 07:40:01PM +0100, Paolo Bonzini wrote:
> On 20/11/18 00:00, Eduardo Habkost wrote:
> > On Mon, Nov 19, 2018 at 04:55:13PM -0500, Bandan Das wrote:
> >> baldu...@units.it writes:
> >>
> >>> hello
> >>>
> >>> I'm building qemu from source and happily using it since a bit
>
On 20/11/18 00:00, Eduardo Habkost wrote:
> On Mon, Nov 19, 2018 at 04:55:13PM -0500, Bandan Das wrote:
>> baldu...@units.it writes:
>>
>>> hello
>>>
>>> I'm building qemu from source and happily using it since a bit
>>> (2.3.0)
>>>
>>> Since 3.1.0-rc0 (including latest 3.1.0-rc1) I'm no more able
hello
> incomplete because it can return 0 for data. Can you try this:
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index f524e7d929..4878ffb90b 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -2002,14 +2002,9 @@ static int kvm_put_msrs(X86CPU *cpu, int level)
>
On Mon, Nov 19, 2018 at 04:55:13PM -0500, Bandan Das wrote:
> baldu...@units.it writes:
>
> > hello
> >
> > I'm building qemu from source and happily using it since a bit
> > (2.3.0)
> >
> > Since 3.1.0-rc0 (including latest 3.1.0-rc1) I'm no more able to start
> > qemu, getting:
> >
> >
baldu...@units.it writes:
> hello
>
> I'm building qemu from source and happily using it since a bit
> (2.3.0)
>
> Since 3.1.0-rc0 (including latest 3.1.0-rc1) I'm no more able to start
> qemu, getting:
>
> 8<
> install:115> qemu
> qemu: error: failed to set MSR 0x10a to 0x0
>
On 11/19/2018 01:35 PM, Dr. David Alan Gilbert wrote:
* baldu...@units.it (baldu...@units.it) wrote:
hi
thanks for taking the time to reply
Dr. David Alan Gilbert writes:
I suspect that this might be some problem on my side, as I couldn't
find any similar report (apart some old (qemu-2.8.50)
* baldu...@units.it (baldu...@units.it) wrote:
> > A colleague has confirmed this on his FX-8320 on Fedora 29 with the
> > virt-next repo; so it's nothing that's special about your machine;
> > it's 3.1 that really doesn't like the old AMDs.
>
> ouch! does this mean that I must stop upgrading
> A colleague has confirmed this on his FX-8320 on Fedora 29 with the
> virt-next repo; so it's nothing that's special about your machine;
> it's 3.1 that really doesn't like the old AMDs.
ouch! does this mean that I must stop upgrading qemu or do you think
that some development work will be
* baldu...@units.it (baldu...@units.it) wrote:
> hi
>
> thanks for taking the time to reply
>
> Dr. David Alan Gilbert writes:
> > > I suspect that this might be some problem on my side, as I couldn't
> > > find any similar report (apart some old (qemu-2.8.50) threads, that
> > > didn't help)
>
* baldu...@units.it (baldu...@units.it) wrote:
> hi
>
> thanks for taking the time to reply
>
> Dr. David Alan Gilbert writes:
> > > I suspect that this might be some problem on my side, as I couldn't
> > > find any similar report (apart some old (qemu-2.8.50) threads, that
> > > didn't help)
>
hi
thanks for taking the time to reply
Dr. David Alan Gilbert writes:
> > I suspect that this might be some problem on my side, as I couldn't
> > find any similar report (apart some old (qemu-2.8.50) threads, that
> > didn't help)
>
> Not necessarily; can you tell me:
> a) At what point does
cc'ing in Paolo, Eduardo and Robert
* baldu...@units.it (baldu...@units.it) wrote:
> hello
>
> I'm building qemu from source and happily using it since a bit
> (2.3.0)
>
> Since 3.1.0-rc0 (including latest 3.1.0-rc1) I'm no more able to start
> qemu, getting:
>
> 8<
>
hello
I'm building qemu from source and happily using it since a bit
(2.3.0)
Since 3.1.0-rc0 (including latest 3.1.0-rc1) I'm no more able to start
qemu, getting:
8<
install:115> qemu
qemu: error: failed to set MSR 0x10a to 0x0
qemu:
19 matches
Mail list logo
