From: Jason Wang <jasowang@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] kvm: virtio-net: saved image requires TUN_F_UFO support
Date: Wed, 8 Nov 2017 16:54:28 +0900 [thread overview]
Message-ID: <54326bae-831d-dfb8-151e-534d3a100c2c@redhat.com> (raw)
In-Reply-To: <f362d043-7293-65b7-734b-c8372a5f16c3@profihost.ag>
On 2017年11月08日 15:41, Stefan Priebe - Profihost AG wrote:
> Hi Paolo,
>
> Am 06.11.2017 um 12:27 schrieb Paolo Bonzini:
>> On 06/11/2017 12:09, Stefan Priebe - Profihost AG wrote:
>>> HI Paolo,
>>>
>>> could this patchset be related?
>> Uh oh, yes it should. Jason, any ways to fix it? I suppose we need to
>> disable UFO in the newest machine types, but do we also have to do
>> (software) UFO in vhost-net and QEMU for migration compatibility?
> Any news on this?
>
> Greets,
Since we probe UFO support, it will be disabled automatically on device
startup.
For the issue of migration, I think the only way is trying to fix it in
kernel.
Thanks
next prev parent reply other threads:[~2017-11-08 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 9:38 [Qemu-devel] kvm: virtio-net: saved image requires TUN_F_UFO support Stefan Priebe - Profihost AG
2017-11-06 9:40 ` Paolo Bonzini
2017-11-06 9:48 ` Stefan Priebe - Profihost AG
2017-11-06 9:49 ` Paolo Bonzini
2017-11-06 9:52 ` Stefan Priebe - Profihost AG
2017-11-06 11:09 ` Stefan Priebe - Profihost AG
2017-11-06 11:27 ` Paolo Bonzini
2017-11-08 6:41 ` Stefan Priebe - Profihost AG
2017-11-08 7:54 ` Jason Wang [this message]
2017-11-08 8:05 ` Stefan Priebe - Profihost AG
2017-11-08 8:21 ` Jason Wang
2017-11-08 9:46 ` Paolo Bonzini
2017-11-08 10:22 ` Jason Wang
2017-11-10 4:18 ` Jason Wang
2017-11-11 18:59 ` Stefan Priebe - Profihost AG
2017-11-13 8:27 ` Paolo Bonzini
2017-11-22 19:41 ` Dr. David Alan Gilbert
2017-11-22 19:48 ` Stefan Priebe - Profihost AG
2017-11-22 19:53 ` Dr. David Alan Gilbert
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=54326bae-831d-dfb8-151e-534d3a100c2c@redhat.com \
--to=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).