From: "Anthony Liguori" <anthony@codemonkey.ws>
To: dlaor@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problem with virtio net in guest
Date: Sun, 21 Dec 2008 13:08:20 -0600 [thread overview]
Message-ID: <f085eb030812211108o402217d5m3e5be165ca28eb1f@mail.gmail.com> (raw)
In-Reply-To: <494E6D72.5090406@redhat.com>
On Sun, Dec 21, 2008 at 10:23 AM, Dor Laor <dlaor@redhat.com> wrote:
>
> nuitari-qemu@nuitari.net wrote:
>>
>> I use virtio_net in guest and use kvm-81
>> After a migration none of the network cards in the guest work.
>>
>> If I check with dmesg, I see bad_partial_csum all over the place.
>
> This is because there is no live migration (dirty bit tracking) in virtio yet.
There is now, actually. I suspect save/restore with GSO is broken or
not resilient enough to deal with two hosts without agreeable GSO
support.
Regards,
Anthony Liguori
>>
>> If I use e1000 for the guest NICs, everything works.
>>
>>
>
>
>
prev parent reply other threads:[~2008-12-21 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 15:18 [Qemu-devel] Problem with virtio net in guest nuitari-qemu
2008-12-21 16:23 ` Dor Laor
2008-12-21 19:08 ` Anthony Liguori [this message]
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=f085eb030812211108o402217d5m3e5be165ca28eb1f@mail.gmail.com \
--to=anthony@codemonkey.ws \
--cc=dlaor@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).