public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin Gallant" <martyg@goodbit.net>
To: "'Avi Kivity'" <avi@redhat.com>
Cc: <kvm@vger.kernel.org>
Subject: RE: "-cpu host" AMD Host
Date: Tue, 27 Oct 2009 08:50:12 -0500	[thread overview]
Message-ID: <000201ca570c$6877b4a0$39671de0$@net> (raw)
In-Reply-To: <4AE6C429.9060408@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

I still see the problem with the kernel patch applied.

/proc/cpuinfo attached

Will post a formal bug report with all dumps in a few minutes.

Thanks for the quick response.

--
Marty

-----Original Message-----
From: Avi Kivity [mailto:avi@redhat.com] 
Sent: Tuesday, October 27, 2009 4:58 AM
To: Martin Gallant
Cc: kvm@vger.kernel.org
Subject: Re: "-cpu host" AMD Host

On 10/27/2009 11:39 AM, Avi Kivity wrote:
> On 10/26/2009 09:55 PM, Martin Gallant wrote:
>> Is "-cpu host" supported on AMD hosts?
>>
>
> Yes.
>
>> Whenever I try to use this option on a Windows Vista/7 client, I get 
>> blue screen.
>> Removing the option, the client works fine.
>>
>> Host kernel 2.6.31.4.  Userspace is qemu-kvm-0.11.0.  (Previous 
>> versions fail too)
>>
>> /proc/cpuinfo snippet:
>> vendor_id       : AuthenticAMD
>> cpu family      : 15
>> model           : 107
>> model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
>
> Please post the flags : field as well.
>

You might try the attached patch.


--
error compiling committee.c: too many arguments to function


[-- Attachment #2: cpuinfo.txt --]
[-- Type: text/plain, Size: 1570 bytes --]

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 107
model name	: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
stepping	: 2
cpu MHz		: 2700.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips	: 5429.84
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

processor	: 1
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 107
model name	: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
stepping	: 2
cpu MHz		: 2700.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips	: 5429.84
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps


      reply	other threads:[~2009-10-27 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 19:55 "-cpu host" AMD Host Martin Gallant
2009-10-27  9:39 ` Avi Kivity
2009-10-27  9:58   ` Avi Kivity
2009-10-27 13:50     ` Martin Gallant [this message]

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='000201ca570c$6877b4a0$39671de0$@net' \
    --to=martyg@goodbit.net \
    --cc=avi@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