public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: paolo pedaletti <paolo.pedaletti@gmail.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: kvm-82 doesn't boot 64bit (?) [cpu0 unhandled wrmsr]
Date: Fri, 16 Jan 2009 15:49:04 +0100	[thread overview]
Message-ID: <49709E60.8080507@gmail.com> (raw)
In-Reply-To: <20090111085153.GA27301@amit-x200.pnq.redhat.com>

Ciao Amit,

>> 1) with -cpu qemu64 I obtain in the guest:
>> cat /proc/cpuinfo
>> vendor_id: GenuineIntel
>> but it doesn't seem a 64 bit cpu (?)
> 
> Check for the 'lm' flag in cpuinfo output.

with -cpu qemu64:

cat /proc/cpuinfo | grep flags
flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse6
clflush mmx fxsr sse sse2 syscall nx lm up pni

http://www.linuxquestions.org/questions/linux-general-1/proccpuinfo-flag-lm-358563/?s=58094402abd82d488b3daf02e520f6bf

ok, it's 64 bit

> Have you used 'core2duo' in a previous version without problems?

no, it's the first time, the hardware is new

> I could reproduce this with 32-bit and 64-bit guests. It works fine with
> -no-kvm. I looked at this briefly; it's a problem in cpuid function 4
> which has the Intel cache identification bits. We need updated info there.

can I provide you this information?
How?

> Just for the refernce, kvm_stat shows this and CPU usage goes beyond 95%:
> 
> $ ./kvm_stat -1
> efer_reload                   27         0
> exits                    2652516    591716
> fpu_reload                276172         0
> halt_exits                    55         0

the meaning of the two columns is .... ?

thank you.

-- 
Paolo Pedaletti

  reply	other threads:[~2009-01-16 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  3:16 kvm-82 doesn't boot 64bit (?) [cpu0 unhandled wrmsr] Paolo Pedaletti
2009-01-11  8:51 ` Amit Shah
2009-01-16 14:49   ` paolo pedaletti [this message]
2009-01-16 15:00     ` Amit Shah
2009-01-16 15:10       ` paolo pedaletti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49709E60.8080507@gmail.com \
    --to=paolo.pedaletti@gmail.com \
    --cc=amit.shah@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox