Triaging old bug tickets... has this ever been fixed, thus could we close this ticket nowadays? Or is there something left to do here?
** Changed in: qemu Status: Confirmed => Incomplete ** Changed in: qemu Assignee: Anthony Liguori (anthony-codemonkey) => (unassigned) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/530077 Title: kvm: 16-bit code execution failure should be more friendly Status in QEMU: Incomplete Bug description: Today, when kvm fails at 16-bit code execution, we report: spirit:~/qemu> qemu-kvm ./hda-fedora.img kvm: unhandled exit 80000021 kvm_run returned -22 There are three reasons exit reason 21 happens. The first is that a user is executing an image containing a workload that uses GFXBOOT or some other bootloader that exercises big real mode. On pre-Westmere Intel processors, VT could not handle big real mode. The second reason is that the guest's image is corrupted and we're executing random code. We accidentally fall into one of the unsupported modes for VT. Again, this is addressed on WSM. The third case is where there's an actual bug in KVM. This should be exceedingly rare at this stage. We should present a friendly error message explaining the possible causes and recommending corrective action. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/530077/+subscriptions