From owner-freebsd-virtualization@freebsd.org Wed Feb 3 13:46:24 2016 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 515D7A997AD for ; Wed, 3 Feb 2016 13:46:24 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0137.outbound.protection.outlook.com [157.56.110.137]) (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 6A18D1B31 for ; Wed, 3 Feb 2016 13:46:21 +0000 (UTC) (envelope-from decui@microsoft.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=VUYzF4UbKDotOEs4JjN0qbmrtIuCcpqo1MnQtG31qDk=; b=Zu4qeqXQdn9nBhVvRy9z+MbLa4vXi397KtLu8CAllndG/4F3pJkbtCsmrMuPMrC0PMEvjRDEA9F8Fqa/Rz7uLjv66x5oEgtfAC1+dqIssHOA3fC1uNLPN4GPjZTOXpnpJxNxeHDZ25/9UxZWmZ7CHxRDEA1g6/YijowtsBzbzV0= Received: from BLUPR0301CA0005.namprd03.prod.outlook.com (10.162.113.143) by BY2PR0301MB0694.namprd03.prod.outlook.com (10.160.63.149) with Microsoft SMTP Server (TLS) id 15.1.396.15; Wed, 3 Feb 2016 09:10:47 +0000 Received: from BY2FFO11OLC001.protection.gbl (2a01:111:f400:7c0c::148) by BLUPR0301CA0005.outlook.office365.com (2a01:111:e400:5259::15) with Microsoft SMTP Server (TLS) id 15.1.403.16 via Frontend Transport; Wed, 3 Feb 2016 09:10:47 +0000 Authentication-Results: spf=pass (sender IP is 23.103.249.84) smtp.mailfrom=microsoft.com; bugworks.com; dkim=none (message not signed) header.d=none; bugworks.com; dmarc=pass action=none header.from=microsoft.com; Received-SPF: Pass (protection.outlook.com: domain of microsoft.com designates 23.103.249.84 as permitted sender) receiver=protection.outlook.com; client-ip=23.103.249.84; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (23.103.249.84) by BY2FFO11OLC001.mail.protection.outlook.com (10.1.15.185) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Wed, 3 Feb 2016 09:10:46 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) by HKXPR3004MB0085.064d.mgd.msft.net (141.251.197.85) with Microsoft SMTP Server (TLS) id 15.1.403.10; Wed, 3 Feb 2016 09:10:09 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net ([141.251.197.88]) by HKXPR3004MB0088.064d.mgd.msft.net ([141.251.197.88]) with mapi id 15.01.0403.011; Wed, 3 Feb 2016 09:10:09 +0000 From: Dexuan Cui To: Jac Backus , "Sephe Qiao (Wicresoft)" , Kylie Liang , "'freebsd-virtualization@freebsd.org'" , BSD Integration Components for Hyper-V Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pAAABp5MAAD39gwAAxCoKAALasVEAAz7EpgAAH/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZAAANu3cAABSbQQ Date: Wed, 3 Feb 2016 09:10:09 +0000 Message-ID: References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> <1430812ff38c4e08a4b91ea25fdb5a7b@HKXPR3004MB0088.064d.mgd.msft.net> <1fdbb9b939c54e31ac00329f61bf6f41@ORTELIUS.internal.bugworks.com> <2323532a95934cdfae0142a9d6f88fd8@SG2PR3004MB0090.064d.mgd.msft.net> <2b22a9544c6c4ff3b017133a346e75e2@SG2PR3004MB0090.064d.mgd.msft.net> <7df41cc958ee408297487d4ffbb91903@HKXPR3004MB0088.064d.mgd.msft.net> <4e85ad234a0b4618ae5862fbcd266e3d@ORTELIUS.internal.bugworks.com> <0f761afc10864ad3aeb89ee7c9b6e8ac@HKXPR3004MB0088.064d.mgd.msft.net> <4105829efb1e4b3a91bc17f7fbdf8ac8@HKXPR3004MB0088.064d.mgd.msft.net> <0ce04bf413204478b1e7cc71ac28ecac@ORTELIUS.internal.bugworks.com> <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> <4a98b41221ed4c3b84a8c733aa23f24d@HKXPR3004MB0088.064d.mgd.msft.net> <5a09277abe094f5989fb145c12a511df@ORTELIUS.internal.bugworks.com> <17b639f383df4f42b1e050f6e40d1ad2@HKXPR3004MB0088.064d.mgd.msft.net> In-Reply-To: <17b639f383df4f42b1e050f6e40d1ad2@HKXPR3004MB0088.064d.mgd.msft.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [141.251.56.69] X-MS-Office365-Filtering-Correlation-Id: 3ed00858-8405-4a50-0540-08d32c79e719 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11OLC001; 1:/yjtJheu9G/TEmHM7uDVHekqNJ2S0BmRXiRE/HKjdy8iOFIPVYgyUw84j5mwIHD+reemlMIwY/bUwK9KnXjnAi1EVBdZmQYXbXQ0hsGEEq4A2U4Qtm7hnDR4CxlkuI76dJpEQPTGEAoWK7bRNxwcFJPRhPSzDV0vORF8s24WGTPtxB3olRauorIq+WeHCyrhDczJBWYUd5FguCv2uAgjuyx+aNqfq49LON/TIW7h6G2SqQWf45Debs/sCiTzxOrYnq2PoGYlT7eb6awoJAX64BFK9Y0iME9g/C5JBrq782/YP1S2sj3UxYTZAhTI6xVWAjFzhMADrpDYxIMRXDGSpQ== X-Forefront-Antispam-Report: =?us-ascii?Q?CIP:23.103.249.84; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(100190?= =?us-ascii?Q?20)(2980300002)(438002)(377454003)(71364002)(51914003)(39050?= =?us-ascii?Q?03)(13464003)(164054003)(199003)(189002)(24736003)(6806005)(?= =?us-ascii?Q?3846002)(18206015028)(19625215002)(15975445007)(102836003)(2?= =?us-ascii?Q?60700001)(87936001)(6116002)(790700001)(586003)(19300405004)?= =?us-ascii?Q?(2950100001)(92566002)(33646002)(16796002)(2900100001)(25610?= =?us-ascii?Q?02)(1220700001)(5008740100001)(1096002)(108616004)(76176999)?= =?us-ascii?Q?(107886002)(300700001)(1511001)(3900700001)(5001960100002)(1?= =?us-ascii?Q?89998001)(16236675004)(11100500001)(86146001)(93886004)(6606?= =?us-ascii?Q?6001)(512954002)(50986999)(54356999)(66926002)(19617315012)(?= =?us-ascii?Q?84326002)(5005710100001)(5003600100002)(10400500002)(5004730?= =?us-ascii?Q?100002)(19580395003)(2421001)(575784001)(2906002)(99936001)(?= =?us-ascii?Q?67866002)(5001770100001)(86362001)(19580405001)(400145010000?= =?us-ascii?Q?2)(106466001)(17760045003)(10290500002)(10090500001)(1962759?= =?us-ascii?Q?5001)(7099028)(491001)(559001)(579004)(562774006);DIR:OUT;SF?= =?us-ascii?Q?P:1102;SCL:1;SRVR:BY2PR0301MB0694;H:064-smtp-out.microsoft.c?= =?us-ascii?Q?om;FPR:;SPF:Pass;MLV:sfv;A:1;MX:1;LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB0694; 2:hVfqOxGfrnUlTBFaypPeAmmgcJmmTt+aXhcMk/N0fbCjrDgxbeR2ZR/gPZeHqaV53cszerD/FxaGoPeVCRd9JRcK4f19K8xN/TFEJC9RPOPacTqIEYQuuzCjw/ps64QOrHMkek3W0b+W1wFlP8+6qcmx3h4OuCiZuYC0BtdCdyhvSqssbPx0Lo67HSPG0q4c; 3:DqHT5OR7ixN7BOT/XjamaAOEW+SfMk40p41ymO6kNS7EloV+xScTvjJGAQYOLtsh0SLcTr6FpQMizAL6teEUxlwmAgkEQz7GKOd3ZwN8ikCiwMk+rFFfIyRJxgSag0YenHuRd6d/LuNnHo7hs6TYiHzUlobNWWvQKV7C9wrGz+JcjdzX0Lgj7kPQPKOCNDTSWxxvscEoXNnxkTbJvrabShZsYbEKSSG5T9iZWlfv0UGQH6LQg0GJ1lInw5QQ7Fi926jp5DyBvHynNl9B84D/Pg==; 25:lJF3vBIY0GxtpyOFsP7m2Fvvs9OOiPNg40WtXSrFt2swjtvtS7mZsYTH7J9oFWoqOO4uwvRL4ehfg0O+QCrc6mNCZV7JBJvb5579hvkjF7n9msEDqCEk6BrIBl+Ift6dWm0Hw1nLVyIe0NAU/JHhP0HRjmgoaHBjbsKkG2/fWGW/OksJZnl47y7GLDpC4J+9VTm7dvmn2ubZp6jZQEL5KwrXoBYaPU1ETNbXCiFL+DdwVqpFNT5RmJhXmmAOn7dCP69Awoqf6A1FFLDsyJNEu9tiW7hNbod66xrp2A29uMM= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BY2PR0301MB0694; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB0694; 20:gGcwqUo9wH5g14EYnG993LXos+uIj97tUaIgel+xuJl3Ef+GhqhnQRQt7SIebGhLePwE6GNn15CQZgJATWC1zgpsqMALhyjDA9HiE35RNHszKUoz4h2E4kbgwbhlvDZBAEYTDJ+sgjd2lyXY3lMGtcRFAiG3OCQW1XR/Ahf7Mf1Ei2XFh0Ot8vas507+GGjLP1Ykf9CAIoT0E0voZNIWm8byMzNl535/HuolQ4ft4m8cofF+EHWuo9XniD/5jvMj7AgZZiV09CFcnFXnxow+F5wizDnAtBaKoVTGIram3n1qwAnKVSrea+cSMDz/5s/Ltdk/PUCzRhiiUhaLEpMnkzY5kswTvgSL12gtVopwM1nvmRN3+OVKzckrnVMVbSMzJJMmd0WmRNXH55yPZ1FFNNE5exf91AAG9HS2Tm/kg8T0FnHDqSY5zJ4IQx2EF7ygNpbwluxN4EfBg/ME2vo7plPs7uGEW9iDJA/Pwmz3w5AqaoTyxQwKHIG7M6KdV9v3IQJ+M+6BiCkPLDUsBidiTYfAUK7KUwzcnVx+hgMuAWalhH/leFWwM5I5bXhnErzkLT5oXtwBbcdM7Lifhpv6r0RGVQHHstVEoqS9WUEkX08= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(102415267)(61425038)(102615245)(601004)(2401047)(8121501046)(13016025)(13018025)(5005006)(10201501046)(3002001)(61426038)(61427038); SRVR:BY2PR0301MB0694; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0301MB0694; X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB0694; 4:tRbZ2+2vhN7Z3zbwP7aoTaRzqtG9ev4CvTd+JVsSXUWk8TzYsjSW3Qpin0pbDJWjr0bDFYbughewOtwQgLN0/I0pXjK/PjDcvFKo69ic3HHsAQGuTmflpM6D66oF/w2fNw34O5m7J0Hif/3USMdB/1v6IPU8/rQRxknCS5FK9veydgwP9PHoMm8UPMX9J50rubTuhSnbGf9VU8EeLpWejlaP2ZVM8QTW3NWFYn0RV1rAGfNTTr4uieAuPMmyukShzW5rjWzpAV9bVGJSL99UBlcEzWfkUy1GSr/4hAMdR+KofH28XDDRd8UCkS715Ed/OMM0X+aLCrTpKMQ75wfxhd10xT6UjjHG+akQS7Z4TmsPxQYglB8j09pSH7lYUwaOnOushZSHEzACFsIRp7Z/NV+iTdgeBbDAzOVT1XeMBrFcz0fDo2YW5sNkZdveit849oNMnKwpaw1hfssz2wLwF18zivirHut+fsJtL4JQprkTZakloGuIEK/Jod5ApK3e X-Forefront-PRVS: 08417837C5 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY2PR0301MB0694; 23:QxmaVs0TX4B1x+k/JmnVIRadvJusB/AjdpEo5tV?= =?us-ascii?Q?XfdlYUshvXrzo+gB9JNTmTp5X5yeUqcGBFe7X8/NtUrMbg32N5hFY8cRZiZ/?= =?us-ascii?Q?vTnb66/L7VETLDwhPfZAnKcmWVI4j/2X2LjIh+AMHovZDXfUOigj6bXo3mR2?= =?us-ascii?Q?c28bKjP25QnE9XUBvVh4HzMc8UVRUoj0thORw8g3DSOH7Gw3VjXnh4zwFSbz?= =?us-ascii?Q?o9qncCWz8y6hxPxRQ3THS9j77RbwWuWVW4JMG8FHogz7lIS8kNo3ASZUD64H?= =?us-ascii?Q?EpzSMvo65O5GowVbi22uicNnZcc5IVgHHZVW/fuCLj36kMIkXF2vb3VZrUBY?= =?us-ascii?Q?P1TfHDCdsn/A+KbkeNEIHCeW2/h5Pt5W88/9S61CGyessGoMDpVAHyfDqmXB?= =?us-ascii?Q?qD619H52hYu0wrdtB/AWlOqN7ORihSZ9diJxQdsSiJDnuO+9LMvlbQqeJwjI?= =?us-ascii?Q?WwyTzWxtmvW1ATwn6EaI1xryvB3AklgaQTXl0muhDMYhtGeLYApnMG79NNV2?= =?us-ascii?Q?Uh/5XhYMhmLZUIe6swwgcy4K/erF9hLiVbd4SS4Ewn7TIe+7qq+4Snm+bxO5?= =?us-ascii?Q?spi2qsGInmNARvtvfvGsZeS+kD8KqMogypNh8gkEj/duIds1o6N2o5H+yIge?= =?us-ascii?Q?pUeIroClkfzE5yfihArHLl5WnHSHxQPqj0rNAGzWuGZf8Zndoloo1mjUBbRK?= =?us-ascii?Q?NwARQueYD5FIwAs2so9ZXuAkY8z0W104rpY7txKok/TfLx4kxEeFiY/BRN1n?= =?us-ascii?Q?MAdV5h0KOYg4nMaRPw/FKlvFPA5d9MlOZMA4fpRLHFaJqqnFMuQyBXAQgyd1?= =?us-ascii?Q?u7qb3a6UQgELzdkxZpVFrKfPImNTNEqsTUZPMT8vhAnIR1hETDNZ1G8eb2rI?= =?us-ascii?Q?OGSxSS3X9VdaOOSbF2tOyGRQ1MthLE6wehvqgtmuwhAoCEp5loIkei2GA6K7?= =?us-ascii?Q?wzE8YPYYx4MlBmXclf+o89O7SZamovJoModw8DkSFDv7j9Bwm3HbFwXWWKjU?= =?us-ascii?Q?lsgxodK4XXAov6ssfCaPuMUGyIzRSz3jMHbuyOfhrZLk+S4KKpzB7SR6IDlI?= =?us-ascii?Q?3d8joC2YrXNmbsJQ9gXa4q/NbtSEp/+Us5vKs6tWw85UtorUcVCqcVxlHcBU?= =?us-ascii?Q?iSFsdpHaW6R9KcCLPUxEZ3ukowTcGKRHiLn+fid+s10L50dwzFns/BRyd2l4?= =?us-ascii?Q?rzE5SH4/GVULfkzDP1ZlFJRy9O8oedR/Pt5W5p6El/t6sfcX1Pe1kAaV50Hi?= =?us-ascii?Q?oy5Uh11irn/qNFDFU4N60khECMJorzwr7rAzK3TcVW5T6e6reFtK1wxzrA1t?= =?us-ascii?Q?crrgAPeIoofhni+t4KoRAYIMdy/cVzdpFEi1Jz5EHeCKEJTJmSqUHaP+tUvh?= =?us-ascii?Q?Jtd4uizs2OlZTOj5lR/YMfSndC4h16kwDmOd4TJgAJz9UW0xn72V5xwxkdrq?= =?us-ascii?Q?LjzITIiqMN7kR1SyVDg7ia7VZ47JPQfg0VdycRpdaUBuTVqb+LFPUyxbtGju?= =?us-ascii?Q?Qs+frJt9Vd26pP9v1lfx0wTZkhUBObRmFUUb06aHP+b3p3+JnS8ifhlvsdns?= =?us-ascii?Q?IE6zITwqLx8txmTnNdDNVIu4wpFmXHeOBqKsXY2oGYH7tmFFBgginhYjhV8V?= =?us-ascii?Q?+aDbKjFb2UCbnFtm91sR262nykvt96wCrnnkgQIjcOOrBZcbVPnupblIXKby?= =?us-ascii?Q?CL7egjwHvOEPuzpKSfAg2fr8RnAibF3rfy97tdCPhAVRZrw8/SgNo+nXlPAl?= =?us-ascii?Q?TbTl0YuFjiWpo+szLE341VmecNhRQEs1B3ysutoRwzky+Vfzt4INIc1LO2mO?= =?us-ascii?Q?q0G7BWXsfKQUX+31ML6cwGgHkI+HvuUZgWIX14SB/nrY9d5rBpCD9ZIUU5Io?= =?us-ascii?Q?+REiq8srXhLM0yKCWYaMAM8n77VyaDBDyBhGjQfno5mFzy80O3iz3xurZUvk?= =?us-ascii?Q?=3D?= X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB0694; 5:pXnoDnf9ZUXq9cgrwZvBtUlvzpKM/vPOwTxrLx6EOwosKvlYjub0Km3Hv/1FO+czo6nAYKKoMyN6ioQz1dDdQD0SfDoENWnH+JempCfMF7hdlp5cSCirHytUb89oFr0y4WYekK9Aig8gQXjzKILl0w==; 24:HeUqe3/mLLqNcPtqSwLl/sK+D7KsJyUVbDpooUIblKLsa6DpBUwGpMvB3dbHtkIiMySIqt7ew4mvkxX7ScBfEgFFAFYiDALNwq9mmhQ/ivw= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2016 09:10:46.6249 (UTC) X-MS-Exchange-CrossTenant-Id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=72f988bf-86f1-41af-91ab-2d7cd011db47; Ip=[23.103.249.84]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0301MB0694 X-Mailman-Approved-At: Wed, 03 Feb 2016 16:07:22 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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, 03 Feb 2016 13:46:24 -0000 Or, you can just use the 10/stable branch, which has included the fixes for= this issue: git clone git@github.com:freebsd/freebsd.git cd freebsd git checkout -b local/stable/10 origin/stable/10 make buildkernel KERNCONF=3DGENERIC -j8 make installkernel reboot Thanks, -- Dexuan From: Dexuan Cui Sent: Wednesday, February 3, 2016 17:05 To: Jac Backus ; Sephe Qiao (Wicresoft) ; Kylie Liang ; 'freebsd-virtualization@f= reebsd.org' ; BSD Integration Component= s for Hyper-V Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Thanks for the confirmation, Jac. I might be wrong with 10.1 - it may not have the issue. In 10.2 we made a lot of changes and I think the race condition was introdu= ced. To test the 2 patches, you can do something like cd /usr/src (supposing the 10.2 kernel code is in the sys/ sub-directory) wget https://github.com/freebsd/freebsd/commit/850d0994e48b0ef68d33875e2632= 6d44931fcf1e.patch patch -sp1 < 850d0994e48b0ef68d33875e26326d44931fcf1e.patch wget https://github.com/freebsd/freebsd/commit/1e469c559048fe6ec3641da3bb21= ab87215c6506.patch patch -sp1 < 1e469c559048fe6ec3641da3bb21ab87215c6506.patch make buildkernel KERNCONF=3DGENERIC -j8 make installkernel reboot You may get a small issue when applying the second patch as I did: 1 out of 8 hunks failed--saving rejects to sys/dev/hyperv/vmbus/hv_channel_= mgmt.c.rej You can fix this by checking the .patch/.c files and manually editing the .= c file. Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Wednesday, February 3, 2016 16:10 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Good day Dexuan, I think it is. I should like to test. Are there some instructions for patching the 10.2 ke= rnel source? You mention 10.1 too, but I never had the problem with 10.1. Thanks very for your kind help! With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: woensdag 3 februari 2016 1:50 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Jac, really great news! So, can I think the whole issue in your side is caused by Bug 205156? The fix to the bug has been in the 10/stable branch and should be in the co= ming 10.3. For 10.1 and 10.2 , I'm afraid you'll have to manually apply the patches an= d build a new kernel. BTW, the bug is actually a race condition when the netvsc driver registers = multiple NIC devices, so sometimes we can easily repro the issue and someti= mes we can't. Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Wednesday, February 3, 2016 2:28 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Dexuan, you are briljant! That is the problem: Hn0 has the mac address of hn1, hn1 of hn2 and hn2 of = hn0. So they have shifted one position to the left. With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: maandag 1 februari 2016 10:41 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hmm, it's really strange... what's the difference between your existing 10.= 1 VM and a fresh 10.1 VM... :( BTW, please check if you are seeing this bug (it looks in your side the ne= twork can stop working after a VM reboot): Bug 205156 - [Hyper-V] NICs' (hn0, hn1) MAC addresses can appear in an unce= rtain way across reboot (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id= =3D205156)? Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Monday, February 1, 2016 17:17 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Good day Dexuan, I did. Unfortunately, no difference. And at the moment the server is running on the 10.2 kernel: uname -a FreeBSD roadrunner.acme.inc 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu= Jan 14 01:32:46 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/u= sr/src/sys/GENERIC amd64 But there is a big chance, that after a reboot, the network is gone again. I will see if, when it works, it keeps working. I suppose it does. With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: maandag 1 februari 2016 3:07 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, Good to know this! It looks to me something in the VM or in the host might be causing the issu= e??? Can you please do another quick test: shut down the "buggy" VM and remove i= t in Hyper-V Manager (this will keep the .vhdx image) and then re-create th= e VM with the .vhdx image? Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Sunday, January 31, 2016 23:21 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, I did a fresh install of a 10.1 VM and upgraded it to 10.2. Is looks like i= t works well. With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: zondag 31 januari 2016 7:07 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, Good to know the information. Since I can't repro the issue, it's difficult for me to debug it. :( I'm guessing if it would help if you use a permanent ARP entry in the VM ("= arp -s hostname ether_addr") for the other end - surely this is only for de= bug purpose. During the VM boot-up, can you keep pinging the VM from the other host. I m= ean: it looks the NIC never works since it becomes UP in the VM? BTW, I'm not sure if it's easy for you to do the same test as mine, i.e., d= o a fresh installation of 10.1 VM and upgrade it to 10.2. @Sephe, any idea? Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Sunday, January 31, 2016 3:42 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Good day Dexuan, There is something wrong with getting mac addresses for host on the lan, it= seems. When I ping the 10.2 server from a host on the net, I see on that host arp= requests (Wireshark: who has ... Tell ...) for the 10.2 server. Arp -a on the 10.2 server itself says for the non-server entries ?
at (imcomplete) on hn0 expired [ethernet] Tcpdump on the 10.2 server only shows arp requests: ARP, Request who-has ... tell ... Does this help? With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: vrijdag 29 januari 2016 9:59 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hmm, it's strange we can't repro. I suppose you can't ping the netgate VM (or machine) 's IP address either? = When this happens, can you check the arp table in both sides? Can you please run tcpdump in the VM and in the gateway to diagnose the iss= ue? Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Friday, January 29, 2016 15:36 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, That remarkable. My uname -a is indentical. I can ping local interfaces. Ping to other addresses in local subnet gives:= Ping: sendto: Host is down. Ping to other addresses gives: Ping: sendto: N= o route to host. Routing tables (netstat -rn) for both versions look the same. Is there something I can test? With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: vrijdag 29 januari 2016 4:25 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, I installed a 10.1 VM with FreeBSD-10.1-RELEASE-amd64-dvd1.iso and upgraded= it to 10.2 by running "freebsd-update upgrade -r 10.2-RELEASE". Everything worked just fine. With the new kernel (see the below), ssh and s= cp still works fine for me. # uname -a FreeBSD bsd101 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32= :46 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GE= NERIC amd64 What's the specific symptom for "networking does not work anymore" in your = side(upgrading from 10.1 to 10.2)? Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Wednesday, January 27, 2016 17:35 To: Dexuan Cui >; Sephe Qia= o (Wicresoft) >; Kyli= e Liang >; 'freebsd-virtu= alization@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, Unfortunetely, no OACTIVE flag: hn0: flags=3D8843 metric 0 mtu 1500 options=3D31b With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: woensdag 27 januari 2016 4:09 Aan: Sephe Qiao (Wicresoft); Jac Backus; Kylie Liang; 'freebsd-virtualizati= on@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, Please show 'ifconfig -a' when the issue happens (when you upgrade 10.1 fro= m 10.2). We suspect it may be a known OACTIVE issue and "ifconfig -a' can confirm th= is, the output has the string "OACTIVE". It looks somehow the issue doesn't happen when we use a 10.2 fresh installa= tion. Thanks, -- Dexuan From: Sephe Qiao (Wicresoft) Sent: Wednesday, January 27, 2016 9:13 To: Jac Backus >; Dexua= n Cui >; Kylie Liang >; 'freebsd-virtualization@free= bsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Oh, please ignore this, I think its solved :) From: Sephe Qiao (Wicresoft) Sent: Wednesday, January 27, 2016 9:10 AM To: Jac Backus >; Dexua= n Cui >; Kylie Liang >; 'freebsd-virtualization@free= bsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, What's the output of 'ifconfig -a' when this happened? Thanks, sephe From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Tuesday, January 26, 2016 6:37 PM To: Dexuan Cui >; Kylie Lia= ng >; 'freebsd-virtualiza= tion@freebsd.org' >; BSD Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, It seems, it is not completely correct, although the effect is as if it is = not working. Systat -ifstat 1 shows this: [cid:image001.png@01D159DA.65A3A0E0] So something is happening. But I can not reach anything. And the server can= not be reached from the lan (hn0) or internet (hn1 and hn2). I get a firewall message in /var/log/messages (first message from 11:18:55)= : [cid:image002.png@01D159DA.65A3A0E0] But this is just caused by the problem? If I can help with further information, please let me know. Regarding Bug 187006, all interfaces have fixed addresses. With kind regards, Jac -----Oorspronkelijk bericht----- Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: dinsdag 26 januari 2016 7:55 Aan: Kylie Liang; Jac Backus; 'freebsd-virtualization@freebsd.org'; BSD Int= egration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, BTW, what do you mean by saying "networking does not work anymore" -- can = you please check if your issue is the same as Bug 187006 - [hyper-v] dynamic address (dhcp) obtaining doesn't work on HYP= ER-V OS 2012 R2 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187006 ? Thanks, -- Dexuan > -----Original Message----- > From: Dexuan Cui > Sent: Tuesday, January 26, 2016 14:49 > To: Kylie Liang >; Jac = Backus > >; 'freebsd-virtualiz= ation@freebsd.org' > >; BSD Integration Components for > Hyper-V > > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 > > Hi Jac, > Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso"). > > The message " hn0: unknown status 1073872902 received" should be an > unnecessary warning only. > My 10.2 VM can work fine even if I see the message too. > > Can you please install a 10.2 VM from the 10.2 .ISO file directly as I > did and see if it works for you? > > I guess we never tried upgrading 10.1 from 10.2. > Can you please list the steps how you did the upgrading? We'll try the > same steps. > > Thanks, > -- Dexuan > > > -----Original Message----- > > From: Kylie Liang > > Sent: Tuesday, January 26, 2016 8:01 > > To: Jac Backus >; '= freebsd- > virtualization@freebsd.org' > > >; BSD Integration Components for > > Hyper- > V > > > > > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 > > > > Hi Jac, > > > > Thank you for asking. To isolate your issue, could you please try > > disabling SO > on > > your 10.2 system first? Thank you. > > > > And I would like to confirm with you > > 1) You met issue for 10.2 kernel + 10.2 system > > 2) No issue for 10.1 kernel + 10.1 system > > 3) No issue for 10.1 kernel + 10.2 system > > > > Right? And add our engineers in the list. > > > > Thanks, > > Kylie Liang > > > > -----Original Message----- > > From: owner-freebsd-virtualization@freebsd.org > > [mailto:owner-freebsd- virtualization@freebsd.org] On Behalf Of Jac > > Backus > > Sent: Tuesday, January 26, 2016 5:56 AM > > To: 'freebsd-virtualization@freebsd.org' > > > > > Subject: Hyper-V networking: problem after upgrade to 10.2 > > > > Dear reader, > > > > Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a > > full > patched > > Windows Server 2012 R2 x64 version. > > > > After the update, networking does not work anymore. > > > > In /var/log/messages is this: > > > > Jan 25 21:02:01 mercurius kernel: hn0: > > on > > vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: unknown > > status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: hv > > send offload request succeeded Jan 25 21:02:01 mercurius kernel: hn0: U= sing defaults for TSO: > > 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn0: Ethernet address: > > 00:15:5d:ac:11:08 Jan 25 21:02:01 mercurius kernel: hn1: > Network > > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown > > Interface> status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown > > status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send > > offload request succeeded Jan 25 21:02:01 mercurius kernel: hn1: > > Using defaults for > TSO: > > 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn1: Ethernet address: > > 00:15:5d:ac:11:09 Jan 25 21:02:01 mercurius kernel: hn2: > Network > > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown > > Interface> status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown > > status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send > > offload request succeeded Jan 25 21:02:01 mercurius kernel: hn2: > > Using defaults for > TSO: > > 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn2: Ethernet address: > > 00:15:5d:ac:11:07 > > > > It worked fine with the 10.1 kernel, and when I boot this kernel, it wo= rks again: > > > > Jan 25 22:20:02 mercurius kernel: hn0: > > on > > vmbus0 Jan 25 22:20:02 mercurius kernel: hn0: Ethernet address: > > 00:15:5d:ac:11:07 Jan 25 22:20:02 mercurius kernel: hn1: > Network > > Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet ad= dress: > > 00:15:5d:ac:11:08 Jan 25 22:20:02 mercurius kernel: hn2: > Network > > Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn2: Ethernet ad= dress: > > 00:15:5d:ac:11:09 > > > > So I am running a 10.2 system on a 10.1 kernel at the moment. > > > > I found nothing in /usr/src/UPDATING and not really anything on the net= . > > > > So, could you tell why does this happen, and how can I solve this? > > > > Thanks for the help! > > > > With kind regards, > > > > Jac Backus > > > > > > > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list > > > https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%2flists > .freebs > > d.org%2fmailman%2flistinfo%2ffreebsd- > > > virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2e > > > 0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1&s > > data=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d > > To unsubscribe, send any mail to "freebsd-virtualization- > > unsubscribe@freebsd.org"