Jump to: navigation, search

Note: This page is used to gather ideas about what we could do when switching to the next major version of QEMU, i.e. version 3.0. The ideas here are by no means mandatory - it is rather meant as a base for discussion.

So for version 3.0, we very likely should do the following:

  • Make sure that we remove all interfaces and features that are marked as deprecated since two releases according to the qemu-doc deprecation chapter (see https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features for details)
  • Use "--accel kvm:tcg" by default instead of running in TCG mode by default (hax is too far from feature parity, but we could also add "hvf" to the list in case it gets merged in time and is stable enough)
  • Stop supporting SDL 1.2

Controversial ideas that likely need some discussion first:

  • Update all python code to use python 3.x instead of python 2.x
  • Get rid of some really, really old and very likely completely unused machine types, like pc-0.10 and pc-0.11
  • Remove some code which is likely hardly used anymore and where we do not have an active maintainer since years? Especially if we do not have an "make check" regression test for it. (i.e. did anybody test the bluetooth code in the recent years?)
    • Samsung was using it as recently as 2014. Also don't underestimate the Android emulator, it's in widespread use.
  • Stop supporting GTK2 ?
  • Use q35 as default instead of pc-i440fx ? We likely can not do it due to compatibility issues ... but let's keep it in mind in case somebody comes up with a clever solution...