On Mon, Feb 1, 2016 at 7:52 PM, Charles Kozler wrote:
> Sorry to be clear..the only way to resolve the memory leak I am facing now
> is to upgrade to el7?
If you want to use official packages, yes.
But this is free software, so *you* are free to build your own package.
Nir -
At this time I cant do anything. I succesfully upgraded the CentOS 6.7
engine VM to 3.6 but after migrating it to a new node packet loss on the VM
is significant. I was able to finally get access to the VM by running SSH
client command with -C and running 'service ovirt-engine stop' of
Thank you. I am in the process of upgrading my nodes to 7 although since
the upgrade of my engine to ovirt 3.6 the network on the VM itself has
become very instable. Ping packets are unresponsive from time to time and I
cannot get a reliable SSH connection. My guess is something inside ovirt
3.6
So I will still have the memory leak?
On Feb 1, 2016 12:39 PM, "Simone Tiraboschi" wrote:
>
>
> On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler
> wrote:
>
>> So what about the bug that I hit for vdsm as listed above by Nir? Will I
>> have that patch to
Sorry to be clear..the only way to resolve the memory leak I am facing now
is to upgrade to el7?
Also the engine can stay running on el6 yes? I successfully upgraded my
engine to ovirt 3.6 in el6. Do I need to make my engine vm el7 too?
On Feb 1, 2016 12:49 PM, "Charles Kozler"
On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler wrote:
> Sandro / Nir -
>
> I followed your steps plus
>
> http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL
>
> Engine upgraded fine but then when I got to upgrading a node I did:
>
> $ yum install
Sandro / Nir -
I followed your steps plus
http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL
Engine upgraded fine but then when I got to upgrading a node I did:
$ yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
$ yum update -y
And then rebooted the
So what about the bug that I hit for vdsm as listed above by Nir? Will I
have that patch to avoid the memory leak or no? Upgrading an entire node to
centos 7 is not actually feasible and was previously outlined above that I
just needed to upgrade to ovirt 3.6 and no mention of OS change ...
On Feb
On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler wrote:
> So what about the bug that I hit for vdsm as listed above by Nir? Will I
> have that patch to avoid the memory leak or no? Upgrading an entire node to
> centos 7 is not actually feasible and was previously outlined
Hi Nir -
do you have a release target date for 3.5.8? Any estimate would help.
If its not VDSM, what is it exactly? Sorry, I understood from the ticket it
was something inside vdsm, was I mistaken?
CentOS 6 is the servers. 6.7 to be exact
I have done all forms of flushing that I can (page
Hi Nir -
Thanks for getting back to me. Will the patch to 3.6 be backported to 3.5?
As you can tell from the images, it takes days and days for it to increase
over time. I also wasnt sure if that was the right bug because VDSM memory
shows normal from top ...
PID USER PR NI VIRT RES
On Fri, Jan 22, 2016 at 9:25 PM, Charles Kozler wrote:
> Here is a screenshot of my three nodes and their increased memory usage over
> 30 days. Note that node #2 had 1 single VM that had 4GB of RAM assigned to
> it. I had since shut it down and saw no memory reclamation
Il 22/Gen/2016 22:31, "Charles Kozler" ha scritto:
>
> Hi Nir -
>
> do you have a release target date for 3.5.8? Any estimate would help.
>
There won't be any supported release after 3.5.6. Please update to 3.6.2
next week
> If its not VDSM, what is it exactly? Sorry, I
Sandro -
Do you have available documentation that can support upgrading self hosted?
I followed this
http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/
Would it be as easy as installing the RPM and then running yum upgrade?
Thanks
On Fri, Jan 22, 2016 at 4:42 PM, Sandro
On Fri, Jan 22, 2016 at 11:08 PM, Charles Kozler wrote:
> Hi Nir -
>
> Thanks for getting back to me. Will the patch to 3.6 be backported to 3.5?
We plan to include them in 3.5.8.
> As you can tell from the images, it takes days and days for it to increase
> over time. I
Here is a screenshot of my three nodes and their increased memory usage
over 30 days. Note that node #2 had 1 single VM that had 4GB of RAM
assigned to it. I had since shut it down and saw no memory reclamation
occur. Further, I flushed page caches and inodes and ran 'sync'. I tried
everything but
On Fri, Jan 22, 2016 at 11:30 PM, Charles Kozler wrote:
> Hi Nir -
>
> do you have a release target date for 3.5.8? Any estimate would help.
>
> If its not VDSM, what is it exactly? Sorry, I understood from the ticket it
> was something inside vdsm, was I mistaken?
The bug
Thanks Sandro. Should clarify my storage is external on a redundant SAN.
The steps I was concerned about was the actual upgrade. I tried to upgrade
before and it brought my entire stack crumbling down so I'm hesitant. This
bug seems like a huge bug that should at least somehow backported if at all
On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler
wrote:
> Sandro -
>
> Do you have available documentation that can support upgrading self
> hosted? I followed this
> http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/
>
> Would it be as easy as
19 matches
Mail list logo