From owner-freebsd-virtualization@freebsd.org Wed Feb 3 00:50:29 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 3400EA9A52F for ; Wed, 3 Feb 2016 00:50:29 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0138.outbound.protection.outlook.com [157.56.111.138]) (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 0BB2A13CC for ; Wed, 3 Feb 2016 00:50:27 +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=BcNEd+5UxkEGGw465tniUhw9Jibgcxw6f3Xb2aMUaUw=; b=OaleLUZQsBDnLOxVepGVp6JjLhyaXFkZHDmAZzoGWKEN/mYl/skk9YepcNu6rFF22mLDVmBPOxtyF8QDvJlk5eRl/NYt5/TQHiK+MNB5Tko04wzBApt0B4F9GU3DBCuEqqmhoSI+2zGXj/L6QlqQNUO0V2VLrrdCznyF9U+kXW0= Received: from BY2PR03CA006.namprd03.prod.outlook.com (10.255.93.23) by BL2PR03MB100.namprd03.prod.outlook.com (10.255.230.25) with Microsoft SMTP Server (TLS) id 15.1.396.15; Wed, 3 Feb 2016 00:50:22 +0000 Received: from BN1AFFO11FD034.protection.gbl (10.255.93.4) by BY2PR03CA006.outlook.office365.com (10.255.93.23) with Microsoft SMTP Server (TLS) id 15.1.403.16 via Frontend Transport; Wed, 3 Feb 2016 00:50:22 +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 BN1AFFO11FD034.mail.protection.outlook.com (10.58.52.158) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Wed, 3 Feb 2016 00:50:20 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) by HKXPR3004MB0087.064d.mgd.msft.net (141.251.197.87) with Microsoft SMTP Server (TLS) id 15.1.403.10; Wed, 3 Feb 2016 00:50:17 +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 00:50:17 +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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNA Date: Wed, 3 Feb 2016 00:50:17 +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> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [112.65.1.254] X-MS-Office365-Filtering-Correlation-Id: 46317db5-e495-4c3b-e231-08d32c33fe87 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD034; 1:QRHMIumCrLSLg9s+AU66/RKr8tDPKv+9eF+TW/LDF6xyOsZ9mZYi9raAqNQCt0h/d60L8htd+gPCaKMotxeomu3Y6zUw80/6l7uEA+5eUdgwwvOhDbJ/ldV9Vkm7xcy0gBo4lh+g2CpCZGLiv/6yUD/RB6nzZTuTiteB3Uqg0ICN3CygvMY2rBOnK+KNznrNtXv73r68sb/gqzm4DGz7SFE5h/c+VsO4MA1mD3WD2Ag+9nMbmJL3eK48u8N3O7lRruo2UvjpOr4a4oYD1lLnDGGcJm17q0du9Fb48jnWSPr6wRW2zPAlNvYiX16NQ8OOY1JR6BGbPbWgsUOYjnPibw== X-Forefront-Antispam-Report: CIP:23.103.249.84; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(2980300002)(438002)(51914003)(199003)(13464003)(71364002)(377454003)(3905003)(189002)(164054003)(10400500002)(33646002)(10290500002)(19300405004)(84326002)(67866002)(93886004)(2421001)(15975445007)(2561002)(575784001)(19580405001)(106466001)(86362001)(11100500001)(5008740100001)(16796002)(108616004)(19580395003)(5005710100001)(19617315012)(5001770100001)(107886002)(2950100001)(2900100001)(5001960100002)(16236675004)(54356999)(17760045003)(18206015028)(66926002)(99936001)(50986999)(24736003)(6806005)(76176999)(102836003)(586003)(300700001)(1220700001)(10090500001)(6116002)(1096002)(790700001)(19627595001)(19625215002)(189998001)(87936001)(66066001)(4001450100002)(86146001)(5003600100002)(92566002)(260700001)(2906002)(512954002)(3846002)(7099028)(579004)(559001)(562774006); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR03MB100; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; MLV:sfv; A:1; MX:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB100; 2://HhQ8e9SjRos9poDSrCbrbfFYhX04uaLIBPzsSvNZJprsOSVAiS7C/mXPhGmtO9B5Bi1ZZ27yErZOss9dA4f2Ppp2JVS0LOPHb6QBeezJM++nPMVj5rbhmb7mOipTZBoFk5hGAA7TYpkDBp2ILdlQXud7+rtoVmrMZ09Yh3PHI68B+vp4b8GCrmVsH0Rd4x; 3:fejhM9Tspq2rYAqr1f6vVS5kf+xwTth5yMx8UZ4ZNl7md2XOwKLAO+TApkQc+JeIyQUvRVsLU2i8s25B0QFRkqVwIjscOSdEjwDUJeEr4/KLucrYLnaC73XSQeswKFPeX2HiQhX8BQwB8bMMsdcJxBvMgwZMKjEHUUqNhCKIax2LNI/vnm1tApN3eH0xWo6HuRuTG2r4EO8GGyaaHg09pxZBVpDbbbpdU4GdHRCVV/V5mU+DboiWSTZVrfoGiD1REe89iuB6v7Q5VeU20TOHvQ==; 25:9nE2uK7ENd9APXxR2UEDgjYydkX1rRg8ePixHV5A2H7YJZhdCrQh55kJXc9cO3FqSw1g7xBEBcF7D6pWwMKvDgl+4BuGe7yjyFritQ5/sM1x4kKuAQ9uFkW49WFykwios+d9Mc7+ZJcoR5kYhKMP4vpay5UObMjzaDQ3R4JpLMNgdvy3lu6rui2OFYKWCOzC7J0e5tz99A9Zwq+m+PpPjhNwPpcgCzLdLZWfmWvAkGrlkgSIX4yB6Evim9xpEiCLAJoCUuRFp25JiGvKLaKbnpuXKs9TDC8HL9WHOtv0DMw= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BL2PR03MB100; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB100; 20:D+yjKUWoW0NUmNe1WXzFB2KmvqJ5RN0QzXnaDzPr8YYGk9kt1Tnug/7LGb+/gMMssOWySl3V+KUYh86JM4/KmxLRgAyx3+EfU9zslI2Gvr3wzo0r6JqTBxIex6XLslIB7X8H0HfWsd7D3ubP0a+/j8Df8is8mGFfqfzZrnvgDtWSZ3kLIPui46QSQZKS8Ok/TAzecs3DE6v3n/YpJ1W6Ikh/ZBkRFzkegWgnhJhWr9FN9lYaqKmlIDEszm/JUhYo0x8psbCWgVxfNsDBHKLSJAbRmiijchLlwvF9SDNC4Z/IcR5FjXi5FgO/TLy13UY2TPHyiYjxAlWJmMVwnnIZNhU4xDv7GoEQ+KEMoEsyQtB2Dq0heu3plTmau7mskukT5R9KXdmOeVMoGTh24D9OR2T5cJOM8OHqLWNU7dY7hksifqhNGMnitmZT1jqnzFGHmOJEb3rnIlkUalP8l6aRLAa3jTzNs4hTjgkrMx8VHEYhQ48e8N/SwpUbYMKtKB2jL4huM2AWRvrfLVCsYXl2CXCscs9HlCZyrP7M8CWWi3H4MqHrSjXV8DH7BAXwD+n3nx0V7+WF7Gyh7ttIh62K25soB4HWPV60wloouetWLDk= 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)(5005006)(13018025)(8121501046)(13016025)(3002001)(10201501046)(61426038)(61427038); SRVR:BL2PR03MB100; BCL:0; PCL:0; RULEID:; SRVR:BL2PR03MB100; X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB100; 4:PlraO9XSkvwE88d62+affGMNnd3Lk+JnBBMoJcn0IIJ9ujKJ1TqecWdUd2uem6J2MLVAqmDb9uulDAe9OsPSZC8fHej3x+Bp+ORa5KUc8XM3HMTpPnh8P2HkimhQh67PHZDxkXkHrIgGzlhV5sKvvtqEiaibMeX2J3czOzkzG1ncc22lKYANWhTmlIXa4l0Phauswh1p1LUaZY6MA1L/ETpqz1im+AztGPsz6EFU6i/CK2Ng1BCqt952JJVlB0wax6JDy5HpZ3pvnnvOLb1AwGiN2UnrkOa+wZniCFMlGgoaWLrvLUsar7zU+oeWfkx5HwYlzB+0G4dl2e5PlmtkG95/dvxu7DHgBoW2lyVGx6rEjkAiFP0HraVH6vgdhPlR+q35Xq9aaVp53kh+eUkP/1eQP9Gj/i3Z4Z87oHOBVtCupXtA3LvQaj17r5knPExZ4vawxYhvkeoeLsiNInfUPWLfZN+hHg2DwMc77bgJElItNwVFMxhDY7DMo/ImQ+RwrqxZLVoDuwuOi1AponuCww== X-Forefront-PRVS: 08417837C5 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BL2PR03MB100; 23:VyChM5k46p2Irx5Ko1wxuIADwaD9CqnOr8lTw3ahlo?= =?us-ascii?Q?UWCEIeOzi1dxPJRl5pSReS1C+4MQ1BokE2BJYWwU+5Pu/YLIoZZKeZkOb3Wh?= =?us-ascii?Q?3QIV0GX06H0WnSc1byTWEGoP69XFoqhdcBL5AyN/VR0d7DuN3GTaqYVnztF2?= =?us-ascii?Q?+QozoDO2K0Z9vhJeJi8Dw0hjrCtSxJLMoP8S7h6Hv02a2jYxtj15Rc/ws5fw?= =?us-ascii?Q?fj8g3BhLev5Vw+bNavz0yBQo+k48LeoCTEktIu65aQLxb5B+i8ZCW8DaKRVw?= =?us-ascii?Q?ZQ8X0UjXOh5q3PIxI9Ce93QwrwKPdATmm9UWuYM1vJLLNMtzxDhviM0M6Mj1?= =?us-ascii?Q?e5OOUrB9nsxavl4PE+yA8jHm4GudMuZqVKXbdyQwbbrmsq1hYQNuBylsZM+L?= =?us-ascii?Q?lh4EqVbhBqx/wfjVImLKeITiJ0EGz7qinDvXIOkjA1Ujik+oUwNQ4ztzLJhQ?= =?us-ascii?Q?cdvRwpN2/pjbPsPsTq8fD50A1bJJwWREIPMG4cMR2HQoDKa+CYA5E7vplv1B?= =?us-ascii?Q?BYBoRPkqrA+nNYpuPuCfGlGIKcUqZGfOupEB/S5H9+M5Hqbk+1aAKCtO1l0R?= =?us-ascii?Q?Tc9On9bMKbV1nzLON6EYMEZ847mOizcpz0DIF4mmvkCwXcGPeQVU7b2Xgg9b?= =?us-ascii?Q?j70emDPsWfoNPZd2MHj91B0/dEI/EXYh1v/wrrBToe1BNLHms8dzAk4h4gR4?= =?us-ascii?Q?oOndstJbyHy0j1tLn5lkpOKTIJtGogMDnYcM5pSW2KO+ncUfWztLVB8xqF5O?= =?us-ascii?Q?hBbdEtUluguXruOu2mE0b0Ls+XNPmZHjPXWXRgZIfeUGmi1H1Y3zUfejr4Ps?= =?us-ascii?Q?hiIkOEDPOxmK1T4DuTXxb8gBT3bJ6NnoVQdW2/pS7nsfHVgxmO3L6+ickXY3?= =?us-ascii?Q?JI4RZ9MNkW11r3ORiISIjr6or5Tzn+tSLyruyZ6tg0zalsEu6gNcX10yXdeB?= =?us-ascii?Q?1yW5JPpBdzzj+i7/upjd2UjvXgyD3wpcQiVWoWj2XmRJSZMmBh/1iygffrCP?= =?us-ascii?Q?Hd95BIAEuXbXXSxZ3nxeg40sOVmc+kSJqe/vo3UkFUZVXxCKI5TXcUjFDl9X?= =?us-ascii?Q?w4nDPo9da15SuERecWk3b87WYxrDjzV+qrhkknfeMn3NAAUzi9xTIk3LA3SF?= =?us-ascii?Q?zI8fX9LKLMlSuwMx2RFbQz5iZkP53biALvyWV8qoHb/i1JoQSXg6gIC77h8s?= =?us-ascii?Q?GQLJ/8eKXjdQdS8sKqlUeeFTIkwE7vqkzhOiq6sNV+HbdrtdFGk4RNr/cYJ4?= =?us-ascii?Q?eHLt5M4kvfxqcwdW//oFQoNTw4ajYNSncqL6FgcQX2nXuE6FYLknzs8AeZ8G?= =?us-ascii?Q?9EiqE47Pwd2Z4pdPEN0tVHi5U0pxgW1AuvnL0iDxAFkK2fysBNj8zEGWmLCE?= =?us-ascii?Q?bK0bi3gn3GKB3JgRb4pL1UwzTOohTDcaca5vgXV8Rs+0hvvRIX/8qE0Gb2XO?= =?us-ascii?Q?IqLdOPoc6DQUvEbXEqe5WLzuG7uA0nre4+OTS/XR6qYHIWOn+uy9YbP4Do9w?= =?us-ascii?Q?iWQIUnSNs0lFee/swzp5U0OdBbYwetc15RLHt39+lh9fOVtutFSDfsSo91sT?= =?us-ascii?Q?gZtLoShr95IZu8Qz3UmbB2i2zJxhCpx3Tj4Q43nGVmhrY6+jmHVqgCzmRTfQ?= =?us-ascii?Q?joaGKftzEInOs0froGS4qmi/W9DWAaOSfZwqoZk+MOAEGt2lxKCmGTCNvGlX?= =?us-ascii?Q?FhvPctm9jBtOErhGSErgC9Hkbrk8lEsdJqF6GcH802X3wjlodwWqbWHk0MYJ?= =?us-ascii?Q?6wiJjoHs1pXqqpFAtCKN7qYyTLdJW0F0/IXYNSnzSKyJtWyMevLYwBpAWqLl?= =?us-ascii?Q?p514h0N02F2mYVpGUs4/itUf6OSkmpqw=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB100; 5:m1wbnmEsEElTYrhjFMZ1ZVCHLZX6lxoZQNHHSdZNv0xjlBj/9ceZ8dNfZmitgzFeXbtWqvEUoUuTOQCp85NSxI9MxLruejPnwaBuQPYnLKhMkGj8IVeoztIFrUMOvZQvQFbWUqb1cfHKE+p+1hnQ0Q==; 24:6s6QxqM08aibSek5ovsoKiPD1ClkExIDD2FdvOiiGHJWn4/sV9WtQGKgTn9BfANtMrCEB2gWCnSkE3ZoiQt4rXDc3OGXU21/NxHxK3fHXb8= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2016 00:50:20.9964 (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: BL2PR03MB100 X-Mailman-Approved-At: Wed, 03 Feb 2016 01:21:09 +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 00:50:29 -0000 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 Qiao (Wicresoft) ; Kylie Liang ; 'freebsd-virtualization@fre= ebsd.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"