At the moment QEMU and libvirt are quite far behind in the latest rc (rc3 when this was posted).

 

RC3 versions:

Libvirt version: 1.3.1

QEMU version: 2.5.1 (cant find anything anywhere about this release?)

 

Current:

Libvirt version: 2.1.0 (7 releases behind)

QEMU version: 2.6.1 \ 2.7.0 rc3 (2\3 releases behind)

 

Are there plans to keep more up to date with these releases now unraid is trying to market itself as a hypervisor\NAS combo OS? or at least allow parts like this to be more modular and able to be upgraded outside of a major\minor OS update?

 

sources:

https://libvirt.org

http://wiki.qemu.org/

 

Mark

At the moment QEMU and libvirt are quite far behind in the latest rc (rc3 when this was posted).

 

RC3 versions:

Libvirt version: 1.3.1

QEMU version: 2.5.1 (cant find anything anywhere about this release?)

 

Current:

Libvirt version: 2.1.0 (7 releases behind)

QEMU version: 2.6.1 \ 2.7.0 rc3 (2\3 releases behind)

 

Are there plans to keep more up to date with these releases now unraid is trying to market itself as a hypervisor\NAS combo OS? or at least allow parts like this to be more modular and able to be upgraded outside of a major\minor OS update?

 

sources:

https://libvirt.org

http://wiki.qemu.org/

 

Mark

 

What features in Libvirt / QEMU stable (2.1.0 and 2.6.1) are desirable that aren't available in the currently stable unRAID OS release?  I would hardly call the current versions "quite far behind" in the grand scheme of things.

 

Libvirt 1.3.1 released in January 2016

QEMU 2.5.1 released in March 2016

 

The number of releases behind really doesn't matter as each software maintainer can put out as many releases in whatever timeframe they want.  What really matters is when a release adds features or fixes bugs that will affect the majority of our users.  Those are the things we look for to justify prioritization of a software package update.  That and of course security fixes.

 

This isn't to say we won't update these packages.  On the contrary, we have plans to do both in 6.3.  However, there are reasons we haven't upgraded them yet (some compatibility issues that need to be sorted out) and quite frankly, the major features behind added to virtualization are slated for QEMU 2.7, which is when we plan to upgrade next.

 

What features in Libvirt / QEMU stable (2.1.0 and 2.6.1) are desirable that aren't available in the currently stable unRAID OS release?  I would hardly call the current versions "quite far behind" in the grand scheme of things.

 

 

The ability to spoof vendor_id as hyperV enlightenment to fool Nvidia drivers into loading, is only available for libvirt v 1.3.3 and up.

 

 

What features in Libvirt / QEMU stable (2.1.0 and 2.6.1) are desirable that aren't available in the currently stable unRAID OS release?  I would hardly call the current versions "quite far behind" in the grand scheme of things.

 

 

The ability to spoof vendor_id as hyperV enlightenment to fool Nvidia drivers into loading, is only available for libvirt v 1.3.3 and up.

 

These are the versions in 6.3 RC6:

 

Libvirt version:2.4.0

QEMU version:2.7.0