New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When system memory is low VMs are started but cannot boot correctly #412

Closed
marmarek opened this Issue Mar 8, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 6 Jan 2012 15:31 UTC
OOM kills almost everything in them... Seems like we have to little threshold for VM. Perhaps FC15 is more mem hungry?

Migrated-From: https://wiki.qubes-os.org/ticket/412

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 15 Jan 2012 00:02 UTC
What is your startup memory size for this VM? Default 400MB? Is it reproductable?

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 15 Jan 2012 00:02 UTC
What is your startup memory size for this VM? Default 400MB? Is it reproductable?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 15 Jan 2012 10:13 UTC
It's 400MB for all VMs (except for the dvm template):

[appvms](joanna@dom0)$ find . -name *.conf -exec grep "memory" {} \;
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 198
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 171
memory = 400

The problem is reproducible -- I often need to manually qvm-kill an AppVM that was started, but killed by an OOM. This problem didn't occur on Beta 2.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 15 Jan 2012 10:13 UTC
It's 400MB for all VMs (except for the dvm template):

[appvms](joanna@dom0)$ find . -name *.conf -exec grep "memory" {} \;
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 198
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 400
memory = 171
memory = 400

The problem is reproducible -- I often need to manually qvm-kill an AppVM that was started, but killed by an OOM. This problem didn't occur on Beta 2.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 16 Jan 2012 02:34 UTC
Strange. Before any qrexec command, VM should have 400MB memory constantly, which is double size really used after VM startup.
Perhaps there was to many services enabled in FC15? Not all services have /etc/init.d script here, some of them have only systemd unit. If this was the reason - should be fixed by installing qubes-core-vm-systemd package.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 16 Jan 2012 02:34 UTC
Strange. Before any qrexec command, VM should have 400MB memory constantly, which is double size really used after VM startup.
Perhaps there was to many services enabled in FC15? Not all services have /etc/init.d script here, some of them have only systemd unit. If this was the reason - should be fixed by installing qubes-core-vm-systemd package.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 18 Jan 2012 10:14 UTC
Doesn't seem to be a problem anymore, once upgraded to systemd init on fc15.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 18 Jan 2012 10:14 UTC
Doesn't seem to be a problem anymore, once upgraded to systemd init on fc15.

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment