From: Jason Wang <jasowang@redhat.com>
To: Dave Hill <dhill@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: Shutting down a VM with Kernel 4.14 will sometime hang and a reboot is the only way to recover.
Date: Wed, 29 Nov 2017 13:15:55 +0800 [thread overview]
Message-ID: <918c4152-bcf9-b28c-0f54-f51d07d82bfc@redhat.com> (raw)
In-Reply-To: <1f789868-7fda-3553-7078-3298873fb355@redhat.com>
On 2017年11月29日 10:52, Dave Hill wrote:
>>>
>>
>> Thanks. Zerocopy is disabled by several distribution by default. For
>> upstream, the only reason to let it on is to hope more developers can
>> help and fix the issues.
>>
>>
> So I never hit this issue with previous kernel and this issue started
> happening with the v4.14-rc series.
Right, this still need to be investigated if it was introduced recently.
Looking at git history, the only suspected commit is for 4.14 is
commit 1e6f74536de08b5e50cf0e37e735911c2cef7c62
Author: Willem de Bruijn <willemb@google.com>
Date: Fri Oct 6 13:22:31 2017 -0400
vhost_net: do not stall on zerocopy depletion
Maybe you can try to revert it and see.
If it does not solve your issue, I suspect there's bug elsewhere that
cause a packet to be held for very long time.
> I'm using rawhide so perhaps this is why it isn't disabled by
> default but I have to mention it's an update of FC25 up to FC28 and it
> never got disabled.
> Perhaps it should be disabled in Fedora too if it's not the case...
> I'm not sure this is the place to discuss this ... is it?
Probably not, but I guess Fedora tries to use new technology aggressively.
Thanks
next prev parent reply other threads:[~2017-11-29 5:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <efd45fba-5724-0036-8473-0274b5816ae9@redhat.com>
2017-11-13 15:54 ` Shutting down a VM with Kernel 4.14 will sometime hang and a reboot is the only way to recover. [1] David Hill
[not found] ` <CALapVYHmf7gG25nA-5LkoaTDR8gB0xQ1Ro_FyyCQNbzrfSp+aQ@mail.gmail.com>
2017-11-15 21:08 ` David Hill
2017-11-22 18:22 ` Shutting down a VM with Kernel 4.14 will sometime hang and a reboot is the only way to recover David Hill
2017-11-23 23:48 ` Paolo Bonzini
2017-11-24 3:11 ` Jason Wang
2017-11-24 16:19 ` David Hill
2017-11-24 16:22 ` David Hill
2017-11-27 3:44 ` Jason Wang
2017-11-27 19:38 ` David Hill
2017-11-28 18:00 ` David Hill
2017-11-29 1:52 ` Jason Wang
2017-11-29 2:52 ` Dave Hill
2017-11-29 5:15 ` Jason Wang [this message]
2017-11-29 19:13 ` David Hill
2017-11-30 2:42 ` Jason Wang
2017-11-30 20:52 ` David Hill
2017-11-30 20:59 ` David Hill
2017-12-01 16:38 ` David Hill
2017-12-04 4:08 ` Jason Wang
2017-12-04 19:51 ` David Hill
2017-12-07 4:34 ` David Hill
2017-12-07 4:42 ` David Hill
2017-12-07 5:13 ` Jason Wang
2017-12-08 18:03 ` David Hill
2017-12-12 3:53 ` David Hill
2017-12-19 3:36 ` Jason Wang
2017-12-19 16:19 ` Willem de Bruijn
2017-12-07 5:12 ` Jason Wang
2017-12-02 12:16 ` Harald Moeller
2017-12-02 16:37 ` Harald Moeller
2017-12-07 2:44 ` David Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=918c4152-bcf9-b28c-0f54-f51d07d82bfc@redhat.com \
--to=jasowang@redhat.com \
--cc=dhill@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.