From owner-freebsd-virtualization@freebsd.org Wed Feb 3 09:20:55 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 5C3B0A76FF3 for ; Wed, 3 Feb 2016 09:20:55 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0128.outbound.protection.outlook.com [65.55.169.128]) (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 E1C051A36 for ; Wed, 3 Feb 2016 09:20:53 +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=rdHlwZc2/a/1IkzlFThMXLZZyC4/6E1DWOQU5b/qyVQ=; b=nFKCWrGQCUob2LdjYoce5zTTjmPXu9ov1j9UaUteyZHJtJ23uEXsuYiwoy4jJq7dDvhHq5WbjfidrLaFseAr8M8EmqiCsoem0W67h3xHqKlTa2htoQkZyFiKDyKjILO+ZQqz971VenBY4w+nkEnmtYFt+IcQLKQAxl2dRX4yW00= Received: from CH1PR03CA006.namprd03.prod.outlook.com (10.255.156.151) by SN1PR0301MB1998.namprd03.prod.outlook.com (10.163.225.27) with Microsoft SMTP Server (TLS) id 15.1.396.15; Wed, 3 Feb 2016 09:05:06 +0000 Received: from BL2FFO11FD038.protection.gbl (10.255.156.132) by CH1PR03CA006.outlook.office365.com (10.255.156.151) with Microsoft SMTP Server (TLS) id 15.1.403.16 via Frontend Transport; Wed, 3 Feb 2016 09:05:06 +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 BL2FFO11FD038.mail.protection.outlook.com (10.173.161.134) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Wed, 3 Feb 2016 09:05:05 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) by HKXPR3004MB0086.064d.mgd.msft.net (141.251.197.86) with Microsoft SMTP Server (TLS) id 15.1.403.10; Wed, 3 Feb 2016 09:05:02 +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:05:02 +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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZAAANu3cA== Date: Wed, 3 Feb 2016 09:05:02 +0000 Message-ID: <17b639f383df4f42b1e050f6e40d1ad2@HKXPR3004MB0088.064d.mgd.msft.net> 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> In-Reply-To: <5a09277abe094f5989fb145c12a511df@ORTELIUS.internal.bugworks.com> 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: 516695c3-9110-4121-20f8-08d32c791bf9 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BL2FFO11FD038; 1:lev9aKYGfuop+gvWRQF91/ZIE/LovvW5Zvkg4N61aGcGB/7KmNK4sPZcxGU+ChJUCISkv1MQxQPjV5WvowRHjIqi9pLskMlsyI53lsSyhb4cQImOJdrIYLrZOcdX+Nq8RWHBpnDHUaDhFqOh3VzFiU7Qvt1aNS5widzljFu6/LZa1oyx6E325CYJf+HSTbn6VFBUMsnwnx3Teg5ggpJlx66s89K4uNyDGqO6/NY6sbw7+t9UgPFg0rUTdmZNavktS+x+0t1+YjT39M1HmopkAEMFL80jzXb+FhH+zHN5UBTtOmwuZKFPmPTHVjT49/MwillHHHNiWD6DxjrYNjifng== 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)(189002)(199003)(3905003)(13464003)(3?= =?us-ascii?Q?77454003)(51914003)(164054003)(71364002)(575784001)(19617315?= =?us-ascii?Q?012)(260700001)(2950100001)(2900100001)(106466001)(2906002)(?= =?us-ascii?Q?4001450100002)(2421001)(2561002)(300700001)(19627595001)(159?= =?us-ascii?Q?75445007)(10090500001)(19300405004)(92566002)(11100500001)(1?= =?us-ascii?Q?9580405001)(3900700001)(19580395003)(19625215002)(189998001)?= =?us-ascii?Q?(5005710100001)(54356999)(5004730100002)(10400500002)(247360?= =?us-ascii?Q?03)(84326002)(86146001)(10290500002)(17760045003)(1511001)(5?= =?us-ascii?Q?008740100001)(6806005)(512954002)(18206015028)(87936001)(863?= =?us-ascii?Q?62001)(1096002)(586003)(5003600100002)(1220700001)(76176999)?= =?us-ascii?Q?(108616004)(107886002)(790700001)(6116002)(5001960100002)(10?= =?us-ascii?Q?2836003)(50986999)(3846002)(99936001)(67866002)(33646002)(93?= =?us-ascii?Q?886004)(66926002)(66066001)(16796002)(5001770100001)(1623667?= =?us-ascii?Q?5004)(7099028)(491001)(559001)(579004)(562774006);DIR:OUT;SF?= =?us-ascii?Q?P:1102;SCL:1;SRVR:SN1PR0301MB1998;H:064-smtp-out.microsoft.c?= =?us-ascii?Q?om;FPR:;SPF:Pass;MLV:sfv;MX:1;A:1;LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1998; 2:UvwS7mbog0hk8lyJd3MYawi8kWkZRn2PtvmmLlIT6fNfBPbbidTJ2J60WP6C+RXrwFuXU8oLDcDM2TM3Mk4clwnvoA53qHKZ07PdPqzDbfGqtrZVqrj76NdxWdgN/aC4FKjZzl2vE6pcFlNgi2tA2hAXC+XVK5zyHc+yALlEIBSKnGOmP6CjyUkqp+zis0eJ; 3:P/8j4bYo1JKaK4pwurFJO4MocD4pkKVODLneiuCH7zV4lniOfNvnciE6A2xxoVjFBqVCvtDimKzg1kT9dqt4nng1PLgfUOC0zgVPurugvSVrZ9bT4mT1FHiaoYiX009UigNsww8UfrW0oQq3HSsPADb91z+tQC9Fjs0cpFijKhqlxO3Q9NAjmjdzQGNDPODOMUMZYSND5m/kQwoycdvKFE1UJJoSj62icN1YmJArLeMZhG2PCw9osaMgM602pSjRZUk/947auLh8r2l7YaGqIQ==; 25:s+xhG0DxgGbi1wwM7ihR+loFJSIomg8Cza79eMKIo8T+MQ0d2z7kdW6NEz0KrayQBcC6z1jenkshBdSC4qXaz2AmCS5eacKUrHG92e4A00pGuYwtGdaqI1STvLg7y59oB9W0j8K0W1xuRnfvVAiJmfG32xsdBGmjx4AMl5OJiTurYp7zddp9U7OKW6FbZArMnSoDezUjNyeY4T3k+TtyDHI5dDPPmh4KdsNH5ReblP7YJLX1qnurtPhVuH8zGgOZcg76CqsXcW7HIog6kUF27sR+mCoIepG/wYlwl9zEgUI= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:SN1PR0301MB1998; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1998; 20:34ugBNUemgH8fmmUhY4wlEsMPB7iImqKRUP2EmdfBQDfgpFKsjLxko5o7zgHthD2pGYnVAx23ErSQxY+SkQ62pBHRTSOdzScRBEj8lcopicrKUdN4YDxX50jeXMVNkT+HmUgpezLDpbe3clgS3awDvsUwCtbuvSn5gN2vG/bnrwGJf2dtqMtQgChfCIMTgcXXHD/lCDdUwMLM0vNY3QUXwJMYvwIyP+ERwo6/NupfyF+wUtd9PBzSd0RrIkVN4GCSXf/lcluBATXPrKWDUDlEGzc1EI2+CM47bFRHPfEBu5DNDOWG4181OAsq2DTpbK+jg6I1FzxzuBtq1lZh2o0h61RCo4OcUCW5tKOwa21ivf4kD4dFgAfcwaHfUzB930v9RA2KHp6RgVomnaWFe2BRGRgUYpQtLro/WsxLSA701FCsgBtklHTtcq1FYPY0qYB7PeH/g3SdULklIzwHcdqHYBGncmYUg+VHpZRkv4lzt7p1tpLaWiW4ONHuPABNVwV55/8eH9pdvaqXOi86BtzD+1hhRycLR9ZYPVPtQHO08AoxYoNju3ZRMu7Os+OIFXrhystJRNLBCSI4skRi062lLuSiEcZTLOMpPfNJkHyxao= 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:SN1PR0301MB1998; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0301MB1998; X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1998; 4:4+9mld/4phtp5+GPUGOELiRIhQUyQisOo3m36Nbaw+qpFGUSftfyK+aqlnCvPAZVDZ55F4DytJpTKdLrEMx5W5N0Qln6Ql3mcHNA9gx36qedW0qEfGxkter1947CvK49mgZIuXZ8G7r3PRC0HrVhCLYYf+vC2zMhcVM5P7y1aGf8BTqWyWv2PBhCIwVS8bl/VQ4str2em0rUvikpcOAMJeYxETj6Vi9moGshEcWrWXWmrhbpzrSShKiaJ7Cjo0qT6ZRuQB6B3t2gcKyEO28ob1ZnCc9EHGmDy98XAlqgYJ7eNV1FddFGgKb6AoYSu9TQvL2lZfsdo9BqHx8w023226NiHAXJ/5u5mcz7EZxbOVy10tNMRjs/XsksZJpDGhJ82aLwfnLhfaiuRiDzapHaQVb37J1ZE2e1A8ftS+LtIbAumSrVxEDjcHqRcpHefOj4T0VnIiZ/oXwF6j2oFmlwZTeDSQUWDXdDsfInQoOwjg+d87cxyKo7Vt4CunrToyd3 X-Forefront-PRVS: 08417837C5 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; SN1PR0301MB1998; 23:V/AhUd7f6btH1gh++tdMLe27BHjyVZ1E0+l53/u?= =?us-ascii?Q?FmwkcbMoFMZbzaX6X4QwWT8vN9KocZAfsBZ+2NRjScaZ07EeEfeWt8XabojV?= =?us-ascii?Q?Squ8R4zxsMRYDpizFdFjhX7JKtDtlS4w6JvQevTDJBXFw2OqR4O/8UPTdxkg?= =?us-ascii?Q?DA2g4oBRUFZZIszNf2CMcGf6KDANxer+MaGsbSB9a7S1Dby3NzJBtt5tpR1H?= =?us-ascii?Q?19UQeHFRBW4Zcj3Y7UEqnr5gHju8cIaF5fS0xvCxXFvYpQAeKmOaoLgJ3/3q?= =?us-ascii?Q?smcNmUs1ua70X4pOONthDO/x6rFS8MNLNTWSZQVz3JzRx8ghXiJwFiTi/ZgI?= =?us-ascii?Q?AIsMm/s7BwrpGLQBPA2d2fcp26/5tRT6BPic3oJeT0/fSXI1MAPufPbpMLLm?= =?us-ascii?Q?Xap+6a+zNvuM/Pnpa6GOqRrqwdwU5TtBRU184fi6yVLAvFTxkPiWyw9uZ9hg?= =?us-ascii?Q?QY9oRjzwmA0DtMZxkO5x5oBpuDZ+BqrecsSMc4+ZYARq+/7cO7XLlu5Q8EpP?= =?us-ascii?Q?66uYo/uNUGA6ODANVpFVn/2cDMIKGzC3NHREFR8EL0xWzbpLNF1wyxJq5ySx?= =?us-ascii?Q?eRLUQHrG4l/FtFf80enZqnJfZw42MThG6cXmGkm8dWxvG5hTpUlsBk98M8qN?= =?us-ascii?Q?jYvuZi27IFNorZACVhFtbv2KqNMlcB4k7ZGPJtJnRvDMEQSSOADTEcKRTHCs?= =?us-ascii?Q?st8IMgtdy9XeCD6uzEiyIFzyrY5sKMQHWyE3NCN1gv0Lpb+hvH5ERA+czyGr?= =?us-ascii?Q?xdDrO/Hhzln1omegB1vdrGo5qBIKAeB9VJ0pILnQ8noOZVQztrKg7DTRe0zM?= =?us-ascii?Q?dsa0EFJNX6mCZvCWGRUrx2lX8+dwffFLRh89m6ofuffmlBELl+6KN9C1Lvow?= =?us-ascii?Q?gKOa+fR7L1xCEcd8A8/lWjjcgyh4HuHeINGmn2J7FsIQnupRrYrDGMFHmN9f?= =?us-ascii?Q?hYspFz5peX6TKkmrRNeKDv/rv5PLPdxiQcZEKfgkrq7X8qtaMXKJzLygNmjJ?= =?us-ascii?Q?k+WVeR1XFvOALaeUxYGKXP/g6mT69x1SxBufXEhiIqtricqT+s0POI4/9YVo?= =?us-ascii?Q?X7Gwmm0KxTXSAaEu4YCD0y7bCRBdrTGDQoG7OzCo556ypeZ76fNQQ9ocl/t1?= =?us-ascii?Q?CIa7C6z+dBswCWbkHdvn6p4vemCPUy8+Bg67PDouuhYxHMsPOA+x1+AHxQO2?= =?us-ascii?Q?1zUYkb9g+7vHJ0+/uffuwEXRfG73YNbq+FZz6TtZfWAJGemSraQqIlF6s6Lu?= =?us-ascii?Q?6EweU4ild1grWgmMKnYK/4W/0HHZh4WtSm4V+6LNYv4e81Cga2IluK1++8ZY?= =?us-ascii?Q?hHbPzeADpbZGWPH8egLIR9sUgY7qGbjUCcny9zqLALPMW+3wKZwX83XK7sHq?= =?us-ascii?Q?4gyDJe3QaDMFD0ZYRvcPVrRabh6F2Id7tCLLXD7y6qfIANrv2fPviqshUk1S?= =?us-ascii?Q?J8FxPQXq8FPSToyAwXkRzYFYwg0jAcL19LZ16w3qWcdp8NGBfQCyd3hbN8WO?= =?us-ascii?Q?JowZiAhjrZjwrHWUpFJ//jw4alhjvq+cfO9RakR2W0xtVJnBGB6FmJ5Ue95O?= =?us-ascii?Q?Imgpme2bl712LW/C0tBFhBMIbiTz/LhBJn41MP7YvrpIAr0Z+urychYt4O1n?= =?us-ascii?Q?6/DncdRJE+i9a8AJ0HSod6t4VL31vVuJW+RG4CZzWYzsi8oy+pCdGCucY3H5?= =?us-ascii?Q?BuUY2JpqHZFXLG17iT46Q2q/d+MMNb6bbZzGk5Q6tSGuYBYOuGdfK2lAxyVU?= =?us-ascii?Q?Hmlg5GAU1cQbE8k2cxdWa3F3nEgzsk8g4JrtHuKcVx2XlysMCbXcy59sQSeB?= =?us-ascii?Q?A1Vso0AZTtLMIdBIDFWSWaroNxHKEc+2l/1543+bXTDH7zHDtKYGT4aQHPDg?= =?us-ascii?Q?/8j2cUxuMr0B6j8zJjkzWjFqlKJdbZRU6QY6qKA/vvjVBf8ggFabRKz5qIZw?= =?us-ascii?Q?=3D?= X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1998; 5:qqebW6RV4RMkDKqV62YVxFpetl9c6/Ld+aSotN7Tw8yYhNOA1u7TeehI/thwnDAKP1FCtQpPKLI/Xc8SB3mRgVyJqyAVFBYpmJQ27oyqrmyjPSPPOIIFkdKoyT5jEgO6mmNY2tSzmq3mPzlkq9Iy9w==; 24:qBlc/maiYVobgouCFVc+gs/1asDzSaUDEEmELdKYcL1GqX/YrBzGT0EOnpuS5xduBMJJbG6rSa0/JH60eQuE9CJz38qzbjR+rL7TNXJ4BcE= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2016 09:05:05.6824 (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: SN1PR0301MB1998 X-Mailman-Approved-At: Wed, 03 Feb 2016 12:54:33 +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 09:20:55 -0000 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 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 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"