From owner-freebsd-virtualization@freebsd.org Thu Feb 4 06:00:58 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 83CA0A9B7A7 for ; Thu, 4 Feb 2016 06:00:58 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0111.outbound.protection.outlook.com [207.46.100.111]) (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 E46C71152 for ; Thu, 4 Feb 2016 06:00:57 +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=ToCyE/AyQpmgUFN1IkZxb3CXOLgCxLl+yLZhyprevSI=; b=GxLWzU4BCwKYO1virUBftQvpur7NQoljhg3JStFoG7+vGs5smcrEjRjbi6SaOtLK9LNmLYsYAnHO9Sg2jlEWDCPoVEhRs0vJDxngiWP6v9LPSV6+CDHF6s9uNFWULzvKgqMgGOLxS983IaqCPBee5rI9U7zSdNKNOPyTf8+V0WM= Received: from DM2PR03CA0004.namprd03.prod.outlook.com (10.141.96.14) by BN1PR0301MB0689.namprd03.prod.outlook.com (10.160.171.26) with Microsoft SMTP Server (TLS) id 15.1.396.15; Thu, 4 Feb 2016 06:00:47 +0000 Received: from BN1AFFO11FD005.protection.gbl (2a01:111:f400:7c10::136) by DM2PR03CA0004.outlook.office365.com (2a01:111:e400:2428::14) with Microsoft SMTP Server (TLS) id 15.1.403.16 via Frontend Transport; Thu, 4 Feb 2016 06:00: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 BN1AFFO11FD005.mail.protection.outlook.com (10.58.52.65) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Thu, 4 Feb 2016 06:00:46 +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; Thu, 4 Feb 2016 06:00:43 +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; Thu, 4 Feb 2016 06:00:42 +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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZAAANu3cAAenrMwAA2JiMA= Date: Thu, 4 Feb 2016 06:00:42 +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> <53238096372f4362b436382a430bde57@ORTELIUS.internal.bugworks.com> In-Reply-To: <53238096372f4362b436382a430bde57@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.5] X-MS-Office365-Filtering-Correlation-Id: 706da2d8-a402-4ef3-b708-08d32d2886a0 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD005; 1:aQOmpRAWMzgQ7Fr05lbYInXK4qXNLLIyEV11/YjdaZHgOQZisOVlGqoFUktwD306N52Pj1O4VyfoIflF5hERWdcP96wJM0gRJc8HQA0OtOp0CvRK9xp9FKlgD4f+E3Kc7Fm3vl2kkLUhVaARzd7S0qXXgmw1IEmY1PTJLbzciYdaG/u6Eqlghgg6680XLWOC/ZXPmsORmE9Gh13VnPyBG0jofkfYpHGGeVEYY7kznBmLkAplp/lA8XjJ2m9sev5cc4UJ2kZnjaK6kO3ldJd0Od7EXAisLJREnBVzRDwF0zhyL3oBLCFBB2RrVBz7ybMPaVcnY5YmtlAoUnsRsCHfag== 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)(51914003)(199003)(189002)(71364002)(?= =?us-ascii?Q?377454003)(164054003)(377424004)(13464003)(3905003)(19580395?= =?us-ascii?Q?003)(66926002)(2421001)(10090500001)(4001450100002)(58901000?= =?us-ascii?Q?01)(5003600100002)(10290500002)(3846002)(19625215002)(159754?= =?us-ascii?Q?45007)(5005710100001)(19617315012)(19627595001)(50986999)(51?= =?us-ascii?Q?2954002)(92566002)(189998001)(2561002)(6806005)(300700001)(2?= =?us-ascii?Q?900100001)(11100500001)(2906002)(10400500002)(66066001)(1220?= =?us-ascii?Q?700001)(67866002)(17760045003)(102836003)(1096002)(162366750?= =?us-ascii?Q?04)(790700001)(5008740100001)(6116002)(586003)(1511001)(9388?= =?us-ascii?Q?6004)(16796002)(18206015028)(19580405001)(76176999)(84326002?= =?us-ascii?Q?)(54356999)(33646002)(5004730100002)(108616004)(107886002)(2?= =?us-ascii?Q?60700001)(575784001)(2950100001)(87936001)(5001770100001)(39?= =?us-ascii?Q?00700001)(24736003)(99936001)(106466001)(86612001)(86362001)?= =?us-ascii?Q?(5001960100002)(19300405004)(7099028)(491001)(579004)(559001?= =?us-ascii?Q?)(562774006);DIR:OUT;SFP:1102;SCL:1;SRVR:BN1PR0301MB0689;H:0?= =?us-ascii?Q?64-smtp-out.microsoft.com;FPR:;SPF:Pass;MLV:sfv;A:1;MX:1;LAN?= =?us-ascii?Q?G:en;?= X-Microsoft-Exchange-Diagnostics: 1; BN1PR0301MB0689; 2:iJHeBw6dUunVkwiWWCQvdiEJLa0Q7+IHKfkCVqaMUrvy3mPaDpjzhmSPkGxzm7L1THa9TEomnZkJGjaSZtY7l0Bj5YXBK2vkNXfP1bwtxUE873DQDjWYNFn2NnGinaggnJX9eHL/Gj/YO7lFLiwUurtaX6743GH0GcCiYmmIB1mHoeN7QRfA6EzJ7TOkzPta; 3:snjJAOa0oR0SE+ssiePK+sdelHOTqLZbjnHzC64Y/OEbOSKFZtIpDt23Ij3CXYRCjgqk3RoxLRPAgMZgpOdl4EFZxZx0UeN7yRXvxzTR0zrVKk7pniwzkAigsXk5Vi27ylyHxQH5KqAlFukojgj507RvC94FnhcRag0/IZErB29K8DzsGjbCh9ABZMz2uq5nJAnlHkKoa4rrsoFjx1OUd/PUH+EnSFqqbUdIVv9etZrAwTCnCWc+t2QZ/iU0IgPgIh9YaRv+Tu467etH9sBb3A==; 25:QWex/Z84XLj1gNIkAC7VtdXgVqXKRf9rZBO+8zFcrOApDCg0DPxdgBK2MnobE+LHkBZR7S/p2Ierh40WZSsUClrKu1eLc+tKmnkt8Cef+oSr1/4nCLJ/p1R/RmkGE0mk/jYgeaJswxb16LVW4p/KoRnsU6WsXF7G1UNoWHJWiZ06fG5bT3vGw3yf29VIImGtq3ljLyuKEvk9/ODx5VqH0tCV+N8N3JuoPSAen9iTLfAn3/DTEme3FJI/mtnSZ+e3s+Enaen+/krhGBTWdjESnKJa3uWnI5kZrh0p+kKZup8= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BN1PR0301MB0689; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BN1PR0301MB0689; 20:L4GD6CcfhNI8WcRwwpQ7k5JhcMW/xvrww4XAygtON2kHzprGKerXR9Yr0okdhGSeOgBqVqAo5XXNWalVM7EuF5uHWTKBcM7c7261hVaA6e+iqxTEJDNhR61/GasdVo+jH7157hdylU6TiRJA+riiSAqDikOJdwfYKeJTRe3qiKB6LE25D/xv61YlAYn7oglnU1EAH16jL3TG0/LPh2CzR0FCNRUnrN6fBnrKgRCKMW4mSJ52QMB569BW7SrrL+iSDLVJBI7miVHklcDewEfYZx+mnXIBDBNPCvJ+WrlpZ+nZEIQyFi0NfTYA9WfnSfnN93yM44RlHihkIc1KRORwBbJ3gS6AaZ9pyA2G9QL2EaqJ84zaEVPulHOoeE/2VvlX9ZtF9464C0g4+6lfOg0BEwvDMpAmnAaIQGneVu7vehLRzsX0ZiLlgp21nWFMrV7Ho3tGutdeGrgs2EbseWmrW1x+Q64guRQWjPpbVFoGHw8X0Jqj4y6i6nmJaK8ID2PHsrwq8h2VlnAUZmw8c7FjtbRHKM6BhCLWyKm1Z7w1GFNhGJpveDsZUfTl8MynxO9Okb0EhcC99j/An5uGg7AIpQOirxPqxwcvgHFkrIfylho= 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)(13016025)(8121501046)(13018025)(5005006)(3002001)(10201501046)(61426038)(61427038); SRVR:BN1PR0301MB0689; BCL:0; PCL:0; RULEID:; SRVR:BN1PR0301MB0689; X-Microsoft-Exchange-Diagnostics: 1; BN1PR0301MB0689; 4:0sF2VEPgZT7TKLdicB9zT1LfEB8z+O+JVRihBcyCBY3GvJOjjH4m7oVgObdmpmSXxztVTcBTrH9n3X+rYFWtgDNMmI0HiKqod5ly2hr81MI0ISd3b9MjnP7ZU/cDadSkZZb7JOnBrmDiYOsvtBTqf59Wj1xuMtRx4Q5KuKV45q3Az0qabARpfaWgTbN8I0QmG/wsuJOlTdJ332zKLG68PynWzrziBGveI+e1OMU+2GO+nK/Q39lIefRtXfoNi6VrxMIE3oRYdxCVpacymvN21x8EoZhZQMFP9bX9g2aKGvzUME3WTjaOsg/w8V7fZ3ubkXWovuYyR7NyC4Uy19XF0S0pdH3Fy5y+dXYhAk8HDFg5Fgw9e5XGroKVXuIDSIYk7efsSi7Prm6q4IaOrv83M531fF3BBTcFQDyohbT67zbuFrLLuscSEUI+BExQqd/vi8PRyvneXEjtMqyQclOJp6SV2vq/kssdFsgyx8HseKFzLYKIMvrcadnWt4O+iSPRnbkq7XzEIRMFOhnq5z8yVQ== X-Forefront-PRVS: 084285FC5C X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN1PR0301MB0689; 23:C95sDK16xkkr0ts1LQxceqtFG8vI4a4tmisMOjK?= =?us-ascii?Q?QYc2R4PbyH3fpgiFaha1OijnK2Q/eUmDx3LTwBFxhbQdTuiNRJZ/Ansk56o8?= =?us-ascii?Q?76YjOVzKLyEpRp2Jix0Ajs+T433bkPGSY5myeJzHbpPHqD8B0eHRIwuSN0D5?= =?us-ascii?Q?1UG0v6Bt8Ifz6eWFHWRf8yHeFrUnnAdOsXJzEbrTinRAH3iLQ20nCslGMc3b?= =?us-ascii?Q?E79LsWZJ37IpJ3RFrE0mTqYU1guoW4MZe/YwCgdQVD4N2rTcUu9jZqXRm/79?= =?us-ascii?Q?XBcWypy85To0oBhhw2/bCbSkOQz9AUBWF7XBVxtvKk45SEd9sQc+Pe+h9Geh?= =?us-ascii?Q?hHWkyfZmI4zTva5HqusKuC/DISE9rtPLoXpxydRuq+Db3oVz4c+CEHfJWY9/?= =?us-ascii?Q?ernKprEhbBzjHrTDeBt4+B/AGRt1URssoeOAul4PSUhV/TuJUXcKsAiP8I2h?= =?us-ascii?Q?c2CQVqcrztLCtclcXQ/Xzjk69STS512uMz3/HK9fG1pR1SV3Pcae7gRa0hef?= =?us-ascii?Q?5Sjg8d+RLiW9hoUtXWvMuq9Tsrl33+g1QqhhUGINxtS0Rw+SSx7EugwWJAM/?= =?us-ascii?Q?dq5EDAOu7ZiVpYsmCvvOAeFsAwl5AulTi/WYFm8GOyUyzW3oUMq57NUFWq/B?= =?us-ascii?Q?vxLz9KR5gn/6+rNmE9KQ1/oh48zZ0u8EmsqB6CFHYdv5U69bQAJ2oSkP1CCm?= =?us-ascii?Q?K+VteGwR96PLeYkiQfLjbFY/lHCUUOSYC4wCbCSWQdSMRd/J7nKe4XLfWDwY?= =?us-ascii?Q?drAMlzdRKk0yqcBLA/Evo+IoBQDwwTyzFF+QtSA0tfFT+dT2UWxg+H/yZ8B3?= =?us-ascii?Q?bWFjqShC5P4lIhHFGfQBd+AQ+9asutDlkValmX59z6yLEuPP6jnbPoYviyf7?= =?us-ascii?Q?w9e/S2UKv+5WtAZi2h7qCAOX5njHYhTS+wR4LENCN+IDXB3H6XQ+crTauqKa?= =?us-ascii?Q?4CdDBhHj74MNGKGQIVUHxOnHBtVGB5crwf0gvwwwYYaX63I1QvH1+KPvd8ew?= =?us-ascii?Q?2rQNTjc5wPK7bscdhpuZj3lxy5CQwqlUYuMQNKlJkfeL2cWI5HfqhBTscHoi?= =?us-ascii?Q?O1QvjsG3s8xwpqCDT9h7ZDGaiF5+dYO40MplVErkbgMTg6Hk02yY76/YObH3?= =?us-ascii?Q?XUC70ku7WF1UHdJtclkw5MNYjfX9VeAF4YNc+nM4xZzW3WrGqSAygvJDvYrH?= =?us-ascii?Q?mSarUcC51+WWUpjLcW5/8OWHv7lfSg6pqRSvXAOO5gyLCcDXtnoFc0mU9hjE?= =?us-ascii?Q?8sdBsFHyrld1dDWRDCkL+mCgOHW8KTsqoNQER1cOcR3Na813B3IPo6TQEZ3T?= =?us-ascii?Q?5auh078O0dZY+YtQFWLVnmFMARUNfCCLm9EKHLg6cW23Ct9rBBrt+wZN+nSJ?= =?us-ascii?Q?jvHziHur8/INjPWTtNBhIUDXr0P4Zb0RMpgylfsjQJOIq+K2LKjG0AVv0mgp?= =?us-ascii?Q?3aLDX1NsBJbuQhmD+VZemEOXxyNTk70PR152m4SxUCLGMikVnd5mGwW8fVbg?= =?us-ascii?Q?H0hqN4bnGhY8g3Cf9PaxMsSVlr5eBPZFZGfSwwiyx+8inYsHqf7MfU+BQXDz?= =?us-ascii?Q?xVqVZCazIleL9/w97IjQhAuhNuIV3jQ4MyBjBArQBJLynfO0CHgeKeZHdZWl?= =?us-ascii?Q?2gw9e9cciC8fR0EJo/ydQV3m1s7OAnAsylWJg65WC3sOXblInFFXZ4RP/NnI?= =?us-ascii?Q?TNDOKv5/3bcgtpGJNzCiFDqL7G1Wyb0b+pd7F+aVzoqEsRr9fN6th7cg0VhL?= =?us-ascii?Q?q3b96RfvWVBEBbO7aQ97pGUb3F6nyd/gUsKF5OKK/Cg6FmpBWltl8x2vBq6f?= =?us-ascii?Q?gmpQ96H+pj9y1vm27zXOKU7Bq3+G9AHUlWp+6SkY+JiRvohh1ip/6L4X+gKR?= =?us-ascii?Q?SNoyJdXA0NYwnz6BRAiw7LmzBFhMtazRXbLzZvUx1AsppDrvhh9zQSHvcYq+?= =?us-ascii?Q?S/hZWJMMsqHY7OJzL6F3hueILiW6WoP9a3if4GGriXyUxVq0vnHa7h5Rt+Fc?= =?us-ascii?Q?fS8Q=3D?= X-Microsoft-Exchange-Diagnostics: 1; BN1PR0301MB0689; 5:l5UVt/VYZ07PPVxlu673mRD8fNPpti5c8VGZ51/R6TTlVwu25Osh477ACxdeXkaHis/vbWuY9VlTP3PaZ8iptIIuD0OhcqlpzJ1dWsh7tb+uveYUaU77iLI0nxCulSJyjNYBjgfIOHRdz4lEmMXqXg==; 24:sUDYOopC4Nl8zQhDAvVXdtYXrhsqciCM+EelRSekYQqOfgU/OayHGdSmCYRWOYHEKhbgX49YKBS9IKrrezcKwzcFLXXD072cNgZquJnq9sE= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2016 06:00:46.5781 (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: BN1PR0301MB0689 X-Mailman-Approved-At: Thu, 04 Feb 2016 12:03:06 +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: Thu, 04 Feb 2016 06:00:58 -0000 Hi Jac, The easiest way to get the fixes is just using the latest stable/10 branch = as I mentioned in another mail. Alternatively, if you want to use your local 10.2 source code in /usr/src/ = + the fixes only, please read the below: I put the 10.2-specific fixes onto my github branch "decui/10.2/fix_mac_ord= er" (please see the top 2 patches) : https://github.com/dcui/freebsd/commits/decui/10.2/fix_mac_order (I resolve= d a small code conflict) I verified the 2 patches could be cleanly applied to a clean installation o= f 10.2 VM: [root@decui-bsd102 /usr/src]# pwd /usr/src [root@decui-bsd102 /usr/src]# wget https://github.com/dcui/freebsd/commit/b= 706b383da285376554bcb69f44c4cc10270de24.patch --2016-02-04 13:37:04-- https://github.com/dcui/freebsd/commit/b706b383da2= 85376554bcb69f44c4cc10270de24.patch Resolving github.com (github.com)... 192.30.252.131 Connecting to github.com (github.com)|192.30.252.131|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: 'b706b383da285376554bcb69f44c4cc10270de24.patch.1' b706b383da285376554bcb69f44c4cc10270de24.pa [ <=3D> = ] 7.13= K --.-KB/s in 0.006s 2016-02-04 13:37:05 (1.22 MB/s) - 'b706b383da285376554bcb69f44c4cc10270de24= .patch.1' saved [7297] [root@decui-bsd102 /usr/src]# patch -sp1 < b706b383da285376554bcb69f44c4cc1= 0270de24.patch [root@decui-bsd102 /usr/src]# wget https://github.com/dcui/freebsd/commit/2= bff041dbed26b5da88c4be72b4701bbf6c460cd.patch --2016-02-04 13:37:26-- https://github.com/dcui/freebsd/commit/2bff041dbed= 26b5da88c4be72b4701bbf6c460cd.patch Resolving github.com (github.com)... 192.30.252.129 Connecting to github.com (github.com)|192.30.252.129|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: '2bff041dbed26b5da88c4be72b4701bbf6c460cd.patch.1' 2bff041dbed26b5da88c4be72b4701bbf6c460cd.pa [ <=3D> = ] 4.22= K --.-KB/s in 0.003s 2016-02-04 13:37:27 (1.31 MB/s) - '2bff041dbed26b5da88c4be72b4701bbf6c460cd= .patch.1' saved [4323] [root@decui-bsd102 /usr/src]# patch -sp1 < 2bff041dbed26b5da88c4be72b4701bb= f6c460cd.patch [root@decui-bsd102 /usr/src]# If the related files in your /usr/src/sys/dev/hyperv/ were messed up by the= previous failed patch commands, you can replace the files with the version= here (https://github.com/dcui/freebsd/tree/decui/10.2/fix_mac_order/sys/de= v/hyperv. You can use the "Raw" format functionality to get the related URL= s of the files and use 'wget' to get them): sys/dev/hyperv/include/hyperv.h sys/dev/hyperv/vmbus/hv_channel_mgmt.c sys/dev/hyperv/vmbus/hv_vmbus_drv_freebsd.c sys/dev/hyperv/vmbus/hv_vmbus_priv.h Please let me know if this will work for you. Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Thursday, February 4, 2016 7:18 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 Hello Dexuan, The first patch gives no messages. When trying the second: 112 # patch -sp1 < 1e469c559048fe6ec3641da3bb21ab87215c6506.patch 1 out of 7 hunks failed--saving rejects to sys/dev/hyperv/vmbus/hv_channel_= mgmt.c.rej Attached you find the patched file (as a session log). With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: woensdag 3 februari 2016 10:05 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 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"