From owner-freebsd-virtualization@freebsd.org Sun Jul 5 21:26:25 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 701A498E84D for ; Sun, 5 Jul 2015 21:26:25 +0000 (UTC) (envelope-from neelnatu@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 0F3AE10B9; Sun, 5 Jul 2015 21:26:25 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by wiwl6 with SMTP id l6so268373432wiw.0; Sun, 05 Jul 2015 14:26:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2fraxoEn2UjD2xQ4lZ7YFnrZR65ShdpSBnU4ZcROcGg=; b=ZF4kJhA02OJ/2bCF0HTu70nGglPh0cX1iZn+8TM1vT23UsnPyfyxmFzToR5AWkwIKu ybOCM0/D/60YOuV6lHgFZVW+WNoEzfRV5ugc11J+a4R8sRabmEtiT9futeHJz71cyIzT yXI3hG6Br1lHCs1XTEuZdQHukgT2EJl/u4ZocIizNZYYoEqs0CZuUHoqpcfVwKuMqJwq VYyLclKU9fspbj7Ky35qXi7qYAusGasODFCweF7wkrhQzQOV0gYrkNF5NXSJZQ/BUbe1 1t/TfrTF1JBk4iHD01vukV0SoJR/O2LRM/TMiL8JtHEGsei6jAfmWiv3k9k4XAm9I/So AfEQ== MIME-Version: 1.0 X-Received: by 10.194.2.137 with SMTP id 9mr42104737wju.75.1436131583522; Sun, 05 Jul 2015 14:26:23 -0700 (PDT) Received: by 10.27.52.79 with HTTP; Sun, 5 Jul 2015 14:26:23 -0700 (PDT) In-Reply-To: References: Date: Sun, 5 Jul 2015 14:26:23 -0700 Message-ID: Subject: Re: bhyve - map user-space buffer in the VM From: Neel Natu To: Stefano Garzarella Cc: "freebsd-virtualization@freebsd.org" , Luigi Rizzo , Peter Grehan , Neel Natu , stefano@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: Sun, 05 Jul 2015 21:26:25 -0000 Hi Stefano, Sorry for the late reply. On Tue, Jun 30, 2015 at 2:57 AM, Stefano Garzarella wrote: > Hi all, > I'm working on bhyve to support ptnetmap (netmap passthrough) for my GSoC. > http://wiki.freebsd.org/SummerOfCode2015/ptnetmapOnBhyve > > I've already implemented it on QEMU/KVM and, to expose the netmap memory in > the VM, I used a PCI BAR and I mapped the netmap memory (the buffer returned > by mmap() on netmap fd in the user space) on the BAR in the VM through KVM > API. > > In bhyve I able to create a PCI BAR but I only found vm_map_pptdev_mmio() > API to map physical host page into the VM. I saw that this IOCTL is > implemented in the kernel module with sglist_append_phys() to populate a > scatter/gather list, than it is mapped in VM. > > I would like to add a new function in the API to map a user buffer in the > VM: > int vm_map_user_buf(struct vmctx *ctx, vm_paddr_t gpa, size_t len, void > *host_buf) > > I would implement it adding a new IOCTL and I would create, in the kernel > module, a new function like vmm_mmio_alloc() (sys/amd64/vmm/vmm_mem.c) but > using sglist_append_user() instead of sglist_append_phys(). > > What do you think about it? > There is another way to map an user-space buffer in the VM? > bhyve represents the guest address space as a vmspace that is independent from the bhyve process's vmspace. If a mapping is shared between the two address spaces then both mappings should point to the same vm_object. Also, the virtual machine lifetime can span the bhyve process lifetime. Therefore a shared mapping that points to the bhyve process's heap or data segment needs special handling. So, the general case of mapping an arbitrary bhyve user-space mapping into the guest address space is not trivial. Regarding 'vmm_mmio_alloc()' - this API maps PCI passthru device BARs into the guest address space. Note that it deals with both issues pointed above: 1. vmm.ko owns the passthru device so it can guarantee that the BAR addresses cannot change underneath the guest. 2. vm_cleanup() guarantees that the passthru mappings are removed from the guest address space before the next bhyve process starts running. The 'vmm_mmio_alloc()/vmm_mmio_free()' APIs are very narrow so should not be used a model for the general case. Having said that I think that for the specific case (netmap) your proposal might work assuming wired mappings of the netmap buffers. If the underlying netmap buffers are not physically contiguous then there will be a bit more work to do. I hope that allows you to make progress with the GSoC while we figure out a long-term viable solution. best Neel > Thanks, > Stefano > From owner-freebsd-virtualization@freebsd.org Mon Jul 6 19:35:27 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 A1257AF39 for ; Mon, 6 Jul 2015 19:35:27 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (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 3C7591BF2 for ; Mon, 6 Jul 2015 19:35:27 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by wibdq8 with SMTP id dq8so163049464wib.1 for ; Mon, 06 Jul 2015 12:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vH6ZllLyFJF2n0g8Fks1qxs08aydtC/DGEJ3DgCBTYg=; b=scGTDfVw887WNGRixkQjyxodDti1g0aXKrC3hSlajaFOtBhbllfWrr/+UsAF3WOQLk XUMfjCazLBO9T3pbrkhHVxv1bLVX9MQGdHomMHnYV1NvG1XqPB2LtqiYg6y4NeYTCh7j OXpcuZN3aHRDtiTB+F3eMTVjsQIiP7/SNHCzXZ7enY2lYLuBKyj+CPMKABjZbqDhWpya 18ghvlVOnNWCY+2HPkZaf3icFH67zyXrs4rLX+EYUElu4lVU1kxu/yS8kuu+t4hdjCof YeY9+0Phqg104tLq+NY1BtWRKJwzUWsRlJwhdp2I7LiIkIygtwFhOWso/SXmKJ8FAsQ2 YxVA== MIME-Version: 1.0 X-Received: by 10.180.205.139 with SMTP id lg11mr56811703wic.62.1436211325782; Mon, 06 Jul 2015 12:35:25 -0700 (PDT) Received: by 10.27.52.79 with HTTP; Mon, 6 Jul 2015 12:35:25 -0700 (PDT) In-Reply-To: <55903687.1070601@ptree32.com.au> References: <20150628162059.GU96349@funkthat.com> <55903687.1070601@ptree32.com.au> Date: Mon, 6 Jul 2015 12:35:25 -0700 Message-ID: Subject: Re: weird console issue w/ bhyve... From: Neel Natu To: Peter Grehan Cc: John-Mark Gurney , "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: Mon, 06 Jul 2015 19:35:27 -0000 Fixed in r285217: https://svnweb.freebsd.org/changeset/base/285217 best Neel On Sun, Jun 28, 2015 at 11:01 AM, Peter Grehan wrote: > Hi John-Mark, > >> more and less work perfectly fine when I first login from the console.. >> Sometimes due to terminal issues, the cursor gets "stuck" at the bottom >> on the screen... If I run the rest command, more and less "break" in >> that they do not output... It appears that they are waiting on open >> of the tty... >> >> # less /etc/motd >> load: 0.89 cmd: less 674 [ttydcd] 0.96r 0.00u 0.00s 0% 2528k >> load: 0.89 cmd: less 674 [ttydcd] 1.14r 0.00u 0.00s 0% 2528k >> >> # more /etc/motd >> load: 0.16 cmd: more 677 [ttydcd] 1.34r 0.00u 0.00s 0% 2528k >> load: 0.16 cmd: more 677 [ttydcd] 2.82r 0.00u 0.00s 0% 2528k >> load: 0.16 cmd: more 677 [ttydcd] 3.20r 0.00u 0.00s 0% 2528k >> >> Ideas? > > > /usr/bin/reset clears the clocal flag. That can be reenabled with 'stty > clocal'. > > The bhyve 16550 emulation doesn't nail up DCD so modem control has to be > disabled in software (i.e. by setting clocal). Perhaps this should be > changed so the default is to have DCD always 1 unless specified otherwise. > > later, > > Peter. > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" 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! 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 From owner-freebsd-virtualization@freebsd.org Tue Jul 7 13:09:12 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 2154B995C46; Tue, 7 Jul 2015 13:09:12 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D18C71E82; Tue, 7 Jul 2015 13:09:11 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZCScQ-000Aoo-Rw; Tue, 07 Jul 2015 16:09:02 +0300 Date: Tue, 7 Jul 2015 16:09:02 +0300 From: Slawa Olhovchenkov To: Pavel Timofeev Cc: freebsd-current@freebsd.org, "freebsd-virtualization@freebsd.org" Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V Message-ID: <20150707130902.GA41189@zxy.spb.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false 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:09:12 -0000 On Tue, Jul 07, 2015 at 02:50:49PM +0300, Pavel Timofeev wrote: > 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! Author: whu Date: Wed Jun 24 06:01:29 2015 New Revision: 284746 URL: https://svnweb.freebsd.org/changeset/base/284746 Log: TSO and checksum offloading support for Netvsc driver on Hyper-V. ===== Try tcpdump/wireshark on FreeBSD and MS DNS host. Check validating IP/UDP checksums. Try off checksum offloading on network interface (ifconfig ifname -txcsum -rxcsum) From owner-freebsd-virtualization@freebsd.org Tue Jul 7 13:26:26 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 E3C5C9950E3; Tue, 7 Jul 2015 13:26:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (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 7DB111EDD; Tue, 7 Jul 2015 13:26:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wibdq8 with SMTP id dq8so183061553wib.1; Tue, 07 Jul 2015 06:26:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JKzn7Yg9H4+2S+207Tw+wAYPdU2CBMar/TgWew7Msqc=; b=ax5nGpUp4wvFKi4dRaevqBozhSgtKcQo3AZmnGiSJwShP1sARW5ymTSJOZAsny6kez L/BIpA7Tzj9INXg/UktxNTA3LLgeBT09UwvehobgEIpEK4ICFrtaWyrjeteYPl+ugK/r 0V8hHlbcn9ry8fSsRbZPjE7BOUGNbJhTfeOAa+bQrGnj/7KLFoo5hYFM5Iz5AsjxBwuu jdA++FP74r7HFzFA7xxM8hkRL62zg8chnc1cohMDR9Zp8Phh0KCKmH35XBa8hTvxQ8U8 p1VBJ2x1E3ZNGCv9APKHkqlDvcrE4xrpQM8UF4yOSFoj1ndoG7ZYBoDJW9EBnhCb/Nyt VWTA== MIME-Version: 1.0 X-Received: by 10.180.81.38 with SMTP id w6mr69242920wix.14.1436275585034; Tue, 07 Jul 2015 06:26:25 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 06:26:24 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Jul 2015 16:26:24 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Wei Hu Cc: "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 13:26:27 -0000 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-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 >> >> 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. >> > 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 > > > From owner-freebsd-virtualization@freebsd.org Tue Jul 7 13:55:41 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 A45BB995812; Tue, 7 Jul 2015 13:55:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (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 3818811F6; Tue, 7 Jul 2015 13:55:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wiwl6 with SMTP id l6so315518430wiw.0; Tue, 07 Jul 2015 06:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WJIHvJPa0Og9qb8qR2Ppvg5lZkeWy3bCbj2za2QEPjw=; b=yjGw4NwCnd2uYNDoG0a0BueDEiNcu1u4uU5A4vTGQenJLjOk4y5v6v6RjCNiGiR8JQ aad/kStqyxFaTQwN3EVK/vkD2agaO/VTbBu8VPjAF9Ilb1/VvIFKvRMNy76EEWCIZ+h4 WJW6Q4O2Utw7ZL/XHPrO5guRxSQbkVl9HyU4yTE832KFPySazWUTjRmWbA3uqrGEKEXi 1lYx2aDKIL4AzazyV/dPrLHVCXt15nApDnXRii+cemN5curh2XK15v9h7P+FuDUeMSWb G7y9tODwj+I0we/eIQlMYhSJC3C9l+IBe+U6viF4LFqlasW5akOCFeSuYXyWPw3uNDZq pJYA== MIME-Version: 1.0 X-Received: by 10.180.37.230 with SMTP id b6mr63984260wik.14.1436277339417; Tue, 07 Jul 2015 06:55:39 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 06:55:39 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Jul 2015 16:55:39 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Wei Hu Cc: "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 13:55:41 -0000 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-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 >>> >>> 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. >>> >> 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 >> >> >> From owner-freebsd-virtualization@freebsd.org Tue Jul 7 13:58:50 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 D77129958B6; Tue, 7 Jul 2015 13:58:50 +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 BA8B213E0; Tue, 7 Jul 2015 13:58:50 +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 08BA31B11; Tue, 7 Jul 2015 13:58:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 7 Jul 2015 13:58:47 +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: <20150707135847.GJ13404@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HcccYpVZDxQ8hzPO" 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 13:58:51 -0000 --HcccYpVZDxQ8hzPO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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! >=20 > 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-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 > >>> > >>> 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 t= hree > >>> 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 i= gnores > >>> 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. > >>> > >> There was a commit for Hyper-V TSO and checksum offloading support (r= 284746) 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 tom= orrow. > >> > >> 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@free= bsd.org" --HcccYpVZDxQ8hzPO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVm9sXAAoJEAMUWKVHj+KTracP/1m6DdbB4wv/oSuveQQJsIah ysFvLJATXHYvJ9j1H6hw3WbcLpDF0looUnqlmYwgoZzMBmFT8h4z0c6/PHCBfTOh D4PqUZBSDDFYXOkvx5ICH52UID5GnCNsfNQ5pBzLpCg6FXV3ZT1jZ4ABXy3JnGei krYtDClTrJbzDCDuHRiLd7yR8GgF1lptyyCJqlwvASbvdTVKoATXa8g+Qra2RFxb a3Ac//SUaPhe66JmWouzUfnf/RF0MNVbsZKWeOFMgt1pWnI0ZuH1ZCJRAP+mFQ+z Meh76FbmSPpnYLcryr5uygNVCsVBQ18ryc8iGP3HFjMt/AUwPzbxOtplGoCO2D9x z5m2bqX9vBL+pEdVqhcQNF2UxoIC4MiQIcwQrApG64KZY9yFGVcgZQ/ooL15ucs4 qlCE3AU1SvdPU3qQDXQDQPyqpgwuVnmHNfAGt34Gz1wotl8xElhPuyJWcynXJ5S2 DrX+6cqVvakluhZWAydPRr5zTE1CyFvXIcABYgWPYS9X8FC9zvIkQ3r7xLpM7lut YDhShjO5aFpo+0mM0sDcM+XXP7rxj2dxmzfuClgRGRCdmTzExp1PHawTQc/NnRKV EHhEzsmFEQhmwO8tkBUGTsWXtnuMq2qWDqvKYRM7BmRkuFQrf4c4tb8/DqeVu5+O GaK6T5F2kny00Tvt5999 =7Rn4 -----END PGP SIGNATURE----- --HcccYpVZDxQ8hzPO-- From owner-freebsd-virtualization@freebsd.org Tue Jul 7 14:10: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 8D6AF995BA8; Tue, 7 Jul 2015 14:10:32 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (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 264B51D29; Tue, 7 Jul 2015 14:10:32 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wgfr2 with SMTP id r2so14237803wgf.1; Tue, 07 Jul 2015 07:10:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S6LaFcCRlRkz4oWDGbzGk3PD5/2yGptDnUNj5dv9jf4=; b=cUCQoEROkRbe16l+i+/I2zrwoW3g2JQeEDPWnUczA41gFoGW+bw418brQueFV3D+OH 2dPuFHqStvo50t+gz2tJ1thXW7/JfNyAhlBUUDUN9vW9DnRlnk4fqmShAWUDfueGbqxj rerYVA8YI9TEIYvioTtDjm6M75kuAZBvQOfaKetGxzaWyCMqwATyRmt5LTLo/Hc2eVkd 95R8c5KNF7ZjRJJWtDmR+FOoKzAz3It5iihLNJaxzT7Tm/GN7qDX7DPZVZBMfN1CFSf8 QnfObtVTjNl7NRvUD8NOyJVwnKS744cvguU0yFDtiRW2wfY/ZyEBVo02rgJ1kl6yzTH7 EHyw== MIME-Version: 1.0 X-Received: by 10.194.109.97 with SMTP id hr1mr8669853wjb.95.1436278230702; Tue, 07 Jul 2015 07:10:30 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 07:10:30 -0700 (PDT) In-Reply-To: <20150707135847.GJ13404@FreeBSD.org> References: <20150707135847.GJ13404@FreeBSD.org> Date: Tue, 7 Jul 2015 17:10:30 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Glen Barber Cc: Wei Hu , "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 14:10:32 -0000 No, I don't even know what VMDepot is, sorry! Didn't know ;) 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-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 >> >>> >> >>> 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. >> >>> >> >> 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@freebsd.org" 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-- From owner-freebsd-virtualization@freebsd.org Tue Jul 7 15:04:53 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 A78909956BC; Tue, 7 Jul 2015 15:04:53 +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 433D713DD; Tue, 7 Jul 2015 15:04:53 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wifm2 with SMTP id m2so62499075wif.1; Tue, 07 Jul 2015 08:04:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oVWz4GUQ11mx+XZIDxb74Hc25EjyzqtUWUV2oPflpng=; b=NA+dTsKVKJviyW6VuSshgXZiILa0Z1v+cgq6O5gV/xR9m6zvtKFCiYeBWrrBGZT2RN 7f326VnMww3WnqwuyZNptTw8HN5tQ/ygUzTlEPat+98ufAEPde9XskxE0NvuwEwjHZah Ni1uZrHUrvEv2/EnM5iQfMlt8uIP/yofSiY1kQ09kwqDge1f6R9tDYyYRtVjtvWnxtIf OpvXN3tkqR4itbR28j9dJzXntNUafcc9Ut2Xt+PKVQp4KzDsGgE6u1Pb6HS4hJDqXUJA B8ivIWhdrv++LGPzK2CPOafJ86e7JLZ0Ftd3SqYxR18oUVeN/CdSlfYzXVHCSjseiQ6b KyJQ== MIME-Version: 1.0 X-Received: by 10.194.7.97 with SMTP id i1mr9461703wja.107.1436281486760; Tue, 07 Jul 2015 08:04:46 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 08:04:46 -0700 (PDT) In-Reply-To: <20150707130902.GA41189@zxy.spb.ru> References: <20150707130902.GA41189@zxy.spb.ru> Date: Tue, 7 Jul 2015 18:04:46 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Slawa Olhovchenkov Cc: 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 15:04:53 -0000 Well, turning off checksum offloading by `ifconfig hn0 -txcsum -rxcsum` definitely helps. As for tcpdump I'm not completely sure if I did it right, but I see "bad udp cksum" phrase: # tcpdump -i hn0 -vvv -nn udp dst port 53 tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture size 262144 bytes 18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags [none], proto UDP (17), length 51) 192.168.25.26.45683 > 192.168.25.3.53: [bad udp cksum 0xb39e -> 0xf210!] 52886+ A? ya.ru. (23) 18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags [none], proto UDP (17), length 51) 192.168.25.26.12575 > 192.168.25.3.53: [bad udp cksum 0xb39e -> 0x7365!] 52886+ A? ya.ru. (23) 2015-07-07 16:09 GMT+03:00 Slawa Olhovchenkov : > On Tue, Jul 07, 2015 at 02:50:49PM +0300, Pavel Timofeev wrote: > >> 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! > > Author: whu > Date: Wed Jun 24 06:01:29 2015 > New Revision: 284746 > URL: https://svnweb.freebsd.org/changeset/base/284746 > > Log: > TSO and checksum offloading support for Netvsc driver on Hyper-V. > > ===== > > Try tcpdump/wireshark on FreeBSD and MS DNS host. > Check validating IP/UDP checksums. > Try off checksum offloading on network interface > (ifconfig ifname -txcsum -rxcsum) From owner-freebsd-virtualization@freebsd.org Tue Jul 7 15:49:10 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 F11049961D3; Tue, 7 Jul 2015 15:49:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABC7A198F; Tue, 7 Jul 2015 15:49:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZCV7K-000DM1-PE; Tue, 07 Jul 2015 18:49:06 +0300 Date: Tue, 7 Jul 2015 18:49:06 +0300 From: Slawa Olhovchenkov To: Pavel Timofeev Cc: freebsd-current@freebsd.org, "freebsd-virtualization@freebsd.org" Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V Message-ID: <20150707154906.GA44094@zxy.spb.ru> References: <20150707130902.GA41189@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false 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 15:49:11 -0000 On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote: > Well, turning off checksum offloading by `ifconfig hn0 -txcsum > -rxcsum` definitely helps. > > As for tcpdump I'm not completely sure if I did it right, but I see > "bad udp cksum" phrase: > > # tcpdump -i hn0 -vvv -nn udp dst port 53 > tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture size > 262144 bytes > 18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags [none], > proto UDP (17), length 51) > 192.168.25.26.45683 > 192.168.25.3.53: [bad udp cksum 0xb39e -> > 0xf210!] 52886+ A? ya.ru. (23) > 18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags [none], > proto UDP (17), length 51) > 192.168.25.26.12575 > 192.168.25.3.53: [bad udp cksum 0xb39e -> > 0x7365!] 52886+ A? ya.ru. (23) tcpdump "bad udp cksum" is normal on FreeBSD host in case checksum offload (and may be need only for help finding issuse in code). Need wireshark capturing from MS DNS host (or from mirroring port). From owner-freebsd-virtualization@freebsd.org Wed Jul 8 07:25:54 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 35D4B9967F8 for ; Wed, 8 Jul 2015 07:25:54 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6B9741A0F for ; Wed, 8 Jul 2015 07:25:49 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA17728; Wed, 08 Jul 2015 10:25:48 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZCjjn-0007f2-PU; Wed, 08 Jul 2015 10:25:47 +0300 Message-ID: <559CD04F.4090003@FreeBSD.org> Date: Wed, 08 Jul 2015 10:25:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Neel Natu CC: "freebsd-virtualization@freebsd.org" Subject: Re: bhyve: centos 7.1 with multiple virtual processors References: <5587EE05.2020001@FreeBSD.org> <558900A7.40609@FreeBSD.org> <55891335.5090403@FreeBSD.org> In-Reply-To: <55891335.5090403@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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: Wed, 08 Jul 2015 07:25:54 -0000 On 23/06/2015 11:05, Andriy Gapon wrote: > P.S. meanwhile I found this old-ish thread that seems to describe exactly the > problem I am seeing but on real hardware: > http://thread.gmane.org/gmane.linux.kernel/1483297 An update: the problem is fixed by http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=c4288334818c81c946acb23d2319881f58c3d497 P.S. Perhaps, it's worth checking if those spurious interrupts (from PIT) are just a result of timing or if bhyve might deviate from the specifications there. -- Andriy Gapon From owner-freebsd-virtualization@freebsd.org Wed Jul 8 08:05:41 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 5FF209961A4; Wed, 8 Jul 2015 08:05:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 E679F1A3B; Wed, 8 Jul 2015 08:05:40 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wiclp1 with SMTP id lp1so72253287wic.0; Wed, 08 Jul 2015 01:05:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UK8+D7Rbcpf98O0j6X4PpC5CagaQ7+VXr3vjUWY7D8k=; b=TddoHBMkiSaUXeBij58P9i4FOSWm+S6efxv163+SINqxl+JIIEiWnz+Jdtp/iFHcJs F6dHOO2PwRPAFHlTkG+VFZ0W3NssSK8JoDEGS9+v2+zca53Frv/dnEGZkosv8ebmB5Wr yH704/N/yVcxuXznqMI1Sb7liRvE+qEtqnLucVu0V/rzPMoe0WmhCR/AE+QwACguHr+k kFzMUc6QD1AQym8I94tR3VIAglU58L67orIwcm+jwCtKLqTY+5iuDznKETcRjGEbZNRX toJbg9AN/RjmCkQg4A5baq7rNefPeJgX7mFKcZ+3xAgzX+9YqdSClBxEoujrIkPpFQuU lYcQ== MIME-Version: 1.0 X-Received: by 10.194.109.97 with SMTP id hr1mr16424107wjb.95.1436342739470; Wed, 08 Jul 2015 01:05:39 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Wed, 8 Jul 2015 01:05:39 -0700 (PDT) In-Reply-To: <20150707154906.GA44094@zxy.spb.ru> References: <20150707130902.GA41189@zxy.spb.ru> <20150707154906.GA44094@zxy.spb.ru> Date: Wed, 8 Jul 2015 11:05:39 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Slawa Olhovchenkov Cc: 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: Wed, 08 Jul 2015 08:05:41 -0000 Ok, r284746 is the root of the problem. MS DNS works under r284745 and doesn't work under r284746. Slawa, what should I look at in wireshark output? 2015-07-07 18:49 GMT+03:00 Slawa Olhovchenkov : > On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote: > >> Well, turning off checksum offloading by `ifconfig hn0 -txcsum >> -rxcsum` definitely helps. >> >> As for tcpdump I'm not completely sure if I did it right, but I see >> "bad udp cksum" phrase: >> >> # tcpdump -i hn0 -vvv -nn udp dst port 53 >> tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture size >> 262144 bytes >> 18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags [none], >> proto UDP (17), length 51) >> 192.168.25.26.45683 > 192.168.25.3.53: [bad udp cksum 0xb39e -> >> 0xf210!] 52886+ A? ya.ru. (23) >> 18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags [none], >> proto UDP (17), length 51) >> 192.168.25.26.12575 > 192.168.25.3.53: [bad udp cksum 0xb39e -> >> 0x7365!] 52886+ A? ya.ru. (23) > > tcpdump "bad udp cksum" is normal on FreeBSD host in case checksum > offload (and may be need only for help finding issuse in code). Need > wireshark capturing from MS DNS host (or from mirroring port). From owner-freebsd-virtualization@freebsd.org Wed Jul 8 08:22:30 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 8EACB99649A; Wed, 8 Jul 2015 08:22:30 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47CD2120C; Wed, 8 Jul 2015 08:22:30 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZCkca-0003Sm-Jf; Wed, 08 Jul 2015 11:22:24 +0300 Date: Wed, 8 Jul 2015 11:22:24 +0300 From: Slawa Olhovchenkov To: Pavel Timofeev Cc: freebsd-current@freebsd.org, "freebsd-virtualization@freebsd.org" Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V Message-ID: <20150708082224.GB44094@zxy.spb.ru> References: <20150707130902.GA41189@zxy.spb.ru> <20150707154906.GA44094@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false 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: Wed, 08 Jul 2015 08:22:30 -0000 On Wed, Jul 08, 2015 at 11:05:39AM +0300, Pavel Timofeev wrote: > Ok, r284746 is the root of the problem. MS DNS works under r284745 and > doesn't work under r284746. > Slawa, what should I look at in wireshark output? I think developers can want look at same packet before entering in NIC and after receiving MS DNS server. I.e. hexdump of all packet. FreeBSD's tcpdump do this by `tcpdump -X` for IPv4 payload and `tcpdump -XX` for IPv4 and Ethernet payload (wireshark by default include ethernet, for easy comparasion do same). wireshar do same by 'Export Packet Dissections' 'as plain text' with checked 'Packet Deatils - All expanded' and 'Packet Bytes'. This is will be very verbose output. > 2015-07-07 18:49 GMT+03:00 Slawa Olhovchenkov : > > On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote: > > > >> Well, turning off checksum offloading by `ifconfig hn0 -txcsum > >> -rxcsum` definitely helps. > >> > >> As for tcpdump I'm not completely sure if I did it right, but I see > >> "bad udp cksum" phrase: > >> > >> # tcpdump -i hn0 -vvv -nn udp dst port 53 > >> tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture size > >> 262144 bytes > >> 18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags [none], > >> proto UDP (17), length 51) > >> 192.168.25.26.45683 > 192.168.25.3.53: [bad udp cksum 0xb39e -> > >> 0xf210!] 52886+ A? ya.ru. (23) > >> 18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags [none], > >> proto UDP (17), length 51) > >> 192.168.25.26.12575 > 192.168.25.3.53: [bad udp cksum 0xb39e -> > >> 0x7365!] 52886+ A? ya.ru. (23) > > > > tcpdump "bad udp cksum" is normal on FreeBSD host in case checksum > > offload (and may be need only for help finding issuse in code). Need > > wireshark capturing from MS DNS host (or from mirroring port).