Date: Tue, 30 Jul 2024 14:22:54 -0700 From: Bakul Shah <bakul@iitbombay.org> To: Alex Arslan <ararslan@comcast.net> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Diagnosing virtual machine network issues Message-ID: <2B0A1E6F-7B89-4F7C-9ECE-ABA94E476D5A@iitbombay.org> In-Reply-To: <0747ED5F-2ED6-461C-9C0B-CFD0EE480D82@comcast.net> References: <FA265FAA-216D-4DCC-92C0-50017C17F7DE@comcast.net> <4a5a177a-5356-453c-8a09-f1d63d5d2e16@sentex.net> <4AB1C33B-DD93-4484-B63A-9FF8FE612B15@comcast.net> <E72DA395-3C66-4520-B58B-31C19E7462A3@comcast.net> <799c7a15-52b8-4b44-bcbd-5ab6a3ef97a6@gmail.com> <0747ED5F-2ED6-461C-9C0B-CFD0EE480D82@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Jul 30, 2024, at 2:11=E2=80=AFPM, Alex Arslan = <ararslan@comcast.net> wrote: >=20 >=20 >> Can you provide more context? I'm not seeing earlier messages = anywhere in my email folders. Is this a Qemu issue? >=20 > The original message is from just over a month ago, archived here: > = https://lists.freebsd.org/archives/freebsd-hackers/2024-June/003378.html > Basically, we have FreeBSD 13.2 VMs running under KVM on a Linux = machine. > Some code is using libcurl to make a request to an invalid domain and = is > testing that the error is a resolution failure. This test passes on = all > platforms except specifically in these FreeBSD VMs; I can't reproduce > locally on FreeBSD. That made me think that there's an issue with how = the > VM was set up, prompting the original message and discussion. Then = what > I recently found was that we set a 30-second timeout for the libcurl > request, which FreeBSD hits in the VM, as it evidently spends a full > 30 seconds attempting to resolve the host, while e.g. Linux reports a > resolution failure immediately. What does /etc/resolv.conf look like on the FreeBSD VM?=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2B0A1E6F-7B89-4F7C-9ECE-ABA94E476D5A>