01.05.2010 10:05, Martin Stut wrote:
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.
I'm using kernel 2.6.32-3-bigmem #1 SMP, the one that is currently
shipped with Debian testing (squeeze).
Ok, excellent.
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?
Thank you for the hint. I tried, together with the other options I need,
but it didn't help:
The system run attempt
kvm -m 1024 -hda /backup/qemu/francke4/francke4.img -cdrom
/backup/qemu/francke4/winnt4.iso -cpu host -boot order=cd -net
nic,model=rtl8139,vlan=0,macaddr=00:11:22:33:44:66 -net user,vlan=0
-localtime -name francke4 -monitor stdio
results in => BSOD stop 0x0000001e in ntoskrnl.exe
Ok, it appears we've 2 problems here (but I think I mentioned this
already) -- one is 0x1E and other is 0x3E. Let's deal with the
latter first.
And with reversed boot order, so an installation attempt the result is
=> BSOD stop 0x0000003e
Adding the option -smp 1 didn't help either.
Removing most of the other options doesn't help either.
Ok.
Now one more try please:
kvm ... -cpu qemu64,level=1
this should cure the 0x3E issue during install time.
See http://marc.info/?t=127266127400005 for the actual
discussion on k...@vger about this one.
If this works, the next step is to look at the 0x1E stop
(inaccessible boot device). I'll try to reproduce it here
now.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
