From owner-freebsd-virtualization@freebsd.org Tue Jul 7 13:07:08 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 C3484995BD5; Tue, 7 Jul 2015 13:07:08 +0000 (UTC) (envelope-from weh@microsoft.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0784.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc09::784]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A96C1DFB; Tue, 7 Jul 2015 13:07:08 +0000 (UTC) (envelope-from weh@microsoft.com) Received: from BY1PR03MB1434.namprd03.prod.outlook.com (10.162.127.152) by BY1PR03MB1434.namprd03.prod.outlook.com (10.162.127.152) with Microsoft SMTP Server (TLS) id 15.1.201.16; Tue, 7 Jul 2015 13:06:48 +0000 Received: from BY1PR03MB1434.namprd03.prod.outlook.com ([10.162.127.152]) by BY1PR03MB1434.namprd03.prod.outlook.com ([10.162.127.152]) with mapi id 15.01.0201.000; Tue, 7 Jul 2015 13:06:48 +0000 From: Wei Hu To: Pavel Timofeev , "freebsd-current@freebsd.org" , "freebsd-virtualization@freebsd.org" Subject: RE: MS DNS doesn't answer to CURRENT under Hyper-V Thread-Topic: MS DNS doesn't answer to CURRENT under Hyper-V Thread-Index: AQHQuKsxHCAHG2fAnE6RlFoo4JehXp3P8GRw Date: Tue, 7 Jul 2015 13:06:48 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: gmail.com; dkim=none (message not signed) header.d=none; x-originating-ip: [167.220.232.8] x-microsoft-exchange-diagnostics: 1; BY1PR03MB1434; 5:Np7VvWK7GxX3SBYKfIz8mjOeELizMWcqPko1saTZmTAlOXNXoVyHLROSfHGApy/HmvQyvXlwhq6wyA9U/xM3EMBaU7ew1K7VVfJWpxJEWjLE7F3dAUmMVGOin8fRuybpHFF2z2XtIpuOuSBzyMY4lg==; 24:Vtv0c8Tkq9PV0hRnfpSlY3x3ukYoS+dah2ml5MmrO+KP0RueFxqoFvaXtiddokuNV+0S1qfEdV0HyDHz5nkPM42Cr23GIuoeJUjHQ+nL5iU=; 20:b7CujLD826fdZwGa+kUxX7xNjr6VC1lbEQ1nf2mrBLixDUt35IjIrTD8m3Hu8Qvu3oMomP7z3rhIGF5wNZnZeg== x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR03MB1434; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401001)(5005006)(3002001); SRVR:BY1PR03MB1434; BCL:0; PCL:0; RULEID:; SRVR:BY1PR03MB1434; x-forefront-prvs: 0630013541 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(51704005)(164054003)(13464003)(377454003)(77156002)(99286002)(2201001)(19580395003)(86612001)(33656002)(2501003)(74316001)(5003600100002)(2656002)(5002640100001)(54356999)(76576001)(50986999)(189998001)(76176999)(5001960100002)(92566002)(122556002)(86362001)(46102003)(2950100001)(66066001)(2900100001)(4477795004)(40100003)(106116001)(19580405001)(5001770100001)(87936001)(62966003)(102836002)(107886002)(77096005)(19626775001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR03MB1434; H:BY1PR03MB1434.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jul 2015 13:06:48.1969 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR03MB1434 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 13:07:09 -0000 > -----Original Message----- > From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd- > virtualization@freebsd.org] On Behalf Of Pavel Timofeev > Sent: Tuesday, July 7, 2015 7:51 PM > To: freebsd-current@freebsd.org; freebsd-virtualization@freebsd.org > Subject: MS DNS doesn't answer to CURRENT under Hyper-V >=20 > 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!). >=20 > What I do: > # host google.ru 192.168.25.3 > I see that MS DNS (192.168.25.3) server receives these packets, but ignor= es > them. > And no matter how my system asks MS DNS. Every daemon can't get > response too. >=20 > I know that nothing was changed in MS DNS server. No doubt. > Then I tried different available CURRENT snapshot ISOs. >=20 > FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso - MS DNS does > not answer. >=20 > FreeBSD-11.0-CURRENT-amd64-20150625-r284814-disc1.iso - MS DNS does > not answer. >=20 > FreeBSD-11.0-CURRENT-amd64-20150618-r284544-disc1.iso - MS DNS > answers! >=20 > So something was committed to CURRENT between 20150618 and 20150625. > This something ruins communication with MS DNS. >=20 There was a commit for Hyper-V TSO and checksum offloading support (r28474= 6) on=20 June 24th. I think this commit is the cause. Can you verify the MS DNS beha= vior between The builds of June 23rd and 24th? I will take a look of this issue tomorrow= . Thanks, Wei