[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2] libxl: Handle xen_platform_pci=0 case with qemu-xen.

Il 29/11/2013 11:34, Ian Campbell ha scritto:
On Wed, 2013-11-27 at 18:21 +0000, Anthony PERARD wrote:
This should result in QEMU *not* adding the xen-platform device.

Since QEMU 1.6, this can be achieved by using a different qemu machine.
The one used by libxl is "xenfv", but using QEMU >=1.6 with "-machine
pc,accel=xen" works as well with only one difference compared to
"xenfv", there is no xen-platform device.

Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>

I wonder -- should we make a statement somewhere about the minimum
supported version qemu? Similar to how we do with e.g. gcc. I suppose we
would start at 1.5 since that is when support first went upstream? As
time goes by we will need to take into account what version is in the
various stable distros.

Perhaps we should add this to the README as an optional build
dependency. e.g. "Although Xen ships with an included qemu-xen you can
also choose to use a system provided qemu provided it is built with Xen
support and is at least version X.Y"?

I think is good to suggest qemu>=1.6.1
In the last months I have kept tested a lot of the newer versions of qemu upstream from upstream git (xen git was with qemu 1.3), if I remember good qemu 1.5 have an important bug with xen on some cases, solved with 1.6 but 1.6 have a critical bug with all xen hvm domUs solved with 1.6.1. With 1.6.1 I not found any critical or important xen related new bugs or regressions for now, I tested windows 7, xp and some fedora, ubuntu and debian versions as hvm domUs.


Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.