On Thu, Sep 13, 2012 at 02:56:33PM +0200, Peter Lieven wrote:
> On 13.09.2012 14:42, Gleb Natapov wrote:
> >On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
> >>On 13.09.2012 10:05, Gleb Natapov wrote:
> >>>On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> Il 13/09/2
On 13.09.2012 14:42, Gleb Natapov wrote:
On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
On 13.09.2012 10:05, Gleb Natapov wrote:
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
Il 13/09/2012 09:57, Gleb Natapov ha scritto:
#rdmsr -0 0x194
00011100
#rdmsr
On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
> On 13.09.2012 10:05, Gleb Natapov wrote:
> >On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> >>Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>>#rdmsr -0 0x194
> >>>00011100
> >>>#rdmsr -0 0xce
> >
On 13.09.2012 10:05, Gleb Natapov wrote:
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
Il 13/09/2012 09:57, Gleb Natapov ha scritto:
#rdmsr -0 0x194
00011100
#rdmsr -0 0xce
0c0004011103
Yes, that can help implementing it in KVM. But without a spec to
understand wh
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>> > >
> >>> > > #rdmsr -0 0x194
> >>> > > 00011100
> >>> > > #rdmsr -0 0xce
> >>> > > 0c0004011103
> >> >
> >> > Yes, that can help implementing it in KVM. But without a
Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>> > >
>>> > > #rdmsr -0 0x194
>>> > > 00011100
>>> > > #rdmsr -0 0xce
>>> > > 0c0004011103
>> >
>> > Yes, that can help implementing it in KVM. But without a spec to
>> > understand what the bits actually mean, it's just as risky...
>>
On Thu, Sep 13, 2012 at 09:55:06AM +0200, Paolo Bonzini wrote:
> Il 13/09/2012 09:53, Peter Lieven ha scritto:
>
> >>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
> >>> or -cpu qemu64.
> >> On the host.
> >>
> >>
> > did you get my output?
> >
> > #rdmsr -0 0x194
>
Il 13/09/2012 09:53, Peter Lieven ha scritto:
>>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>>> or -cpu qemu64.
>> On the host.
>>
>>
> did you get my output?
>
> #rdmsr -0 0x194
> 00011100
> #rdmsr -0 0xce
> 0c0004011103
Yes, that can help implementi
On 10.09.2012 14:32, Avi Kivity wrote:
On 09/10/2012 03:29 PM, Peter Lieven wrote:
On 09/10/12 14:21, Gleb Natapov wrote:
On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
Il 10/09/2012 13:52, Peter Lieven ha scritto:
dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
dd if=
On 09/10/12 14:32, Avi Kivity wrote:
On 09/10/2012 03:29 PM, Peter Lieven wrote:
On 09/10/12 14:21, Gleb Natapov wrote:
On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
Il 10/09/2012 13:52, Peter Lieven ha scritto:
dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
dd if=/d
On 09/10/2012 03:29 PM, Peter Lieven wrote:
> On 09/10/12 14:21, Gleb Natapov wrote:
>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> dd if=/dev/cpu/0/msr skip=$((0
On 09/10/12 14:21, Gleb Natapov wrote:
On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
Il 10/09/2012 13:52, Peter Lieven ha scritto:
dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
it only works without the skip. but
On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
> Il 10/09/2012 13:52, Peter Lieven ha scritto:
> >> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> >> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
> > it only works without the skip. but the msr device returns all
Il 10/09/2012 13:52, Peter Lieven ha scritto:
>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
> it only works without the skip. but the msr device returns all zeroes.
Hmm, the strange API of the MSR device doesn't work well with
On 09/10/2012 02:29 PM, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>>
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kv
On 09/10/12 13:29, Paolo Bonzini wrote:
Il 10/09/2012 13:06, Peter Lieven ha scritto:
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
0x11478 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194
On 09/10/12 13:29, Paolo Bonzini wrote:
Il 10/09/2012 13:06, Peter Lieven ha scritto:
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
0x11478 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194
Il 10/09/2012 13:06, Peter Lieven ha scritto:
>
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
> 0x11478 info 0 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
> qemu-kvm-1.0.1-510
On 09/06/12 16:58, Avi Kivity wrote:
On 08/22/2012 06:06 PM, Peter Lieven wrote:
Hi,
has anyone ever tested to run memtest with -cpu host flag passed to
qemu-kvm?
For me it resets when probing the chipset. With -cpu qemu64 it works
just fine.
Maybe this is specific to memtest, but it might be
On 08/22/2012 06:06 PM, Peter Lieven wrote:
> Hi,
>
> has anyone ever tested to run memtest with -cpu host flag passed to
> qemu-kvm?
> For me it resets when probing the chipset. With -cpu qemu64 it works
> just fine.
>
> Maybe this is specific to memtest, but it might be sth that can happen
> in
Hi,
has anyone ever tested to run memtest with -cpu host flag passed to
qemu-kvm?
For me it resets when probing the chipset. With -cpu qemu64 it works
just fine.
Maybe this is specific to memtest, but it might be sth that can happen
in other
applications to.
Any thoughts?
Thanks,
Peter
-
21 matches
Mail list logo