On Mon, Jan 21, 2019 at 04:16:35PM +, Anthony PERARD wrote:
> As for
> https://lists.xenproject.org/archives/html/xen-devel/2018-10/msg01950.html
> It appear that the same QEMU 2.9.1 is used, but QEMU isn't supposed to
> use the function xc_map_foreign_bulk when built against Xen 4.12. That
>
On Fri, Oct 26, 2018 at 12:10:16PM +0200, Olaf Hering wrote:
> A given Qemu version can not predict what version of Xen it will run on.
> There are some checks in configure to decide what Xen libraries and
> functions are available. How exactly these functions must be accessed
> has to be decided b
Am Thu, 13 Dec 2018 11:05:25 +
schrieb Anthony PERARD :
> Hi,
>
> Ian, we have those XC_WANT_COMPAT_* #defines to allow consumers of Xen
> libs be able to use old interfaces. Do you think it's a good idea to
> have this consumers (QEMU here) #undef the flag when it has implemented
> the newer
Hi,
Ian, we have those XC_WANT_COMPAT_* #defines to allow consumers of Xen
libs be able to use old interfaces. Do you think it's a good idea to
have this consumers (QEMU here) #undef the flag when it has implemented
the newer interface?
I guess the issue we have here is that when libxc interface
Ping?
On Fri, Oct 26, Olaf Hering wrote:
> A given Qemu version can not predict what version of Xen it will run on.
> There are some checks in configure to decide what Xen libraries and
> functions are available. How exactly these functions must be accessed
> has to be decided by configure and t