From: Wei Xu <wexu@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: jasowang@redhat.com, netdev@vger.kernel.org, mst@redhat.com,
nhorman@tuxdriver.com, davem@davemloft.net
Subject: Re: "virtio-net: enable multiqueue by default" in linux-next breaks networking on GCE
Date: Wed, 14 Dec 2016 12:24:43 +0800 [thread overview]
Message-ID: <95568017-e7b1-df95-ec49-f38ae8eb1b14@redhat.com> (raw)
In-Reply-To: <20161213194431.42vtozn6bs24vwda@thunk.org>
On 2016年12月14日 03:44, Theodore Ts'o wrote:
> Jason's patch fixed the issue, so I think we have the proper fix, but
> to answer your questions:
>
> On Wed, Dec 14, 2016 at 01:46:44AM +0800, Wei Xu wrote:
>>
>> Q1:
>> Which distribution are you using for the GCE instance?
>
> The test appliance is based on Debian Jessie.
>
>> Q2:
>> Are you running xfs test as an embedded VM case, which means XFS test
>> appliance is also a VM inside the GCE instance? Or the kernel is built
>> for the instance itself?
>
> No, GCE currently doesn't support running nested VM's (e.g., running
> VM's inside GCE). So the kernel is built for the instance itself.
> The way the test appliance works is that it initially boots using the
> Debian Jessie default kernel and then we kexec into the kernel under
> test.
>
>> Q3:
>> Can this bug be reproduced for kvm-xfstests case? I'm trying to set up
>> a local test bed if it makes sense.
>
> You definitely can't do it out of the box -- you need to build the
> image using "gen-image --networking", and then run "kvm-xfstests -N
> shell" as root. But the bug doesn't reproduce on kvm-xfstests, using
> a 4.9 host kernel and linux-next guest kernel.
>
OK, thanks a lot.
BTW, although this is a guest issue, is there anyway to view the GCE
host kernel or qemu(if it is) version?
>
> Cheers,
>
> - Ted
>
next prev parent reply other threads:[~2016-12-14 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 23:33 "virtio-net: enable multiqueue by default" in linux-next breaks networking on GCE Theodore Ts'o
2016-12-13 2:28 ` Michael S. Tsirkin
2016-12-13 3:12 ` Theodore Ts'o
2016-12-13 3:30 ` Michael S. Tsirkin
2016-12-13 3:43 ` Jason Wang
2016-12-13 4:19 ` Theodore Ts'o
2016-12-13 17:46 ` Wei Xu
2016-12-13 19:44 ` Theodore Ts'o
2016-12-14 4:24 ` Wei Xu [this message]
2016-12-14 16:42 ` Theodore Ts'o
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=95568017-e7b1-df95-ec49-f38ae8eb1b14@redhat.com \
--to=wexu@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=tytso@mit.edu \
/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).