monitor exception bug about osv

[xgithub]

hi,i got the same problem today,finaly I found it, memory is not enough. Because I started osv use "...... qemu-system-x86_64 -vnc :1 -gdb tcp::1234,server,nowait -m 1G -smp 2 .....", So change "-m 1G" to "-m 2G", clear!

[tzach]

@dorlaor @penberg
Why dont we update run.py to use 2G instead of 1G for now?
In current default run.py the monitoring tab throw.

[dorlaor]

On Thu, Dec 5, 2013 at 11:25 AM, Tzach Livyatan [email protected]:

@dorlaor https://github.com/dorlaor @penberghttps://github.com/penberg
Why dont we update run.py to use 2G instead of 1G for now?
In current default run.py the monitoring tab throw.

It's a possibility although we should fix the root cause of running w/
smaller amount of mem

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-29882933
.

[glommer]

On Thu, Dec 5, 2013 at 1:34 PM, dorlaor [email protected] wrote:

On Thu, Dec 5, 2013 at 11:25 AM, Tzach Livyatan [email protected]:

@dorlaor https://github.com/dorlaor @penberg<
https://github.com/penberg>
Why dont we update run.py to use 2G instead of 1G for now?
In current default run.py the monitoring tab throw.

It's a possibility although we should fix the root cause of running w/
smaller amount of mem

If you have a lot of java threads, this is likely stacks. One workaround is
to reduce the stack size to a smaller amount.

[penberg]

@tzach Yeah, I guess we can bump it up for v0.04 but it's pretty sad that we need 2GB for the default guest... 😭

[tzach]

State right now is trouble user experience.
I suggest to change the default value, and fix the core issue on parallel/right after

[penberg]

@tzach Fixed in master.

[nyh]

On Thu, Dec 5, 2013 at 11:37 AM, Glauber Costa [email protected]:

If you have a lot of java threads, this is likely stacks. One workaround is
to reduce the stack size to a smaller amount.

The even better solution to the stacks problem will be to bring back
demand-paged stacks.

I can send my patch which "almost" fixes it, but unfortunately it's not
perfect yet.

Nadav Har'El
[email protected]

[nyh]

On Thu, Dec 5, 2013 at 12:36 PM, Pekka Enberg [email protected]:

@tzach https://github.com/tzach Yeah, I guess we can bump it up for
v0.04 but it's pretty sad that we need 2GB for the default guest... [image:
😭]

I agree. Here's an idea for v0.0.5 - let's change the default to 0.5 GB.
If things break (and they will), we'll fix them.

This should be the direction we're heading - not towards increasing
memory requirements!

Nadav Har'El
[email protected]

[glommer]

On Thu, Dec 5, 2013 at 5:48 PM, nyh [email protected] wrote:

On Thu, Dec 5, 2013 at 12:36 PM, Pekka Enberg <[email protected]

wrote:

@tzach https://github.com/tzach Yeah, I guess we can bump it up for

v0.04 but it's pretty sad that we need 2GB for the default guest...
[image:
😭]

I agree. Here's an idea for v0.0.5 - let's change the default to 0.5 GB.
If things break (and they will), we'll fix them.

This should be the direction we're heading - not towards increasing
memory requirements!

+10.

I suggest though 800Mb. Just because that is the smallest available Amazon
instance

Nadav Har'El
[email protected]

—

Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-29898464
.

[tzach]

Checkout the 0.0.5 doc,
We already have a goal to run on a EC2 micro instance :)

[nyh]

On Thu, Dec 5, 2013 at 4:00 PM, Glauber Costa [email protected]:

I agree. Here's an idea for v0.0.5 - let's change the default to 0.5
GB.
If things break (and they will), we'll fix them.

This should be the direction we're heading - not towards increasing
memory requirements!

+10.

I suggest though 800Mb. Just because that is the smallest available Amazon
instance

I think we should be more aggressive - aim towards 0.5 GB in the next
release, 0.25 GB in the release after that, and maybe 0.125 GB in the
release after that.

If certain things (e.g., the Jruby stuff) can't work with such limits, then
we need to make them optional, in case someone wants really high VM density.
Even Java and ZFS can be made optional. E.g., someone who wants to run a
load balancer does not necessarily need them.

First time I ran Linux was on an 80386 with 8 megabytes of memory. It ran
X-Windows and applications. We can't go so low (software really bloated in
the 20 years that have passed), but I don't see why 100 times that number
is the best we can do.

[penberg]

I'm 100% with @nyh on this, we should aim for very small default.