When shutting down VMs, they often get stuck at 50% CPU usage

[andrewdavidwong]

Qubes OS version:

R3.2

Affected component(s):

Using qvm-shutdown from the command-line and shutting down VMs using Qubes Manager

---

Steps to reproduce the behavior:

1. Select a running VM in Qubes Manager.
2. Press the shut down button.

or

1. Use qvm-shutdown --wait to shut down the VM.

Expected behavior:

The VM shuts down normally.

Actual behavior:

Around 30-40% of the time, the VM's CPU usage (as shown in Qubes Manager) goes up to 50%. The laptop's fan speeds up (ThinkPad T450s), and the VM does not shut down for a long time. If you wait, it will eventually either shut down or get killed due to the timeout.

[donob4n]

Hi, I think this also happens in Qubes 4.0, I have seen it many of times but I didn't report since I didn't found a way for reproduce it.

In my case I tailed '/var/log/xen/console/guest-'vm-name'.log' and I saw systemd waiting for some services to stop but unfortunately I could not read the affected services (the output was pretty ugly).

[donob4n]

Hi, I think this also happens in Qubes 4.0, I have seen it many of times but I didn't report since I didn't found a way for reproduce it.

In my case I tailed '/var/log/xen/console/guest-'vm-name'.log' and I saw systemd waiting for some services to stop but unfortunately I could not read the affected services (the output was pretty ugly).

[andrewdavidwong]

@marmarek, let us know if there are any logs we should collect on 3.2 and 4.0 next time this happens.

[andrewdavidwong]

@marmarek, let us know if there are any logs we should collect on 3.2 and 4.0 next time this happens.

[mig5]

I see this happening too pretty frequently.

Another way to connect to the shutting-down VM is using Xen's xl tool via dom0:

sudo xl console VMNAME

When I console to the VM that is taking a long time to shutdown, I see this shutdown job is taking a long time to finish:

[ **    ] A stop job is running for Session c3 of user user (1min 2/ 1min 30s)

As you can see there is a kill-switch timer there of 1.5 minutes. After this the machine shuts down. I don't know why this particular stop job takes so long, may not be Qubes-specific. Feels SystemD specific.

http://forums.debian.net/viewtopic.php?f=10&t=134311

I too am on a Thinkpad T450s. I think it has affected both Fedora and Debian VMs for me.

[mig5]

I see this happening too pretty frequently.

Another way to connect to the shutting-down VM is using Xen's xl tool via dom0:

sudo xl console VMNAME

When I console to the VM that is taking a long time to shutdown, I see this shutdown job is taking a long time to finish:

[ **    ] A stop job is running for Session c3 of user user (1min 2/ 1min 30s)

As you can see there is a kill-switch timer there of 1.5 minutes. After this the machine shuts down. I don't know why this particular stop job takes so long, may not be Qubes-specific. Feels SystemD specific.

http://forums.debian.net/viewtopic.php?f=10&t=134311

I too am on a Thinkpad T450s. I think it has affected both Fedora and Debian VMs for me.