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

AppVMs have max vcpus assigned by default #2900

Closed
Yethal opened this Issue Jul 10, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@Yethal

Yethal commented Jul 10, 2017

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

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


Expected behavior:

Each AppVM has 2 vcpus assigned

Actual behavior:

Each AppVM has maximum avilable number of vcpus assigned (12 on my machine)

Steps to reproduce the behavior:

  1. Install Qubes 4.0 prerelease
  2. Boot into it
  3. view qvm-prefs of any AppVM

General notes:


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 10, 2017

Member

This is intended behavior, to not allow any single AppVM block all the machine. If you need some more computing power in a specific AppVM, you can adjust the setting.

Member

marmarek commented Jul 10, 2017

This is intended behavior, to not allow any single AppVM block all the machine. If you need some more computing power in a specific AppVM, you can adjust the setting.

@marmarek marmarek closed this Jul 10, 2017

@Yethal

This comment has been minimized.

Show comment
Hide comment
@Yethal

Yethal Jul 11, 2017

I don't quite understand. How does assigning all vcpus to all AppVMs at once help prevent DoS attack (I assume this is what you meant by blocking the machine) ?

Yethal commented Jul 11, 2017

I don't quite understand. How does assigning all vcpus to all AppVMs at once help prevent DoS attack (I assume this is what you meant by blocking the machine) ?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 11, 2017

Member

Ah, sorry, I've mixed "actual bevavior" with "expected behavior" in your report. It should be 2 by default.

Member

marmarek commented Jul 11, 2017

Ah, sorry, I've mixed "actual bevavior" with "expected behavior" in your report. It should be 2 by default.

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Jul 18, 2017

Automated announcement from builder-github

The package qubes-core-dom0-4.0.2-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

Automated announcement from builder-github

The package qubes-core-dom0-4.0.2-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Jul 18, 2017

Closed

core-admin v4.0.2 (r4.0) #144

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