Comment 21 for bug 886521

On Lucid (and I think Maverick), the CONFIG_XEN_PVHM and CONFIG_XEN_PLATFORM_PCI settings are not defined, and indeed do not exist in the code. However, Lucid (and I think Maverick) still do not boot on Xen4 in HVM mode. I believe this is because these kernels behave in the same way as later kernels with CONFIG_XEN_PLATFORM_PCI=y and CONFIG_XEN_PVHVM=y. IE, early in the boot sequence the Xen code is writing to the magic port, and on the basis of the host domU supporting PCI, unplugging the sda and eth0 devices. The pv modules appear to be omitted from the various udebs and installers and/or the the install CDs., and CONFIG_XEN_NETDEV_FRONTEND and CONFIG_XEN_BLKDEV_FRONTEND are defined as 'm' in in the common config.

The manner to support these consistent with the Xen4 changes proposed on Natty and Oneiric, and the upstream plus common config fix already applied to Precise, is to build these modules as builtins (I think a change to the installer CDs and udeb builds might be possible, but that is inconsistent and complicated).

The attached patch therefore makes a simple change to the common config to make CONFIG_XEN_NETDEV_FRONTEND=y and CONFIG_XEN_BLKDEV_FRONTEND=y, replacing the previous value 'm' (both cases). I have not build-tested or install-tested this patch as I do not have the compile and test resources.

This was developed against Lucid, but visual inspection suggests the same needs to be done on Maverick (but not Oneiric or Natty - see previous comment).

No change is necessary on Precise.

THIS PATCH IS FOR COMMENT AND REVIEW ONLY. IT IS NOT EVEN COMPILE TESTED. DO NOT APPLY WITHOUT TESTING.