From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] kvm: virtio-net: saved image requires TUN_F_UFO support
Date: Mon, 6 Nov 2017 10:49:20 +0100 [thread overview]
Message-ID: <f4b0cb70-7f86-f7cf-bb89-3a9f7ae15dc2@redhat.com> (raw)
In-Reply-To: <748c4d0d-f84b-303d-f9a6-bafa6037d669@profihost.ag>
On 06/11/2017 10:48, Stefan Priebe - Profihost AG wrote:
> Hi Paolo,
>
> Am 06.11.2017 um 10:40 schrieb Paolo Bonzini:
>> On 06/11/2017 10:38, Stefan Priebe - Profihost AG wrote:
>>> Hello,
>>>
>>> i've upgraded some servers from kernel 4.4 to 4.12 - both running Qemu
>>> 2.9.1.
>>>
>>> If i migrate a VM from a host running kernel 4.4 to a host running 4.12
>>> i get:
>>>
>>> kvm: virtio-net: saved image requires TUN_F_UFO support
>>> kvm: Failed to load virtio-net-device:tmp
>>> kvm: Failed to load virtio-net:virtio
>>> kvm: error while loading state for instance 0x0 of device
>>> '0000:00:12.0/virtio-net'
>>> kvm: load of migration failed: Invalid argument
>>>
>>>
>>> while migrating from 4.12 to 4.4 works fine.
>>>
>>> Can anybody help? Is this expected?
>>
>> Can you check why peer_has_ufo failed (in hw/net/virtio-net.c)?
>
> May be - how can i archieve this? Patching the code is not a problem if
> you can give me a hint.
>
>> Also, did this ioctl fail when the tap device was set up on the 4.12 destination?
>> int tap_probe_has_ufo(int fd)
>> {
>> unsigned offload;
>>
>> offload = TUN_F_CSUM | TUN_F_UFO;
>>
>> if (ioctl(fd, TUNSETOFFLOAD, offload) < 0)
>> return 0;
>>
>> return 1;
>> }
>
> Should there be any kernel output or how can i detect / check it?
For both, the simplest answer is probably just using printf.
Paolo
next prev parent reply other threads:[~2017-11-06 9:49 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 [this message]
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
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=f4b0cb70-7f86-f7cf-bb89-3a9f7ae15dc2@redhat.com \
--to=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).