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
On 05/05/2010 11:32 AM, 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:
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:
Avi Kivity wrote:
On 05/05/2010 11:32 AM, 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:
On 05/05/2010 11:51 AM, Michael Tokarev wrote:
In the AMD CPUID guide leafs _0002 till _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
Michael Tokarev wrote:
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:
On 05/05/2010 01:18 PM, Andre Przywara wrote:
Michael Tokarev wrote:
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
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
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
Andre Przywara wrote:
[]
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
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
04.05.2010 20:23, 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:
Michael Tokarev wrote:
02.05.2010 14:04, Avi Kivity wrote:
On 05/01/2010 12:40 AM, Michael Tokarev wrote:
01.05.2010 00:59, Michael Tokarev wrote:
Apparently with current kvm stable (0.12.3)
Windows NT 4.0 does not install anymore.
With default -cpu, it boots, displays the
Inspecting your
On 05/03/2010 11:24 AM, Andre Przywara wrote:
can you try -cpu kvm64? This should be somewhat in between -cpu host
and -cpu qemu64.
Also look in dmesg for uncatched rd/wrmsrs. In case you find something
there, please try:
# modprobe kvm ignore_msrs=1
(You have to unload the modules first)
Avi Kivity wrote:
On 05/03/2010 11:24 AM, Andre Przywara wrote:
can you try -cpu kvm64? This should be somewhat in between -cpu host
and -cpu qemu64.
Also look in dmesg for uncatched rd/wrmsrs. In case you find something
there, please try:
# modprobe kvm ignore_msrs=1
(You have to unload
03.05.2010 12:24, Andre Przywara wrote:
Michael Tokarev wrote:
02.05.2010 14:04, Avi Kivity wrote:
On 05/01/2010 12:40 AM, Michael Tokarev wrote:
01.05.2010 00:59, Michael Tokarev wrote:
Apparently with current kvm stable (0.12.3)
Windows NT 4.0 does not install anymore.
With default -cpu,
03.05.2010 13:28, Andre Przywara wrote:
Avi Kivity wrote:
On 05/03/2010 11:24 AM, Andre Przywara wrote:
can you try -cpu kvm64? This should be somewhat in between -cpu host
and -cpu qemu64.
Also look in dmesg for uncatched rd/wrmsrs. In case you find
something there, please try:
# modprobe
02.05.2010 14:04, Avi Kivity wrote:
On 05/01/2010 12:40 AM, Michael Tokarev wrote:
01.05.2010 00:59, Michael Tokarev wrote:
Apparently with current kvm stable (0.12.3)
Windows NT 4.0 does not install anymore.
With default -cpu, it boots, displays the
Inspecting your hardware configuration
On 05/02/2010 07:12 PM, Michael Tokarev wrote:
After installing, winNT does not boot without -cpu host,
with exactly the same diagnostics as before (0x003E).
But: After installing service pack 6, it boots just fine
with any -cpu, including the default qemu64.
With qemu-kvm-0.11.4 it all
02.05.2010 20:40, Avi Kivity wrote:
On 05/02/2010 07:12 PM, Michael Tokarev wrote:
After installing, winNT does not boot without -cpu host,
with exactly the same diagnostics as before (0x003E).
But: After installing service pack 6, it boots just fine
with any -cpu, including the default
Apparently with current kvm stable (0.12.3)
Windows NT 4.0 does not install anymore.
With default -cpu, it boots, displays the
Inspecting your hardware configuration
message and BSODs with STOP: 0x003E
error as shown here:
http://www.corpit.ru/mjt/winnt4_1.gif
With -cpu pentium the
01.05.2010 00:59, Michael Tokarev wrote:
Apparently with current kvm stable (0.12.3)
Windows NT 4.0 does not install anymore.
With default -cpu, it boots, displays the
Inspecting your hardware configuration
message and BSODs with STOP: 0x003E
error as shown here:
22 matches
Mail list logo
