

QEMU in a Xen system only provides device model (DM) emulation and not any CPU instruction emulation, so the nominal arch doesn't actually matter and Xen builds i386 everywhere as a basically arbitrary choice. Why is qemu-system-i386 used even on x86_64 and even non-x86? These trees are still around for reference, but are not in use any more.

#Qemu system i386 hardware code#

Some guest operating systems, especially non-free systems that rely on licensing bound to a specific hardware, do not behave nicely when hardware is changed under their feet.
#Qemu system i386 hardware upgrade#
After a Dom0 upgrade to a newer Xen version the new 'qemu-xen' device model is recognized as a significant hardware change. The 'qemu-xen-traditional' fork remains available to support guest OSs that were installed using it. The xl toolstack describes this version as 'qemu-xen', and this became the default from Xen 4.3 onward. However since Qemu 1.0 support for Xen has been part of the mainline Qemu and can be used with Xen from 4.2 onwards. Historically Xen contained a fork of qemu with Xen support added, known as 'qemu-xen-traditional' in the xl toolstack.
