From: Thomas Huth <1898954@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1898954] Re: x86 f1 opcode hangs qemu
Date: Sun, 09 May 2021 14:28:37 -0000 [thread overview]
Message-ID: <162057051712.16081.7876019943158371696.malone@soybean.canonical.com> (raw)
In-Reply-To: 160211647401.12043.14789296539766807523.malonedeb@gac.canonical.com
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
next prev parent reply other threads:[~2021-05-09 14:37 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 ` Thomas Huth [this message]
2021-07-09 4:17 ` [Bug 1898954] " Launchpad Bug Tracker
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=162057051712.16081.7876019943158371696.malone@soybean.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 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).