qubes-issues icon indicating copy to clipboard operation
qubes-issues copied to clipboard

Add a `--noforce` argument to `qvm-shutdown`

Open Atrate opened this issue 4 weeks ago • 4 comments

How to file a helpful issue

The problem you're addressing (if any)

I have a keybind that does qvm-shutdown --all --exclude=... to shut down most qubes and then locks the screen. Unfortunately, qvm-shutdown --all also implies --force. This causes issues with preloaded dispVMs (such as "orphaned" WaitForSession processes consuming CPU time).

The solution you'd like

Add a --noforce (or some other name) argument that would make it possible to use --all without implying --force.

Alternative solutions considered

Allow for wildcard/regex matches in --exclude to exclude DispVMs, or a way to exclude paused qubes.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

Atrate avatar Nov 30 '25 19:11 Atrate

Maybe simply --exclude could disable implied --force? Implied --force with --all works on assumption you shutdown everything anyway, but with --exclude this is no longer the case.

marmarek avatar Nov 30 '25 23:11 marmarek

This causes issues with preloaded dispVMs (such as "orphaned" WaitForSession processes consuming CPU time).

Can you explain this again? Where do you see this?

ben-grande avatar Dec 01 '25 10:12 ben-grande

You mean the notifications:

  • https://github.com/QubesOS/qubes-issues/issues/10032
  • https://github.com/QubesOS/qubes-core-admin/pull/697

ben-grande avatar Dec 01 '25 10:12 ben-grande

Actually, after a bit of testing, I'm not fully sure it's related to the qvm-shutdown thing. The feature request still stands, I could use that feature. Marek's suggestion seems good.

@ben-grande I've created a separate issue for my problem: #10443

Atrate avatar Dec 01 '25 11:12 Atrate