How to shutdown a transient state qube?

areix · June 19, 2022, 10:27am

How to shutdown a transient state qube? (yellow color)

I tried pressing the shutdown button, but I get the error “Domain is powered off” and it is not shutdown, it remains transient, yellow.
Tried also qvm-shutdown --force, same result.
qvm-kill is also not shutting it down.

Using Qubes 4.1

It remains in transient state after I tried to add a PCI device. It didn’t manage to add it. And now the qube is transient, I cannot remove the PCI device and I cannot shutdown it.

One solution that I found is to restart the whole OS or re-login in the OS. But not convenient to do it every time a qube goes transient.

stumpi · August 1, 2022, 1:31pm

Hi were you able to solve this? I could have sworn that I posted about this and @marmarek responded but I cant find the post (maybe it was in irc?). Anyway, while it seems to be hung it also seems to “count” as running as it seems to be using mem which limits my already really limited system

adw · August 1, 2022, 7:08pm

I think it’s just a bug in the Qube Manager. It shows yellow even though the qube has already shut down. If you restart the Qube Manager, it should no longer show yellow next to that qube.

stumpi · August 2, 2022, 11:08am

Thanks, not sure if i am happy to hear that or not LOL, was kinda hoping they were open so I could close them and save some mem. Oh well, thanks you nailed it.

logoerthiner · August 4, 2022, 11:24am

github.com/QubesOS/qubes-issues

Long interval or forever since guest poweroff until Qubes announce VM shutdown

opened 03:02AM - 29 Jul 22 UTC

logoerthiner1

T: bug C: core P: default needs diagnosis

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release R4.1 ### Brief summary In many various cases, when a VM guest has shutdown (in VM console log the systemd says that VM has shutdown), the dom0 will wait for a long time until announcing that the VM has shutdown. Obviously there are some other things that Qubes OS need to do. Even on `qvm-kill` a VM, such time interval exists, where the VM cannot be shutdown any more nor cannot be started up. Sometimes it seems that the VM is impossible to be admitted to be shutdown anymore and I have to reboot the whole system, for example when sys-net driver gets crazy and deadlocks the machine. I do not understand where I can see relevant logs to check out what happens and what task is blocking the VM from being poweroff from the hypervisor side. ### Steps to reproduce Use the OS a little bit and shutdown various machines. ### Expected behavior For a short time after guest shutdowns, dom0 announces the VM shutdown and the VM can be started again. ### Actual behavior Sometimes for longer then 1 minutes after the guest shutdown, the guest is not fully shutdown and cannot be started up again.

Dev says that a qube that is shutdown in guest side but not in the dom0 side is mostly doing LVM snapshot cleanups.

I have an elementary conclusion. If you are (a)using HDD, (b)playing with a VM that has private storage of more than 300GB, and (c)the 300GB is mostly docker container layers so that each time docker daemon starts up, the atime of nearly each file inside your filesystem is updated, then it will not be strange that handling LVM snapshot takes a great deal of time (over 1 hr).

A good question is to ask whether there is a better progress bar of shutdowning for such qube.

slcoleman · April 20, 2023, 2:58pm

My qube manager stopped showing the transient state (yellow) all together, though I have a similar problem shutting down some qubes on occasion. It will continue to display green (running state) but when attempting to shut it down again it says its alteady disconnected. When this happens the kill command generally works, but not always. Upon restarting qube manager it usually displays the correct shutdown state, but not always.

Since qube manager never (since last reinstall of qubes 4.1) shows the transient state, so I was thinking this was just the new behavior of 4.1. Since I now know that the transient state still exists in qube manager, can anyone tell me where to look for this state change interaction? Perhaps my issue is related, so I would like to explore this issue.

More generally, where would I find the docs for the qubes python class heirchy so I could understand how this is acctually supposed to work? I always wanted to understand this qubes class heirchy but never had the time to reverse engineer it just to satisfy my own curiosity.