05.05.2010 12:32, Andre Przywara wrote:
Avi Kivity wrote:
On 05/04/2010 06:27 PM, Andre Przywara wrote:
3. In all other cases so far it BSoDs with STOP 0x3E error
right before displaying that kernel message.
MSDN talks about a mulitprocessor configuration error:
http://msdn.microsoft.com/en-us/library/ms819006.aspx
I suspected the offline CPUs in the mptable that confuse NT. But -smp
1,maxcpus=1 does not make a difference. I will try to dig deeper in
this area.
OK, I tackled this down. It is the max CPUID level that differs.
In the AMD CPUID guide leafs 0000_0002 till 0000_0004 are reserved, the
CPU that Michael and I used (K8RevF) actually have a max leaf of 1 here.
Default qemu64 has a max leaf of 4.
So by saying -cpu qemu64,level=1 (or 2 or 3) it works for me.
Modern OS only read leaf 4 on Intel systems, it seems that NT4 is
missing this.
Confirmed, with -cpu qemu64,level=[123] it works for me as well.
Note again that after service pack 6 (I haven't tried other SPs),
the problem goes away entirely -- winNT SP6 works with the default
kvm cpu just fine.
Thanks!
/mjt
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html