On Wed, Mar 28, 2018 at 03:13:35PM +0100, Daniel P. Berrangé wrote:
On Wed, Mar 28, 2018 at 08:10:34AM -0600, Jim Fehlig wrote:On 03/28/2018 07:28 AM, Daniel P. Berrangé wrote: > On Wed, Mar 28, 2018 at 10:03:51AM +0100, Daniel P. Berrangé wrote: > > On Tue, Mar 27, 2018 at 04:31:29PM -0600, Jim Fehlig wrote: > > > Currently the libxl driver claims support for Xen >= 4.4, but > > > Xen 4.4 and 4.5 are no longer supported upstream. Let's increase > > > the minimum supported version to 4.6. > > > > Generally libvirt would keep supporting things even if upstream > > drops support, if some relevant distro still ships and supports > > it. RHEL doesn't ship libxl though, so just Q of whether these > > libxl versions are relevant to any Suse or Debian distros that > > are actively used. > > BTW, if we're willing to drop old versions of Xen wrt the libxl > driver, shouldn't we first drop the legacy Xen driver which is > used with even older versions of Xen < 4.2 ? Touche :-). I have a dusty patchset to do that too. Time to brush it off and nuke the old driver first.Great, I look forward to seeing that, because it will simplify some work I'm trying todo to cleanup the virDrvConnectOpen method impls.
Sorry for hijacking the thread, but this is somehow related.
From the hypervisor drivers we have, can we also drop the following ones?
- openvz: Last hypervisor-related non-trivial feature added in 0.9.12.
- PHYP: Apart from leaks, coverity fixes and trivial implementation changes, there was:
- no bigger change since Jul 2011
- no feature-related (functionality-adding) change since Apr 2011 which
was less than 2 years since its inclusion in libvirt
- UML: I tired to find when some patch was related to UML, but I stopped
scrolling due to boredom
From the non-hypervisor drivers, is anyone using the HAL backend of nodedev driver?
Have a nice day,
MartinAttachment:
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
