> Boris, are you suggesting the for pre-3.2 kernels, the fix is to backport the > 3.2 fix (i.e commit > 5fbdc10395cd500d6ff844825a918c4e6f38de37, remove XEN_PLATFORM_PCI config > option)?
No , I am not suggesting this back port. XEN_PLATFORM_PCI should be equal "y" for Oneiric kernels (3.0.X), (3.1.X) > From memory, I think on 3.1 Oneiric, CONFIG_XEN_BLKDEV_FRONTEND=y, > CONFIG_XEN_NETDEV_FRONTEND=y are already fixed I don't think so. Please view :- boris@boris-System-P5Q3:/boot$ cat config-3.0.0-13-generic | grep XEN CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set # CONFIG_XEN_DEBUG is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m <= not fixed CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m <= not fixed CONFIG_XEN_NETDEV_BACKEND=m CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m CONFIG_HVC_XEN=y CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=m CONFIG_XEN_GRANT_DEV_ALLOC=m CONFIG_XEN_PLATFORM_PCI=m CONFIG_SWIOTLB_XEN=y I am just saying , that due to Precise will go with 3.2.X kernel, issue is already closed upstream I've already tested Precise (11/26/11) as PV-on-HVM at Xen 4.1.2 Oneiric Dom0. It works as expected. Ubuntu has nothing to fix with this kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886521 Title: CONFIG_XEN_PLATFORM_PCI should be "y" when building 3.1 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
