<commit_before>---
title: OVirt 3.6 Release Notes
category: documentation
authors: didi, mperina, sandrobonazzola
wiki_category: Documentation
wiki_title: OVirt 3.6 Release Notes
wiki_revision_count: 34
wiki_last_updated: 2015-05-22
---

# oVirt 3.6.0 Release Candidate Notes

The oVirt Project is pleased to announce the availability of oVirt 3.6.0 First Candidate Release as of September 28th, 2015.

oVirt is an open source alternative to VMware vSphere, and provides an awesome KVM management interface for multi-node virtualization. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7, (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar).

To find out more about features which were added in previous oVirt releases, check out the [previous versions release notes](http://www.ovirt.org/Category:Releases). For a general overview of oVirt, read [ the Quick Start Guide](Quick_Start_Guide) and the [about oVirt](about oVirt) page.

### Experimental Docker Integration

oVirt Engine setup now provides experimental [ Cinder and Glance](CinderGlance Docker Integration) automated deployment using Docker

Cinder and Glance images are from kollaglue project. <https://github.com/openstack/kolla> kollaglue is 'the official' effort from openstack project to provide production-ready containers and deployment tools for operating OpenStack clouds. The kollaglue Docker images are built by the Kolla project maintainers. On oVirt side we have an optional plugin for oVirt engine-setup to pull and deploy their ready to use containers (glance and cinder only) and automatically adding them into your oVirt engine isntance.

Recently the cinder container setup for oVirt got broken cause they introduced the use of Ansible's playbooks to customize and complete the container setup and unfortunately we are still not ready for that. You should be able to manually setup cinder with that containers following this guides: <https://github.com/openstack/kolla/blob/master/doc/ansible-deployment.rst> <https://github.com/openstack/kolla/blob/master/doc/cinder-guide.rst>

Glance container setup and its oVirt integration are still working.

Kolla images will not run on Fedora 22 or later currently. Fedora 22 compresses kernel modules with the .xz compressed format. The guestfs system in the CentOS family of containers cannot read these images because a dependent package supermin in CentOS needs to be updated to add .xz compressed format support.

### Self Hosted Engine FC Support

Hosted Engine has now added support for [FC storage](Features/Self_Hosted_Engine_FC_Support)

### Self Hosted Engine Gluster Support

*   Hosted Engine has now added support for [Gluster storage](Features/Self_Hosted_Engine_Gluster_Support)

### oVirt Live

oVirt Live has been rebased on CentOS 7 allowing to run oVirt in 3.6 compatibility mode

### Experimental Debian Support for Hosts

Experimental support for running oVirt Hosts on Debian (or similar) has been added providing custom packaging of needed dependencies.

### Fedora 22 Support

Support for running oVirt on Fedora 22 (or similar) has been added providing custom packaging of Wildfly 8.2.0.

### VirtIO Serial Console

Users can now directly connect, using ssh, to the [ serial consoles](Features/Serial_Console) of the VMs.

### Known Issues

*   Use SELinux Permissive mode in order to avoid denials using VDSM and Gluster

<!-- -->

*   If engine-setup is stuck when starting ovirt-websocket-proxy manually stop the service and re-start it when engine-setup finishes.

### Affinity Rules Enforcement Manager

This feature is a manager that checks if hard affinity rules are broken and migrates VMs in order to enforce them.
Behavior of the manager:

1.  Manager only starts migrations when no other migrations are active in the cluster.
2.  Manager uses scheduler's automatic migration command to comply with filter and weight policies.
3.  Manager has a new and improved algorithm for finding affinity rule contradictions called "Unified Affinity Group Algorithm".
4.  Manager will enforce affinity rules one by one, starting with the violated affinity rule which consists of most VMs.
5.  Manager's strategy to enforce affinity rules in case of positive groups is to migrate VMs from the hypervisor that has the minimum number of VMs from the same affinity group to the one that has the most VMs(Taking into account the Scheduler policies. Sometimes VMs might be migrated to a different host if the scheduler thinks it's better).
6.  Affinity rules only work for clusters with version >= 3.5.

### Distribution specific issues

#### Fedora 22

*   You'll need to execute

      dnf install yum

reintroducing yum package manager in order to use the host, being dnf not yet supported by otopi.

*   on hosts you need to add following line to **/etc/ssh/sshd_config**

      KexAlgorithms curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

and then execute

      # systemctl restart sshd

before adding the host to the engine.

#### RHEL 7.1 - CentOS 7.1 and similar

*   NFS startup on EL7.1 requires manual startup of rpcbind.service before running engine setup in order to avoid

      [ INFO  ] Restarting nfs services
      [ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute

*   v2v feature on EL 7.1 requires manual installation of virt-v2v packages. See for more details. This workaround will not be needed once EL 7.2 is out

#### RHEL 6.7 - CentOS 6.7 and similar

*   Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the packages requiring it are not built anymore for EL6

# Install / Upgrade from previous versions

### RELEASE CANDIDATE

In order to install this release you've to enable oVirt 3.6 pre release repository.

### Fedora / CentOS / RHEL

In order to install it on a clean system, you need to run (see also [Known Issues](#Known_Issues) above):

`# yum install `[`http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm`](http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm)<commit_msg>Updated OVirt 3.6 Release Notes<commit_after>---
title: OVirt 3.6 Release Notes
category: documentation
authors: didi, mperina, sandrobonazzola
wiki_category: Documentation
wiki_title: OVirt 3.6 Release Notes
wiki_revision_count: 34
wiki_last_updated: 2015-05-22
---

# oVirt 3.6.0 Release Candidate Notes

The oVirt Project is pleased to announce the availability of oVirt 3.6.0 First Candidate Release as of September 28th, 2015.

oVirt is an open source alternative to VMware vSphere, and provides an awesome KVM management interface for multi-node virtualization. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7, (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar).

To find out more about features which were added in previous oVirt releases, check out the [previous versions release notes](http://www.ovirt.org/Category:Releases). For a general overview of oVirt, read [ the Quick Start Guide](Quick_Start_Guide) and the [about oVirt](about oVirt) page.

### Experimental Docker Integration

oVirt Engine setup now provides experimental [ Cinder and Glance](CinderGlance Docker Integration) automated deployment using Docker

Cinder and Glance images are from kollaglue project. <https://github.com/openstack/kolla> kollaglue is 'the official' effort from openstack project to provide production-ready containers and deployment tools for operating OpenStack clouds. The kollaglue Docker images are built by the Kolla project maintainers. On oVirt side we have an optional plugin for oVirt engine-setup to pull and deploy their ready to use containers (glance and cinder only) and automatically adding them into your oVirt engine isntance.

Recently the cinder container setup for oVirt got broken cause they introduced the use of Ansible's playbooks to customize and complete the container setup and unfortunately we are still not ready for that. You should be able to manually setup cinder with that containers following this guides: <https://github.com/openstack/kolla/blob/master/doc/ansible-deployment.rst> <https://github.com/openstack/kolla/blob/master/doc/cinder-guide.rst>

Glance container setup and its oVirt integration are still working.

Kolla images will not run on Fedora 22 or later currently. Fedora 22 compresses kernel modules with the .xz compressed format. The guestfs system in the CentOS family of containers cannot read these images because a dependent package supermin in CentOS needs to be updated to add .xz compressed format support.

### Self Hosted Engine FC Support

Hosted Engine has now added support for [FC storage](Features/Self_Hosted_Engine_FC_Support)

### Self Hosted Engine Gluster Support

*   Hosted Engine has now added support for [Gluster storage](Features/Self_Hosted_Engine_Gluster_Support)

### oVirt Live

oVirt Live has been rebased on CentOS 7 allowing to run oVirt in 3.6 compatibility mode

### Experimental Debian Support for Hosts

Experimental support for running oVirt Hosts on Debian (or similar) has been added providing custom packaging of needed dependencies.

### Fedora 22 Support

Support for running oVirt on Fedora 22 (or similar) has been added providing custom packaging of Wildfly 8.2.0.

### VirtIO Serial Console

Users can now directly connect, using ssh, to the [ serial consoles](Features/Serial_Console) of the VMs.

### Affinity Rules Enforcement Manager

This feature is a manager that checks if hard affinity rules are broken and migrates VMs in order to enforce them.
Behavior of the manager:

1.  Manager only starts migrations when no other migrations are active in the cluster.
2.  Manager uses scheduler's automatic migration command to comply with filter and weight policies.
3.  Manager has a new and improved algorithm for finding affinity rule contradictions called "Unified Affinity Group Algorithm".
4.  Manager will enforce affinity rules one by one, starting with the violated affinity rule which consists of most VMs.
5.  Manager's strategy to enforce affinity rules in case of positive groups is to migrate VMs from the hypervisor that has the minimum number of VMs from the same affinity group to the one that has the most VMs(Taking into account the Scheduler policies. Sometimes VMs might be migrated to a different host if the scheduler thinks it's better).
6.  Affinity rules only work for clusters with version >= 3.5.

### Known Issues

*   Use SELinux Permissive mode in order to avoid denials using VDSM and Gluster

<!-- -->

*   If engine-setup is stuck when starting ovirt-websocket-proxy manually stop the service and re-start it when engine-setup finishes.

### Distribution specific issues

#### Fedora 22

*   You'll need to execute

      dnf install yum

reintroducing yum package manager in order to use the host, being dnf not yet supported by otopi.

*   on hosts you need to add following line to **/etc/ssh/sshd_config**

      KexAlgorithms curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

and then execute

      # systemctl restart sshd

before adding the host to the engine.

*   OTOPI 1.4.0 introduce DNF package manager support. If DNF packager is used, the version locking plugin is not working properly . To workaround the issue:

       # dnf install python-dnf-plugins-extras-versionlock.noarch
       # cp /etc/yum/pluginconf.d/versionlock.list /etc/dnf/plugins/versionlock.list

#### RHEL 7.1 - CentOS 7.1 and similar

*   NFS startup on EL7.1 requires manual startup of rpcbind.service before running engine setup in order to avoid

      [ INFO  ] Restarting nfs services
      [ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute

*   v2v feature on EL 7.1 requires manual installation of virt-v2v packages. See for more details. This workaround will not be needed once EL 7.2 is out

#### RHEL 6.7 - CentOS 6.7 and similar

*   Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the packages requiring it are not built anymore for EL6

# Install / Upgrade from previous versions

### RELEASE CANDIDATE

In order to install this release you've to enable oVirt 3.6 pre release repository.

### Fedora / CentOS / RHEL

In order to install it on a clean system, you need to run (see also [Known Issues](#Known_Issues) above):

`# yum install `[`http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm`](http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm)
{'fraction_non_alphanumeric': 0.05856102716667971, 'fraction_numerical': 0.01824160338213419, 'mean_word_length': 4.394425675675675, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 13, 'https://': 6, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2954442', 'n_tokens_mistral': 3765, 'n_tokens_neox': 3483, 'n_words': 1693}