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
