From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 197861] Shutting down a VM with Kernel 4.14 will sometime hang
 and a reboot is the only way to recover.
Date: Wed, 03 Jan 2018 11:41:44 +0000
Message-ID: <bug-197861-28872-cBnQ3xU1Xq@https.bugzilla.kernel.org/>
References: <bug-197861-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:39484 "EHLO
        mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1751687AbeACLlp (ORCPT
        <rfc822;kvm@vger.kernel.org>); Wed, 3 Jan 2018 06:41:45 -0500
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
        by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 29F5E2908E
        for <kvm@vger.kernel.org>; Wed,  3 Jan 2018 11:41:45 +0000 (UTC)
In-Reply-To: <bug-197861-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

https://bugzilla.kernel.org/show_bug.cgi?id=197861

--- Comment #35 from Giancarlo Razzolini (grazzolini@archlinux.org) ---
LimeTech, the kernel should be telling you exactly why the task is in blocked
state, unless you have disabled the hung_task_timeout_secs with:

echo 0 > /proc/sys/kernel/hung_task_timeout_secs

If you have done so, revert that, and you should be able to know why. If, on
the call trace you see vhost_net, then I think it is the same issue. That
workaround works just fine, I have been able to shutdown/reboot several guests,
with different OS'es, across 2 hosts with it.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.