All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marco Cianfriglia <mcian@hotmail.it>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Windows 7 on pure qemu-0.14
Date: Wed, 16 Mar 2011 11:05:12 +0200	[thread overview]
Message-ID: <20110316090512.GE10151@redhat.com> (raw)
In-Reply-To: <4D807CB3.5000609@siemens.com>

On Wed, Mar 16, 2011 at 10:02:43AM +0100, Jan Kiszka wrote:
> On 2011-03-16 09:33, Gleb Natapov wrote:
> > On Tue, Mar 15, 2011 at 11:41:19PM +0100, Marco Cianfriglia wrote:
> >>
> >>
> >>
> >>
> >>
> >> Hi to all, 
> >>
> >>  thanks for the suggestion to make use of the -cpu nehalem switch.
> >>
> > It should be -cpu Nehalem.
> 
> We neither have "nehalem" nor "Nehalem" as CPU definition in qemu or
> qemu-kvm.
> 
We do in both. Look at sysconfigs/target/target-x86_64.conf. But for
qemu to find this file it needs to be installed.

> In fact, I stumbled over this problem a while back as well [1]. I tried
> all obvious CPU types in the hope Windows is only unhappy about some CPU
> features, but found no working combination as well.
> 
> Jan
> 
> [1] http://permalink.gmane.org/gmane.comp.emulators.qemu/92457
> 
> -- 
> Siemens AG, Corporate Technology, CT T DE IT 1
> Corporate Competence Center Embedded Linux

--
			Gleb.

  reply	other threads:[~2011-03-16  9:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 22:41 [Qemu-devel] Windows 7 on pure qemu-0.14 Marco Cianfriglia
2011-03-16  8:33 ` Gleb Natapov
2011-03-16  9:02   ` [Qemu-devel] " Jan Kiszka
2011-03-16  9:05     ` Gleb Natapov [this message]
2011-03-16 10:49       ` TeLeMan
2011-03-16 11:07         ` Gleb Natapov
2011-03-16 11:54           ` TeLeMan
2011-03-16 12:42       ` Jan Kiszka

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=20110316090512.GE10151@redhat.com \
    --to=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mcian@hotmail.it \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.