From owner-freebsd-virtualization@freebsd.org Tue Jul 7 11:50:51 2015 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B38F999535A; Tue, 7 Jul 2015 11:50:51 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 518D4192F; Tue, 7 Jul 2015 11:50:51 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by widjy10 with SMTP id jy10so186353748wid.1; Tue, 07 Jul 2015 04:50:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=v6y1JyN8/ZdQIJpd9Z9Z5o+WKcSI9w256ZYN3hesObA=; b=UVQ6RSKppvkiPjnkyvTB5VCFtlYu1V1S0WTw2A1AKT4v56r32y0GaQGT+kmwcGIawK jDXZArILx37KrHuk6pzeWkR+ajgU3SMgE5dxBXt5BrWpMeo/d3lwpwXxkWkx7wcfwHVc qzSqg9wOzxWnsTsN8YDQh+lCvcpgp8EU1pGJR5mjkWKMzYQ3IQPC2dGLpEHmIlgHun5f 3ThTdPteVohHS1jtaLyYpA/TO/xV/LTIOHh/wwCsMtVLTEuJhbx4gOuyPRc062IlHHvi hZKnL/siSnrmEGm/ys2HoYw+/9uvEQVfXkzSS2dSCh7A71TPmEQ08dSWAOGuZgtmIYVN WzhQ== MIME-Version: 1.0 X-Received: by 10.180.37.230 with SMTP id b6mr62964409wik.14.1436269849885; Tue, 07 Jul 2015 04:50:49 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 04:50:49 -0700 (PDT) Date: Tue, 7 Jul 2015 14:50:49 +0300 Message-ID: Subject: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: freebsd-current@freebsd.org, "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2015 11:50:51 -0000 Hi! I have a test virtual machine which runs CURRENT under Hyper-V. It's amd64 r285198 now. It can't get any response from MS DNS server. Well, it could two or three weeks ago, but after upgrade it's not able to do it anymore. Google DNS answers without problems meanwhile (sic!). What I do: # host google.ru 192.168.25.3 I see that MS DNS (192.168.25.3) server receives these packets, but ignores them. And no matter how my system asks MS DNS. Every daemon can't get response too. I know that nothing was changed in MS DNS server. No doubt. Then I tried different available CURRENT snapshot ISOs. FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso - MS DNS does not answer. FreeBSD-11.0-CURRENT-amd64-20150625-r284814-disc1.iso - MS DNS does not answer. FreeBSD-11.0-CURRENT-amd64-20150618-r284544-disc1.iso - MS DNS answers! So something was committed to CURRENT between 20150618 and 20150625. This something ruins communication with MS DNS. Then I tried latest FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso on bare metal - MS DNS answered! Looks like that something is related to Hyper-V code. Maybe it changes packets somehow? I can gather and provide more info (tcpdump?) if you ask, it's not a problem!