p!
>
>Cheers,
>
>Funs
>
>
>-Original Message-
>From: Alex Huang [mailto:alex.hu...@citrix.com]
>Sent: vrijdag 6 september 2013 2:05
>To: dev@cloudstack.apache.org; Marcus Sorensen
>Cc: Roeland Kuipers; int-cloud
>Subject: RE: [DISCUSS] OOM killer and Routin
Sent: Thursday, September 5, 2013 12:48 PM
> To: dev@cloudstack.apache.org; Marcus Sorensen
> Cc: Roeland Kuipers; int-cloud
> Subject: Re: [DISCUSS] OOM killer and Routing/System VM's = :(
>
> Maintaining a custom kernel is a big hassle, even if it is a few lines
> of c
8 PM
> To: dev@cloudstack.apache.org; Marcus Sorensen
> Cc: Roeland Kuipers; int-cloud
> Subject: Re: [DISCUSS] OOM killer and Routing/System VM's = :(
>
> Maintaining a custom kernel is a big hassle, even if it is a few lines of code
> change.
> Can we do something in
Maintaining a custom kernel is a big hassle, even if it is a few lines of
code change.
Can we do something in userspace? What about the software watchdog that is
available?
Along the lines of: http://goo.gl/oO3Lzr
http://linux.die.net/man/8/watchdog
On 9/5/13 7:13 AM, "Funs Kessen" wrote:
>
>>
> Well, you can't as far as I've looked in the source of panic.c. So I'm
> thinking of
> investigating of adding -1 as an option and seeing if I can push halt in,
> let's hope
> the guys that do kernel stuff find this useful too.
>
So it seems the patch, I conjured up for panic.c, is seen
On Wed, Sep 04, 2013 at 12:14:27PM -0700, Darren Shepherd wrote:
> On 09/04/2013 11:37 AM, Roeland Kuipers wrote:
> >Hi Darren,
> >
> >Thanks for your reply! Could you share a bit more on your plans/ideas?
> >
> >We also have been braining on other approaches of managing the
> >systemvm's, especial
I'd support adding these parameters in some form in
/etc/init.d/cloud-early-config. Agree that OOM killer is of no use.
On 9/4/13 11:15 AM, "Roeland Kuipers" wrote:
>Hi Dev!
>
>We have experienced a serious customers outage due to the OOM killer on a
>redundant routing vm pair member. Somehow th
Well, you can't as far as I've looked in the source of panic.c. So I'm thinking
of investigating of adding -1 as an option and seeing if I can push halt in,
let's hope the guys that do kernel stuff find this useful too.
Cheers,
Funs
Sent from my iPhone
On 4 sep. 2013, at 23:35, "Marcus S
What would work as a quick fix for this sort of situation would be if
the machine could be configured to power off rather than rebooting on
oom. Then the HA system would restart the VM, applying all configs.
Anyone know how to do that? :-)
On Wed, Sep 4, 2013 at 1:14 PM, Darren Shepherd
wrote:
>
On 09/04/2013 11:37 AM, Roeland Kuipers wrote:
Hi Darren,
Thanks for your reply! Could you share a bit more on your plans/ideas?
We also have been braining on other approaches of managing the systemvm's,
especially small customizations for specific tenants. And maybe even leveraging
a config
ility to integrate CS with
that in some way.
Cheers,
Roeland
-Original Message-
From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
Sent: woensdag 4 september 2013 20:30
To: dev@cloudstack.apache.org
Cc: Roeland Kuipers; int-cloud
Subject: Re: [DISCUSS] OOM killer and Routing/S
On 09/04/2013 11:15 AM, Roeland Kuipers wrote:
It would be nice to see that the VPC router config is persistent across reboots
even when rebooted outside cloudstack and using the same mechanism as the other
system vm's to make things more consistent and reliable.
What is your opinion on this?
12 matches
Mail list logo
