[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 Ben Woods changed: What|Removed |Added Status|In Progress |Closed Resolution|---

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 Shirkdog changed: What|Removed |Added CC||msh...@daemon-security.com --- Comment

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 --- Comment #13 from commit-h...@freebsd.org --- A commit references this bug: Author: vmaffione Date: Tue Nov 19 21:10:44 UTC 2019 New revision: 354864 URL: https://svnweb.freebsd.org/changeset/base/354864 Log: bhyve: virtio-net: disabl

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 Vincenzo Maffione changed: What|Removed |Added Status|Open|In Progress --- Comment #12 fr

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 --- Comment #11 from Ben Woods --- (In reply to Aleksandr Fedorov from comment #10) Indeed, that patch fixes it for me. -- You are receiving this mail because: You are on the CC list for the bug. __

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 --- Comment #10 from Aleksandr Fedorov --- I created a guest system with windows 10. It seems my theory is correct. I started ping -f on tap interface before starting the VM. root@q1u001:/afedorov/vm # /usr/obj/afedorov/freebsd-head-clean

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 --- Comment #9 from Aleksandr Fedorov --- Negotiated futures looks fine for me. VIRTIO_NET_F_MRG_RXBUF flag is zero. But I'm worried about how we use sc->rx_merge flag. During initialization, we set it to 1: https://svnweb.freebsd.org/bas

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 Rodney W. Grimes changed: What|Removed |Added CC||virtualizat...@freebsd.org --

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 Vincenzo Maffione changed: What|Removed |Added Assignee|virtualizat...@freebsd.org |vmaffi...@freebsd.org -- You

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 --- Comment #1 from Ben Woods --- I can confirm that rebooting to an older boot environment running r354376 has worked around the issue. Therefore the problem is not the updated Windows 10 version 1909 VM guest, but a regression in the bhyv

[Bug 242023] bhyve pci_vtnet_rx broken after r354552

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242023 Bug ID: 242023 Summary: bhyve pci_vtnet_rx broken after r354552 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Af