libvirt freeze after VM shutdown
27 views
Skip to first unread message
HW42
Nov 3, 2015, 1:52:30 PM11/3/15
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
when I shutdown a VM the qubes/qvm tools (qubes-manager, qvm-ls, ...)
become often (but not always) unresponsive for about 60 s.
After a bit debugging it seems the libvirt requests are blocking. And
indeed "virsh -c xen:/// list" blocks also. A strace of virsh shows
that it sends some request to the libvirt socket and then blocks while
waiting for an answer.
This problem is not new. If I remember correctly this always existed
in R3. I just haven't had time to debug.
The most reliable way to trigger to problem is to shutdown multiple
VMs at the same moment (for example via qvm-shutdown --all).
I observed that often the loop devices doesn't get cleaned up
correctly - but this might be a separate problem.
Does somebody observe the same problem? Has somebody already debugged
this?
Qubes-Issue #1288 might be related.
HW42
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJWOQI+AAoJEOSsySeKZGgWTUQQAKhX2O0gloC+W303H6gmBTJu
b6o1mpZybLmzqODHjcKX0szRoJ4fYaDW3BkDoBIPNc+pKl4aEV7YZ3lcxUr4pfcX
mvPiK3vRMtY83B2TdRDVxWopgRtW3KhzvlnmaQhb2MvkjeWJnFxeEXUpUC/lSPSo
K1JMAQFf9RogOgJmhCMX1k00DEBCdiIsU1zgyOOdxMBQdhPQRHgsuzvzQUF87gPz
LEjpN7301vLq5fOmKcV8L+NE08fwHLIozH+W7LIZPrqBS7sGRMeUMOE0sYnNGGBw
hOZDni0+WCrztUZKlfA9RVp4InsXJOGmysZSljSRk59gzqnSPGzzCM+cSxDzlSeL
qBpMMSA1hRy38wlZnJT97nnB6J/XlcDjRCvLI/OL4TFZPMWbA7Dk4/MVaaSggai7
cauMZ6qCm7kAAUA8Qq5f5laOOi3NESjNqaBAk1rTBnuwqnEjNNfrwRDfaNp+yoS8
jKEo+8WCVqMu2YjWoROkp6esIhpSHDFeC9y79UVFFcCuBkYMFdWGgOu5+u0Jsl9z
Y1Cqer+U/pLstzswbbKt8Qsi5qn1AKO3L81sV3heqg8pF1ATXDibbfvbU8IbuqVa
5G25oP2ahwyoAZ+4rdOQpZ6IZkKqOWDP0R8ej2HUTI41JCLxLbhsjzOMCeX1L7vM
lIIQhgygmmfqpaM98V7C
=xZZu
-----END PGP SIGNATURE-----
Hash: SHA512
Hi,
when I shutdown a VM the qubes/qvm tools (qubes-manager, qvm-ls, ...)
become often (but not always) unresponsive for about 60 s.
After a bit debugging it seems the libvirt requests are blocking. And
indeed "virsh -c xen:/// list" blocks also. A strace of virsh shows
that it sends some request to the libvirt socket and then blocks while
waiting for an answer.
This problem is not new. If I remember correctly this always existed
in R3. I just haven't had time to debug.
The most reliable way to trigger to problem is to shutdown multiple
VMs at the same moment (for example via qvm-shutdown --all).
I observed that often the loop devices doesn't get cleaned up
correctly - but this might be a separate problem.
Does somebody observe the same problem? Has somebody already debugged
this?
Qubes-Issue #1288 might be related.
HW42
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJWOQI+AAoJEOSsySeKZGgWTUQQAKhX2O0gloC+W303H6gmBTJu
b6o1mpZybLmzqODHjcKX0szRoJ4fYaDW3BkDoBIPNc+pKl4aEV7YZ3lcxUr4pfcX
mvPiK3vRMtY83B2TdRDVxWopgRtW3KhzvlnmaQhb2MvkjeWJnFxeEXUpUC/lSPSo
K1JMAQFf9RogOgJmhCMX1k00DEBCdiIsU1zgyOOdxMBQdhPQRHgsuzvzQUF87gPz
LEjpN7301vLq5fOmKcV8L+NE08fwHLIozH+W7LIZPrqBS7sGRMeUMOE0sYnNGGBw
hOZDni0+WCrztUZKlfA9RVp4InsXJOGmysZSljSRk59gzqnSPGzzCM+cSxDzlSeL
qBpMMSA1hRy38wlZnJT97nnB6J/XlcDjRCvLI/OL4TFZPMWbA7Dk4/MVaaSggai7
cauMZ6qCm7kAAUA8Qq5f5laOOi3NESjNqaBAk1rTBnuwqnEjNNfrwRDfaNp+yoS8
jKEo+8WCVqMu2YjWoROkp6esIhpSHDFeC9y79UVFFcCuBkYMFdWGgOu5+u0Jsl9z
Y1Cqer+U/pLstzswbbKt8Qsi5qn1AKO3L81sV3heqg8pF1ATXDibbfvbU8IbuqVa
5G25oP2ahwyoAZ+4rdOQpZ6IZkKqOWDP0R8ej2HUTI41JCLxLbhsjzOMCeX1L7vM
lIIQhgygmmfqpaM98V7C
=xZZu
-----END PGP SIGNATURE-----
yaqu
Nov 3, 2015, 2:16:46 PM11/3/15
to qubes...@googlegroups.com
On Tue, 3 Nov 2015 19:51:44 +0100, HW42 <hw...@ipsumj.de> wrote:
> This problem is not new. If I remember correctly this always existed
> in R3. I just haven't had time to debug.
>
> The most reliable way to trigger to problem is to shutdown multiple
> VMs at the same moment (for example via qvm-shutdown --all).
>
> I observed that often the loop devices doesn't get cleaned up
> correctly - but this might be a separate problem.
>
> Does somebody observe the same problem? Has somebody already debugged
> this?
I have the same problem since I upgraded from R2 to R3.0,
> This problem is not new. If I remember correctly this always existed
> in R3. I just haven't had time to debug.
>
> The most reliable way to trigger to problem is to shutdown multiple
> VMs at the same moment (for example via qvm-shutdown --all).
>
> I observed that often the loop devices doesn't get cleaned up
> correctly - but this might be a separate problem.
>
> Does somebody observe the same problem? Has somebody already debugged
> this?
'qvm-shutdown -all' freezes Qubes Manager and qvm-* tools for some time.
I haven't tried to debug it.
--
yaqu
Axon
Nov 3, 2015, 6:37:43 PM11/3/15
to HW42, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
HW42:
Hash: SHA512
> Hi,
>
> when I shutdown a VM the qubes/qvm tools (qubes-manager, qvm-ls,
> ...) become often (but not always) unresponsive for about 60 s.
>
> After a bit debugging it seems the libvirt requests are blocking.
> And indeed "virsh -c xen:/// list" blocks also. A strace of virsh
> shows that it sends some request to the libvirt socket and then
> blocks while waiting for an answer.
>
> This problem is not new. If I remember correctly this always
> existed in R3. I just haven't had time to debug.
>
> The most reliable way to trigger to problem is to shutdown
> multiple VMs at the same moment (for example via qvm-shutdown
> --all).
>
> I observed that often the loop devices doesn't get cleaned up
> correctly - but this might be a separate problem.
>
> Does somebody observe the same problem? Has somebody already
> debugged this?
>
> Qubes-Issue #1288 might be related.
>
I don't see how this can't be #1228. Added this message to the issue.
>
> when I shutdown a VM the qubes/qvm tools (qubes-manager, qvm-ls,
> ...) become often (but not always) unresponsive for about 60 s.
>
> After a bit debugging it seems the libvirt requests are blocking.
> And indeed "virsh -c xen:/// list" blocks also. A strace of virsh
> shows that it sends some request to the libvirt socket and then
> blocks while waiting for an answer.
>
> This problem is not new. If I remember correctly this always
> existed in R3. I just haven't had time to debug.
>
> The most reliable way to trigger to problem is to shutdown
> multiple VMs at the same moment (for example via qvm-shutdown
> --all).
>
> I observed that often the loop devices doesn't get cleaned up
> correctly - but this might be a separate problem.
>
> Does somebody observe the same problem? Has somebody already
> debugged this?
>
> Qubes-Issue #1288 might be related.
>
Thank you for looking into this!
> HW42
>
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJWOUU9AAoJEJh4Btx1RPV8UwkQAKl0fRaCTKOjoJ3wKnbsp3c0
8QOaUs69ztHejh0mZNMhRQHjL+GKSlbK0nrOWyrHKppYzjjyG/+0CKND/bjBRxzw
sk4XBES6Miq+4LYK+zt4Akuc2DBJYZnnxBtGFz/YCw3MD+PChctvD5cPyAhbxhaq
UmgCy+2xj2P6d9WNs2U1DjhWyTHSGOwlQaJuLFfkCP+n5soOitrtO/68Kxwj4oZ+
oKkDk5A5Eg/B5ITIGKJpTcaaSVJZ11eo6MVp6Y5L3irmCu/OLQz4Q893klh5X8qo
2MAEZkiBjxndLI+UZuqdHtjWOkWaXBRhbviiHRAD7fXFf8ORmlqxwMuL0QxwmoZl
L3e8+b8/gmH+yNCWZZKimdAJ7kW0MxN81ovEe6tYhajMgmnmVN0kDjbAqXTOrgu5
1rls06UjAk4/0BmFGvh4miOZeeSP5EQ6wmXGgDCjdYS7zkH/lO3B0xziMXNNJe9i
Xp+Bgak2UOf8hf01pTXvOD6bmlo718fh8nTM2yuXGKXfDOOPkD0sjbIag0tP4+2B
h35Tz1zVv1yB/X4Gyq9OZOJs8p8mm9Iwlnao00iG1V+M/FZfH8u5cVGgm6uJR8KJ
Yjdb9IY92eDZyXWkUyEUGOEv6KZHmVWksn8+9k4LMXVVBuwTU2WkhoRwc3bQh7Pz
7j2og7oBqhY9iwmeTYxW
=5veX
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages