Date: Tue, 24 Jan 2017 11:40:18 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 216425] When transfer large files, NFS hangs when VM network card is if_vmx or if_vxn, ok for e1000 Message-ID: <bug-216425-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216425 Bug ID: 216425 Summary: When transfer large files, NFS hangs when VM network card is if_vmx or if_vxn, ok for e1000 Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: patrick_dkt@yahoo.com.hk CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Setup: FreeBSD VM guest as NFS server. The physical host running VMware workstation. FreeBSD version: FreeBSD 11.0-STABLE #0 r309850: Sun Dec 11 19:30:14 One disk is ZFS, de-duplication and compression is enabled for the ZFS data= set. It is shared out for NFS to another client (The host is Linux) When the NIC setting of the VM is vmxnet3 (if_vmx) or vmxnet (if_vxn): After the client had mount the NFS, the client side would hang if there are large file operations such as 'dd if=3D/dev/zero of=3D/nfs_mount_point/file= bs=3D100M count=3D1' or copy large files to the NFS mount point. When it had problem. The CPU usage in FreeBSD is normal. There would be ser= ious packet loss for all the NICs in the FreeBSD VM guest. Besides packet loss, = for the other NFS Linux clients, they will see these error message: [ 5843.755544] nfs: server FreeBSD_SERVER_IP not responding, timed out After changing the emulated ethernet card to e1000. It is fine but the spee= d is slower (10 gigabit vs 1 gigabit). I have tested with other Linux guests, they do not have such problem. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216425-6>