On Fri, Feb 21, 2020 at 07:19:26PM +0100, Marc Haber wrote: > After such a suspend-resume cycle, when shutting down the host, or > issueing an explicit virsh shutdown, the VM doesn't shut down cleanly.
Right after sending this message, I had the bug without suspending host and/or VM before. So you can ignore my blurb in this regard. > The "stop job pending" lines are written in an endless loop, at a rate > of about 6500 (sic!) lines per second, interrupted with spurious > "Looping too fast. Throttling execution a little." lines. In this state, > it is too late to log in again, the only way to recover is virsh destroy > (which might lead to data loss in the VM, hence the severity > 'important'). After virsh destroy, the syslog is truncated and doesn't show the issue at all. So it is advised to have a tail -f syslog running before trying the virsh shutdown if debugging. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
