Avi Kivity wrote:
On 05/03/2010 08:03 PM, Michael Tokarev wrote:
Michael, can you try to use -cpu host,-vme and see if that makes a
difference?
With -cpu host,-vme winNT boots just fine as with just -cpu host.
I also tried with -cpu qemu64 and kvm64, with +vme and -vme (4
combinations in total) - in all cases winNT crashes with the
same 0x0000003E error. So it appears that vme makes no
difference.
Please try again the model/vendor/family. I suggest using x86info on
both to see what the differences are, using -cpu host with overrides to
make it equivalent to qemu64 (and verifying it fails), then removing the
overrides one by one until it works.
I managed to get a NT4 CD and can acknowledge the issues you see. I am
about to debug this now.
With -cpu host (on a AMD K8, similar to Michael's) I get to the point
Michael mentioned:
Microsoft (R) Windows NT (TM) Version 4.0 (Build 1381).
1 System Processor [512 MB Memory] Multiprocessor Kernel
Then it _seems_ to hang, checking for getting beyond a certain TSC value
in a tight loop.
(rdtsc; cmp %edx, %edi; ja @rdtsc; jb bailout; cmp %eax, %ebx; ja
@rdtsdc; bailout:)
But after some time (when I got back from the monitor, but also without
going into) I could proceed with the installation.
Michael, can you confirm this?
I will now try to get behind the STOP 3E error.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
