qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] Help with Windows NT 4.0
Date: Fri, 18 Aug 2017 10:46:54 +0200	[thread overview]
Message-ID: <CACXAS8BKpKbkAMXPDKw2exX-MKO7sC_R5NbMSysCvjcx0qZJ6Q@mail.gmail.com> (raw)
In-Reply-To: <D7EDAC6E-E598-491A-BB4F-789DC57196A0@gmail.com>

On Fri, Aug 18, 2017 at 6:31 AM, Programmingkid
<programmingkidx@gmail.com> wrote:
>
>> On Aug 15, 2017, at 6:27 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 15/08/2017 20:46, Programmingkid wrote:
>>>
>>>> On Aug 14, 2017, at 2:51 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>>
>>>> On 13/08/2017 21:13, Programmingkid wrote:
>>>>> Lately I found out that Windows NT 4.0 seems to work well with the
>>>>> 486 and pentium processors. Using "-cpu 486" made installing it
>>>>> actually work. Now I am seeing another issue. When I boot Windows NT
>>>>> 4.0 I see this error message:
>>>>>
>>>>> *** STOP: 0x0000007B (0x807A8610,0x00000000,0x00000000,0x00000000)
>>>>> INACESSIBLE_BOOT_DEVICE
>>>>>
>>>>> Would anyone know a way to solve this issue?
>>>>
>>>> Hervé is probably the best person to answer this question.  Maybe try
>>>> installing it with SCSI disks ("-drive if=scsi,id=hd,file=... -drive
>>>> if=scsi,id=cd,file=... -device lsi -device scsi-hd,drive=hd -device
>>>> scsi-cd,drive=cd").
>>>>
>>>> Thanks,
>>>>
>>>> Paolo
>>>
>>> Thanks for the help. Unfortunately trying to boot from the install CD leads to the INACCESSIBLE_BOOT_DEVICE error when using SCSI.
>>
>> Try with 0.12.
>>
>> Paolo
>
> I finally figured out why I was seeing the INACESSIBLE_BOOT_DEVICE error. It was because of the qcow2 image format. As soon as I switched to the qcow format, the error disappeared.

That's weird. The image format is not guest visible. Probably you are
hitting some sort of timing issue.


-- 
Regards,
Artyom Tarasenko

SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu

  reply	other threads:[~2017-08-18  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 19:13 [Qemu-devel] Help with Windows NT 4.0 Programmingkid
2017-08-14  6:51 ` Paolo Bonzini
2017-08-14  7:18   ` Mark Cave-Ayland
2017-08-15 19:26     ` Programmingkid
2017-08-22 15:19     ` Programmingkid
2017-08-15 18:46   ` Programmingkid
2017-08-15 22:27     ` Paolo Bonzini
2017-08-16 16:32       ` G 3
2017-08-16 23:19       ` G 3
2017-08-18  4:31       ` Programmingkid
2017-08-18  8:46         ` Artyom Tarasenko [this message]
2017-08-18 13:36           ` Programmingkid
2017-08-18 19:23             ` John Snow
2017-08-18 19:48               ` Programmingkid

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=CACXAS8BKpKbkAMXPDKw2exX-MKO7sC_R5NbMSysCvjcx0qZJ6Q@mail.gmail.com \
    --to=atar4qemu@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=hpoussin@reactos.org \
    --cc=pbonzini@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).