From owner-freebsd-virtualization@freebsd.org Tue Jul 7 14:11:32 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 3AD43995C0E; Tue, 7 Jul 2015 14:11:32 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 22E3A1ECD; Tue, 7 Jul 2015 14:11:32 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 66B9B1EE3; Tue, 7 Jul 2015 14:11:31 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 7 Jul 2015 14:11:29 +0000 From: Glen Barber To: Pavel Timofeev Cc: Wei Hu , "freebsd-current@freebsd.org" , "freebsd-virtualization@freebsd.org" Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V Message-ID: <20150707141129.GK13404@FreeBSD.org> References: <20150707135847.GJ13404@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="W2ydbIOJmkm74tJ2" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) 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 14:11:32 -0000 --W2ydbIOJmkm74tJ2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sorry, I misread part of your email, and thought you were using Azure (which is Hyper-V based). Sorry for the noise. Glen On Tue, Jul 07, 2015 at 05:10:30PM +0300, Pavel Timofeev wrote: > No, I don't even know what VMDepot is, sorry! Didn't know ;) >=20 > 2015-07-07 16:58 GMT+03:00 Glen Barber : > > BTW, are you using the images from VMDepot? If so, this was MFC'd after > > the recent images. I can easily regenerate an updated image, if you are > > using those. > > > > Glen > > > > On Tue, Jul 07, 2015 at 04:55:39PM +0300, Pavel Timofeev wrote: > >> Wow, r284746 was MFCed to 10 STABLE! > >> I should hurry up! > >> > >> 2015-07-07 16:26 GMT+03:00 Pavel Timofeev : > >> > Ok, I'll try r284745 and then r284746 and see what happens. > >> > > >> > 2015-07-07 16:06 GMT+03:00 Wei Hu : > >> >>> -----Original Message----- > >> >>> From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freeb= sd- > >> >>> 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 > >> >>> > >> >>> 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 o= r 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, bu= t 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 2015062= 5. > >> >>> This something ruins communication with MS DNS. > >> >>> > >> >> There was a commit for Hyper-V TSO and checksum offloading support = (r284746) on > >> >> June 24th. I think this commit is the cause. Can you verify the MS = DNS behavior between > >> >> The builds of June 23rd and 24th? I will take a look of this issue = tomorrow. > >> >> > >> >> Thanks, > >> >> Wei > >> >> > >> >> > >> >> > >> _______________________________________________ > >> freebsd-virtualization@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@f= reebsd.org" >=20 --W2ydbIOJmkm74tJ2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVm94RAAoJEAMUWKVHj+KTUzwQAJyVvmZ9EHjYsD+zFtz3iAXW Ecn5MQrCg7ONNIJcoA40bwhqMjpWQ9/OwiH1Rdb548uPJAoqHp51CJZ4XwKscnOb qN33sc2hWM+I2rZJJyZJOo+SKMggpylg6fFG3Z6pjpP5a3Js564U9b9ubuAceFl7 kv0KP5NWGFzZAubdv6fPVk35ygKPOsIhn0eS0kilvgkJidOuzFsb+b4hyX1vkPsj aBvU+OHpls0fjT/Ialf1QfFcf++fV1lcgpsn+cDl+SQwmemkaOITwFRNLi1iRz9g 8mMKA/UvW8gxhWXpRpc6ETgtfMVN7+q2qRyCkvEt/i0Vo9l0O/IUhgJdjWUtklGQ hWScveohJCusNhbdZwEH2IvkhgMGUUiiBvkqwTxzfpetUYs5yLvUjQpHmOnglQwy 5PVjVE2u/avDF0qpnW+Iuh3xGV2vhnfeykJbZNbNm6f281+eR3JqvUKlLlwjpj0U MbUyIPJIPMfMwsZjSBd6jEMfB0JJ3Wrjjnv6+Yzqq0xMdkWsPnSWMMiQyQDsewHU GG+195v9qXVui93fyZ/FJYHjNvS7+mjM77ZhkvzfjCGmyG6ujxeWmeCFsvztBohe zjqqh05HEGO422YEMjFwBQQ8G8cCxOU/WKeAMKsw+CSTY5AdkNHH4j57vwjG27Os pfxSOE4qYE0t1XWwXAo1 =eu+9 -----END PGP SIGNATURE----- --W2ydbIOJmkm74tJ2--