From: "Alex Bennée" <alex.bennee@linaro.org>
To: Bug 1706296 <1706296@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1706296] Re: Booting NT 4 disk causes /home/rjones/d/qemu/cpus.c:1580:qemu_mutex_lock_iothread: assertion failed: (!qemu_mutex_iothread_locked())
Date: Fri, 18 Aug 2017 09:40:31 +0100 [thread overview]
Message-ID: <87shgpi800.fsf@linaro.org> (raw)
In-Reply-To: <150240857521.18943.1371547756430353016.malone@chaenomeles.canonical.com>
John Arbuckle <programmingkidx@gmail.com> writes:
> Using '-cpu 486' gets past the assertion error. I guess Windows NT 4.0
> is not compatible with newer Intel processors.
It might be related. The assertion error is caused by the fact an
exception has occurred and processor is trying to dump a stack frame that
overlaps from RAM into device memory. As the IRQ/exception handling is
already under the BQL (as it changes machine state) we get the assertion
when it tries to take the BQL a second time when accessing device
memory.
We can drop the lock in the stack frame writing code but I don't know
what effect that would have as the guest still might crash having tried
to write a stack frame to device memory....
>
> Currently I can install Windows NT 4.0, but booting from the
> installation has its problems. It won't boot unless you use the NTFS
> file system. Even with this file system I still see a BSOD that states
> INACCESSIBLE_BOOT_DEVICE. Not sure what is wrong. Switching to a SCSI
> controller didn't help.
--
Alex Bennée
next prev parent reply other threads:[~2017-08-18 8:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 9:30 [Qemu-devel] [Bug 1706296] [NEW] Booting NT 4 disk causes /home/rjones/d/qemu/cpus.c:1580:qemu_mutex_lock_iothread: assertion failed: (!qemu_mutex_iothread_locked()) Richard Jones
2017-07-25 11:36 ` Thomas Huth
2017-07-25 14:54 ` Alex Bennée
2017-07-25 15:12 ` Peter Maydell
2017-07-25 17:54 ` Dr. David Alan Gilbert
2017-07-31 20:34 ` [Qemu-devel] [Bug 1706296] " Paolo Bonzini
2017-08-10 23:42 ` John Arbuckle
2017-08-18 8:40 ` Alex Bennée [this message]
2017-08-18 8:59 ` Peter Maydell
2017-08-18 10:23 ` Alex Bennée
2017-08-18 10:33 ` Peter Maydell
2017-09-21 9:23 ` Peter Maydell
2017-08-18 12:20 ` Richard Jones
2017-08-18 12:51 ` Peter Maydell
2017-08-17 18:53 ` John Arbuckle
2017-08-17 19:20 ` John Arbuckle
2017-08-18 13:32 ` John Arbuckle
2020-11-09 18:27 ` Thomas Huth
2020-11-09 20:03 ` Peter Maydell
2020-11-09 21:18 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shgpi800.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=1706296@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.