Today I installed the kvm-qemu update from 0.12.3-dfsg-4 to 0.12.4-dfsg-1.
Unfortunately I still can't start the precious accounting database VM-guest based on NT4. I also still can't (re)install NT4 SP0.
Here ist my test log:2010-05-25: update from kvm 0.12.3-dfsg-4 auf 0.12.4-dfsg-1, normal system start
result: BSOD *** STOP: 0x0000001E (0xC0000005,0x8001449C,0x00000000,0x8011A95B)KMODE_EXCEPTION_NOT_HANDLED*** Address 8001449c has base at 80010000 - hal.dll
attempt: reinstallation from CD (-boot order=dc): result: same STOP attempt: -M pc-0.10 -cpu pentium3 result: kvm_run: Exec format error, kvm_run returned -8 attempt: -cpu pentium2 result: kvm_run: Exec format error, kvm_run returned -8 attempt: -cpu qemu32 result: BSOD STOP 0x0000003E attempt: -cpu pentium result: kvm_run: Exec format error, kvm_run returned -8 attempt: ohne -cpu result: BSOD STOP 0x0000003E attempt: -M pc-0.11 -cpu pentium3 result: kvm_run: Exec format error, kvm_run returned -8 attempt: -M pc-0.11 -cpu qemu64,level=1 result: BSOD STOP 0x0000001E attempt: -M pc-0.11 -cpu 486 result: kvm_run: Exec format error, kvm_run returned -8What can I do to continue accounting on the NT4 guest even after upgrading from kvm version 72+dfsg-5+squeeze1 (works) to something current? What strategy should I follow to avoid even the slightest change of (virtual) hardware? I thought, virtualisation was a good idea to keep legacy systems running.
-- Martin Stut ------------------------------------------------------------------------ Dünsbergstr. 38 Phone: +49-6421-953639 35043 Marburg Email: mar...@stut.de GERMANY Web: www.stut.de <http://www.stut.de/>
smime.p7s
Description: S/MIME Cryptographic Signature
