30.04.2010 19:32, Martin Stut wrote:
[]
kvm -m 1024 -hda /backup/qemu/francke4/francke4.img -cdrom
/backup/qemu/francke4/winnt4.iso -net
nic,vlan=0,macaddr=00:11:22:33:44:66 -net user,vlan=0 -localtime -name
francke4 -monitor stdio
results in: STOP 0x0000001E (0xC0000005, 0x8001449C, 0x00000000, 0x8011A95B)
8011a95b has base at 80100000 - ntoskrnl.exe
I have tried to start the installed OS with these modifications:
-cpu pentium => same BSOD
-M pc-0.10 ; omit -cpu => very similar BSOD, this time with hal.dll
-no-hpet => same BSOD
I have then tried to re-install the OS from an image of the NT4 CD:
-boot order=dc ; omit -no-hpet => BSOD STOP 0x0000003E (0x00000080, 0,
0, 0) very early in the boot process
-cpu pentium => it gets a bit further, but then kvm exits with this
error message:
kvm_run: Exec format error
kvm_run returned -8
I can't reproduce this one. It just hangs for me with
-cpu pentium after displaying this (first text-mode
stage still):
Microsoft (R) Windows NT (TM) Version 4.0 (Build 1381).
1 System Processor [512 MB Memory] Multiprocessor Kernel
(it uses smp kernel during install).
-cpu pentium2 => same as above (kvm exits)
omit -M => same as above (kvm exits)
-cpu pentium3 => same as above (kvm exits)
-cpu 486 => same as above (kvm exits)
omit -cpu => stop 0x0000003e, as further above
-smp 1 => stop 0x0000003e, as further above
-M pc-0.10 -smp 1 => stop 0x0000003e, as further above
-M pc-0.10 -cpu pentium3 -smp 1 => kvm exits, as above
Interesting. Here, kvm nevers stops. But this is,
perhaps, due to a more recent host kernel: mine is
2.6.33.3, which received qutie a few kvm updates.
But I were able to install a winNT 4.0 system using,
surprizingly, -cpu host. My CPU is AMD Athlon x2-64,
definitely something which winNT didn't know in 1996,
but it installs and works nicely. I didn't use any
other options, just 4:
kvm -hda winNT.raw -cdrom winNT4.iso -m 512 -cpu host
Care to try it out?
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
