On Mon, Jul 28, 2008 at 04:52:28PM +0200, Gerd Hoffmann wrote:
+/* xen_machine.c */
+extern QEMUMachine xenpv_machine;
+extern QEMUMachine xenfv_machine;
Why does xenfv need its own machine type?
This is how xen's qemu-dm handles it at the moment and I've decided to
do it the same way for simplicity. I think qemu could also figure it
using a hypercall.
This is something I originally added to QEMU in Xen's tree. The basic
idea is that the 'xenpv' macjine is a machine which /only/ provides the
paravirtualized Xen backends drivers. The 'xenfv' machine type is just
the same as the 'pc' machine type, but with the /addition/ of the Xen
paravirtualized backends. Perhaps the latter could be thought of as
more of a 'xenpc' (cf 'pc' and 'isapc') becasue its a variation on the
regular PC machine type. Annoying that all the acronyms I come up with
only differ by one letter :-)