From: Launchpad Bug Tracker <1898954@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1898954] Re: x86 f1 opcode hangs qemu
Date: Fri, 09 Jul 2021 04:17:22 -0000 [thread overview]
Message-ID: <162580424305.19936.11467059373325406672.malone@loganberry.canonical.com> (raw)
In-Reply-To: 160211647401.12043.14789296539766807523.malonedeb@gac.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1898954
Title:
x86 f1 opcode hangs qemu
Status in QEMU:
Expired
Bug description:
I have qemu installed and running in linux and windows
in linux i execute the following simple code in real mode of cpu in my vm
90 nop
90 nop
90 nop
f1 ;this should conjure up my interrupt handler from ivt int 1
--------- end of code ----
it works properly in vbox,qemu linux,and even in my boot loder
on a real platform
it doeas not work fine in windows 10 (32 bit efi) based qemu
---
all of the below was retyped there may be typo
so onwards to the flawed software
********** for qemu-system-x86_64.exe **********
info version
4.2.0v4.2.0.11797-g2890edc853-dirty
********** for qemu-system-i386.exe **********
info version
4.2.0v4.2.0.11797-g2890edc853-dirty
***********************************************
my startup code is
"d:\programs\qemu\qemu-system-x86_64.exe" -m 16M -boot a -fda "d:\floppy.img" -cpu Nehalem -machine pc
---
also same flaw if i change above section to
"d:\programs\qemu\qemu-system-i386.exe"
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1898954/+subscriptions
prev parent reply other threads:[~2021-07-09 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 0:21 [Bug 1898954] [NEW] x86 f1 opcode hangs qemu pat leese
2021-05-09 14:28 ` [Bug 1898954] " Thomas Huth
2021-07-09 4:17 ` Launchpad Bug Tracker [this message]
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=162580424305.19936.11467059373325406672.malone@loganberry.canonical.com \
--to=1898954@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.