3:27 p.m.
The oVirt Team is happy to announce that the EL6 rpms for the 3.2
release are now available in the beta repositories.
To access this content,
* download and install the release rpm [1] on your EL6 host.
* Edit the ovirt.repo file in /etc/yum.repos.d to enable the ovirt-beta
repository.
* Follow the rest of the instructions on http://www.ovirt.org/Download.
This content is in beta, so feedback on issues found is greatly appreciated.
Issues can be filed in Bugzilla[2] in the Community/Ovirt project. You
can also get help on IRC in #ovirt on OFTC.net or through the
users(a)ovirt.org mailing list.
Thanks
The oVirt Team
[1] http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
[2] https://bugzilla.redhat.com/
3:34 p.m.
On Thu, Mar 21, 2013 at 2:27 PM, Mike Burns wrote:
The oVirt Team is happy to announce that the EL6 rpms for the 3.2
release
are now available in the beta repositories.
To access this content,
* download and install the release rpm [1] on your EL6 host.
* Edit the ovirt.repo file in /etc/yum.repos.d to enable the ovirt-beta
repository.
* Follow the rest of the instructions on http://www.ovirt.org/Download.
This content is in beta, so feedback on issues found is greatly appreciated.
Issues can be filed in Bugzilla[2] in the Community/Ovirt project. You can
also get help on IRC in #ovirt on OFTC.net or through the users(a)ovirt.org
mailing list.
Thanks
The oVirt Team
[1] http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
[2] https://bugzilla.redhat.com/
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
do they already contain the fix from
http://gerrit.ovirt.org/#/c/11254/
that was one of the biggest problems of 3.2?
Gianluca
3:36 p.m.
On 03/21/2013 09:34 AM, Gianluca Cecchi wrote:
On Thu, Mar 21, 2013 at 2:27 PM, Mike Burns wrote:
> The oVirt Team is happy to announce that the EL6 rpms for the 3.2 release
> are now available in the beta repositories.
>
> To access this content,
> * download and install the release rpm [1] on your EL6 host.
> * Edit the ovirt.repo file in /etc/yum.repos.d to enable the ovirt-beta
> repository.
> * Follow the rest of the instructions on http://www.ovirt.org/Download.
>
> This content is in beta, so feedback on issues found is greatly appreciated.
>
> Issues can be filed in Bugzilla[2] in the Community/Ovirt project. You can
> also get help on IRC in #ovirt on OFTC.net or through the users(a)ovirt.org
> mailing list.
>
> Thanks
>
> The oVirt Team
>
>
> [1] http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
> [2] https://bugzilla.redhat.com/
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
do they already contain the fix from
http://gerrit.ovirt.org/#/c/11254/
that was one of the biggest problems of 3.2?
Gianluca
Looking at gerrit, the 3.2 branch fix for that[1] is still in review.
That would mean that it's not included.
I'll defer to the engine team on when that will get into a build.
Mike
[1] http://gerrit.ovirt.org/#/c/13172/
11:24 a.m.
On Thu, Mar 21, 2013 at 2:36 PM, Mike Burns wrote:
>
>
> do they already contain the fix from
> http://gerrit.ovirt.org/#/c/11254/
>
> that was one of the biggest problems of 3.2?
>
> Gianluca
>
Looking at gerrit, the 3.2 branch fix for that[1] is still in review. That
would mean that it's not included.
I'll defer to the engine team on when that will get into a build.
Mike
[1] http://gerrit.ovirt.org/#/c/13172/
Is there a particular reason for it to be still in review?
Any drawbacks?
Any way at my side to accelerate the process?
Gianluca
10:37 a.m.
(dropping announce list. they only care about the finished product, not
the road to get it done)
On Tue, Mar 26, 2013 at 10:24:16AM +0100, Gianluca Cecchi wrote:
On Thu, Mar 21, 2013 at 2:36 PM, Mike Burns wrote:
>>
>>
>> do they already contain the fix from
>> http://gerrit.ovirt.org/#/c/11254/
>>
>> that was one of the biggest problems of 3.2?
>>
>> Gianluca
>>
>
> Looking at gerrit, the 3.2 branch fix for that[1] is still in review. That
> would mean that it's not included.
>
> I'll defer to the engine team on when that will get into a build.
>
> Mike
>
> [1] http://gerrit.ovirt.org/#/c/13172/
Is there a particular reason for it to be still in review?
Any drawbacks?
Any way at my side to accelerate the process?
Maor, Daniel: when is this expected to be merge and built?
3:47 p.m.
On 03/27/2013 10:37 AM, Dan Kenigsberg wrote:
(dropping announce list. they only care about the finished product,
not
the road to get it done)
On Tue, Mar 26, 2013 at 10:24:16AM +0100, Gianluca Cecchi wrote:
> On Thu, Mar 21, 2013 at 2:36 PM, Mike Burns wrote:
>
>>>
>>>
>>> do they already contain the fix from
>>> http://gerrit.ovirt.org/#/c/11254/
>>>
>>> that was one of the biggest problems of 3.2?
>>>
>>> Gianluca
>>>
>>
>> Looking at gerrit, the 3.2 branch fix for that[1] is still in review. That
>> would mean that it's not included.
>>
>> I'll defer to the engine team on when that will get into a build.
>>
>> Mike
>>
>> [1] http://gerrit.ovirt.org/#/c/13172/
>
> Is there a particular reason for it to be still in review?
> Any drawbacks?
> Any way at my side to accelerate the process?
Maor, Daniel: when is this expected to be merge and built?
Hi, the patch has been merged, sorry for the delay, I wanted to
re-verify it with the build team before.
Unfortunately I'm not aware of a specific date when next version of
engine should be built.
Regards,
Maor
11:26 a.m.
On Thu, Mar 21, 2013 at 02:34:22PM +0100, Gianluca Cecchi wrote:
On Thu, Mar 21, 2013 at 2:27 PM, Mike Burns wrote:
> The oVirt Team is happy to announce that the EL6 rpms for the 3.2 release
> are now available in the beta repositories.
>
> To access this content,
> * download and install the release rpm [1] on your EL6 host.
> * Edit the ovirt.repo file in /etc/yum.repos.d to enable the ovirt-beta
> repository.
> * Follow the rest of the instructions on http://www.ovirt.org/Download.
>
> This content is in beta, so feedback on issues found is greatly appreciated.
>
> Issues can be filed in Bugzilla[2] in the Community/Ovirt project. You can
> also get help on IRC in #ovirt on OFTC.net or through the users(a)ovirt.org
> mailing list.
>
> Thanks
>
> The oVirt Team
>
>
> [1] http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
> [2] https://bugzilla.redhat.com/
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
do they already contain the fix from
http://gerrit.ovirt.org/#/c/11254/
that was one of the biggest problems of 3.2?
Gianluca
Are there plans on releasing a SRPM for jboss-as-7.1.1-10.el6.x86_64.rpm ?
Vincent
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:57 a.m.
Just installed ovirt 3.2 from this new repo
(http://resources.ovirt.org/releases/3.2/rpm/EL/6/) on centos-6.4
New VM's cannot be started, fails with
internal error process exited while connecting to monitor: Supported
machines are:
pc RHEL 6.4.0 PC (alias of rhel6.4.0)
rhel6.4.0 RHEL 6.4.0 PC (default)
rhel6.3.0 RHEL 6.3.0 PC
rhel6.2.0 RHEL 6.2.0 PC
rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC
rhel5.5.0 RHEL 5.5.0 PC
rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC
From vdsm.log i presume problem in this string
"<type arch="x86_64"
machine="pc-0.14">hvm</type>", machine=pc-0.14 doesnt supported by
libvirt in el6. Logs attached.
Looks like same bug, that is discussed here:
http://lists.ovirt.org/pipermail/users/2012-January/005930.html
Searched in bugzilla and didn't found any opened bugs - should I open
one or I mislooked?
Yuriy Demchenko
On 03/21/2013 05:27 PM, Mike Burns wrote:
The oVirt Team is happy to announce that the EL6 rpms for the 3.2
release are now available in the beta repositories.
To access this content,
* download and install the release rpm [1] on your EL6 host.
* Edit the ovirt.repo file in /etc/yum.repos.d to enable the
ovirt-beta repository.
* Follow the rest of the instructions on http://www.ovirt.org/Download.
This content is in beta, so feedback on issues found is greatly
appreciated.
Issues can be filed in Bugzilla[2] in the Community/Ovirt project.
You can also get help on IRC in #ovirt on OFTC.net or through the
users(a)ovirt.org mailing list.
Thanks
The oVirt Team
[1] http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
[2] https://bugzilla.redhat.com/
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:34 a.m.
On 03/26/2013 08:57 AM, Yuriy Demchenko wrote:
Just installed ovirt 3.2 from this new repo
(http://resources.ovirt.org/releases/3.2/rpm/EL/6/) on centos-6.4
New VM's cannot be started, fails with
> internal error process exited while connecting to monitor: Supported
> machines are:
> pc RHEL 6.4.0 PC (alias of rhel6.4.0)
> rhel6.4.0 RHEL 6.4.0 PC (default)
> rhel6.3.0 RHEL 6.3.0 PC
> rhel6.2.0 RHEL 6.2.0 PC
> rhel6.1.0 RHEL 6.1.0 PC
> rhel6.0.0 RHEL 6.0.0 PC
> rhel5.5.0 RHEL 5.5.0 PC
> rhel5.4.4 RHEL 5.4.4 PC
> rhel5.4.0 RHEL 5.4.0 PC
From vdsm.log i presume problem in this string "<type arch="x86_64"
machine="pc-0.14">hvm</type>", machine=pc-0.14 doesnt supported
by
libvirt in el6. Logs attached.
Looks like same bug, that is discussed here:
http://lists.ovirt.org/pipermail/users/2012-January/005930.html
Searched in bugzilla and didn't found any opened bugs - should I open
one or I mislooked?
Try to do this:
# engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.2
Then restart the engine:
# service ovirt-engine restart
Yuriy Demchenko
On 03/21/2013 05:27 PM, Mike Burns wrote:
> The oVirt Team is happy to announce that the EL6 rpms for the 3.2
> release are now available in the beta repositories.
>
> To access this content,
> * download and install the release rpm [1] on your EL6 host.
> * Edit the ovirt.repo file in /etc/yum.repos.d to enable the
> ovirt-beta repository.
> * Follow the rest of the instructions on http://www.ovirt.org/Download.
>
> This content is in beta, so feedback on issues found is greatly
> appreciated.
>
> Issues can be filed in Bugzilla[2] in the Community/Ovirt project.
> You can also get help on IRC in #ovirt on OFTC.net or through the
> users(a)ovirt.org mailing list.
>
> Thanks
>
> The oVirt Team
>
>
> [1] http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
> [2] https://bugzilla.redhat.com/
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
10:46 a.m.
Thanks, that solved my problem.
However, shouldn't that be "out-of-box" for el6 packages? (just as a
feedback)
Yuriy Demchenko
On 03/26/2013 12:34 PM, Juan Hernandez wrote:
On 03/26/2013 08:57 AM, Yuriy Demchenko wrote:
> Just installed ovirt 3.2 from this new repo
> (http://resources.ovirt.org/releases/3.2/rpm/EL/6/) on centos-6.4
>
> New VM's cannot be started, fails with
>> internal error process exited while connecting to monitor: Supported
>> machines are:
>> pc RHEL 6.4.0 PC (alias of rhel6.4.0)
>> rhel6.4.0 RHEL 6.4.0 PC (default)
>> rhel6.3.0 RHEL 6.3.0 PC
>> rhel6.2.0 RHEL 6.2.0 PC
>> rhel6.1.0 RHEL 6.1.0 PC
>> rhel6.0.0 RHEL 6.0.0 PC
>> rhel5.5.0 RHEL 5.5.0 PC
>> rhel5.4.4 RHEL 5.4.4 PC
>> rhel5.4.0 RHEL 5.4.0 PC
> From vdsm.log i presume problem in this string "<type
arch="x86_64"
> machine="pc-0.14">hvm</type>", machine=pc-0.14 doesnt
supported by
> libvirt in el6. Logs attached.
> Looks like same bug, that is discussed here:
> http://lists.ovirt.org/pipermail/users/2012-January/005930.html
>
> Searched in bugzilla and didn't found any opened bugs - should I open
> one or I mislooked?
>
Try to do this:
# engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.2
Then restart the engine:
# service ovirt-engine restart
>
> Yuriy Demchenko
>
> On 03/21/2013 05:27 PM, Mike Burns wrote:
>> The oVirt Team is happy to announce that the EL6 rpms for the 3.2
>> release are now available in the beta repositories.
>>
>> To access this content,
>> * download and install the release rpm [1] on your EL6 host.
>> * Edit the ovirt.repo file in /etc/yum.repos.d to enable the
>> ovirt-beta repository.
>> * Follow the rest of the instructions on http://www.ovirt.org/Download.
>>
>> This content is in beta, so feedback on issues found is greatly
>> appreciated.
>>
>> Issues can be filed in Bugzilla[2] in the Community/Ovirt project.
>> You can also get help on IRC in #ovirt on OFTC.net or through the
>> users(a)ovirt.org mailing list.
>>
>> Thanks
>>
>> The oVirt Team
>>
>>
>> [1]
>> http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
>> [2] https://bugzilla.redhat.com/
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
10:56 a.m.
On 03/26/2013 09:46 AM, Yuriy Demchenko wrote:
Thanks, that solved my problem.
However, shouldn't that be "out-of-box" for el6 packages? (just as a
feedback)
Unfortunately it is not as simple as it seems. The problem is that if
you make that the default for el6 packages it will fail if you try to
add a oVirt node as hypervisor, as that is based on Fedora where the
rhel6.4.0 machine type is not supported by libvirt. So we need to set
this according to the type of hypervisor, not to the distro where the
engine is running.
You may want to open a bug to request this.
Yuriy Demchenko
On 03/26/2013 12:34 PM, Juan Hernandez wrote:
> On 03/26/2013 08:57 AM, Yuriy Demchenko wrote:
>> Just installed ovirt 3.2 from this new repo
>> (http://resources.ovirt.org/releases/3.2/rpm/EL/6/) on centos-6.4
>>
>> New VM's cannot be started, fails with
>>> internal error process exited while connecting to monitor: Supported
>>> machines are:
>>> pc RHEL 6.4.0 PC (alias of rhel6.4.0)
>>> rhel6.4.0 RHEL 6.4.0 PC (default)
>>> rhel6.3.0 RHEL 6.3.0 PC
>>> rhel6.2.0 RHEL 6.2.0 PC
>>> rhel6.1.0 RHEL 6.1.0 PC
>>> rhel6.0.0 RHEL 6.0.0 PC
>>> rhel5.5.0 RHEL 5.5.0 PC
>>> rhel5.4.4 RHEL 5.4.4 PC
>>> rhel5.4.0 RHEL 5.4.0 PC
>> From vdsm.log i presume problem in this string "<type
arch="x86_64"
>> machine="pc-0.14">hvm</type>", machine=pc-0.14 doesnt
supported by
>> libvirt in el6. Logs attached.
>> Looks like same bug, that is discussed here:
>> http://lists.ovirt.org/pipermail/users/2012-January/005930.html
>>
>> Searched in bugzilla and didn't found any opened bugs - should I open
>> one or I mislooked?
>>
>
> Try to do this:
>
> # engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.2
>
> Then restart the engine:
>
> # service ovirt-engine restart
>
>>
>> Yuriy Demchenko
>>
>> On 03/21/2013 05:27 PM, Mike Burns wrote:
>>> The oVirt Team is happy to announce that the EL6 rpms for the 3.2
>>> release are now available in the beta repositories.
>>>
>>> To access this content,
>>> * download and install the release rpm [1] on your EL6 host.
>>> * Edit the ovirt.repo file in /etc/yum.repos.d to enable the
>>> ovirt-beta repository.
>>> * Follow the rest of the instructions on http://www.ovirt.org/Download.
>>>
>>> This content is in beta, so feedback on issues found is greatly
>>> appreciated.
>>>
>>> Issues can be filed in Bugzilla[2] in the Community/Ovirt project.
>>> You can also get help on IRC in #ovirt on OFTC.net or through the
>>> users(a)ovirt.org mailing list.
>>>
>>> Thanks
>>>
>>> The oVirt Team
>>>
>>>
>>> [1]
>>> http://resources.ovirt.org/releases/ovirt-release-el6-5-3.noarch.rpm
>>> [2] https://bugzilla.redhat.com/
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
2:32 p.m.
Ah, I see. Thanks for clarification
i've opened a bug https://bugzilla.redhat.com/show_bug.cgi?id=927874 for
this
Yuriy Demchenko
On 03/26/2013 12:56 PM, Juan Hernandez wrote:
> Thanks, that solved my problem.
> However, shouldn't that be "out-of-box" for el6 packages? (just as a
> feedback)
>
Unfortunately it is not as simple as it seems. The problem is that if
you make that the default for el6 packages it will fail if you try to
add a oVirt node as hypervisor, as that is based on Fedora where the
rhel6.4.0 machine type is not supported by libvirt. So we need to set
this according to the type of hypervisor, not to the distro where the
engine is running.
You may want to open a bug to request this.
4258
days inactive
4265
days old
11 comments
7 participants
participants (7)
-
Dan Kenigsberg -
Gianluca Cecchi -
Juan Hernandez -
Maor Lipchuk -
Mike Burns -
Vincent Van der Kussen -
Yuriy Demchenko