[ANN] oVirt 4.1.0 First Release Candidate is now available
The oVirt Project is pleased to announce the availability of the First Release candidate of oVirt 4.1.0 for testing, as of January 23rd, 2016 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the first release candidate of the 4.1 release series. 4.1.0 brings more than 250 enhancements and more than 700 bugfixes, including more than 300 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 24 (tech preview) * oVirt Node 4.1 See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Live iso is already available[5] - oVirt Node NG iso is already available[5] - Hosted Engine appliance is already available A release management page including planned schedule is also available[4] Additional Resources: * Read more about the oVirt 4.1.0 release highlights: http://www.ovirt.org/release/4.1.0/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.0/ [4] http://www.ovirt.org/develop/release-management/releases/4.1/release-managem... [5] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Mon, Jan 23, 2017 at 2:35 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
The oVirt Project is pleased to announce the availability of the First Release candidate of oVirt 4.1.0 for testing, as of January 23rd, 2016
This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production.
This update is the first release candidate of the 4.1 release series. 4.1.0 brings more than 250 enhancements and more than 700 bugfixes, including more than 300 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed.
This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later
This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 24 (tech preview) * oVirt Node 4.1
See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed.
Notes: - oVirt Live iso is already available[5] - oVirt Node NG iso is already available[5] - Hosted Engine appliance is already available
An updated Windows Guest Tools ISO is now available as well, from: http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24... An RPM package wrapping it is in the 4.1-pre repositories. Changes compared to the 4.0 version: - Uninstall fixes - Correct path to QEMU GA MSI files - Add Display Version as a postfix to the Display Name - Add Windows 10 support - Update to latest virtio-win/vdagent releases - Install virtio-rng driver Best,
A release management page including planned schedule is also available[4]
Additional Resources: * Read more about the oVirt 4.1.0 release highlights:http://www.ovirt.org/release/4.1.0/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/
[1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.0/ [4] http://www.ovirt.org/develop/release-management/releases/4.1/release-managem... [5] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Didi
On Wed, Jan 25, 2017 at 8:00 AM, Yedidyah Bar David <didi@redhat.com> wrote:
An updated Windows Guest Tools ISO is now available as well, from:
http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt- toolsSetup/4.1-1.fc24/
Is it meant to be used also in 4.0.x environments?
On Wed, Jan 25, 2017 at 10:38 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Wed, Jan 25, 2017 at 8:00 AM, Yedidyah Bar David <didi@redhat.com> wrote:
An updated Windows Guest Tools ISO is now available as well, from:
http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24...
Is it meant to be used also in 4.0.x environments?
I guess it should work - briefly tested it on a 4.0 and didn't notice problems. Please file bugs if you find them. Thanks! -- Didi
I tested this on a Windows 2012 R2 (x64) DataCenter VM, newly built, on oVirt 4.0.5. It suffers from the same bug that’s been present since at least oVirt 3.6: The Balloon service is setup with the wrong path: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\w2k12R2\amd64\blnsvr.exe" The correct path being: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" Note the small typo: “w2k12R2” when the actual files are under “2k12R2”. The fix is much the same as before: sc config BalloonService binpath= "C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" DisplayName= "Balloon Service" start= auto How is it that this bug persists? Is it being actively tracked? I found reference to someone possibly having “a look” but no follow-up: http://lists.ovirt.org/pipermail/users/2016-June/073690.html I did note one thing that appears to be fixed: the QEMU agent service is properly setup and runs (it had to be manually started in previous versions.) The oVirt and Spice services start up as expected. Thanks, Daniel On 1/25/17, 2:54 AM, "users-bounces@ovirt.org on behalf of Yedidyah Bar David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote: On Wed, Jan 25, 2017 at 10:38 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote: > On Wed, Jan 25, 2017 at 8:00 AM, Yedidyah Bar David <didi@redhat.com> wrote: >> >> >> >> An updated Windows Guest Tools ISO is now available as well, from: >> >> >> http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24... > > > Is it meant to be used also in 4.0.x environments? > I guess it should work - briefly tested it on a 4.0 and didn't notice problems. Please file bugs if you find them. Thanks! -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I tested this on a Windows 2012 R2 (x64) DataCenter VM, newly built, on oVirt 4.0.5. It suffers from the same bug that’s been present since at least oVirt 3.6: The Balloon service is setup with the wrong path: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\w2k12R2\amd64\blnsvr.exe" The correct path being: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" Note the small typo: “w2k12R2” when the actual files are under “2k12R2”. The fix is much the same as before: sc config BalloonService binpath= "C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" DisplayName= "Balloon Service" start= auto How is it that this bug persists? Is it being actively tracked? I found reference to someone possibly having “a look” but no follow-up: http://lists.ovirt.org/pipermail/users/2016-June/073690.html I did note one thing that appears to be fixed: the QEMU agent service is properly setup and runs (it had to be manually started in previous versions.) The oVirt and Spice services start up as expected. Thanks, Daniel On 1/25/17, 2:54 AM, "users-bounces@ovirt.org on behalf of Yedidyah Bar David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote: On Wed, Jan 25, 2017 at 10:38 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote: > On Wed, Jan 25, 2017 at 8:00 AM, Yedidyah Bar David <didi@redhat.com> wrote: >> >> >> >> An updated Windows Guest Tools ISO is now available as well, from: >> >> >> http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24... > > > Is it meant to be used also in 4.0.x environments? > I guess it should work - briefly tested it on a 4.0 and didn't notice problems. Please file bugs if you find them. Thanks! -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I’ve added this to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1416533 On 1/25/17, 11:02 AM, "users-bounces@ovirt.org on behalf of Beckman, Daniel" <users-bounces@ovirt.org on behalf of Daniel.Beckman@ingramcontent.com> wrote: I tested this on a Windows 2012 R2 (x64) DataCenter VM, newly built, on oVirt 4.0.5. It suffers from the same bug that’s been present since at least oVirt 3.6: The Balloon service is setup with the wrong path: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\w2k12R2\amd64\blnsvr.exe" The correct path being: C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" Note the small typo: “w2k12R2” when the actual files are under “2k12R2”. The fix is much the same as before: sc config BalloonService binpath= "C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" DisplayName= "Balloon Service" start= auto How is it that this bug persists? Is it being actively tracked? I found reference to someone possibly having “a look” but no follow-up: http://lists.ovirt.org/pipermail/users/2016-June/073690.html I did note one thing that appears to be fixed: the QEMU agent service is properly setup and runs (it had to be manually started in previous versions.) The oVirt and Spice services start up as expected. Thanks, Daniel On 1/25/17, 2:54 AM, "users-bounces@ovirt.org on behalf of Yedidyah Bar David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote: On Wed, Jan 25, 2017 at 10:38 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote: > On Wed, Jan 25, 2017 at 8:00 AM, Yedidyah Bar David <didi@redhat.com> wrote: >> >> >> >> An updated Windows Guest Tools ISO is now available as well, from: >> >> >> http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24... > > > Is it meant to be used also in 4.0.x environments? > I guess it should work - briefly tested it on a 4.0 and didn't notice problems. Please file bugs if you find them. Thanks! -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, Jan 25, 2017 at 8:08 PM, Beckman, Daniel <Daniel.Beckman@ingramcontent.com> wrote:
I’ve added this to Bugzilla:
Thanks!
On 1/25/17, 11:02 AM, "users-bounces@ovirt.org on behalf of Beckman, Daniel" <users-bounces@ovirt.org on behalf of Daniel.Beckman@ingramcontent.com> wrote:
I tested this on a Windows 2012 R2 (x64) DataCenter VM, newly built, on oVirt 4.0.5.
It suffers from the same bug that’s been present since at least oVirt 3.6: The Balloon service is setup with the wrong path:
C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\w2k12R2\amd64\blnsvr.exe"
The correct path being:
C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe"
Note the small typo: “w2k12R2” when the actual files are under “2k12R2”. The fix is much the same as before:
sc config BalloonService binpath= "C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k12R2\amd64\blnsvr.exe" DisplayName= "Balloon Service" start= auto
How is it that this bug persists? Is it being actively tracked? I found reference to someone possibly having “a look” but no follow-up:
http://lists.ovirt.org/pipermail/users/2016-June/073690.html
I did note one thing that appears to be fixed: the QEMU agent service is properly setup and runs (it had to be manually started in previous versions.) The oVirt and Spice services start up as expected.
Thanks, Daniel
On 1/25/17, 2:54 AM, "users-bounces@ovirt.org on behalf of Yedidyah Bar David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote:
On Wed, Jan 25, 2017 at 10:38 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote: > On Wed, Jan 25, 2017 at 8:00 AM, Yedidyah Bar David <didi@redhat.com> wrote: >> >> >> >> An updated Windows Guest Tools ISO is now available as well, from: >> >> >> http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/oVirt-toolsSetup/4.1-1.fc24... > > > Is it meant to be used also in 4.0.x environments? >
I guess it should work - briefly tested it on a 4.0 and didn't notice problems. Please file bugs if you find them. Thanks! -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
participants (4)
-
Beckman, Daniel -
Gianluca Cecchi -
Sandro Bonazzola -
Yedidyah Bar David