From: Dario Faggioli <dario.faggioli@citrix.com>
To: Martin Kletzander <mkletzan@redhat.com>, Jim Fehlig <jfehlig@suse.com>
Cc: Libvirt List <libvir-list@redhat.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [libvirt] Opinions on removing the old, legacy libvirt Xen driver
Date: Mon, 21 Nov 2016 10:57:01 +0100 [thread overview]
Message-ID: <1479722221.3832.106.camel@citrix.com> (raw)
In-Reply-To: <20161120223715.GB26559@wheatley>
[-- Attachment #1.1: Type: text/plain, Size: 1336 bytes --]
On Sun, 2016-11-20 at 23:37 +0100, Martin Kletzander wrote:
>
> I'm not familiar with Xen to such detail, particularly with its
> history,
> but allow me to (hopefully) help you with the decision by saying that
> we
> dropped support for any QEmu older than 0.12.0 (released on December
> 2009). And by that I don't mean that we stopped fixing bugs for
> those,
> but that libvirt now *mandates* version 0.12.0 or newer. That is
> what
> is available in CentOS 6 and similar (or as Dan stated it "RHEL-6 era
> distros). For others like me, who don't know when the Xen releases
> were
> made, I found out (for you) that it should be March 2011 for 4.1 and
> September that year for 4.2. So I'm not even going to ask in which
> version xl/libxl was introduced.
>
FYI, xl was introduced in Xen 4.1:
https://wiki.xen.org/wiki/XL
Xen 4.1 was indeed released on 25th March 2011:
https://wiki.xen.org/wiki/Xen_4.1_Release_Notes
Xen 4.2 was released on 17 Sept _2012_:
https://wiki.xen.org/wiki/Xen_Project_Release_Features
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-21 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 21:25 Opinions on removing the old, legacy libvirt Xen driver Jim Fehlig
2016-11-18 22:41 ` Dario Faggioli
2016-11-19 3:55 ` Konrad Rzeszutek Wilk
2016-11-19 16:34 ` Wei Liu
2016-11-20 22:37 ` [libvirt] " Martin Kletzander
2016-11-21 9:57 ` Dario Faggioli [this message]
2016-11-21 15:27 ` Neal Gompa
2016-11-21 15:37 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479722221.3832.106.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=jfehlig@suse.com \
--cc=libvir-list@redhat.com \
--cc=mkletzan@redhat.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.