From: Alexander Graf <agraf@suse.de>
To: Riccardo Veraldi <Riccardo.Veraldi@cnaf.infn.it>
Cc: kvm@vger.kernel.org
Subject: Re: kvm and cpu type
Date: Thu, 22 Jan 2009 14:43:06 +0100 [thread overview]
Message-ID: <497877EA.8050305@suse.de> (raw)
In-Reply-To: <4978719F.1000007@cnaf.infn.it>
Riccardo Veraldi wrote:
> Hello Iam using kvm83 on CentOS5.2
>
> my system has 2x dual Core intel CPU
>
> Intel(R) Xeon(R) CPU 5110 @ 1.60GHz
>
> asdetected by Centos.
>
> If I start kvm-qemu with no CPU option everythign works and hte guest
> machine detects cpu as
>
> QEMU Virtual CPU version 0.9.1
>
>
> iv I run qemu-kvm -cpu core2duo
>
> the guest hangs at boot time when it detects the CPU.
>
> I do not know how to fix it.
>
> I also do not know if using -cpu swtch can improve performances.
Yes, -cpu core*duo is broken in kvm < 84. Please use the default.
There's usually no real benefit for anyone to use a specific cpu type,
unless you know that you need it.
Alex
next prev parent reply other threads:[~2009-01-22 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 13:16 kvm and cpu type Riccardo Veraldi
2009-01-22 13:43 ` Alexander Graf [this message]
2009-01-22 16:51 ` Amit Shah
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=497877EA.8050305@suse.de \
--to=agraf@suse.de \
--cc=Riccardo.Veraldi@cnaf.infn.it \
--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