Hi all,
Thanks for coming back to me Ofer.
On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber oschr...@redhat.com wrote:
can you please attach the log file?
(/var/log/ovirt-engine/engine-upgrade-DATE.log)
Attached is the log as requested.
Much appreciated.
Regards.
Neil Wilson.
[root@node02
From http://lists.fedoraproject.org/pipermail/devel/2012-July/170410.html :
* #913 F18 Feature: oVirt engine 3.1 -
https://fedoraproject.org/wiki/Features/oVirtEngine_3.1 (mmaslano,
17:20:45)
* AGREED: oVirt is approved as a feature (+7,-0) (mmaslano, 17:23:49)
- Original Message -
From: Itamar Heim ih...@redhat.com
To: Maxim Burgerhout ma...@wzzrd.com
Cc: users@ovirt.org, Laszlo Hornyak lhorn...@redhat.com, Doron Fediuck
dfedi...@redhat.com
Sent: Tuesday, July 31, 2012 10:36:45 PM
Subject: Re: [Users] How to force VM's to run on different
Hi,
With the latest version of ovirt my host's CPU is not correctly identified,
my host's have an Intel Xeon E5530 (Nehalem family), but is being identified as
Conrad family.
My installed versions:
ovirt-engine-3.1.0-2.fc17.noarch
ovirt-node-iso-2.5.0-2.0.fc17.iso
Best regards,
Ricardo
On 08/01/2012 12:57 PM, Ricardo Esteves wrote:
Hi,
With the latest version of ovirt my host's CPU is not correctly identified,
my host's have an Intel Xeon E5530 (Nehalem family), but is being identified as
Conrad family.
My installed versions:
ovirt-engine-3.1.0-2.fc17.noarch
On Tue, Jul 31, 2012 at 02:15:12PM +0200, Martin Kletzander wrote:
It looks like this exactly could be the problem. I don't know how the
node installation works, but when you install normal system it shouldn't
start any services until you specify that. Of course this is another
story when
[root@blade4 ~]# vdsClient -s 0 getVdsCaps | grep -i flags
Traceback (most recent call last):
File /usr/share/vdsm/vdsClient.py, line 2275, in module
File /usr/share/vdsm/vdsClient.py, line 403, in do_getCap
File /usr/lib64/python2.7/xmlrpclib.py, line 1224, in __call__
File
On 08/01/2012 02:28 PM, Ricardo Esteves wrote:
[root@blade4 mailto:root@blade4 ~]# vdsClient -s 0 getVdsCaps | grep
-i flags
Traceback (most recent call last):
File /usr/share/vdsm/vdsClient.py, line 2275, in module
File /usr/share/vdsm/vdsClient.py, line 403, in do_getCap
File
On Wed, Aug 01, 2012 at 11:29:18AM +0800, Royce Lv wrote:
Is ovirt 3.1 include this patch?
You can see for yourself that the ovirt-3.1 branch does not have it -
We're open source ;-)
But thanks for letting me know - Vdsm should keep starting VMs with
cdrom even with no change in Engine.
Minutes:http://ovirt.org/meetings/ovirt/2012/ovirt.2012-08-01-14.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-08-01-14.00.txt
Log:
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-08-01-14.00.log.html
#ovirt: oVirt Weekly
- Original Message -
Hi all,
Thanks for coming back to me Ofer.
On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber oschr...@redhat.com
wrote:
can you please attach the log file?
(/var/log/ovirt-engine/engine-upgrade-DATE.log)
Attached is the log as requested.
it seems that
I didn't disabled anything, but after installing the node when i
configure the option oVirt Engine it gives an error saying it can't
download the certificate, but i had this error with previous versions of
the node, and it detected ok the CPU family.
This is the output after a fresh install of
The binary directory appears to have gone missing from
http://ovirt.org/releases/, including http://ovirt.org/releases/stable/binary
which contains the 2.3.0-1.0 ovirt-node.
- Nick
___
Users mailing list
On 08/01/2012 12:07 PM, Nicholas Kesick wrote:
The binary directory appears to have gone missing from
http://ovirt.org/releases/, including
http://ovirt.org/releases/stable/binary which contains the 2.3.0-1.0
ovirt-node.
- Nick
___
Users mailing
Once again- you have an unsupported version of ovirt-engine.
The reason engine-upgrade doesn't work is that 3.1.0_0001-1 3.1.0-2
On 1 Aug 2012, at 21:32, Trey Dockendorf treyd...@gmail.com wrote:
On Wed, Aug 1, 2012 at 10:17 AM, Ofer Schreiber oschr...@redhat.com wrote:
- Original
That is actually the same as beta1. Or the same version used on testing
day. To upgrade You have to.
Yum Remove ovirt-engine vdsm
After all the packages are installed. Make sure you are using his the
3.1 repo and not the devel one that is based on master but hasn't been
updated recently.
Date: Wed, 1 Aug 2012 13:27:30 -0400
From: rob...@middleswarth.net
To: cybertimber2...@hotmail.com
CC: users@ovirt.org
Subject: Re: [Users] binary directory missing
On 08/01/2012 12:07 PM, Nicholas Kesick
wrote:
The binary directory appears to have
Will Ovirt actually work when included in Fedora 18? I know a bunch of
people who tried ovirt through fedora 17 and were ticked off. Its listed
as supported but doesn't actually work due to missing packages.
--
Gary Scarborough
IST Lab Manager
Rochester Institute of Technology
Rochester NY
I have 6 node , they all installed by ovirt-node-image-2.2.2-2.2.fc16.iso
some of them had been added from engine web , the others added via admin@node UI
I confirm that they both have the problem .
Since it's reproducible , I'll open a case later.
On 1 Aug, 2012, at 7:00 PM, Dan Kenigsberg
Hi!
Dan, it seems you know something about storage, so I adress you:
I find the oVirt storage framework a bit odd. It has it advantages, but also a
lot of disadvantiages, it seems.
I did earlier, in this thread, ask about storage setups you want to use in
enterprise environments. And I like
Hi again!
I continue, it was something I forgot to mention in last mail.
If the oVirt storage system could bring in two LUN's from different DC's, and
use LVM to join them as one mirrored unit, it would be exactly what I wanted.
That would solve a lot of issues.
But than of coarse the NPIV
21 matches
Mail list logo
