21.05.2010 16:14, Michael Tokarev wrote:
21.05.2010 16:01, Michael Tokarev wrote:
This is a guest issue, not kvm issue. See
http://marc.info/?l=qemu-devel&m=127439130431895
And indeed, I tried to set up winNT on two other
machines here, it fails the same way during boot,
with the same STOP: 0x00000003 error (incorrect
multi-processor configuration). It has been fixed
in service pack 6. There's also a workaround in
kvm, to use -cpu qemu64,level=1 (the level is what
matters, not qemu64).
Correction. The original bugreport, about 0x0000003E
code, is something to do with the windows NT reacting
to (slight) hardware change it is running on. This
is something outside of scope of kvm - yes, kvm changes,
and virtual devices it emulates for the guest changes
too, it's just like hardware upgrade (usually leads to
reinstall of windowsNT). At least upgrading kvm from
-72 to -0.12 does not make windowsNT install performed
in kvm-72 to break, it must be some even older than -72
install.
The other problem reported in this thread, about 0x000003
error code, which leads to inability to reinstall the system,
is also due to windowsNT bug.
Ehm. Another correction.
the two problems:
0x0000003E - invalid smp configuration
this is the guest bug seen during install, fixed in sp6
0x0000001E - inaccessible boot device
this is what you get by changing (even virtual) hardware
on a machine running windows NT
Since the bug mentions both problems.
Please excuse me for the noise: the number of digits in the
error codes puzzled me :)
The recommended course of things is to reinstall windows
NT (or find a way to fix the issue inside it without
reinstalling), for which -cpu qemu64,level=1 is a
work-around for the bug mentioned. After install,
either continue using the level=1 suboption, or apply
service pack 6, which will fix the bug in the guest.
Just to clarify things...
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
