Re: What changed since kvm-72 resulting in winNT to fail to boot (STOP 0x0000001E) ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/30/2010 11:06 PM, Michael Tokarev wrote:
I've a bugreport handy, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575439
about the apparent problem booting winNT 4 in kvm 0.12.
At least 2 people were hit by this issue.  In short, when
booting winNT 4.0, it BSODs with error code 0x0000001E,
which means "inaccessible boot device".

Note that it is when upgrading from -72 to 0.12.  But the
second person on the bug page also tried to reinstall the
OS, and that failed as well, now with a different error
message.


What about 0.11?  Does it work?

--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux