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

DispVM startup fails silently in low-memory conditions after template update #2758

Open
jpouellet opened this Issue Apr 18, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@jpouellet
Contributor

jpouellet commented Apr 18, 2017

Qubes OS version (e.g., R3.2):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

fedora-24


Expected behavior:

When trying to start a DispVM, it either starts, or provides an error message saying why it failed to start.

Actual behavior:

Exact error messages below are not literal quotes. I forget the exact phrases and don't have time to reproduce right now.

After updating the DispVM's template, and if there is insufficient memory to start the corresponding *-dvm vm, then you get the "Please wait while qubes regenerates the template (up to 120 seconds)" message, but no messages after that. If you try to start it again, then only at that time do you get a "dispvm generation failed" message and simultaneously another "Please wait while qubes regenerates ... (120 seconds)".

Also the following:

[user@dom0 ~]$ qvm-create-default-dvm f24-usable
--> Creating volatile image: /var/lib/qubes/appvms/f24-usable-dvm/volatile.img...
--> Loading the VM (type = AppVM)...
ERROR: ERROR: insufficient memory to start VM 'f24-usable-dvm'

Steps to reproduce the behavior:

  • Update the default dispvm's template
  • start a bunch of VMs such that there is insufficient memory to start another
  • try to start a DispVM

General notes:


Related issues:

https://groups.google.com/d/topic/qubes-users/ZhxD-RoqAnY/discussion

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