qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WInd


From: Michal Suchanek
Subject: [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping
Date: Thu, 16 Sep 2010 14:34:45 -0000

Note that most of the section is generated by sysprep (the drivers
referencing C:\windows), only small part at the end is generated by my
script for additional drivers (references C:\drivers).

The previous images that did not have this section worked only on
controllers compatible with the MS generic PCI IDE driver (and also on
KVM).

** Attachment added: "sysprep mass storage section used in the image"
   
https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1593932/+files/paste_89914

-- 
DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping
https://bugs.launchpad.net/bugs/639651
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New
Status in Debian GNU/Linux: New

Bug description:
Positng the issue here since I did not get any reply on the ML.

I was trying to update some windows XP (SP3) images in kvm.

It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot after reseal (the first
is mini-setup) I get a BSOD with message
DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody
thinks it is interesting enough.

The same image works on hardware (which has controllers different from
the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as
PIIX3) so long as IO apic is enabled).

I am not sure if this is an error with the MS drivers or how they are
used in sysprep in this particular case or if his is some strange
error in qemu emulation in the PIIX3 controller or elsewhere.

The image is originally created on hardware with MP acpi (not virtualization).

qemu-kvm                  0.12.5+dfsg-2





reply via email to

[Prev in Thread] Current Thread [Next in Thread]