On Wed, 2013-02-13 at 12:38 +0000, M A Young wrote:
xen-4.2.0 added a second qemu-xen image - the patch takes it out again. As the traditional qemu-xen was still the default so it didn't seem worth adding another, particularly as I would ideally like to drop xen's qemu altogether and go back to Fedora's.
Thanks for the quick response, Michael.
I'll enable the qemu-xen build again and then I should be fine.
As this seems to be about seabios, you should note that Fedora xen 4.2 doesn't build its own seabios either, it uses the Fedora version - see the xen.use.fedora.seabios.patch patch. I didn't see any reason to duplicate what was already in Fedora (and as far as I understand it it is in general against Fedora's policy to do so).
Right. Although AFAICT nothing in your build of Xen will *use* this SeaBIOS binary, since it's for the qemu-xen build that you disabled?
Anyway, when we get to the point that you're enabling qemu-xen in the Fedora builds, I hope you'll be using just OVMF + SeaBIOS as a CSM, and not having to mess around with a choice of firmwares according to what you're booting in it today. I'll look at fixing that in the upstream Xen build setup. But first I'll check I haven't broken native SeaBIOS... :)