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.
** Tags added: tcg
** Tags added: i386
** 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/1908781
Title:
x86-64 not faulting when CS.L = 1 and CS.D = 1
Status in QEMU:
Incomplete
Bug description:
In a UEFI application I accidentally created a code segment descriptor
where both the L and D bits were 1. This is supposed to generate a GP
fault (e.g. see page 2942 of
https://software.intel.com/sites/default/files/managed/39/c5/325462
-sdm-vol-1-2abcd-3abcd.pdf). When running with KVM a fault did indeed
occur, but when not specifying any acceleration, no fault occurred.
Let me know if you need me to develop a minimum example to debug from.
At the moment it's all part of a slightly more complicated bit of
code.
Version: 5.2.0 (compiled from source)
Command line options: -smp cores=4 -m 8192 (plus whatever uefi-run adds to
plug in OVMF and my UEFI application).
Environment: Ubuntu 20.04 on Ryzen 3700X
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1908781/+subscriptions
