/qubes-issues

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

"Operation not permitted" while starting VM #1331

Closed
marmarek opened this Issue Oct 13, 2015 · 3 comments

Comments

Assignees

@marmarek marmarek

Labels
Projects
None yet
Milestone
  Release 3.0 updates
1 participant
@marmarek
@marmarek
Member

marmarek commented Oct 13, 2015

Reported by vuarnet:
When I run qvm-start sys-net as a normal user, I get:

--> Creating volatile image:
/var/lib/qubes/servicevms/sys-net/volatile.img...
--> Loading the VM (type = NetVM)...
--> Starting Qubes DB...
ERROR: [Errno 1] Operation not permitted

@marmarek marmarek added bug C: core P: major labels Oct 13, 2015

@marmarek marmarek self-assigned this Oct 13, 2015

@marmarek marmarek added this to the Release 3.0 updates milestone Oct 13, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 13, 2015

Member

It seems to be this os.kill line:
https://github.com/marmarek/qubes-core-admin/blob/master/core-modules/000QubesVm.py#L1741
Member

marmarek commented Oct 13, 2015

It seems to be this os.kill line:
https://github.com/marmarek/qubes-core-admin/blob/master/core-modules/000QubesVm.py#L1741

@marmarek marmarek closed this in marmarek/old-qubes-core-admin@5c549e1 Oct 13, 2015

marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Nov 15, 2015

@marmarek
core: Provide more meaningful error when failed to kill old QubesDB i… 
…nstance

This process may be running as root in case of default NetVM. But do not
kill it forcibly (through sudo or so), because it may also be stale
pid file. After all, QubesDB should automatically terminate when its VM
is terminated, so this code is already some error handling.

Fixes QubesOS/qubes-issues#1331

(cherry picked from commit 5c549e1)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
210edb3
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 15, 2015

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.0.26-1.fc20 has been pushed to the r3.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
Member

marmarek commented Nov 15, 2015

Automated announcement from builder-github

The package qubes-core-dom0-3.0.26-1.fc20 has been pushed to the r3.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

@marmarek marmarek added the r3.0-dom0-testing label Nov 15, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 29, 2015

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.0.26-1.fc20 has been pushed to the r3.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update
Member

marmarek commented Nov 29, 2015

Automated announcement from builder-github

The package qubes-core-dom0-3.0.26-1.fc20 has been pushed to the r3.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@marmarek marmarek added r3.0-dom0-stable and removed r3.0-dom0-testing labels Nov 29, 2015

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