[email protected]:
On Sunday, 23 September 2018 00:54:26 UTC-4, [email protected] wrote:
Currently in my work I encountered VM lock-ups that can be reliably replayed.
And each time I must cold reboot my laptop in order to recover.
I have allocated 2 VCPUs to the VM and the triggerer process is single
threaded. However when that happens, Qubes VM Manager shows that 50% of the CPU
is busy in the mentioned VM. Noticing that my cpu has 4 cores and a recent
update disabled hyper-threading, certainly some disaster happened to the VM. I
don't know whether Shutdown VM does its job (I believe it should be unlikely),
but to make things worse, Kill VM in the Qubes VM Manager locked up the GUI and
I cannot even use Ctrl+Alt+Fx to open the other ttys.
The lock up is limited to several instructions in userspace.
Any idea of tracking the problems?
For reference I use Qubes 3.2, and the guest is Fedora 28.
Does qvm-kill from the command line work any better than the GUI?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/301206ae-fa0b-21cf-eed0-52968bc31d0e%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
