Bug#575439: I'm hit by this bug too

2010-05-07 Thread Martin Stut
Sure you typed that correctly -- -cpu qemu64,level=1 (I cut-n-pasted that to the command line, it works). Sorry, that was my fault. I cut&pasted it too - doubly, so it read -cpu -cpu ... I tried again, and now the setup process gets a little further, but after loading a bunch of modules

Bug#575439: I'm hit by this bug too

2010-05-06 Thread Michael Tokarev
06.05.2010 23:25, Martin Stut wrote: Am 05.05.2010 10:56, schrieb Michael Tokarev: Now one more try please: kvm ... -cpu qemu64,level=1 this should cure the 0x3E issue during install time. -cpu qemu64,level=1 I tried that, but KVM just produces the error message Unable to find x86 CPU defi

Bug#575439: I'm hit by this bug too

2010-05-06 Thread Martin Stut
Am 05.05.2010 11:56, schrieb Michael Tokarev: Alternative possible cause is that you're using even older NT, for which the problem will be reproduceable when upgrading from kvm-72 to kvm-0.12 (note again I'm using SP1 as base install). I'm pretty sure that my WinNT CDs are "SP0", even before SP

Bug#575439: I'm hit by this bug too

2010-05-06 Thread Martin Stut
Am 05.05.2010 10:56, schrieb Michael Tokarev: Now one more try please: kvm ... -cpu qemu64,level=1 this should cure the 0x3E issue during install time. -cpu qemu64,level=1 I tried that, but KVM just produces the error message Unable to find x86 CPU definition Are we talking about the same

Bug#575439: I'm hit by this bug too

2010-05-05 Thread Michael Tokarev
01.05.2010 10:05, Martin Stut wrote: 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 result

Bug#575439: I'm hit by this bug too

2010-05-05 Thread Michael Tokarev
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)

Bug#575439: I'm hit by this bug too

2010-04-30 Thread Martin Stut
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). But I were able to install a wi

Bug#575439: I'm hit by this bug too

2010-04-30 Thread Michael Tokarev
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 0x001E (0xC005, 0x8001449C, 0x,

Bug#575439: I'm hit by this bug too

2010-04-30 Thread Martin Stut
I have exactly the same problem and situation as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575439#5 ., just a few internal addresses are a bit different. This error occurs when I try the re-setup of the VM The problem appeared with the upgrade from kvm 72+dfsg-5+squeeze1 to kvm-qemu 0.