Date: Fri, 28 Jun 2024 12:08:33 -0400 From: mike tancsa <mike@sentex.net> To: Alex Arslan <ararslan@comcast.net>, freebsd-hackers@freebsd.org Subject: Re: Diagnosing virtual machine network issues Message-ID: <4a5a177a-5356-453c-8a09-f1d63d5d2e16@sentex.net> In-Reply-To: <FA265FAA-216D-4DCC-92C0-50017C17F7DE@comcast.net> References: <FA265FAA-216D-4DCC-92C0-50017C17F7DE@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/28/2024 11:53 AM, Alex Arslan wrote: > We've noticed a number of network-related issues that only occur on the > FreeBSD VMs and cause tests to fail. Currently we reliably see a test > failure that expects a host resolution failure via libcurl from > https://domain.invalid but on the FreeBSD VMs we instead get a timeout. I would start a pcap inside and outside of the VM for all udp port 53 traffic as a start to see if its a network issue going out of the box. If it happens frequently and you think it might be the network, perhaps try with the Intel em driver instead of the virtio network driver ? ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4a5a177a-5356-453c-8a09-f1d63d5d2e16>