Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Jun 2015 21:37:04 -0700
From:      Neel Natu <neelnatu@gmail.com>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: bhyve: corrupting zfs pools?
Message-ID:  <CAFgRE9FVJt8T4%2Bz0EXo=GVHx_NKRHG9Jz6qXizyqVORg3_2RAA@mail.gmail.com>
In-Reply-To: <556ED071.5030009@FreeBSD.org>
References:  <556D9005.4020802@FreeBSD.org> <556DDDA9.6090005@FreeBSD.org> <CAFgRE9G0pp4-HmDZ2mmWyoxc9KNSxcCnWLLh2yrvCwGTXC4q9A@mail.gmail.com> <556ED071.5030009@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andriy,

On Wed, Jun 3, 2015 at 3:01 AM, Andriy Gapon <avg@freebsd.org> wrote:
> On 03/06/2015 00:40, Neel Natu wrote:
>> Perhaps, but I wasn't able to repro this. I tried your recipe to repro
>> on two systems running -current at r283917.
>>
>> - Intel Sandybridge server: Xeon E52650  with 8 cores/16 threads and 64GB memory
>>   - hdd1/hdd2 on UFS
>>   - hdd1/hdd2 on ZFS
>>
>> - AMD Opteron server: Opteron 6230 with 8 cores and 16GB memory
>>   - hdd1/hdd2 on UFS
>>
>> Can you provide some more details about your setup? I can then try to
>> repro on a system similar to your setup.
>>
>> - uname -a
>
> FreeBSD trant 11.0-CURRENT FreeBSD 11.0-CURRENT #134 r283188+ab4f83f(devel): Fri
> May 22 15:55:27 EEST 2015     avg@trant:/usr/obj/usr/src/sys/TRANT  amd64
>
> This is not a pure FreeBSD, there are some local changes, but none to vmm or VM.
>
>> - sysctl hw.model
>
> hw.model: AMD Athlon(tm) II X2 250 Processor
>
>> - sysctl hw.ncpu
>
> hw.ncpu: 2
>
>> - sysctl hw.physmem
>
> hw.physmem: 8029335552
>
>> - sysctl hw.vmm
>
> hw.vmm.npt.pmap_flags: 507
> hw.vmm.svm.num_asids: 64
> hw.vmm.svm.disable_npf_assist: 0
> hw.vmm.svm.features: 15
> hw.vmm.svm.vmcb_clean: 959
> hw.vmm.vmx.vpid_alloc_failed: 0
> hw.vmm.vmx.posted_interrupt_vector: -1
> hw.vmm.vmx.cap.posted_interrupts: 0
> hw.vmm.vmx.cap.virtual_interrupt_delivery: 0
> hw.vmm.vmx.cap.invpcid: 0
> hw.vmm.vmx.cap.monitor_trap: 0
> hw.vmm.vmx.cap.unrestricted_guest: 0
> hw.vmm.vmx.cap.pause_exit: 0
> hw.vmm.vmx.cap.halt_exit: 0
> hw.vmm.vmx.initialized: 0
> hw.vmm.vmx.cr4_zeros_mask: 0
> hw.vmm.vmx.cr4_ones_mask: 0
> hw.vmm.vmx.cr0_zeros_mask: 0
> hw.vmm.vmx.cr0_ones_mask: 0
> hw.vmm.ept.pmap_flags: 0
> hw.vmm.vrtc.flag_broken_time: 1
> hw.vmm.ppt.devices: 0
> hw.vmm.iommu.initialized: 0
> hw.vmm.bhyve_xcpuids: 4
> hw.vmm.topology.cpuid_leaf_b: 1
> hw.vmm.topology.cores_per_package: 1
> hw.vmm.topology.threads_per_core: 1
> hw.vmm.create: beavis
> hw.vmm.destroy: beavis
> hw.vmm.force_iommu: 0
> hw.vmm.trace_guest_exceptions: 0
> hw.vmm.ipinum: 251
> hw.vmm.halt_detection: 1
>
>> - host filesystem underlying hdd1 and hdd2
>
> It's ZFS.
>

Ok, there are some differences in our systems. The interesting ones
are number of ASIDs (64 versus 65536), flush-by-asid capability,
vmcb-clean capability and the number of cores.

I was able to mimic all of these on my Opteron but still wasn't able
to reproduce the issue. I am going to get a Sempron tomorrow which
belongs to the same processor family as the Athlon II so hoping that
it is easier to repro.

BTW does this happen consistently on your system?

best
Neel

> Thank you!
>
> --
> Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFgRE9FVJt8T4%2Bz0EXo=GVHx_NKRHG9Jz6qXizyqVORg3_2RAA>