From owner-freebsd-virtualization@freebsd.org Sun Jan 31 06:21:44 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 4E1A3A74EEA for ; Sun, 31 Jan 2016 06:21:44 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0130.outbound.protection.outlook.com [157.56.111.130]) (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 01D0FB04 for ; Sun, 31 Jan 2016 06:21:42 +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=0sEpdpIBFPK5sH+X4VonClWQdhzA2LbgX0enBGdyK2M=; b=YwvdV7IWVFmscYVqI1nswxBaTEqNIkFWaPXNAQhwDr6eL1Y9Z9pkK4mMXB3io+r9ov1SReXXe9u8iKWHHW2aVaRY4RiXO+GUHUYsYdnymu1c2+O9r+uGYdxxnNNvrMuAEoAx4yMEcXzFjztLl3VZEy9CoAXQr7x0oF5yjQBV1b8= Received: from CH1PR03CA011.namprd03.prod.outlook.com (10.255.156.156) by BY2PR0301MB2056.namprd03.prod.outlook.com (10.163.196.158) with Microsoft SMTP Server (TLS) id 15.1.390.13; Sun, 31 Jan 2016 06:07:11 +0000 Received: from BY2FFO11FD026.protection.gbl (10.255.156.132) by CH1PR03CA011.outlook.office365.com (10.255.156.156) with Microsoft SMTP Server (TLS) id 15.1.396.15 via Frontend Transport; Sun, 31 Jan 2016 06:07:10 +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 BY2FFO11FD026.mail.protection.outlook.com (10.1.15.215) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Sun, 31 Jan 2016 06:07:09 +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; Sun, 31 Jan 2016 06:07:07 +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; Sun, 31 Jan 2016 06:07:07 +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/D1AASYVK4AAUkXXg Date: Sun, 31 Jan 2016 06:07:07 +0000 Message-ID: <1aba0d827b9041b79b85a09cf70e52b1@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> In-Reply-To: <0ce04bf413204478b1e7cc71ac28ecac@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.4] X-MS-Office365-Filtering-Correlation-Id: 6c8c48e9-44f3-4d6f-680c-08d32a04c13f MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD026; 1:a3G1UOxImdfkZpPgPN3wF7GhoovRDxDwbyF42ztBSEf6lhwsK0WXAod8m0nakzI6kMiLghnfCU967eqa74gPx7gdw4jZ1+fy6ANxWbD/zsURai7CqhY2CXVxVoYqINOlbIixf1XHDjfyKsGIZTFX6a6HEqAwc990aYNeA5CJUv2MD4cxJJCJFzcr8lZj624uivjIObfBNWNpZt0FcrbWT42ooYv9IHulwuzuGo28yD0wS7kEbwUaVepkAVALF/mkzFB84h+GHDtbZo7p/uUL+QqMX8oRa0o+t+bggVYSN+AajJ96i6U6RrEWYltHrz09hnBMMZPzAI+cvRHQ5xY1hg== X-Forefront-Antispam-Report: CIP:23.103.249.84; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(2980300002)(438002)(164054003)(189002)(377454003)(51914003)(3905003)(71364002)(199003)(15975445007)(18206015028)(4001450100002)(16796002)(1511001)(19580395003)(19580405001)(10090500001)(108616004)(84326002)(66066001)(87936001)(5004730100002)(106466001)(92566002)(66926002)(93886004)(33646002)(5001770100001)(86146001)(5001960100002)(107886002)(2421001)(19627595001)(19617315012)(86362001)(575784001)(24736003)(2906002)(586003)(16236675004)(300700001)(260700001)(5005710100001)(6806005)(5008740100001)(11100500001)(5003600100002)(512954002)(790700001)(102836003)(3846002)(10400500002)(1096002)(19625215002)(1220700001)(54356999)(76176999)(2950100001)(2900100001)(3470700001)(19300405004)(50986999)(99936001)(17760045003)(189998001)(10290500002)(7099028)(579004)(559001)(562774006); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0301MB2056; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; MLV:sfv; MX:1; A:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB2056; 2:WC07rSbHuJbHHIAPKJJGb/QpgkoGd5ljERnXsBI+ty5FHemM0A5KHqpLinc4BkSN5azJHhtnm9EJKy4kPxnzl5dmT5IWMrFeDXdpeY9o9+G7NiImAvnXCYxNEnuxb0Z23AU0oGg8umM/8iMCQhl0aLo45j2XviN+oEgXtzSQnI/4O7sCSC80DQv8l4YyYH6I; 3:0bJ9/Ze57yBkTtC3ptOXU/vrmD50BesQPYyuN7Xgtj9vfm845n+/mAUFqUB2ARWnYDI0oNml+WC++Snst5damRvg33+2JrrYiZWPWZ2C9XDyEV6k8F8us/a1kNyHkfYMLkNCtQ+lbqc9jjdEtwqobIkZKPcoKKWdmBl+3cuT6PAzOf5v5RIb2HzC7x6NrIUpT2ksoBaRomTM/vz4jWkKKkaW8QLTWXZU7bcd5QqIkZoNJJQqoe35sXHEBI2yWl8lZqK2gVmNCx83WFaxTnqhJA==; 25:8SgkwKzUDpC69vz1bHdOcFA0dzP/C03l3EG2Azu6LnFU2haGFxlD7zhwaVu5tojeUJ8x4DuKzkT7uc6N/Cf1VCFdv93/Ie6DAJTsxamgpSVbximWaYICDeG1b10nn6OkbBmNhr7U+F1QmmcgA8365I0wR9sRPVkTY5xwwm7L5fqKNOe6JCnkzI2xOR/AU+2mK+r67mlxE60zm7HCJFdQg1v4T8R6LNmgarqBRT7edylFG8trHBGSNTIl3MfTVSBDzNgA0lmNm3rcTPIMu2PYL42SQPblLIELRpTYmVtBL1U= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BY2PR0301MB2056; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB2056; 20:ObCbbLDntJTA2TYHKNe+e7XzQ0q/24N8Rmt+6Lw1UBytToXWb0CzeANqeQHRgSRJ7hXUgjpVEXTYNa+N7rLjewG0vFITHKK4RP4hwB44iyeoQ/JRweH9108p+1wJ1MjQ0cSAWh8RElFKatc07Z77aMZ57Dxs+V6lGz6vonR9DMIsEgRgjggaQWJPb0/f5Mv9g1CRqHIe2KGHD2Vx20GuXm9hG9IqvpPjWx9BCzXJjH3RWOPz6UvmOLGjTtoEX7ZwJzNiDE+3jf2byItDO5XePo9RXiAWTEBteL5YR3bTuXxSaE9S6Ph1q5oXI00fIvwLLAEgMD6KippO4B42/wV3A/l2MONVKEOgB1Sjt1aQGvUgnTR0LuxvkMZ+Wso3k6gfxqzmYWuoPvUpsfrrhZZThWfDne7lmsWqoyC8P3KbyE+tgk+XQ+mi71lySzs7mT1VnBgy+Qi5oZ//R6htEPMBjyYIfH55G+sEXO3Iw6BqJU6iDCV37L+lgZrzcmpSv+8TXQ2cpexwU5ruUqtD+dx+kwGsv1zyx72ckhw7P0Kvnogoqq8xwVQHBvPFsm6UifGg8mBvQqAZR7tFptM1UbvWaK+qUS5dv3lYdoJ5i8OZUTw= 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)(13016025)(8121501046)(3002001)(10201501046)(61426038)(61427038); SRVR:BY2PR0301MB2056; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0301MB2056; X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB2056; 4:eH7tqvWmFGzz3lU8WG2plIYeUI7PDEkbSzhjEymQdoErQJwnKyHgr795Q5rcJDYZtsMybaopnvj5pARXPBAwle3t3v0FwZbCWvs3oOviY1hGPxbT1OrWDd60Uf0WW13L3BBXz9VZzlBMFHRGFjVQQioOQAEvAs5Gdavrn6Mr1D6ufzGbyVlB8heMHILhAzMqrDpEzmth9qKSGVzFWzFe4XeInQiUxVksDdxWyqxO3oFXDMKE0QlDNe9JyTkEmDu7SjGKDncUakLn+Dif9mm8ie01BNlB7SbpO6QP7RZAO6DVrUtSSnR0bo7D4oe4dn6KfxaPx9c3Ff0Z/vnTFgMHK51FQZH+qWT4vMobtWqj5Vw55wmzIgiqmITpiZ5pTswQboCWsOUZZFWc0PPcBuWe/xQ6o+rb9Hz7ssFVhksvEZDn9k/LVTQUhPW2Caff/UegDFar36VfBjOTgbzVdOSFDCeVxZdfJtD5pUACCuiQNd455HbdDVYjfUjCgtdAr9UtMBMKmCKH7o7owrRNQBvkKg== X-Forefront-PRVS: 08381C729B X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY2PR0301MB2056; 23:SKDxmdcsnImnjObBD9TTGBBsn1XeCZl0ur1+rbY?= =?us-ascii?Q?G0NwfpzT1d2a019/7vIZJNPdzb4ek60B8dE2ujPv2MVTtg9Ahgi0880cBvvS?= =?us-ascii?Q?jUMyqGxV/Kg5Z2x/slj1Lyhb1rPyh881qHcfccdOl48pfdSMt8MHWbV0XJJC?= =?us-ascii?Q?BQ7r2aL5JuiHCDYS42/4+uBg3DsGD9buQbAWPvIc306KNB2SBMFaHRl0iPeS?= =?us-ascii?Q?CJkN9TiILGn6xJi3Nb934uB0Q21fDQgR2s2r3lt1JdSQrWbseDHKMZVL2G2j?= =?us-ascii?Q?x/W+BAiZxR+Ghj5NJFABvUWV2SY8x51I6u41RMr0E0IlEGkdlZRnLOinDb7j?= =?us-ascii?Q?kSMs6bP1rDfnQa2gLpFvTd+n4CtTDG8KV/bWAkwvb/AlVJPw9wubcU7Nos+7?= =?us-ascii?Q?+5PSzny1sE56bKauqJkTXdmSlOVj3AqmiKM84IDIK5jsmDt8FIlflD5kG7ot?= =?us-ascii?Q?4slAp1czLzqbOXUntaBdeS1P7fICW0LXlZNhGfIhbTL20gHnOy8c0QR9r3Zh?= =?us-ascii?Q?p4ibJRnl1LG4mQDLF5m6NyAIBvXfLzOYZxNSIqXrIpuIqw2dtlFlwtSx25O+?= =?us-ascii?Q?MKGu4Sl6kbLxmspUnuGulxaP2DTa5Fn3KsgY2KJOT7tfqs/MjQ4QTJv2PeSD?= =?us-ascii?Q?1HawJxCtuID5Jys5LJnGL0IgKmXomCBC6lp9ZPpJUNDbdC8LMsPRVA8VQ8tR?= =?us-ascii?Q?rFPc/pw3hq7as/EUlXATL1C+BSC2b5ebNvkas3YehyRfzsQhNi9hMzM7woO0?= =?us-ascii?Q?32vcU85ThURKyas2q5hR1iFynHTxkI2gPGD6sZZ0Xe7YOw9S4sWWc7wN8IwP?= =?us-ascii?Q?SbyUT231bRg7gqyMU2VL/ZFSayfyKwn4D5JugzLykMgAPqGJvGxPsIj8/zbp?= =?us-ascii?Q?hodBp5scyVnR//GO64J2DYNOfi+gH4I8ZnpUhdNZ6F90njDhVyD9k2KYN65e?= =?us-ascii?Q?G963x1K9tD0AXUEkB/MQH3I1KcmB+3efqiQzkHgQaw0QnI0e/vInRpoxD5GL?= =?us-ascii?Q?UXQBtMDtWCVl2iVDRUSib1Sbjv5uk6Zc7lytabl8R/9hNuFBoC9a15HgRVel?= =?us-ascii?Q?TPEk7aNK7nLRzliRNwK9eq9AmnCSfsTitDkgd1UfRfy1kij2xeg0GxvcT6Yz?= =?us-ascii?Q?9kgHb0fwqzZbO4xK52HACb2BX//EMzwJe0RFQ2XK1eKzPeetxQoMQPRF9j8Y?= =?us-ascii?Q?wIXM9MLMSha99fVWtqb6eUczclLn9UtvPecvj2017g0Y43TAyD126ZqTWGex?= =?us-ascii?Q?ouZlSmMoqYkrRxaz5yaUwhl/V22atGeFVVmmL2Z7VYumlODkFI07MD9GKq1x?= =?us-ascii?Q?WNPP1tzpziWiheT0E8p+RhBn15WAfBf+BK68V80HYou1Oq1YJjJUzDoWD396?= =?us-ascii?Q?lmwHTujlr7El/gmSaXtlXxf9TR95Qo/s0F/MquMP07sCNO7d8rmHpcWNSkYT?= =?us-ascii?Q?pMs+Trvuy34vMsmwAnewgGleO7u9BDjn8xD0CdH+L8eImkEdeiMXimFyiO31?= =?us-ascii?Q?Kf9GpjkjuQo9GQuo4iAGzWNydQsLOdKl4bJhX8RmZLcAsl5iprdf3Uosb7W+?= =?us-ascii?Q?9wWH9EINYJTFrjghpqK7Gov5xHfrf6nj5hvbQmG5z5pwvgLxdCpPCT55EtAE?= =?us-ascii?Q?a+LeOCSv7ZPyUcLjNkvYpwmYNLiaiYOjM7UO1YVJeY2i+u4rfSi6XgU7E1Cg?= =?us-ascii?Q?XvZW0qOyal5U8QWjXZJZwOTQJIkSG8pHvQQoiZ9uG+tF63sTz3F2KB7zIIzt?= =?us-ascii?Q?M8V7hh9k8ebnkY2ovx28ZJwnKA1/sKWCF/P2inzM+IrTCiaG8vBqyZ6t3JlE?= =?us-ascii?Q?AG+5hEseP/X5PLim6J2xmYi0MlRrMDb32xw=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB2056; 5:UXnQMknP9QnBPdTptc9yOnzmRRgjxgqtp9BDgbeGfq4kAHXUU6FRPS3Yeqdpa4Z7oXIIutsfop5at9OTToIJSQDdL9qiM9f1nBK26yeo+8gaC+OEaFI34rVL060JoHoK6i7xTGb/r8tECk7Va1zrAQ==; 24:mKZF2APumyQ+Vey31MsoQwhIP5lGH2to6tYRWkajxg3P9TvO5KbPGUaz32tlgRZ3KPcywdBOvQfxtC5Bw+fRLreYEH8lXw1lCrBPD22Vthc= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Jan 2016 06:07:09.6645 (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: BY2PR0301MB2056 X-Mailman-Approved-At: Sun, 31 Jan 2016 12:14:54 +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: Sun, 31 Jan 2016 06:21:44 -0000 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" From owner-freebsd-virtualization@freebsd.org Sun Jan 31 12:24:46 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 0C47972FE for ; Sun, 31 Jan 2016 12:24:46 +0000 (UTC) (envelope-from marieheleneka@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 668D411E9 for ; Sun, 31 Jan 2016 12:24:45 +0000 (UTC) (envelope-from marieheleneka@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id p63so34956694wmp.1 for ; Sun, 31 Jan 2016 04:24:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=rfG1N0ovb3A9fTgGOO/SJxIrh06+AV/jFj8AeBj0RJo=; b=s4iXNL7ig0FfYdfccyxp7Jx7pVnMMUDtSz+uTahg3ZKb15t7K+ZERVLd39/ftVWDTk VgQFhq7rEgLPQImdIe5cdtCyufXFCGUx5Tg26ryOuRwUzJ/OyjDelceA8YmGH8Mik+Ap noCY9vjywIaWBggYMZaq2c/MflaROq0Ek3dVYtnMOasGeYpEe0NySKmJSNnuKvDbjKg+ Oi1Gii5GNnUcyKFJ/s2zz4e5cy5UJihuo22Xpr7Cl2xchCGNMHNgbbbFBxlpcoHKiT85 zhBo7KiT2igW2O1wc866EhAM+Xia3AvnVcJGjgdM1h86vZzeg89AH83NE104DYFJENBI 2IGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=rfG1N0ovb3A9fTgGOO/SJxIrh06+AV/jFj8AeBj0RJo=; b=TqEr/7GLE0PqVf10IZEkDDci+gf8IWu3M7djc9Q8Wh4w67AS4hPwv8kRrvesKUofSP Pk5Fcjzk4btryX8uJvomQMJAsB3j6xUqj8wieOPibW4GOaLpq0lSbXO+geqfH8z70kh8 7EqK/9wZXz1N7P5mRS8bcsomAZkEvnb23gtN9qzmvNyajKXLHy9T55AvwFfYz2WZuNxg NJZdv8Wvao99zpLqJsSOQ5agRQwt+pLikCC7661V9qP4g8O1M5WSjddcviCtPz5iDYff sWhcEqfcV3kM9YkEIiy8Iv2UXIU0nHy28kzFJoZDaMUXgHM7irtZ8H6HxQwJowb1bJ2V Wlxw== X-Gm-Message-State: AG10YOQn+y8Qt3bQ/ihM2Dn5kfOqu3L765hkj418xuKFgJpNahOyq+ORyUb/F9OF6jlamyX/kmaY5QF+ItPnug== X-Received: by 10.194.82.199 with SMTP id k7mr20008122wjy.65.1454243083823; Sun, 31 Jan 2016 04:24:43 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> From: Marie Helene Kvello-Aune Date: Sun, 31 Jan 2016 12:24:34 +0000 Message-ID: Subject: Re: Hyper-V networking: problem after upgrade to 10.2 To: Dexuan Cui , Jac Backus , "Sephe Qiao (Wicresoft)" , Kylie Liang , "freebsd-virtualization@freebsd.org" , BSD Integration Components for Hyper-V Content-Type: text/plain; charset=UTF-8 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: Sun, 31 Jan 2016 12:24:46 -0000 I had this issue with a Windows Server 2012 R2 Hyper-V host and FreeBSD 10.1 sometime last year, but chalked it up to a random fault during upgrade. It wasn't a production VM so I didn't put much effort into debugging it at the time. I remember I was using SR-IOV on the virtual network switch, and had it enabled on the VM as well. I had also enabled DHCP guard. Maybe some of these settings are relevant to reproducing the bug? Regards, Marie Helene Kvello-Aune On Sun, Jan 31, 2016 at 1:15 PM Dexuan Cui wrote: > 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 fo= r > debug purpose. > > During the VM boot-up, can you keep pinging the VM from the other host. I > mean: 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., > do 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 > 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 > > 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-virtualization@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 > issue? > > Thanks, > -- Dexuan > > From: Jac Backus [mailto:j.backus@bugworks.com] > Sent: Friday, January 29, 2016 15:36 > To: Dexuan Cui >; 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 > > 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: No 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-virtualization@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 > scp 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/GENERIC > amd64 > > What's the specific symptom for "networking does not work anymore" in you= r > 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 > 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 > > Hello Dexuan, > > Unfortunetely, no OACTIVE flag: > > hn0: flags=3D8843 metric 0 mtu 15= 00 > 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-virtualization@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 > from 10.2). > We suspect it may be a known OACTIVE issue and "ifconfig -a' can confirm > this, the output has the string "OACTIVE". > > It looks somehow the issue doesn't happen when we use a 10.2 fresh > installation. > > Thanks, > -- Dexuan > > From: Sephe Qiao (Wicresoft) > Sent: Wednesday, January 27, 2016 9:13 > To: Jac Backus >; > Dexuan Cui >; Kylie Liang > >; ' > freebsd-virtualization@freebsd.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 >; > Dexuan Cui >; Kylie Liang > >; ' > freebsd-virtualization@freebsd.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 > Liang >; ' > freebsd-virtualization@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 i= s > 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 > Integration 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" -- ca= n > you please check if your issue is the same as > > > > Bug 187006 - [hyper-v] dynamic address (dhcp) obtaining doesn't work on > HYPER-V OS 2012 R2 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187006< > https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%2fbugs.f= reebsd.org%2fbugzilla%2fshow_bug.cgi%3fid%3d187006&data=3D01%7c01%7cv-yanqi= a%40064d.mgd.microsoft.com%7cef82474449e745da88c908d3263e7e48%7c72f988bf86f= 141af91ab2d7cd011db47%7c1&sdata=3D1IyQb3x7ecm%2f6uESQmVAAyAyOQr4ZMJ3Fkawp93= dZgQ%3d> > ? > > > > Thanks, > > -- Dexuan > > > > > > > -----Original Message----- > > > From: Dexuan Cui > > > Sent: Tuesday, January 26, 2016 14:49 > > > To: Kylie Liang >; > Jac Backus > > > >; ' > freebsd-virtualization@freebsd.org' > > > freebsd-virtualization@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' > > > > 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 owner-freebsd-virtualization@freebsd.org> > > > > [mailto:owner-freebsd- virtualization@freebsd.org virtualization@freebsd.org>] On Behalf Of Jac > > > > Backus > > > > Sent: Tuesday, January 26, 2016 5:56 AM > > > > To: 'freebsd-virtualization@freebsd.org' > > > > 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: > Using 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 > works 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 > address: > > > > 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 > address: > > > > 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 freebsd-virtualization@freebsd.org> mailing list > > > > > > > https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%2flist= s > > > .freebs > > > > d.org%2fmailman%2flistinfo%2ffreebsd- > > > > > > > virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2= e > > > > > > > 0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1&s > > > > data=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d > > > > To unsubscribe, send any mail to "freebsd-virtualization- > > > > unsubscribe@freebsd.org" > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Sun Jan 31 10:56:07 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 B4D77A74A3D for ; Sun, 31 Jan 2016 10:56:07 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C1E61111 for ; Sun, 31 Jan 2016 10:56:02 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id C69532B9EED; Sun, 31 Jan 2016 11:55:58 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01691-03; Sun, 31 Jan 2016 11:55:58 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id 44A3E2B9BAB; Sun, 31 Jan 2016 11:55:58 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sun, 31 Jan 2016 11:55:57 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Sun, 31 Jan 2016 11:55:57 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgAAsMixA= Date: Sun, 31 Jan 2016 10:55:56 +0000 Message-ID: <70053d8ed80248ca9d268e1f8281e64e@ORTELIUS.internal.bugworks.com> 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> In-Reply-To: <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 31 Jan 2016 12:26:10 +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: Sun, 31 Jan 2016 10:56:07 -0000 Hello Dexuan, I would think too this would work, but it doesn't. After adding, the entry = is there, but I can not ping it. No, the nic never works. Although I can ping it from the server itself. And= ifconfig shows it as up, of course. Of course I could this as a test, the upgrade. And see if it has the same p= roblem? It looks like the nics in the 10.2 are working as such. So does Hyper-V net= working. But there is no communication between the nics in the 10.2 kernel= and the Hyper-V network environment. 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" From owner-freebsd-virtualization@freebsd.org Sun Jan 31 11:27:57 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 81A00A73878 for ; Sun, 31 Jan 2016 11:27:57 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F126EE0 for ; Sun, 31 Jan 2016 11:27:52 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 896782B9EED; Sun, 31 Jan 2016 12:27:50 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01697-04; Sun, 31 Jan 2016 12:27:50 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id 017732B9BAE; Sun, 31 Jan 2016 12:27:49 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sun, 31 Jan 2016 12:27:49 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Sun, 31 Jan 2016 12:27:49 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgAAyB/oA= Date: Sun, 31 Jan 2016 11:27:48 +0000 Message-ID: <550f854f657e47eebe92ff0a59e98748@ORTELIUS.internal.bugworks.com> 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> In-Reply-To: <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 31 Jan 2016 12:26: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: Sun, 31 Jan 2016 11:27:57 -0000 Hello Dexuan, Out of the blue, now it works! After my test with the static arp entry, I found the following: http://unix.stackexchange.com/questions/247569/freebsd-adding-ip-alias-to-i= nterface-breaks-network-on-primary-ip So I rebooted the 10.2 kernel again, to test this. Nothing else. And networ= king worked! I am completely baffled. When it starts working like this, it could stop working again as easy, so i= t would be nice to know what the problem is. 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" From owner-freebsd-virtualization@freebsd.org Sun Jan 31 11:38:17 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 38C75A73DE7 for ; Sun, 31 Jan 2016 11:38:17 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B80D686D for ; Sun, 31 Jan 2016 11:38:09 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 715092B9F0A; Sun, 31 Jan 2016 12:38:07 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01693-01; Sun, 31 Jan 2016 12:38:06 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id C7C702B9BE5; Sun, 31 Jan 2016 12:38:06 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sun, 31 Jan 2016 12:38:06 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Sun, 31 Jan 2016 12:38:06 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgAA0tsjA= Date: Sun, 31 Jan 2016 11:38:06 +0000 Message-ID: <4bd4590ce8964dae88b2e414cdee3259@ORTELIUS.internal.bugworks.com> 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> In-Reply-To: <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 31 Jan 2016 12:26:31 +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: Sun, 31 Jan 2016 11:38:17 -0000 And, yes, after a reboot is gone again. 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" From owner-freebsd-virtualization@freebsd.org Sun Jan 31 12:45:08 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 4F8DBA730D0 for ; Sun, 31 Jan 2016 12:45:08 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E42DE1FBD for ; Sun, 31 Jan 2016 12:45:06 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 437DC2B9BE4; Sun, 31 Jan 2016 13:45:03 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01690-05; Sun, 31 Jan 2016 13:45:02 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id C875E2B9BE1; Sun, 31 Jan 2016 13:45:02 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sun, 31 Jan 2016 13:45:02 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Sun, 31 Jan 2016 13:45:02 +0100 From: Jac Backus To: 'Marie Helene Kvello-Aune' , Dexuan Cui , "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/D1AASYVK4AAUkXXgAAy6DAAAApc84A== Date: Sun, 31 Jan 2016 12:45:01 +0000 Message-ID: <76d0987138834d9b9ee6a5f41d28ab76@ORTELIUS.internal.bugworks.com> 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> In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 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: Sun, 31 Jan 2016 12:45:08 -0000 SGVsbG8gTWFyaWUgSGVsZW5lLA0KDQpUaGFua3MgZm9yIHlvdXIgcmVwbHkhDQoNCkFsbCBoYXJk d2FyZSBhY2NlbGVyYXRpb24gaXMgZGlzYWJsZWQgaW4gdGhlIEh5cGVyLVYgc2V0dGluZ3MsIHNv IGlzIERIQ1AgZ3VhcmQuIEFsbCBhZGRyZXNzZXMgb2YgdGhlIFZNIGFyZSBmaXhlZC4NCkhvdyBk byBJIGNoZWNrIHRoaXMgZW5hYmxlZCBvciBkaXNhYmxlZCBpbiB0aGUgRnJlZUJTRCBWTT8gSSBk aWQgbm90IGNvbmZpZ3VyZSBpdC4NCg0KV2l0aCBraW5kIHJlZ2FyZHMsDQoNCkphYw0KDQpWYW46 IE1hcmllIEhlbGVuZSBLdmVsbG8tQXVuZSBbbWFpbHRvOm1hcmllaGVsZW5la2FAZ21haWwuY29t XQ0KVmVyem9uZGVuOiB6b25kYWcgMzEgamFudWFyaSAyMDE2IDEzOjI1DQpBYW46IERleHVhbiBD dWk7IEphYyBCYWNrdXM7IFNlcGhlIFFpYW8gKFdpY3Jlc29mdCk7IEt5bGllIExpYW5nOyBmcmVl YnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnOyBCU0QgSW50ZWdyYXRpb24gQ29tcG9uZW50 cyBmb3IgSHlwZXItVg0KT25kZXJ3ZXJwOiBSZTogSHlwZXItViBuZXR3b3JraW5nOiBwcm9ibGVt IGFmdGVyIHVwZ3JhZGUgdG8gMTAuMg0KDQpJIGhhZCB0aGlzIGlzc3VlIHdpdGggYSBXaW5kb3dz IFNlcnZlciAyMDEyIFIyIEh5cGVyLVYgaG9zdCBhbmQgRnJlZUJTRCAxMC4xIHNvbWV0aW1lIGxh c3QgeWVhciwgYnV0IGNoYWxrZWQgaXQgdXAgdG8gYSByYW5kb20gZmF1bHQgZHVyaW5nIHVwZ3Jh ZGUuIEl0IHdhc24ndCBhIHByb2R1Y3Rpb24gVk0gc28gSSBkaWRuJ3QgcHV0IG11Y2ggZWZmb3J0 IGludG8gZGVidWdnaW5nIGl0IGF0IHRoZSB0aW1lLg0KDQpJIHJlbWVtYmVyIEkgd2FzIHVzaW5n IFNSLUlPViBvbiB0aGUgdmlydHVhbCBuZXR3b3JrIHN3aXRjaCwgYW5kIGhhZCBpdCBlbmFibGVk IG9uIHRoZSBWTSBhcyB3ZWxsLiBJIGhhZCBhbHNvIGVuYWJsZWQgREhDUCBndWFyZC4gTWF5YmUg c29tZSBvZiB0aGVzZSBzZXR0aW5ncyBhcmUgcmVsZXZhbnQgdG8gcmVwcm9kdWNpbmcgdGhlIGJ1 Zz8NCg0KUmVnYXJkcywNCk1hcmllIEhlbGVuZSBLdmVsbG8tQXVuZQ0KDQpPbiBTdW4sIEphbiAz MSwgMjAxNiBhdCAxOjE1IFBNIERleHVhbiBDdWkgPGRlY3VpQG1pY3Jvc29mdC5jb208bWFpbHRv OmRlY3VpQG1pY3Jvc29mdC5jb20+PiB3cm90ZToNCkhpIEphYywNCkdvb2QgdG8ga25vdyB0aGUg aW5mb3JtYXRpb24uDQoNClNpbmNlIEkgY2FuJ3QgcmVwcm8gdGhlIGlzc3VlLCBpdCdzIGRpZmZp Y3VsdCBmb3IgbWUgdG8gZGVidWcgaXQuIDooDQpJJ20gZ3Vlc3NpbmcgaWYgaXQgd291bGQgaGVs cCBpZiB5b3UgdXNlIGEgcGVybWFuZW50IEFSUCBlbnRyeSBpbiB0aGUgVk0gKCJhcnAgLXMgaG9z dG5hbWUgZXRoZXJfYWRkciIpIGZvciB0aGUgb3RoZXIgZW5kIC0gc3VyZWx5IHRoaXMgaXMgb25s eSBmb3IgZGVidWcgcHVycG9zZS4NCg0KRHVyaW5nIHRoZSBWTSBib290LXVwLCBjYW4geW91IGtl ZXAgcGluZ2luZyB0aGUgVk0gZnJvbSB0aGUgb3RoZXIgaG9zdC4gSSBtZWFuOiBpdCBsb29rcyB0 aGUgTklDIG5ldmVyIHdvcmtzIHNpbmNlIGl0IGJlY29tZXMgVVAgaW4gdGhlIFZNPw0KDQpCVFcs IEknbSBub3Qgc3VyZSBpZiBpdCdzIGVhc3kgZm9yIHlvdSB0byBkbyB0aGUgc2FtZSB0ZXN0IGFz IG1pbmUsIGkuZS4sIGRvIGEgZnJlc2ggaW5zdGFsbGF0aW9uIG9mIDEwLjEgVk0gYW5kIHVwZ3Jh ZGUgaXQgdG8gMTAuMi4NCg0KQFNlcGhlLCBhbnkgaWRlYT8NCg0KVGhhbmtzLA0KLS0gRGV4dWFu DQoNCkZyb206IEphYyBCYWNrdXMgW21haWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb208bWFpbHRv OmouYmFja3VzQGJ1Z3dvcmtzLmNvbT5dDQpTZW50OiBTdW5kYXksIEphbnVhcnkgMzEsIDIwMTYg Mzo0Mg0KVG86IERleHVhbiBDdWkgPGRlY3VpQG1pY3Jvc29mdC5jb208bWFpbHRvOmRlY3VpQG1p Y3Jvc29mdC5jb20+PG1haWx0bzpkZWN1aUBtaWNyb3NvZnQuY29tPG1haWx0bzpkZWN1aUBtaWNy b3NvZnQuY29tPj4+OyBTZXBoZSBRaWFvIChXaWNyZXNvZnQpIDx2LXlhbnFpYUBtaWNyb3NvZnQu Y29tPG1haWx0bzp2LXlhbnFpYUBtaWNyb3NvZnQuY29tPjxtYWlsdG86di15YW5xaWFAbWljcm9z b2Z0LmNvbTxtYWlsdG86di15YW5xaWFAbWljcm9zb2Z0LmNvbT4+PjsgS3lsaWUgTGlhbmcgPGt5 bGllbEBtaWNyb3NvZnQuY29tPG1haWx0bzpreWxpZWxAbWljcm9zb2Z0LmNvbT48bWFpbHRvOmt5 bGllbEBtaWNyb3NvZnQuY29tPG1haWx0bzpreWxpZWxAbWljcm9zb2Z0LmNvbT4+PjsgJ2ZyZWVi c2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRp b25AZnJlZWJzZC5vcmc+JyA8ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWls dG86ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZz48bWFpbHRvOmZyZWVic2Qtdmly dHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJl ZWJzZC5vcmc+Pj47IEJTRCBJbnRlZ3JhdGlvbiBDb21wb25lbnRzIGZvciBIeXBlci1WIDxic2Rp Y0BtaWNyb3NvZnQuY29tPG1haWx0bzpic2RpY0BtaWNyb3NvZnQuY29tPjxtYWlsdG86YnNkaWNA bWljcm9zb2Z0LmNvbTxtYWlsdG86YnNkaWNAbWljcm9zb2Z0LmNvbT4+Pg0KU3ViamVjdDogUkU6 IEh5cGVyLVYgbmV0d29ya2luZzogcHJvYmxlbSBhZnRlciB1cGdyYWRlIHRvIDEwLjINCg0KR29v ZCBkYXkgRGV4dWFuLA0KDQpUaGVyZSBpcyBzb21ldGhpbmcgd3Jvbmcgd2l0aCBnZXR0aW5nIG1h YyBhZGRyZXNzZXMgZm9yIGhvc3Qgb24gdGhlIGxhbiwgaXQgc2VlbXMuDQoNCldoZW4gSSBwaW5n IHRoZSAxMC4yIHNlcnZlciBmcm9tIGEgaG9zdCBvbiB0aGUgbmV0LCBJIHNlZSBvbiB0aGF0IGhv c3QgIGFycCByZXF1ZXN0cyAgKFdpcmVzaGFyazogd2hvIGhhcyAuLi4gVGVsbCAuLi4pIGZvciB0 aGUgMTAuMiBzZXJ2ZXIuDQoNCkFycCAtYSBvbiB0aGUgMTAuMiBzZXJ2ZXIgaXRzZWxmIHNheXMg Zm9yIHRoZSBub24tc2VydmVyIGVudHJpZXMNCiA/IDxhZGRyZXNzPiBhdCAoaW1jb21wbGV0ZSkg b24gaG4wIGV4cGlyZWQgW2V0aGVybmV0XQ0KDQpUY3BkdW1wIG9uIHRoZSAxMC4yIHNlcnZlciBv bmx5IHNob3dzIGFycCByZXF1ZXN0czoNCkFSUCwgUmVxdWVzdCB3aG8taGFzIC4uLiB0ZWxsIC4u Lg0KDQpEb2VzIHRoaXMgaGVscD8NCg0KV2l0aCBraW5kIHJlZ2FyZHMsDQoNCkphYw0KVmFuOiBE ZXh1YW4gQ3VpIFttYWlsdG86ZGVjdWlAbWljcm9zb2Z0LmNvbTxtYWlsdG86ZGVjdWlAbWljcm9z b2Z0LmNvbT5dDQpWZXJ6b25kZW46IHZyaWpkYWcgMjkgamFudWFyaSAyMDE2IDk6NTkNCkFhbjog SmFjIEJhY2t1czsgU2VwaGUgUWlhbyAoV2ljcmVzb2Z0KTsgS3lsaWUgTGlhbmc7ICdmcmVlYnNk LXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9u QGZyZWVic2Qub3JnPic7IEJTRCBJbnRlZ3JhdGlvbiBDb21wb25lbnRzIGZvciBIeXBlci1WDQpP bmRlcndlcnA6IFJFOiBIeXBlci1WIG5ldHdvcmtpbmc6IHByb2JsZW0gYWZ0ZXIgdXBncmFkZSB0 byAxMC4yDQoNCkhtbSwgaXQncyBzdHJhbmdlIHdlIGNhbid0IHJlcHJvLg0KDQpJIHN1cHBvc2Ug eW91IGNhbid0IHBpbmcgdGhlIG5ldGdhdGUgVk0gKG9yIG1hY2hpbmUpICdzIElQIGFkZHJlc3Mg ZWl0aGVyPyBXaGVuIHRoaXMgaGFwcGVucywgY2FuIHlvdSBjaGVjayB0aGUgYXJwIHRhYmxlIGlu IGJvdGggc2lkZXM/DQpDYW4geW91IHBsZWFzZSBydW4gdGNwZHVtcCBpbiB0aGUgVk0gYW5kIGlu IHRoZSBnYXRld2F5IHRvIGRpYWdub3NlIHRoZSBpc3N1ZT8NCg0KVGhhbmtzLA0KLS0gRGV4dWFu DQoNCkZyb206IEphYyBCYWNrdXMgW21haWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb208bWFpbHRv OmouYmFja3VzQGJ1Z3dvcmtzLmNvbT5dDQpTZW50OiBGcmlkYXksIEphbnVhcnkgMjksIDIwMTYg MTU6MzYNClRvOiBEZXh1YW4gQ3VpIDxkZWN1aUBtaWNyb3NvZnQuY29tPG1haWx0bzpkZWN1aUBt aWNyb3NvZnQuY29tPjxtYWlsdG86ZGVjdWlAbWljcm9zb2Z0LmNvbTxtYWlsdG86ZGVjdWlAbWlj cm9zb2Z0LmNvbT4+PjsgU2VwaGUgUWlhbyAoV2ljcmVzb2Z0KSA8di15YW5xaWFAbWljcm9zb2Z0 LmNvbTxtYWlsdG86di15YW5xaWFAbWljcm9zb2Z0LmNvbT48bWFpbHRvOnYteWFucWlhQG1pY3Jv c29mdC5jb208bWFpbHRvOnYteWFucWlhQG1pY3Jvc29mdC5jb20+Pj47IEt5bGllIExpYW5nIDxr eWxpZWxAbWljcm9zb2Z0LmNvbTxtYWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb20+PG1haWx0bzpr eWxpZWxAbWljcm9zb2Z0LmNvbTxtYWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb20+Pj47ICdmcmVl YnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0 aW9uQGZyZWVic2Qub3JnPicgPGZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFp bHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+PG1haWx0bzpmcmVlYnNkLXZp cnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZy ZWVic2Qub3JnPj4+OyBCU0QgSW50ZWdyYXRpb24gQ29tcG9uZW50cyBmb3IgSHlwZXItViA8YnNk aWNAbWljcm9zb2Z0LmNvbTxtYWlsdG86YnNkaWNAbWljcm9zb2Z0LmNvbT48bWFpbHRvOmJzZGlj QG1pY3Jvc29mdC5jb208bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5jb20+Pj4NClN1YmplY3Q6IFJF OiBIeXBlci1WIG5ldHdvcmtpbmc6IHByb2JsZW0gYWZ0ZXIgdXBncmFkZSB0byAxMC4yDQoNCkhl bGxvIERleHVhbiwNCg0KVGhhdCByZW1hcmthYmxlLg0KTXkgdW5hbWUgLWEgaXMgaW5kZW50aWNh bC4NCg0KSSBjYW4gcGluZyBsb2NhbCBpbnRlcmZhY2VzLiBQaW5nIHRvIG90aGVyIGFkZHJlc3Nl cyBpbiBsb2NhbCBzdWJuZXQgZ2l2ZXM6IFBpbmc6IHNlbmR0bzogSG9zdCBpcyBkb3duLiBQaW5n IHRvIG90aGVyIGFkZHJlc3NlcyBnaXZlczogUGluZzogc2VuZHRvOiBObyByb3V0ZSB0byBob3N0 Lg0KUm91dGluZyB0YWJsZXMgKG5ldHN0YXQgLXJuKSBmb3IgYm90aCB2ZXJzaW9ucyBsb29rIHRo ZSBzYW1lLg0KDQpJcyB0aGVyZSBzb21ldGhpbmcgSSBjYW4gdGVzdD8NCg0KV2l0aCBraW5kIHJl Z2FyZHMsDQoNCkphYw0KDQpWYW46IERleHVhbiBDdWkgW21haWx0bzpkZWN1aUBtaWNyb3NvZnQu Y29tPG1haWx0bzpkZWN1aUBtaWNyb3NvZnQuY29tPl0NClZlcnpvbmRlbjogdnJpamRhZyAyOSBq YW51YXJpIDIwMTYgNDoyNQ0KQWFuOiBKYWMgQmFja3VzOyBTZXBoZSBRaWFvIChXaWNyZXNvZnQp OyBLeWxpZSBMaWFuZzsgJ2ZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRv OmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+JzsgQlNEIEludGVncmF0aW9uIENv bXBvbmVudHMgZm9yIEh5cGVyLVYNCk9uZGVyd2VycDogUkU6IEh5cGVyLVYgbmV0d29ya2luZzog cHJvYmxlbSBhZnRlciB1cGdyYWRlIHRvIDEwLjINCg0KDQpIaSBKYWMsDQoNCkkgaW5zdGFsbGVk IGEgMTAuMSBWTSB3aXRoIEZyZWVCU0QtMTAuMS1SRUxFQVNFLWFtZDY0LWR2ZDEuaXNvIGFuZCB1 cGdyYWRlZCBpdCB0byAxMC4yIGJ5IHJ1bm5pbmcgImZyZWVic2QtdXBkYXRlIHVwZ3JhZGUgLXIg MTAuMi1SRUxFQVNFIi4NCkV2ZXJ5dGhpbmcgd29ya2VkIGp1c3QgZmluZS4gV2l0aCB0aGUgbmV3 IGtlcm5lbCAoc2VlIHRoZSBiZWxvdyksIHNzaCBhbmQgc2NwIHN0aWxsIHdvcmtzIGZpbmUgZm9y IG1lLg0KDQojIHVuYW1lIC1hDQpGcmVlQlNEIGJzZDEwMSAxMC4yLVJFTEVBU0UtcDkgRnJlZUJT RCAxMC4yLVJFTEVBU0UtcDkgIzA6IFRodSBKYW4gMTQgMDE6MzI6NDYgVVRDIDIwMTYgICAgIHJv b3RAYW1kNjQtYnVpbGRlci5kYWVtb25vbG9neS5uZXQ6L3Vzci9vYmovdXNyL3NyYy9zeXMvR0VO RVJJQzxtYWlsdG86cm9vdEBhbWQ2NC1idWlsZGVyLmRhZW1vbm9sb2d5Lm5ldDxtYWlsdG86cm9v dEBhbWQ2NC1idWlsZGVyLmRhZW1vbm9sb2d5Lm5ldD46L3Vzci9vYmovdXNyL3NyYy9zeXMvR0VO RVJJQz4gIGFtZDY0DQoNCldoYXQncyB0aGUgc3BlY2lmaWMgc3ltcHRvbSBmb3IgIm5ldHdvcmtp bmcgZG9lcyBub3Qgd29yayBhbnltb3JlIiBpbiB5b3VyIHNpZGUodXBncmFkaW5nIGZyb20gMTAu MSB0byAxMC4yKT8NCg0KVGhhbmtzLA0KLS0gRGV4dWFuDQoNCkZyb206IEphYyBCYWNrdXMgW21h aWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb208bWFpbHRvOmouYmFja3VzQGJ1Z3dvcmtzLmNvbT5d DQpTZW50OiBXZWRuZXNkYXksIEphbnVhcnkgMjcsIDIwMTYgMTc6MzUNClRvOiBEZXh1YW4gQ3Vp IDxkZWN1aUBtaWNyb3NvZnQuY29tPG1haWx0bzpkZWN1aUBtaWNyb3NvZnQuY29tPjxtYWlsdG86 ZGVjdWlAbWljcm9zb2Z0LmNvbTxtYWlsdG86ZGVjdWlAbWljcm9zb2Z0LmNvbT4+PjsgU2VwaGUg UWlhbyAoV2ljcmVzb2Z0KSA8di15YW5xaWFAbWljcm9zb2Z0LmNvbTxtYWlsdG86di15YW5xaWFA bWljcm9zb2Z0LmNvbT48bWFpbHRvOnYteWFucWlhQG1pY3Jvc29mdC5jb208bWFpbHRvOnYteWFu cWlhQG1pY3Jvc29mdC5jb20+Pj47IEt5bGllIExpYW5nIDxreWxpZWxAbWljcm9zb2Z0LmNvbTxt YWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb20+PG1haWx0bzpreWxpZWxAbWljcm9zb2Z0LmNvbTxt YWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb20+Pj47ICdmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZy ZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPicgPGZy ZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6 YXRpb25AZnJlZWJzZC5vcmc+PG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qu b3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPj4+OyBCU0QgSW50 ZWdyYXRpb24gQ29tcG9uZW50cyBmb3IgSHlwZXItViA8YnNkaWNAbWljcm9zb2Z0LmNvbTxtYWls dG86YnNkaWNAbWljcm9zb2Z0LmNvbT48bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5jb208bWFpbHRv OmJzZGljQG1pY3Jvc29mdC5jb20+Pj4NClN1YmplY3Q6IFJFOiBIeXBlci1WIG5ldHdvcmtpbmc6 IHByb2JsZW0gYWZ0ZXIgdXBncmFkZSB0byAxMC4yDQoNCkhlbGxvIERleHVhbiwNCg0KVW5mb3J0 dW5ldGVseSwgbm8gT0FDVElWRSBmbGFnOg0KDQpobjA6IGZsYWdzPTg4NDM8VVAsQlJPQURDQVNU LFJVTk5JTkcsU0lNUExFWCxNVUxUSUNBU1Q+IG1ldHJpYyAwIG10dSAxNTAwDQogICAgICAgIG9w dGlvbnM9MzFiPFJYQ1NVTSxUWENTVU0sVkxBTl9NVFUsVkxBTl9IV1RBR0dJTkcsVFNPNCxUU082 Pg0KDQpXaXRoIGtpbmQgcmVnYXJkcywNCg0KSmFjDQoNClZhbjogRGV4dWFuIEN1aSBbbWFpbHRv OmRlY3VpQG1pY3Jvc29mdC5jb208bWFpbHRvOmRlY3VpQG1pY3Jvc29mdC5jb20+XQ0KVmVyem9u ZGVuOiB3b2Vuc2RhZyAyNyBqYW51YXJpIDIwMTYgNDowOQ0KQWFuOiBTZXBoZSBRaWFvIChXaWNy ZXNvZnQpOyBKYWMgQmFja3VzOyBLeWxpZSBMaWFuZzsgJ2ZyZWVic2QtdmlydHVhbGl6YXRpb25A ZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+Jzsg QlNEIEludGVncmF0aW9uIENvbXBvbmVudHMgZm9yIEh5cGVyLVYNCk9uZGVyd2VycDogUkU6IEh5 cGVyLVYgbmV0d29ya2luZzogcHJvYmxlbSBhZnRlciB1cGdyYWRlIHRvIDEwLjINCg0KSGkgSmFj LA0KUGxlYXNlIHNob3cgJ2lmY29uZmlnIC1hJyB3aGVuIHRoZSBpc3N1ZSBoYXBwZW5zICh3aGVu IHlvdSB1cGdyYWRlIDEwLjEgZnJvbSAxMC4yKS4NCldlIHN1c3BlY3QgaXQgbWF5IGJlIGEga25v d24gT0FDVElWRSBpc3N1ZSBhbmQgImlmY29uZmlnIC1hJyBjYW4gY29uZmlybSB0aGlzLCB0aGUg b3V0cHV0IGhhcyB0aGUgc3RyaW5nICJPQUNUSVZFIi4NCg0KSXQgbG9va3Mgc29tZWhvdyB0aGUg aXNzdWUgZG9lc24ndCBoYXBwZW4gd2hlbiB3ZSB1c2UgYSAxMC4yIGZyZXNoIGluc3RhbGxhdGlv bi4NCg0KVGhhbmtzLA0KLS0gRGV4dWFuDQoNCkZyb206IFNlcGhlIFFpYW8gKFdpY3Jlc29mdCkN ClNlbnQ6IFdlZG5lc2RheSwgSmFudWFyeSAyNywgMjAxNiA5OjEzDQpUbzogSmFjIEJhY2t1cyA8 ai5iYWNrdXNAYnVnd29ya3MuY29tPG1haWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb20+PG1haWx0 bzpqLmJhY2t1c0BidWd3b3Jrcy5jb208bWFpbHRvOmouYmFja3VzQGJ1Z3dvcmtzLmNvbT4+Pjsg RGV4dWFuIEN1aSA8ZGVjdWlAbWljcm9zb2Z0LmNvbTxtYWlsdG86ZGVjdWlAbWljcm9zb2Z0LmNv bT48bWFpbHRvOmRlY3VpQG1pY3Jvc29mdC5jb208bWFpbHRvOmRlY3VpQG1pY3Jvc29mdC5jb20+ Pj47IEt5bGllIExpYW5nIDxreWxpZWxAbWljcm9zb2Z0LmNvbTxtYWlsdG86a3lsaWVsQG1pY3Jv c29mdC5jb20+PG1haWx0bzpreWxpZWxAbWljcm9zb2Z0LmNvbTxtYWlsdG86a3lsaWVsQG1pY3Jv c29mdC5jb20+Pj47ICdmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpm cmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPicgPGZyZWVic2QtdmlydHVhbGl6YXRp b25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+ PG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNk LXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPj4+OyBCU0QgSW50ZWdyYXRpb24gQ29tcG9uZW50 cyBmb3IgSHlwZXItViA8YnNkaWNAbWljcm9zb2Z0LmNvbTxtYWlsdG86YnNkaWNAbWljcm9zb2Z0 LmNvbT48bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5jb208bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5j b20+Pj4NClN1YmplY3Q6IFJFOiBIeXBlci1WIG5ldHdvcmtpbmc6IHByb2JsZW0gYWZ0ZXIgdXBn cmFkZSB0byAxMC4yDQoNCk9oLCBwbGVhc2UgaWdub3JlIHRoaXMsIEkgdGhpbmsgaXRzIHNvbHZl ZCA6KQ0KDQpGcm9tOiBTZXBoZSBRaWFvIChXaWNyZXNvZnQpDQpTZW50OiBXZWRuZXNkYXksIEph bnVhcnkgMjcsIDIwMTYgOToxMCBBTQ0KVG86IEphYyBCYWNrdXMgPGouYmFja3VzQGJ1Z3dvcmtz LmNvbTxtYWlsdG86ai5iYWNrdXNAYnVnd29ya3MuY29tPjxtYWlsdG86ai5iYWNrdXNAYnVnd29y a3MuY29tPG1haWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb20+Pj47IERleHVhbiBDdWkgPGRlY3Vp QG1pY3Jvc29mdC5jb208bWFpbHRvOmRlY3VpQG1pY3Jvc29mdC5jb20+PG1haWx0bzpkZWN1aUBt aWNyb3NvZnQuY29tPG1haWx0bzpkZWN1aUBtaWNyb3NvZnQuY29tPj4+OyBLeWxpZSBMaWFuZyA8 a3lsaWVsQG1pY3Jvc29mdC5jb208bWFpbHRvOmt5bGllbEBtaWNyb3NvZnQuY29tPjxtYWlsdG86 a3lsaWVsQG1pY3Jvc29mdC5jb208bWFpbHRvOmt5bGllbEBtaWNyb3NvZnQuY29tPj4+OyAnZnJl ZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWlsdG86ZnJlZWJzZC12aXJ0dWFsaXph dGlvbkBmcmVlYnNkLm9yZz4nIDxmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1h aWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPjxtYWlsdG86ZnJlZWJzZC12 aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWlsdG86ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBm cmVlYnNkLm9yZz4+PjsgQlNEIEludGVncmF0aW9uIENvbXBvbmVudHMgZm9yIEh5cGVyLVYgPGJz ZGljQG1pY3Jvc29mdC5jb208bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5jb20+PG1haWx0bzpic2Rp Y0BtaWNyb3NvZnQuY29tPG1haWx0bzpic2RpY0BtaWNyb3NvZnQuY29tPj4+DQpTdWJqZWN0OiBS RTogSHlwZXItViBuZXR3b3JraW5nOiBwcm9ibGVtIGFmdGVyIHVwZ3JhZGUgdG8gMTAuMg0KDQpI aSBKYWMsDQoNCldoYXQncyB0aGUgb3V0cHV0IG9mICdpZmNvbmZpZyAtYScgd2hlbiB0aGlzIGhh cHBlbmVkPw0KDQpUaGFua3MsDQpzZXBoZQ0KDQpGcm9tOiBKYWMgQmFja3VzIFttYWlsdG86ai5i YWNrdXNAYnVnd29ya3MuY29tPG1haWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb20+XQ0KU2VudDog VHVlc2RheSwgSmFudWFyeSAyNiwgMjAxNiA2OjM3IFBNDQpUbzogRGV4dWFuIEN1aSA8ZGVjdWlA bWljcm9zb2Z0LmNvbTxtYWlsdG86ZGVjdWlAbWljcm9zb2Z0LmNvbT48bWFpbHRvOmRlY3VpQG1p Y3Jvc29mdC5jb208bWFpbHRvOmRlY3VpQG1pY3Jvc29mdC5jb20+Pj47IEt5bGllIExpYW5nIDxr eWxpZWxAbWljcm9zb2Z0LmNvbTxtYWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb20+PG1haWx0bzpr eWxpZWxAbWljcm9zb2Z0LmNvbTxtYWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb20+Pj47ICdmcmVl YnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0 aW9uQGZyZWVic2Qub3JnPicgPGZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFp bHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+PG1haWx0bzpmcmVlYnNkLXZp cnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZy ZWVic2Qub3JnPj4+OyBCU0QgSW50ZWdyYXRpb24gQ29tcG9uZW50cyBmb3IgSHlwZXItViA8YnNk aWNAbWljcm9zb2Z0LmNvbTxtYWlsdG86YnNkaWNAbWljcm9zb2Z0LmNvbT48bWFpbHRvOmJzZGlj QG1pY3Jvc29mdC5jb208bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5jb20+Pj4NClN1YmplY3Q6IFJF OiBIeXBlci1WIG5ldHdvcmtpbmc6IHByb2JsZW0gYWZ0ZXIgdXBncmFkZSB0byAxMC4yDQoNCg0K SGVsbG8gRGV4dWFuLA0KDQoNCg0KSXQgc2VlbXMsIGl0IGlzIG5vdCBjb21wbGV0ZWx5IGNvcnJl Y3QsIGFsdGhvdWdoIHRoZSBlZmZlY3QgaXMgYXMgaWYgaXQgaXMgbm90IHdvcmtpbmcuDQoNClN5 c3RhdCAtaWZzdGF0IDEgc2hvd3MgdGhpczoNCg0KW2NpZDppbWFnZTAwMS5wbmdAMDFEMTU5REEu NjVBM0EwRTBdDQoNCg0KDQpTbyBzb21ldGhpbmcgaXMgaGFwcGVuaW5nLiBCdXQgSSBjYW4gbm90 IHJlYWNoIGFueXRoaW5nLiBBbmQgdGhlIHNlcnZlciBjYW4gbm90IGJlIHJlYWNoZWQgZnJvbSB0 aGUgbGFuIChobjApIG9yIGludGVybmV0IChobjEgYW5kIGhuMikuDQoNCg0KDQpJIGdldCBhIGZp cmV3YWxsIG1lc3NhZ2UgaW4gL3Zhci9sb2cvbWVzc2FnZXMgKGZpcnN0IG1lc3NhZ2UgZnJvbSAx MToxODo1NSk6DQoNCltjaWQ6aW1hZ2UwMDIucG5nQDAxRDE1OURBLjY1QTNBMEUwXQ0KDQpCdXQg dGhpcyBpcyBqdXN0IGNhdXNlZCBieSB0aGUgcHJvYmxlbT8NCg0KDQoNCklmIEkgY2FuIGhlbHAg d2l0aCBmdXJ0aGVyIGluZm9ybWF0aW9uLCBwbGVhc2UgbGV0IG1lIGtub3cuDQoNCg0KDQpSZWdh cmRpbmcgQnVnIDE4NzAwNiwgYWxsIGludGVyZmFjZXMgaGF2ZSBmaXhlZCBhZGRyZXNzZXMuDQoN Cg0KDQpXaXRoIGtpbmQgcmVnYXJkcywNCg0KDQoNCkphYw0KDQoNCg0KDQoNCg0KDQotLS0tLU9v cnNwcm9ua2VsaWprIGJlcmljaHQtLS0tLQ0KVmFuOiBEZXh1YW4gQ3VpIFttYWlsdG86ZGVjdWlA bWljcm9zb2Z0LmNvbTxtYWlsdG86ZGVjdWlAbWljcm9zb2Z0LmNvbT5dDQpWZXJ6b25kZW46IGRp bnNkYWcgMjYgamFudWFyaSAyMDE2IDc6NTUNCkFhbjogS3lsaWUgTGlhbmc7IEphYyBCYWNrdXM7 ICdmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1 YWxpemF0aW9uQGZyZWVic2Qub3JnPic7IEJTRCBJbnRlZ3JhdGlvbiBDb21wb25lbnRzIGZvciBI eXBlci1WDQpPbmRlcndlcnA6IFJFOiBIeXBlci1WIG5ldHdvcmtpbmc6IHByb2JsZW0gYWZ0ZXIg dXBncmFkZSB0byAxMC4yDQoNCg0KDQpIaSBKYWMsDQoNCkJUVywgIHdoYXQgZG8geW91IG1lYW4g Ynkgc2F5aW5nICJuZXR3b3JraW5nIGRvZXMgbm90IHdvcmsgYW55bW9yZSIgLS0gY2FuIHlvdSBw bGVhc2UgY2hlY2sgaWYgeW91ciBpc3N1ZSBpcyB0aGUgc2FtZSBhcw0KDQoNCg0KQnVnIDE4NzAw NiAtIFtoeXBlci12XSBkeW5hbWljIGFkZHJlc3MgKGRoY3ApIG9idGFpbmluZyBkb2Vzbid0IHdv cmsgb24gSFlQRVItViBPUyAyMDEyIFIyDQoNCmh0dHBzOi8vYnVncy5mcmVlYnNkLm9yZy9idWd6 aWxsYS9zaG93X2J1Zy5jZ2k/aWQ9MTg3MDA2PGh0dHBzOi8vbmEwMS5zYWZlbGlua3MucHJvdGVj dGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNhJTJmJTJmYnVncy5mcmVlYnNkLm9yZyUyZmJ1 Z3ppbGxhJTJmc2hvd19idWcuY2dpJTNmaWQlM2QxODcwMDYmZGF0YT0wMSU3YzAxJTdjdi15YW5x aWElNDAwNjRkLm1nZC5taWNyb3NvZnQuY29tJTdjZWY4MjQ3NDQ0OWU3NDVkYTg4YzkwOGQzMjYz ZTdlNDglN2M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3YzEmc2RhdGE9MUl5UWIz eDdlY20lMmY2dUVTUW1WQUF5QXlPUXI0Wk1KM0ZrYXdwOTNkWmdRJTNkPiA/DQoNCg0KDQpUaGFu a3MsDQoNCi0tIERleHVhbg0KDQoNCg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N Cg0KPiBGcm9tOiBEZXh1YW4gQ3VpDQoNCj4gU2VudDogVHVlc2RheSwgSmFudWFyeSAyNiwgMjAx NiAxNDo0OQ0KDQo+IFRvOiBLeWxpZSBMaWFuZyA8a3lsaWVsQG1pY3Jvc29mdC5jb208bWFpbHRv Omt5bGllbEBtaWNyb3NvZnQuY29tPjxtYWlsdG86a3lsaWVsQG1pY3Jvc29mdC5jb208bWFpbHRv Omt5bGllbEBtaWNyb3NvZnQuY29tPj4+OyBKYWMgQmFja3VzDQoNCj4gPGouYmFja3VzQGJ1Z3dv cmtzLmNvbTxtYWlsdG86ai5iYWNrdXNAYnVnd29ya3MuY29tPjxtYWlsdG86ai5iYWNrdXNAYnVn d29ya3MuY29tPG1haWx0bzpqLmJhY2t1c0BidWd3b3Jrcy5jb20+Pj47ICdmcmVlYnNkLXZpcnR1 YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVi c2Qub3JnPicNCg0KPiA8ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWlsdG86 ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZz48bWFpbHRvOmZyZWVic2QtdmlydHVh bGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJz ZC5vcmc+Pj47IEJTRCBJbnRlZ3JhdGlvbiBDb21wb25lbnRzIGZvcg0KDQo+IEh5cGVyLVYgPGJz ZGljQG1pY3Jvc29mdC5jb208bWFpbHRvOmJzZGljQG1pY3Jvc29mdC5jb20+PG1haWx0bzpic2Rp Y0BtaWNyb3NvZnQuY29tPG1haWx0bzpic2RpY0BtaWNyb3NvZnQuY29tPj4+DQoNCj4gU3ViamVj dDogUkU6IEh5cGVyLVYgbmV0d29ya2luZzogcHJvYmxlbSBhZnRlciB1cGdyYWRlIHRvIDEwLjIN Cg0KPg0KDQo+IEhpIEphYywNCg0KPiBLeWxpZSBtZWFudCBkaXNhYmxpbmcgVFNPLiBQbGVhc2Ug dHJ5IHRoaXMgKCJpZmNvbmZpZyBobjAgLXRzbyIpLg0KDQo+DQoNCj4gVGhlIG1lc3NhZ2UgIiBo bjA6IHVua25vd24gc3RhdHVzIDEwNzM4NzI5MDIgcmVjZWl2ZWQiIHNob3VsZCBiZSBhbg0KDQo+ IHVubmVjZXNzYXJ5IHdhcm5pbmcgb25seS4NCg0KPiBNeSAxMC4yIFZNIGNhbiB3b3JrIGZpbmUg ZXZlbiBpZiBJIHNlZSB0aGUgbWVzc2FnZSB0b28uDQoNCj4NCg0KPiBDYW4geW91IHBsZWFzZSBp bnN0YWxsIGEgMTAuMiBWTSBmcm9tIHRoZSAxMC4yIC5JU08gZmlsZSBkaXJlY3RseSBhcyBJDQoN Cj4gZGlkIGFuZCBzZWUgaWYgaXQgd29ya3MgZm9yIHlvdT8NCg0KPg0KDQo+IEkgZ3Vlc3Mgd2Ug bmV2ZXIgdHJpZWQgdXBncmFkaW5nIDEwLjEgZnJvbSAxMC4yLg0KDQo+IENhbiB5b3UgcGxlYXNl IGxpc3QgdGhlIHN0ZXBzIGhvdyB5b3UgZGlkIHRoZSB1cGdyYWRpbmc/IFdlJ2xsIHRyeSB0aGUN Cg0KPiBzYW1lIHN0ZXBzLg0KDQo+DQoNCj4gVGhhbmtzLA0KDQo+IC0tIERleHVhbg0KDQo+DQoN Cj4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KDQo+ID4gRnJvbTogS3lsaWUgTGlhbmcN Cg0KPiA+IFNlbnQ6IFR1ZXNkYXksIEphbnVhcnkgMjYsIDIwMTYgODowMQ0KDQo+ID4gVG86IEph YyBCYWNrdXMgPGouYmFja3VzQGJ1Z3dvcmtzLmNvbTxtYWlsdG86ai5iYWNrdXNAYnVnd29ya3Mu Y29tPjxtYWlsdG86ai5iYWNrdXNAYnVnd29ya3MuY29tPG1haWx0bzpqLmJhY2t1c0BidWd3b3Jr cy5jb20+Pj47ICdmcmVlYnNkLQ0KDQo+IHZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0 bzp2aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZz48bWFpbHRvOnZpcnR1YWxpemF0aW9uQGZyZWVi c2Qub3JnPG1haWx0bzp2aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZz4+Jw0KDQo+ID4gPGZyZWVi c2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRp b25AZnJlZWJzZC5vcmc+PG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3Jn PG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPj4+OyBCU0QgSW50ZWdy YXRpb24gQ29tcG9uZW50cyBmb3INCg0KPiA+IEh5cGVyLQ0KDQo+IFYNCg0KPiA+IDxic2RpY0Bt aWNyb3NvZnQuY29tPG1haWx0bzpic2RpY0BtaWNyb3NvZnQuY29tPjxtYWlsdG86YnNkaWNAbWlj cm9zb2Z0LmNvbTxtYWlsdG86YnNkaWNAbWljcm9zb2Z0LmNvbT4+Pg0KDQo+ID4gU3ViamVjdDog UkU6IEh5cGVyLVYgbmV0d29ya2luZzogcHJvYmxlbSBhZnRlciB1cGdyYWRlIHRvIDEwLjINCg0K PiA+DQoNCj4gPiBIaSBKYWMsDQoNCj4gPg0KDQo+ID4gVGhhbmsgeW91IGZvciBhc2tpbmcuIFRv IGlzb2xhdGUgeW91ciBpc3N1ZSwgY291bGQgeW91IHBsZWFzZSB0cnkNCg0KPiA+IGRpc2FibGlu ZyBTTw0KDQo+IG9uDQoNCj4gPiB5b3VyIDEwLjIgc3lzdGVtIGZpcnN0PyBUaGFuayB5b3UuDQoN Cj4gPg0KDQo+ID4gQW5kIEkgd291bGQgbGlrZSB0byBjb25maXJtIHdpdGggeW91DQoNCj4gPiAx KSBZb3UgbWV0IGlzc3VlIGZvciAxMC4yIGtlcm5lbCArIDEwLjIgc3lzdGVtDQoNCj4gPiAyKSBO byBpc3N1ZSBmb3IgMTAuMSBrZXJuZWwgKyAxMC4xIHN5c3RlbQ0KDQo+ID4gMykgTm8gaXNzdWUg Zm9yIDEwLjEga2VybmVsICsgMTAuMiBzeXN0ZW0NCg0KPiA+DQoNCj4gPiBSaWdodD8gQW5kIGFk ZCBvdXIgZW5naW5lZXJzIGluIHRoZSBsaXN0Lg0KDQo+ID4NCg0KPiA+IFRoYW5rcywNCg0KPiA+ IEt5bGllIExpYW5nDQoNCj4gPg0KDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCg0K PiA+IEZyb206IG93bmVyLWZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRv Om93bmVyLWZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+PG1haWx0bzpvd25lci1m cmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpvd25lci1mcmVlYnNkLXZp cnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPj4NCg0KPiA+IFttYWlsdG86b3duZXItZnJlZWJzZC08 bWFpbHRvOm93bmVyLWZyZWVic2QtPiB2aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWlsdG86 dmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+PG1haWx0bzp2aXJ0dWFsaXphdGlvbkBmcmVlYnNk Lm9yZzxtYWlsdG86dmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+Pl0gT24gQmVoYWxmIE9mIEph Yw0KDQo+ID4gQmFja3VzDQoNCj4gPiBTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDI2LCAyMDE2IDU6 NTYgQU0NCg0KPiA+IFRvOiAnZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWls dG86ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZz4nDQoNCj4gPiA8ZnJlZWJzZC12 aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxtYWlsdG86ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBm cmVlYnNkLm9yZz48bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFp bHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+Pj4NCg0KPiA+IFN1YmplY3Q6 IEh5cGVyLVYgbmV0d29ya2luZzogcHJvYmxlbSBhZnRlciB1cGdyYWRlIHRvIDEwLjINCg0KPiA+ DQoNCj4gPiBEZWFyIHJlYWRlciwNCg0KPiA+DQoNCj4gPiBUb2RheSwgSSBkaWQgIHVwZ3JhZGUg IEZyZWVCU0QgMTAuMSB0byAxMC4yIHJ1bm5pbmcgb24gSHlwZXItViBvbiBhDQoNCj4gPiBmdWxs DQoNCj4gcGF0Y2hlZA0KDQo+ID4gV2luZG93cyBTZXJ2ZXIgMjAxMiBSMiB4NjQgdmVyc2lvbi4N Cg0KPiA+DQoNCj4gPiBBZnRlciB0aGUgdXBkYXRlLCBuZXR3b3JraW5nIGRvZXMgbm90IHdvcmsg YW55bW9yZS4NCg0KPiA+DQoNCj4gPiBJbiAvdmFyL2xvZy9tZXNzYWdlcyBpcyB0aGlzOg0KDQo+ ID4NCg0KPiA+IEphbiAyNSAyMTowMjowMSBtZXJjdXJpdXMga2VybmVsOiBobjA6IDxTeW50aGV0 aWMgTmV0d29yayBJbnRlcmZhY2U+DQoNCj4gPiBvbg0KDQo+ID4gdm1idXMwIEphbiAyNSAyMTow MjowMSBtZXJjdXJpdXMga2VybmVsOiBobjA6IHVua25vd24gc3RhdHVzDQoNCj4gPiAxMDczODcy OTAyIHJlY2VpdmVkIEphbiAyNSAyMTowMjowMSBtZXJjdXJpdXMga2VybmVsOiBobjA6IHVua25v d24NCg0KPiA+IHN0YXR1cyAxMDczODcyOTAyIHJlY2VpdmVkIEphbiAyNSAyMTowMjowMSBtZXJj dXJpdXMga2VybmVsOiBobjA6IGh2DQoNCj4gPiBzZW5kIG9mZmxvYWQgcmVxdWVzdCBzdWNjZWVk ZWQgSmFuIDI1IDIxOjAyOjAxIG1lcmN1cml1cyBrZXJuZWw6IGhuMDogVXNpbmcgZGVmYXVsdHMg Zm9yIFRTTzoNCg0KPiA+IDY1NTE4LzM1LzIwNDggSmFuIDI1IDIxOjAyOjAxIG1lcmN1cml1cyBr ZXJuZWw6IGhuMDogRXRoZXJuZXQgYWRkcmVzczoNCg0KPiA+IDAwOjE1OjVkOmFjOjExOjA4IEph biAyNSAyMTowMjowMSBtZXJjdXJpdXMga2VybmVsOiBobjE6IDxTeW50aGV0aWMNCg0KPiA+IE5l dHdvcmsNCg0KPiA+IEludGVyZmFjZT4gb24gdm1idXMwIEphbiAyNSAyMTowMjowMSBtZXJjdXJp dXMga2VybmVsOiBobjE6IHVua25vd24NCg0KPiA+IEludGVyZmFjZT4gc3RhdHVzDQoNCj4gPiAx MDczODcyOTAyIHJlY2VpdmVkIEphbiAyNSAyMTowMjowMSBtZXJjdXJpdXMga2VybmVsOiBobjE6 IHVua25vd24NCg0KPiA+IHN0YXR1cw0KDQo+ID4gMTA3Mzg3MjkwMiByZWNlaXZlZCBKYW4gMjUg MjE6MDI6MDEgbWVyY3VyaXVzIGtlcm5lbDogaG4xOiBodiBzZW5kDQoNCj4gPiBvZmZsb2FkIHJl cXVlc3Qgc3VjY2VlZGVkIEphbiAyNSAyMTowMjowMSBtZXJjdXJpdXMga2VybmVsOiBobjE6DQoN Cj4gPiBVc2luZyBkZWZhdWx0cyBmb3INCg0KPiBUU086DQoNCj4gPiA2NTUxOC8zNS8yMDQ4IEph biAyNSAyMTowMjowMSBtZXJjdXJpdXMga2VybmVsOiBobjE6IEV0aGVybmV0IGFkZHJlc3M6DQoN Cj4gPiAwMDoxNTo1ZDphYzoxMTowOSBKYW4gMjUgMjE6MDI6MDEgbWVyY3VyaXVzIGtlcm5lbDog aG4yOiA8U3ludGhldGljDQoNCj4gPiBOZXR3b3JrDQoNCj4gPiBJbnRlcmZhY2U+IG9uIHZtYnVz MCBKYW4gMjUgMjE6MDI6MDEgbWVyY3VyaXVzIGtlcm5lbDogaG4yOiB1bmtub3duDQoNCj4gPiBJ bnRlcmZhY2U+IHN0YXR1cw0KDQo+ID4gMTA3Mzg3MjkwMiByZWNlaXZlZCBKYW4gMjUgMjE6MDI6 MDEgbWVyY3VyaXVzIGtlcm5lbDogaG4yOiB1bmtub3duDQoNCj4gPiBzdGF0dXMNCg0KPiA+IDEw NzM4NzI5MDIgcmVjZWl2ZWQgSmFuIDI1IDIxOjAyOjAxIG1lcmN1cml1cyBrZXJuZWw6IGhuMjog aHYgc2VuZA0KDQo+ID4gb2ZmbG9hZCByZXF1ZXN0IHN1Y2NlZWRlZCBKYW4gMjUgMjE6MDI6MDEg bWVyY3VyaXVzIGtlcm5lbDogaG4yOg0KDQo+ID4gVXNpbmcgZGVmYXVsdHMgZm9yDQoNCj4gVFNP Og0KDQo+ID4gNjU1MTgvMzUvMjA0OCBKYW4gMjUgMjE6MDI6MDEgbWVyY3VyaXVzIGtlcm5lbDog aG4yOiBFdGhlcm5ldCBhZGRyZXNzOg0KDQo+ID4gMDA6MTU6NWQ6YWM6MTE6MDcNCg0KPiA+DQoN Cj4gPiBJdCB3b3JrZWQgZmluZSB3aXRoIHRoZSAxMC4xIGtlcm5lbCwgYW5kIHdoZW4gSSBib290 IHRoaXMga2VybmVsLCBpdCB3b3JrcyBhZ2FpbjoNCg0KPiA+DQoNCj4gPiBKYW4gMjUgMjI6MjA6 MDIgbWVyY3VyaXVzIGtlcm5lbDogaG4wOiA8U3ludGhldGljIE5ldHdvcmsgSW50ZXJmYWNlPg0K DQo+ID4gb24NCg0KPiA+IHZtYnVzMCBKYW4gMjUgMjI6MjA6MDIgbWVyY3VyaXVzIGtlcm5lbDog aG4wOiBFdGhlcm5ldCBhZGRyZXNzOg0KDQo+ID4gMDA6MTU6NWQ6YWM6MTE6MDcgSmFuIDI1IDIy OjIwOjAyIG1lcmN1cml1cyBrZXJuZWw6IGhuMTogPFN5bnRoZXRpYw0KDQo+ID4gTmV0d29yaw0K DQo+ID4gSW50ZXJmYWNlPiBvbiB2bWJ1czAgSmFuIDI1IDIyOjIwOjAyIG1lcmN1cml1cyBrZXJu ZWw6IGhuMTogRXRoZXJuZXQgYWRkcmVzczoNCg0KPiA+IDAwOjE1OjVkOmFjOjExOjA4IEphbiAy NSAyMjoyMDowMiBtZXJjdXJpdXMga2VybmVsOiBobjI6IDxTeW50aGV0aWMNCg0KPiA+IE5ldHdv cmsNCg0KPiA+IEludGVyZmFjZT4gb24gdm1idXMwIEphbiAyNSAyMjoyMDowMiBtZXJjdXJpdXMg a2VybmVsOiBobjI6IEV0aGVybmV0IGFkZHJlc3M6DQoNCj4gPiAwMDoxNTo1ZDphYzoxMTowOQ0K DQo+ID4NCg0KPiA+IFNvIEkgYW0gcnVubmluZyAgYSAxMC4yIHN5c3RlbSBvbiBhIDEwLjEga2Vy bmVsIGF0IHRoZSBtb21lbnQuDQoNCj4gPg0KDQo+ID4gSSBmb3VuZCBub3RoaW5nIGluIC91c3Iv c3JjL1VQREFUSU5HIGFuZCBub3QgcmVhbGx5IGFueXRoaW5nIG9uIHRoZSBuZXQuDQoNCj4gPg0K DQo+ID4gU28sIGNvdWxkIHlvdSB0ZWxsIHdoeSBkb2VzIHRoaXMgaGFwcGVuLCBhbmQgaG93IGNh biBJIHNvbHZlIHRoaXM/DQoNCj4gPg0KDQo+ID4gVGhhbmtzIGZvciB0aGUgaGVscCENCg0KPiA+ DQoNCj4gPiBXaXRoIGtpbmQgcmVnYXJkcywNCg0KPiA+DQoNCj4gPiBKYWMgQmFja3VzDQoNCj4g Pg0KDQo+ID4NCg0KPiA+DQoNCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXw0KDQo+ID4gZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZzxt YWlsdG86ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZz48bWFpbHRvOmZyZWVic2Qt dmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25A ZnJlZWJzZC5vcmc+PiBtYWlsaW5nIGxpc3QNCg0KPiA+DQoNCj4gaHR0cHM6Ly9uYTAxLnNhZmVs aW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM2ElMmYlMmZsaXN0cw0KDQo+ IC5mcmVlYnMNCg0KPiA+IGQub3JnPGh0dHA6Ly9kLm9yZz4lMmZtYWlsbWFuJTJmbGlzdGluZm8l MmZmcmVlYnNkLQ0KDQo+ID4NCg0KPiB2aXJ0dWFsaXphdGlvbiZkYXRhPTAxJTdjMDElN2NreWxp ZWwlNDAwNjRkLm1nZC5taWNyb3NvZnQuY29tPGh0dHA6Ly80MDA2NGQubWdkLm1pY3Jvc29mdC5j b20+JTdjYzljYTJlDQoNCj4gPg0KDQo+IDBkMGZlZjQ4MmI1NTNmMDhkMzI1ZDNhZWZiJTdjNzJm OTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN2MxJnMNCg0KPiA+IGRhdGE9byUyYk1aR3VC VzBmcnJRaGpBUGtocldsTGdORUg4TEo3QmlMVXlpTzR0dlIwJTNkDQoNCj4gPiBUbyB1bnN1YnNj cmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC12aXJ0dWFsaXphdGlvbi0NCg0KPiA+IHVu c3Vic2NyaWJlQGZyZWVic2Qub3JnPG1haWx0bzp1bnN1YnNjcmliZUBmcmVlYnNkLm9yZz48bWFp bHRvOnVuc3Vic2NyaWJlQGZyZWVic2Qub3JnPG1haWx0bzp1bnN1YnNjcmliZUBmcmVlYnNkLm9y Zz4+Ig0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmZy ZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6 YXRpb25AZnJlZWJzZC5vcmc+IG1haWxpbmcgbGlzdA0KaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtdmlydHVhbGl6YXRpb24NClRvIHVuc3Vic2NyaWJl LCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLXZpcnR1YWxpemF0aW9uLXVuc3Vic2NyaWJlQGZy ZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uLXVuc3Vic2NyaWJlQGZyZWVi c2Qub3JnPiINCg== From owner-freebsd-virtualization@freebsd.org Sun Jan 31 13:36:49 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 C7767A74855 for ; Sun, 31 Jan 2016 13:36:49 +0000 (UTC) (envelope-from marieheleneka@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B1571DA for ; Sun, 31 Jan 2016 13:36:49 +0000 (UTC) (envelope-from marieheleneka@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id 128so37400269wmz.1 for ; Sun, 31 Jan 2016 05:36:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=Fbiio+iUNBvX32hFlKU6pqvjy3CQbh0bah83+PvJKHQ=; b=PIbmYyugu8Ijnuls3jZIKcNTDYC52GdyQiusvVQzgwP2lVHZYO0HObBWsUvoAgG7XY g3cSzXffDJQwNwpiMR61mQDOXyrw0C8m27q3B5FTPZgLL9OuFNxKEmrZGzowXahPm4es nM1b3zmHqucm0v5Whxk+6gxki5zeWU9T5cSGFwuypLofDYFfSmOkSiJtmwACo0KiOkIR YDtJUHvNj9JYQFpaIpBjVvelkrEyamr89KG/gdim6VUQlmBCEXyyy4wR4noREarexNv0 TsMUDIg4dM63sQOizIYC/kp8uVzTroMqBcBzO7aTx79rkYuL1zY9eSLc/xWjYge88oF1 RVsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=Fbiio+iUNBvX32hFlKU6pqvjy3CQbh0bah83+PvJKHQ=; b=j382bgivyKQ52YE58hzpFTSVdMIYm8zXNuveIVEsI9FCn4eamRKZLnc8dtuQW5CGi4 UK2D20se/YcL+4/ybbUmHHlSYJvI8blkTiYs94wtaDxFWDxRlFd7EvGTG6U7a30fhllc Tm/AMUcrFkPc/E9rpDNIGgoAMZ5M/xGijoPW6uPcCpqU2678iCxXsIcG+74FXOfcSWp8 GCNLVd+1YiebDTvZ6LkM1jKMW6t7GdhfNg/RnuEN4ZoVHLgbK1goLw20t18fficP1ft+ SAVzoC5I6FSdvSa0iQayhV+WkY6SJHSBVG7OdfZNo2+AJySAAcT+ByeQFCqRtn384Vsd pGdw== X-Gm-Message-State: AG10YOQza23eJ7p66Lu5+lLmQjDSKB0384fqLOgGZu8z5/3oIvdiddI9bnTllPU308uBEzlTyblDz69AW294Tw== X-Received: by 10.28.133.141 with SMTP id h135mr6532346wmd.70.1454247407329; Sun, 31 Jan 2016 05:36:47 -0800 (PST) MIME-Version: 1.0 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> <76d0987138834d9b9ee6a5f41d28ab76@ORTELIUS.internal.bugworks.com> In-Reply-To: <76d0987138834d9b9ee6a5f41d28ab76@ORTELIUS.internal.bugworks.com> From: Marie Helene Kvello-Aune Date: Sun, 31 Jan 2016 13:36:37 +0000 Message-ID: Subject: Re: Hyper-V networking: problem after upgrade to 10.2 To: Jac Backus , Dexuan Cui , "Sephe Qiao (Wicresoft)" , Kylie Liang , "freebsd-virtualization@freebsd.org" , BSD Integration Components for Hyper-V Content-Type: text/plain; charset=UTF-8 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: Sun, 31 Jan 2016 13:36:49 -0000 Hey Jac. The setting was enabled in the VM configuration in Hyper-V, for the network card. No such configuration in the guest OS itself. As you've not enabled these features, it doesn't seem those are related to the problem. Regards, Marie Helene On Sun, Jan 31, 2016 at 1:45 PM Jac Backus wrote: > Hello Marie Helene, > > > > Thanks for your reply! > > > > All hardware acceleration is disabled in the Hyper-V settings, so is DHCP > guard. All addresses of the VM are fixed. > > How do I check this enabled or disabled in the FreeBSD VM? I did not > configure it. > > > > With kind regards, > > > > Jac > > > > *Van:* Marie Helene Kvello-Aune [mailto:marieheleneka@gmail.com] > *Verzonden:* zondag 31 januari 2016 13:25 > *Aan:* Dexuan Cui; Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; > freebsd-virtualization@freebsd.org; BSD Integration Components for Hyper-= V > *Onderwerp:* Re: Hyper-V networking: problem after upgrade to 10.2 > > > > I had this issue with a Windows Server 2012 R2 Hyper-V host and FreeBSD > 10.1 sometime last year, but chalked it up to a random fault during > upgrade. It wasn't a production VM so I didn't put much effort into > debugging it at the time. > > > > I remember I was using SR-IOV on the virtual network switch, and had it > enabled on the VM as well. I had also enabled DHCP guard. Maybe some of > these settings are relevant to reproducing the bug? > > > > Regards, > > Marie Helene Kvello-Aune > > > > On Sun, Jan 31, 2016 at 1:15 PM Dexuan Cui wrote: > > 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 fo= r > debug purpose. > > During the VM boot-up, can you keep pinging the VM from the other host. I > mean: 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., > do 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 > 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 > > 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-virtualization@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 > issue? > > Thanks, > -- Dexuan > > From: Jac Backus [mailto:j.backus@bugworks.com] > Sent: Friday, January 29, 2016 15:36 > To: Dexuan Cui >; 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 > > 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: No 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-virtualization@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 > scp 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/GENERIC > amd64 > > What's the specific symptom for "networking does not work anymore" in you= r > 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 > 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 > > Hello Dexuan, > > Unfortunetely, no OACTIVE flag: > > hn0: flags=3D8843 metric 0 mtu 15= 00 > 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-virtualization@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 > from 10.2). > We suspect it may be a known OACTIVE issue and "ifconfig -a' can confirm > this, the output has the string "OACTIVE". > > It looks somehow the issue doesn't happen when we use a 10.2 fresh > installation. > > Thanks, > -- Dexuan > > From: Sephe Qiao (Wicresoft) > Sent: Wednesday, January 27, 2016 9:13 > To: Jac Backus >; > Dexuan Cui >; Kylie Liang > >; ' > freebsd-virtualization@freebsd.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 >; > Dexuan Cui >; Kylie Liang > >; ' > freebsd-virtualization@freebsd.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 > Liang >; ' > freebsd-virtualization@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 i= s > 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 > Integration 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" -- ca= n > you please check if your issue is the same as > > > > Bug 187006 - [hyper-v] dynamic address (dhcp) obtaining doesn't work on > HYPER-V OS 2012 R2 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187006< > https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%2fbugs.f= reebsd.org%2fbugzilla%2fshow_bug.cgi%3fid%3d187006&data=3D01%7c01%7cv-yanqi= a%40064d.mgd.microsoft.com%7cef82474449e745da88c908d3263e7e48%7c72f988bf86f= 141af91ab2d7cd011db47%7c1&sdata=3D1IyQb3x7ecm%2f6uESQmVAAyAyOQr4ZMJ3Fkawp93= dZgQ%3d> > ? > > > > Thanks, > > -- Dexuan > > > > > > > -----Original Message----- > > > From: Dexuan Cui > > > Sent: Tuesday, January 26, 2016 14:49 > > > To: Kylie Liang >; > Jac Backus > > > >; ' > freebsd-virtualization@freebsd.org' > > > freebsd-virtualization@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' > > > > 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 owner-freebsd-virtualization@freebsd.org> > > > > [mailto:owner-freebsd- virtualization@freebsd.org virtualization@freebsd.org>] On Behalf Of Jac > > > > Backus > > > > Sent: Tuesday, January 26, 2016 5:56 AM > > > > To: 'freebsd-virtualization@freebsd.org' > > > > 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: > Using 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 > works 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 > address: > > > > 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 > address: > > > > 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 freebsd-virtualization@freebsd.org> mailing list > > > > > > > https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%2flist= s > > > .freebs > > > > d.org%2fmailman%2flistinfo%2ffreebsd- > > > > > > > virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2= e > > > > > > > 0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1&s > > > > data=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d > > > > To unsubscribe, send any mail to "freebsd-virtualization- > > > > unsubscribe@freebsd.org" > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > > From owner-freebsd-virtualization@freebsd.org Sun Jan 31 15:21:10 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 23A0FA73C83 for ; Sun, 31 Jan 2016 15:21:10 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BDF6F6D3 for ; Sun, 31 Jan 2016 15:21:04 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 739E32B9BE5; Sun, 31 Jan 2016 16:21:02 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 03883-04; Sun, 31 Jan 2016 16:21:01 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id E6A672B9BAC; Sun, 31 Jan 2016 16:21:01 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sun, 31 Jan 2016 16:21:01 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Sun, 31 Jan 2016 16:21:01 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgABTfDnA= Date: Sun, 31 Jan 2016 15:21:00 +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> In-Reply-To: <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 31 Jan 2016 17:43:15 +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: Sun, 31 Jan 2016 15:21:10 -0000 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" From owner-freebsd-virtualization@freebsd.org Sun Jan 31 21:00:04 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 C902FA73193 for ; Sun, 31 Jan 2016 21:00:04 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7E2C1D35 for ; Sun, 31 Jan 2016 21:00:04 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0VL01Mt085275 for ; Sun, 31 Jan 2016 21:00:04 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201601312100.u0VL01Mt085275@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention Date: Sun, 31 Jan 2016 21:00:04 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 21:00:04 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 202321 | [bhyve,patch] More verbose error reporting in bhy New | 202322 | [bhyve,patch] add option to have bhyve write its 2 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Mon Feb 1 02:28:09 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 C8708A754D0; Mon, 1 Feb 2016 02:28:09 +0000 (UTC) (envelope-from jceel@FreeBSD.org) Received: from mail1.uj.edu.pl (mail1.uj.edu.pl [149.156.89.193]) by mx1.freebsd.org (Postfix) with ESMTP id 8AC8119DC; Mon, 1 Feb 2016 02:28:06 +0000 (UTC) (envelope-from jceel@FreeBSD.org) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from [192.168.0.2] ([89.79.116.100]) by mta.uoks.uj.edu.pl (Oracle Communications Messaging Server 7u4-27.01 (7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0O1U00BCXJYAWR10@mta.uoks.uj.edu.pl>; Mon, 01 Feb 2016 03:22:59 +0100 (CET) From: jceel@FreeBSD.org Subject: VirtFS support in bhyve Message-id: <0E724C32-17FB-489A-B6E0-119CE17470E6@FreeBSD.org> Date: Mon, 01 Feb 2016 03:22:58 +0100 To: freebsd-hackers@FreeBSD.org, freebsd-virtualization@FreeBSD.org X-Mailer: Apple Mail (2.3094) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.6 at clamav1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 02:28:09 -0000 Hello, I'm working on virtio-9p (so-called VirtFS) support in bhyve. Project consists of two parts: BSD-licensed lib9p library and actual virtio-9p driver. Right now it's able to do filesystem passthrough using 9P2000.u protocol to Linux guests. You can check it out here: https://github.com/jceel/freebsd/tree/virtfs Syntax: bhyve side: append `-s ,virtio-9p,sharename=/host/path` linux side: `mount -t 9p -o trans=virtio -o version=9p2000.u sharename /mnt/guest/path` Using 9p as root filesystem for Linux guests should work too. Plans: - Definitely in-kernel 9pfs filesystem support for FreeBSD guests using same lib9p library - 9P2000.L support (adds ACLs, extattrs, file locks, atomic reads/writes and so on) - Filesystem backend using AIO - Ability to export multiple trees for different "aname" values using one virtio-9p device (that's actually a low-hanging fruit) I'm looking forward to your feedback - keep in mind that's totally experimental/incomplete/nonworking code. Jakub. From owner-freebsd-virtualization@freebsd.org Mon Feb 1 02:22:23 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 ABA10A752E1 for ; Mon, 1 Feb 2016 02:22:23 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0130.outbound.protection.outlook.com [157.56.111.130]) (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 8F99518B4 for ; Mon, 1 Feb 2016 02:22: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=UXl9ENCtmmuT38XdUbM8NDBRJKp1MQ6gN85B6KinOqU=; b=N0EG27r5B96o5ctnIxb89lvck5l6z5v8weXCETO9/M5vVf41EnafzMyt+TNImPC5ffz80CiySiAq3ebn0tODMGMWRH2pnujEm8MIq0o5moUvG2bfajQZIrCWquso+725WldEX7Ym9msu3rY9Qk2jnIJp4Y2vuMzNQz5CRDJox2o= Received: from BN3PR0301CA0020.namprd03.prod.outlook.com (10.160.180.158) by BLUPR03MB1347.namprd03.prod.outlook.com (10.163.80.25) with Microsoft SMTP Server (TLS) id 15.1.396.15; Mon, 1 Feb 2016 02:07:05 +0000 Received: from BN1AFFO11FD007.protection.gbl (2a01:111:f400:7c10::195) by BN3PR0301CA0020.outlook.office365.com (2a01:111:e400:4000::30) with Microsoft SMTP Server (TLS) id 15.1.396.15 via Frontend Transport; Mon, 1 Feb 2016 02:07:05 +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 BN1AFFO11FD007.mail.protection.outlook.com (10.58.52.67) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Mon, 1 Feb 2016 02:07:04 +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; Mon, 1 Feb 2016 02:07:01 +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; Mon, 1 Feb 2016 02:07:01 +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/D1AASYVK4AAUkXXgABTfDnAAFm9KUA== Date: Mon, 1 Feb 2016 02:07:01 +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> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [141.251.197.69] X-MS-Office365-Filtering-Correlation-Id: aba0548a-aad2-4ad6-e700-08d32aac61a0 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD007; 1:CH4wL0wvYJ3idSSXjZqPxZxsm1fNx2pmOYvL8JWuBIn5692MukgyHxB1Ci+KbUuU2DEcksNFKZTR8+tBuiZoOD9ucUp3f7E6H2RV0pJ5cjcmKhBmAPHQ50hFTUd7O2/Dv2Mru4PnRQlqCqJxtom0Jfb9WTddjH++Y/+35AxNmEjAq13ruPjd6DqOkfWKYfS9k+YtjWQkjF7sR9fgAsYlWznMSSUwNFAnYnpr8yNIxbN1LilMm93pFMdz3FrqlzqHHt24nj9lTlIQNOUoSUjWbOP6g6OxyqV4x880z7MH8h0E04M6HP6Lx9pMO+F+GouY5uMTikdM0Eu+9Rt8+3hDVQ== 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)(979002)(2980300002)(438002)(51914003)(3905003)(164054003?= =?us-ascii?Q?)(13464003)(199003)(189002)(71364002)(377454003)(15975445007?= =?us-ascii?Q?)(19625215002)(2950100001)(2906002)(50986999)(2561002)(29001?= =?us-ascii?Q?00001)(17760045003)(16796002)(106466001)(66926002)(162366750?= =?us-ascii?Q?04)(512954002)(33646002)(81156007)(19300405004)(3470700001)(?= =?us-ascii?Q?11100500001)(19617315012)(19627595001)(108616004)(99936001)(?= =?us-ascii?Q?19580395003)(93886004)(19580405001)(189998001)(4001450100002?= =?us-ascii?Q?)(10090500001)(54356999)(76176999)(66066001)(6806005)(500874?= =?us-ascii?Q?0100001)(86146001)(84326002)(87936001)(86362001)(50019601000?= =?us-ascii?Q?02)(575784001)(107886002)(18206015028)(5001770100001)(678660?= =?us-ascii?Q?02)(1511001)(300700001)(790700001)(1220700001)(10290500002)(?= =?us-ascii?Q?260700001)(102836003)(3846002)(10400500002)(6116002)(5003600?= =?us-ascii?Q?100002)(586003)(2421001)(5004730100002)(24736003)(97736004)(?= =?us-ascii?Q?86612001)(1096002)(5005710100001)(92566002)(7099028)(491001)?= =?us-ascii?Q?(959014)(559001)(569005);DIR:OUT;SFP:1102;SCL:1;SRVR:BLUPR03?= =?us-ascii?Q?MB1347;H:064-smtp-out.microsoft.com;FPR:;SPF:Pass;MLV:ovrnsp?= =?us-ascii?Q?m;A:1;MX:1;PTR:InfoDomainNonexistent;LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB1347; 2:kZuGZwEyAgLniiU5JPIRt6n+iFvd0UCQuSCDWERzMCIajs0jrBsv7wonrQ1Fd8sMJ/BJxfIlqnqkk/o0RijXi7LY8Y0ms7JeZFyDXSjtf8dlP1Hs5ezv6+I4Qq09EQE8fC1PV+r/xq4pZjygkxWi7y7/qa7Zt/4YPD2lIsy5F/mDX87gBDep2b66n9CX9ki7; 3:waJXbuORL4zExr2t3v394ZZaNnCcFXxdZ3BCEq5U35F29grHYQFR9l8Q0x5ZrloZT+MdU6fxuunjcbZLYXFe/emXEoNb4tBf269ucC5ttWDNXZXgjhX5kVR4Qf68aLQSD1rhMF39gsjmJ4ZmBh3I8ldkr/iAtRKxHL5tYu7Jeq4K1JjXnbNzpFlDrYSKI0x20+ff/UUbWL7kr4tZjewwZP1T4xMO7H+qhhXMMW3K1Swy6iuDpq61PKkuhSyc4utMurwsywlk28N2PwiJux0EDQ==; 25:oHSzw3/oB6FUfGr0Kb1mTUa2Ng82Dgd02LRxp+YyG3/zGEGzp8fY3xJU/kDcaujPxK8ht67PfqAefEqnvcpMNr0qZvh1QT/NIiTiaQco23h18+69Z5lOjb2hnBuLAvzCydanXtU69eDU9gq1SNfSYn+K2X1UbzRNUw6uqlXdgf0HmChuLV3ekqsX92EHOR7hckP28lnOKS3O7Yp0QG9mgjPyr/Rm0nr2G2MExosYloMYo6WnCAyn+oH7BquE0udAE+3gaivvVwGVydmx+HpsBjfWuHeC4mpwd0Px10o1YhI= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BLUPR03MB1347; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB1347; 20:MlNnjqKEK3UlyR35k3B++lM9tlQgqrHH/mtL2nEsni2+sNHD0ilg/b/pEhTGmCGk3QDdK4jZF3JizBU/Bw4DbrW+g4r0NQ1pq4zOZoaljGU1SZsC0tos8kDJvWyw/x/bdbE8TzTpS3i7qoQjdbcTTyvWp1ODZTLPDv826x+SSilXctoLd71ERCzyOIst2J2SgKKQLrfajZcSHLvJIb9xHEwyM7b6DtgWpu8aLKDOQwrE9a1s7DSarhukoFSjyhb56PBO1TDOfNcUig/4PhGTcrWA+uJ6ex3lxGV8ET12vrxYB0fItV6JVt2PcgaIfg5sOMmyB6o3h94LtrkdYyD31tUMc/lDrxwGa30p+EItMVAZT5Aq/ScgxSnJanqOdBX2a498nw/KIVj4JkBqHZLg1Jtx/Q4skvGmkXmrL2l7YXyz2fyuVc0piU8cHSP/h+jxCUCEOrKewD3Wx3deqKRIE0z7sosaxNgDaNKXXqBywNq/jrQWr4jZJNo3rJl5krxFAVq5/6bV6eMqwexK8cqYT+7x8cBSbxkcaGNOG0DV8KEj4AhB00Ufha+xlu2hL136B3tws86RJuBjMnMA7yy3Sw6wSNPdb+qBw+4YpIvXTHI= 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)(13016025)(8121501046)(10201501046)(3002001)(61426038)(61427038); SRVR:BLUPR03MB1347; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1347; X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB1347; 4:qu76TWGL8KMzoVijMzABuPKfooARu6iBQCj/TbiWycTw+KHlffVtPX/sfjxPXGcdHpRyo5VywXShj1BA+51wHBoN7clAyRl4rW0/ve+5UPkLhppY+IJihwJGwS2pnccP58GmWL23r7iTilmmoYrcAxoi/WBo/H6daNc/h5W3T45OKuTnYkDo1786dAsonS1eKpXYOKAS3IRSirCynPNiXge1Fd90O8U8bY0Mf59QzxdAXgiUlVOdMvQIXH28mONF2B/fDkXWkyT6vFkJhtA7z/pMolFY5jmtVX7hg6T7jycXlHo7K+1wx8IETa321UEA9nHcknw06lXVY9tcS2xWnmOjAFJVKkPs1KmET47hsUKcE6B0gbd97beuSB8fOHyZ/pxVdjfgU8t87/DT93/IJ6c1cF2CdlrNYIfJfYRt09kz2yeMuCVhySWVBbFKg0FjYNzbvrGB4MjZyMKa7DYcWWtZK97VUxObSNoxdwInHqaSCTOKf1wDAMHeBykeZeix X-Forefront-PRVS: 0839D067E7 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR03MB1347; 23:/fVaksAfiD3RZ8TBcghPzV6c+8shPK0SRr1T23w+m?= =?us-ascii?Q?94h20p+7RWcF4qlOcLUPhQHdzAZa8DruFPOtigMVRhni7pMFFtHaOYGS0rZI?= =?us-ascii?Q?AdFggebBwHV5r0C0JLGVc1ipnNfygraqt7dpwbIFYvUu9lvJ5yPosGK0XOfE?= =?us-ascii?Q?hCjraqQFlHVtlv0avBAGy845H1XP65wzfsqOtto7HQ/Q1cjtFh02i8Rq+9MP?= =?us-ascii?Q?gWAq5j4CFb95hhSPXqktNDlt5mwE53vWoKF4OdOG49nFST5CdzG0NGT+18rv?= =?us-ascii?Q?50mjb/kCGXVn3kgfVI7zCu/8PPrNKbk8MPpOPd5+X4A3umBRpa8F45Bvr8lT?= =?us-ascii?Q?CETAATNMhhfGKXEYsL8mt5v4KARjjYXxJywjvAGoSXA04wSs+RxSrsqKdvbU?= =?us-ascii?Q?XBqTGLG0JLZMTT4xjEjBvacbofBxk48mUE+ov4AFarnYvzAr//1E3/+XwUhH?= =?us-ascii?Q?QnK83PTtH6tfgHfQaXyvgPyCNaWCzunOcjNX3EZ7pyczXAe+P49oMN2TbFVV?= =?us-ascii?Q?KuKdk5IT3He5vMatwSr6HgvmxNmo+xdZ786jZnEwB1c7WoL8vqqt3zR/HcCn?= =?us-ascii?Q?knHbooTBIQNPj0KUL0yX3OpFhDrKG/M0VuilbPS+xURKnCVcvFJvvovzYVQ7?= =?us-ascii?Q?fXgFOoUYNIHyAt7h144o8CKBcpcxLBtONz1lIlN5CM4qy6TMRabrw8dckFCH?= =?us-ascii?Q?tEPmqcnY92qf84sYJmap/rbUHduSvgm52l736Cz7dh4COkFkL5Jg7tx9P8Px?= =?us-ascii?Q?0bNLX4XAs8nx0e3jP+gKYAPJGfOA8eZlkIVp50m19ViMe1Dw9Ze8vmnP9o9i?= =?us-ascii?Q?2wC9+49c832rbZqfNMpSdIZFKIAac3rruguz0cMa3escME0hJp0/VjjjwSL/?= =?us-ascii?Q?F5rKWfiKJsCvMX+4G5dZDV9PodKNZosd3tbr6ukQVV3ghCzMFZmyW0r7uzuZ?= =?us-ascii?Q?ONYNvQbQbcsheHPw6xS5cSgDvgJf8+vC+qVPWTzuSeoezHADsD2y4wer0etq?= =?us-ascii?Q?MUETgKTuI0vK7TdpS3Zrl5XZHlaWRAOQCwMvFmcuCCgYLyU2U1qyvKtkjwJK?= =?us-ascii?Q?ZUJCJBCAEOnMiFyn1UDisYdxRSoRNaTFTNFZXAMgPR98g7kpRgCkvrXnfikq?= =?us-ascii?Q?HidnBsoxeADZqKaaftqE0QHz21VPDux/uajNFIhRuMXX6e9RWff7FEuVLzqp?= =?us-ascii?Q?IXAUdCo0NJYwF9cXBYFaYGWfEXPbBkUv6ZIJHK1dlE8uoV1YW/xo3gC7mpCJ?= =?us-ascii?Q?UMzEtxOZvjxckgbjFW7FiGqsmzSuatgof7bnmYwoJVIHsSfkdWywsP6PORcV?= =?us-ascii?Q?g9ph4PSO4rWOa86PjPjP+ZyitVbchkV+qdS28Cbxp89U0XJ6TrZlBemeztgp?= =?us-ascii?Q?t3I0HvhvI+4mh3J+kB3Fg5SRC5CnPfTJP4tYCyBEz0ur3rWFk7Gj/ljzAoGu?= =?us-ascii?Q?nFSPDPG3CuVbpwIGi5bYDmXUwgg2GLzBtp4BqUzEvmvWvk/JmeLG7Ajzotwt?= =?us-ascii?Q?HgEIeisd/MAq1RaMUPGqOYEUgNMmjxY+cvE0Yh7UlL6c2e/ZTPn7AbD969r5?= =?us-ascii?Q?phlhBEMKyCx9DiSXOREl2LXqHwTdtSr39I2eKw9Mp+Q6Fa9S63kd+Kj5JEk9?= =?us-ascii?Q?i+Rb20zU9hxzBf8HbYpfKkHOAQY9NGF2agiRqF4JIbF3iMUbV8gbeQOhyl2+?= =?us-ascii?Q?Ut5oS+GqoaPjcQh6ciYN9pnN7RhQnKOqcivdG03NMOHGnqauBGWAvhhKZo0+?= =?us-ascii?Q?zzU6RR24c0BC0+o1MSm18hA7z56ywux9GxDDrdXOdtp/o6FAa16/qU9+INVN?= =?us-ascii?Q?DFhkalwBlsfGr2bXOt6+F1hR1Vb0aDe375n/Dr3XYexN89C5gmtBXOrVel99?= =?us-ascii?Q?7aOPaeBeNjgiAXYvwIMKo2MPSQ9e/Rk0Q38ijjqqfAWPBtNxondl7D43s9qK?= =?us-ascii?Q?NIW2yZhohzwCLzyf20xSyRuEf33JrTRU49uoa7sQh8LIjBv9pivuzl7tz+c8?= =?us-ascii?Q?B1RUxK7aelB1EtaoiIasGsg?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB1347; 5:PYgeA8qbD6f/hW/7EYftWOiwYz55hSevRpGROuIahvTWXOB6jsUEuL9IbtjnIhq/QxwWgAi5kRHwrQ4aAhw3WlVgT/Q1+JAYXGmWNSBZuQNjktATNg8wMd7LZH9eYN6itJw1hY+9VYsQ4AlK8MQsTg==; 24:dSi8yX+hO6hsFCd7clW/IYOgrbrxBuqNOcMXYGnjrZNQ+jZqCsnmYrFfKC5Z/3QUdh+8PshBz+fP6/HN1QqNYS98TJRqAUFH98yYBCddPpk= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Feb 2016 02:07:04.1936 (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: BLUPR03MB1347 X-Mailman-Approved-At: Mon, 01 Feb 2016 03:19:24 +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: Mon, 01 Feb 2016 02:22:23 -0000 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 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, 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" From owner-freebsd-virtualization@freebsd.org Mon Feb 1 09:17:04 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 5A347A75577 for ; Mon, 1 Feb 2016 09:17:04 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 75AEB1592 for ; Mon, 1 Feb 2016 09:16:59 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 0CC952B9BE5; Mon, 1 Feb 2016 10:16:51 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01728-02; Mon, 1 Feb 2016 10:16:50 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id 7B2292B9BAE; Mon, 1 Feb 2016 10:16:50 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Mon, 1 Feb 2016 10:16:49 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Mon, 1 Feb 2016 10:16:49 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQ Date: Mon, 1 Feb 2016 09:16:49 +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> In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 01 Feb 2016 12:15:30 +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: Mon, 01 Feb 2016 09:17:04 -0000 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" From owner-freebsd-virtualization@freebsd.org Mon Feb 1 09:56:38 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 86DF4A9758E for ; Mon, 1 Feb 2016 09:56:38 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0123.outbound.protection.outlook.com [207.46.100.123]) (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 E9C51967 for ; Mon, 1 Feb 2016 09:56:37 +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=WpBrUursilgbO1ZrUgO2aDIrBJstzKcR8keOV+vPIZU=; b=GAidFrMwQlDbJEb3BDppmwZDDubEFxfBIYkYViMwTefS1MBq/3kKMd0UNRRnjg/D8+DhVl4oEnOXEHvk6j1uCD4tt1SmMYJAET/zz6Jxhg5MHnFJNvHpSF+1sZVP6lV9hYFqEb/uMhODZKrQAVmkERzP52Bct0LBRPQD9sp6Ync= Received: from BN3PR0301CA0030.namprd03.prod.outlook.com (10.160.180.168) by BN3PR0301MB0834.namprd03.prod.outlook.com (10.160.154.144) with Microsoft SMTP Server (TLS) id 15.1.396.15; Mon, 1 Feb 2016 09:40:41 +0000 Received: from BL2FFO11FD049.protection.gbl (2a01:111:f400:7c09::152) by BN3PR0301CA0030.outlook.office365.com (2a01:111:e400:4000::40) with Microsoft SMTP Server (TLS) id 15.1.396.15 via Frontend Transport; Mon, 1 Feb 2016 09:40:41 +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 BL2FFO11FD049.mail.protection.outlook.com (10.173.161.211) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Mon, 1 Feb 2016 09:40:40 +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; Mon, 1 Feb 2016 09:40:36 +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; Mon, 1 Feb 2016 09:40:36 +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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAA= Date: Mon, 1 Feb 2016 09:40:36 +0000 Message-ID: <4a98b41221ed4c3b84a8c733aa23f24d@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> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [141.251.56.133] X-MS-Office365-Filtering-Correlation-Id: 0151be1c-d758-4750-c6a4-08d32aebbf55 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BL2FFO11FD049; 1:8d2r7WqBxjgdPqxrlSDFiMDWt7PXn2y5VISToF4PInQzm+FxsfuOATyUP0Wthi8JApO2/9m+Wu3/zKr/1N1SRL7TA4e5cq8pJ2vbegWV+ycUHpR3y+h5TTILkwtCFL6py2HhGWfYxHxjZZYvRFGBmyxYPYte9FAt65j3Z6dLrgO1MUgnexlyOIchesG1JaiEYvwcT0v7db3W+eIG2BTMtLZSL4HauGZ/W/ByDKKBBrd0xB0cAGzWtM/kR7FAgJ6lti9MKkS2Bf3cB95G99qCZW5I0XCu2rqbTW3rIf1RebJ+oxq2T6AYCWq0PnYTvLy4zy7D5Wb4oKjalPp0AUggYA== X-Forefront-Antispam-Report: CIP:23.103.249.84; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(2980300002)(438002)(51914003)(71364002)(164054003)(189002)(13464003)(3905003)(199003)(377454003)(10400500002)(11100500001)(10090500001)(2906002)(512954002)(86612001)(86362001)(66066001)(5008740100001)(66926002)(19580395003)(6806005)(3470700001)(5005710100001)(19625215002)(10290500002)(1511001)(33646002)(260700001)(5003600100002)(586003)(24736003)(19580405001)(5004730100002)(16796002)(84326002)(300700001)(4001450100002)(17760045003)(790700001)(19300405004)(3846002)(102836003)(108616004)(5001770100001)(2561002)(106466001)(54356999)(76176999)(107886002)(189998001)(86146001)(93886004)(50986999)(2950100001)(92566002)(99936001)(1220700001)(16236675004)(19627595001)(19617315012)(575784001)(15975445007)(1096002)(67866002)(87936001)(18206015028)(5001960100002)(7099028)(491001)(579004)(559001)(562774006); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0301MB0834; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; MLV:sfv; MX:1; A:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BN3PR0301MB0834; 2:WYKLnYTKoDu0Jh4PnqKlkLdo257lrh/88MKN/5JoRX1Rts+mwkE1+TCnlWIyc/9ZiuHNayd2+CX52O0gm5AY+DFyrVsrcyWtb8/ME5Yq9GgMrveeoWd0dlglK1ugDhLPhSl/C2XPURC4t50R3wHR4iVgVn0/yHwGDOIDBL4BnmGSrbdgVBY/eHVIBa4DD5Wl; 3:hbtGYTPjXPmYSf2csLVcAyZcAI/+YZhu/U/7V9Kh61UUL87Gg02KhAsyhXFJznueIfRomuTA8jLRAVpsyvMwnHi6XFRaLu0UqVFbMieN9FVrjbiEdMB62vTUpp1+N92A+9YEpwMvUehOzfC1hcRR/8bTCyxwZSpHnNZB2h+kE3JphkUaTwDFeL4UadBlGPleu0/Do43PDQQUruAnDskhnsNQ03gMe+hat9lXo8cQUwVJBpBmuc4CJmaUYkP/lLMry2K+3gvUF7HhF/rG25YBXw==; 25:+3QsaAm+LbabCEPq2gTxAWJmi90jlBQxbKm02CIkm1e8Lx3x6DXOX0s3PhO0JFMP6V6yfK9WIePs33k39//YAHA5PSJcY292gvpM5npZ7fwn+IPyFH67WgccaF1tWqi9JJAqaYnwc9dDo4fExHJ8H0Q9rbo923mutzgA9kBX0yrcptfYLbjwtLXS6L24D0qBNaMnCX7A+Bkm6bdOzH65v7NxS7hhN53BQ0qR7snpTLSe/VgBpeKWu2fF9R04d1Gu9q1Gumb6t8lkepJxHIkqOwMlRytK+DstlNJhajtiorQ= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BN3PR0301MB0834; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BN3PR0301MB0834; 20:VuKAOhY//CW7u/cIbzjunwi5Vmw4fyI6yyXEM9GKqDqxwmdbsfoqJY5bV+AbSO0rIZIXI3kz1OHcOS+uTtp02cs//BHIHqjA3BCz5R63J1ZS+MgHI8hgpETxa5ZK8fX9C912vCLAlBqyfK3KP5RriGESEwRiZdqygwykkKyZR+8gbxKenandqKv1tZLGaEQ5xQB94loEUk49jqKB8LVWEnL09ybqz/uxflaY+YEd8+O9jRYWDqqPpqBVbcG+bFCW4BjWB8aFoLzBL7LYDYXXPGofAojqXSNVHPnMsooJ/a5OFGQiOlWpvZ5WWLV79KJn8wHCXgrIxkQy6m8vxF08XXC+3mJNgD2JZ3N/0J7MxGd7x5UF7car2A6tU8JsAWqOC2dGoXYg358R5XeJIo6f3YOdRUAahUk89UZUwpj3Jt8HIMHJUQk2YIXvWF7VSEwKEQigo5R2orY3aYqVCyw0VMgpl09xrgvDlTnv5EOvlCo/WiGImxZjc1xyS7iKwlMzTn+bb2xrx3G8kNG2lzxcY3z6IgCsDOZK/J6opWMnxYx0ozY3dEtP9Ewer4nY0fIx+v3jyBfjJgRymOrm3qClacaXBTx9Y7MuYDF5/0JXMCQ= 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)(13016025)(13018025)(8121501046)(3002001)(10201501046)(61426038)(61427038); SRVR:BN3PR0301MB0834; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0301MB0834; X-Microsoft-Exchange-Diagnostics: 1; BN3PR0301MB0834; 4:PdV0ZkkfftxAIJkOR76qhUTdd5bQpBE/XCLr1fJZHTlWdCnwK8uHhKAXN62QNXf3aljggIR1zWR02fQMONmdDp1dhmzJ/TKlDrxfUjV4sQ7E4yt905pL+ryeWlen56gUHEvXVepcQnZYoLkfNcJ7XCd/ZApvwf0Fhh7clp43XKn4MXoIXBNrV3Rsdew/VulUY2vLPqUeTRMKSaX2wISPA8MHFaenyu2ENgGm/CnIowkxbV7Y/qVFaPSMsRrvh+HKE3uw+h8RcFRqNTOcSy+RjAxZ9yP1Jf6307V2EK8z87TFMGMt24rhu2HounJqkjUwyh4QTBUcQS7iE6q1ZBp6WbI797ZlVZpG+fcY7elEt2FpdMLrksNTdcSd8qmHSLAm7wf1FxQC5IQUuswCZnbyAzf6yUTecuX106WecQT4+Spz2bKbIXOZ8Ru7kLdu/rI2Tv3pTeef7eCiE15iDnUXPUD/90xJvSIkZ+0QWXZk79NsKQL6X4sOwj8PqGbZuKSl X-Forefront-PRVS: 0839D067E7 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN3PR0301MB0834; 23:Iu+5JlQZbAP3vNrVGmC0wu1Z4mIIAotEqw4H6DY?= =?us-ascii?Q?JUceAJRbRYD9+PbmhxkkaoKxUKmC70Lm4VKcoesMwbIuDuDr87JaLPG1h3sH?= =?us-ascii?Q?gWTp8ViEDAU5nJdtgxAxG3LnW0aexZJuiqplxKLxGNOhx/CLjHfHy4JCGewJ?= =?us-ascii?Q?EYuUJ1/0TAD+RbPls67DFaHqSxhxDwTlsfzEYrC4AIIGf3wOs+kyHJccbgXW?= =?us-ascii?Q?eCvxX2opGiYkIUbMRTLsBX9aVMJh61DMb+4XLBLwC9M3yz9KDtl3Jk+PqvRH?= =?us-ascii?Q?N/2tZj2Q+MpRYUBA71sUsSRUR47qdn/08ancZOY3vdp4PYzVKZmtQ60aodgS?= =?us-ascii?Q?j/hGTiDetmYtzlgKC13KL4/I8nB5xiRxCeL5qqt0RiRDVyVyZu9nRsKeveyN?= =?us-ascii?Q?Lop1zddd4Cb/v9zeAcUM1+Y7JgKskP/Fh5xV48A6cSncRsJrbFsQ5Xt33YHC?= =?us-ascii?Q?WANt9qiV9TPTFCK4+XM3p5i55QeK3gHxeALOPGD5fr6/AaiaK8KFpqeXdcRV?= =?us-ascii?Q?+CSaDpQ80xXMl6jkzXJDCHLxaSDUZN5FF+QAKp3tntRGzSM65Sh/Ft9s6k1/?= =?us-ascii?Q?FbhEEBHBiQw4Iqo1ikWMmyZy2a76WEyTLs6mMyrxQEemc8cGPNMkN3/821bI?= =?us-ascii?Q?yISz/a5I2GrWEHc2MsdkguXAn0JdxGkWCXmumpvyveWh8GExqj1RriV9Ltm8?= =?us-ascii?Q?OmfMYBtajcEqPveXySRAKhu+K8OkT/Q8+fLfdg8GhCYMca9lX2miJM/tj4aL?= =?us-ascii?Q?5mn8zka8fKJOykJ3ABI77hLHwVMLCymnfbP4rocFBmAAB+9NqDghjUGmNgnD?= =?us-ascii?Q?kgx4BfRwwLc7x+6ffLgjYKKcfvTwc3RSV0bkcyphMvxoPYEYrG2npFzndwon?= =?us-ascii?Q?NPYDLtHeUHFRhbSG9RrG79DaVKIDCDXeXlS8pKdbZxWQ6GW5m+axtDympomg?= =?us-ascii?Q?ajzVhSxKIJMxyC22k3q+/rVLpIw8YQ/AqapJ2RJP3DDGYDC5TOu7ivyWQFF8?= =?us-ascii?Q?D8vJBUwOp3ufZIM3Er+zz3FRM4q9g2EpjMFL4Kzy+Be4/fYUSnG83QCkWTaA?= =?us-ascii?Q?4EGLeblUJ0t3Ie91w0Fp5KUcZbyE12bEMO1EAwi7mGjSr96dyR4r/ktFX0/9?= =?us-ascii?Q?jsBbkMAYhSraoY2cghVo69pJZwyFhyBsH3f1ZlW928sgxIy9t3IyMPfqpGcd?= =?us-ascii?Q?YUQqIbJW/fuFUwC6XmHsABzhb3AcAs32MQj4ADV/vHAG05oJ+2QVW7NDUBtA?= =?us-ascii?Q?BkTm0EmKGXGk3rvyEyJP1/4Xy05LYj6FnjSD9Ztvf1hHJ7vIS3Y/Kc9kl9Z7?= =?us-ascii?Q?xdaBAEG2ih8KWOEQHUup/hWx4U7JXiEi09Tea8ccMJHewrhstT29vAL+eilH?= =?us-ascii?Q?0/Gr7nhIPUbgxv4nkMnjiNHjbrg8KY9FnUKddktfXUJ16scBX7Qevj/I+9/n?= =?us-ascii?Q?7H0q91qUV+HbOhgKv+alN5jSPamyG79s8qkp7QQqOhyBPeFj3aBvZMmTcWYo?= =?us-ascii?Q?buHyKhLqFky1tJQNGV+1vsIyOj8OUbw7sUZeOnp8n+ZYA0606pispRGWnZfI?= =?us-ascii?Q?bdWExcScJ1EOxHjaFHHeAsWL6aEal94VVVhSNIYxE0vU7BkKE0ewNg8/6+y2?= =?us-ascii?Q?JUvSRaWqB1htxI/AubZ9U1hH569o8w9l4xNX4EGRG3EenX7YFTM4t2i2p2nP?= =?us-ascii?Q?sFVvVq/cnCLZvIBDLKfrZ+qMXPbZ9+KDStNATreRJ5EgtPKxwvbIxMvFWdyR?= =?us-ascii?Q?HCW2F9s88hLe3LCoo0UbLaPSescCzv8Xfk3Q/sw9cXhD9YLhq7LetFKzHG0U?= =?us-ascii?Q?+Dh+osd8VhaBxIMbbw4oLjK2tS/8liacX5n8nsx/mg1TR4MSLd8Lk9mXCxNv?= =?us-ascii?Q?nKD1OFCD4wXmS1yaI?= X-Microsoft-Exchange-Diagnostics: 1; BN3PR0301MB0834; 5:2Oa+uinALlMHnJ01hBmpz7ZmspHJQBe3yk0rRyZtiBXL2dcY60WyNksw5kxZP6Evub2zDuYGuc95190y0NXZB+rruagy9BgPZrIrqn/4khep6cMBl+dfiacld/D7PCFa5/Zg79tFVCIQ4CPThFZ3Lg==; 24:hueQXE3QtYLe1eFt+wDtEObPtFJrK4gCIpvryiwXBJUfCRJr/m7kv0Wtf+fr8FJDbT5JZ/Mr3Oh/QSa/OnUs+8QW9vxJBFNcmXM5kyMJXII= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Feb 2016 09:40:40.0598 (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: BN3PR0301MB0834 X-Mailman-Approved-At: Mon, 01 Feb 2016 12:15:47 +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: Mon, 01 Feb 2016 09:56:38 -0000 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 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 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" From owner-freebsd-virtualization@freebsd.org Mon Feb 1 16:09:40 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 829E5A97C29 for ; Mon, 1 Feb 2016 16:09:40 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 472ACB7E for ; Mon, 1 Feb 2016 16:09:39 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id EA32520B3F77 for ; Tue, 2 Feb 2016 02:09:37 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 80D99280A11 for ; Tue, 2 Feb 2016 02:09:37 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rCY5RijqTn-d for ; Tue, 2 Feb 2016 02:09:37 +1000 (AEST) Received: from Peters-MacBook-Pro.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 0673E2800F9; Tue, 2 Feb 2016 02:09:34 +1000 (AEST) Subject: Re: MFC of bhyve UEFI / Windows support? To: Yamagi Burmeister References: <20160112133403.32b27985cc9984042e08fea0@yamagi.org> Cc: freebsd-virtualization@freebsd.org From: Peter Grehan Message-ID: <56AF833B.6030206@freebsd.org> Date: Mon, 1 Feb 2016 08:09:31 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160112133403.32b27985cc9984042e08fea0@yamagi.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=BP8T1AkG c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=jFJIQSaiL_oA:10 a=6I5d2MoRAAAA:8 a=OnKzTgdZs4VbaPkJUYkA:9 a=pILNOxqGKmIA:10 a=Ho4ZE9sjelcA:10 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 16:09:40 -0000 Hi, > just a small question: Is a MFC of the bhyve UEFI / Windows support > planed in time for FreeBSD 10.3? Thanks to your work :), now in 10-stable as of https://svnweb.freebsd.org/changeset/base/295124 later, Peter. From owner-freebsd-virtualization@freebsd.org Tue Feb 2 14:31:40 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 D569DA99746; Tue, 2 Feb 2016 14:31:40 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A831107A; Tue, 2 Feb 2016 14:31:40 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([79.107.62.61]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M4GND-1a9llH092Z-00rqm5; Tue, 02 Feb 2016 15:31:32 +0100 Subject: Re: VirtFS support in bhyve To: jceel@FreeBSD.org, freebsd-hackers@FreeBSD.org, freebsd-virtualization@FreeBSD.org References: <0E724C32-17FB-489A-B6E0-119CE17470E6@FreeBSD.org> From: Nikos Vassiliadis Message-ID: <56B0BD7E.8080909@gmx.com> Date: Tue, 2 Feb 2016 16:30:22 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <0E724C32-17FB-489A-B6E0-119CE17470E6@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:N3x9Ogr++o6Nbt7wKKTVPGja9biOSvFG13L+Acraw6BdTJx0j6F xoGiPL/CDtI0FJiRmzvM6kA7ZhgdjGPTkpRFJDVxqd8BUgyqw4Lq2wlWBdo4X1QJ8/akrhI ZCeINQGeUqva1RmL2jOxXkvdizPf+HAijrd7doNSoFc5BnzJGmVmOgwiLiTl38ncO2Zf+r6 X9FV10GW5I/WkY6mQHorg== X-UI-Out-Filterresults: notjunk:1;V01:K0:uO2hPVc4ztc=:i4KXBhA7BO5ssUzAOmwHHJ IHt4r7Rx2l+wlLX1mPVf0q31VZQSO1O8KIAysQLZSFFORfojppme8uqDSlFWXFtljntCusVu/ FMAgOakADh9eF8j74eAz7f49omrnWC9YZ0avdpKesyRk8Tv3gaT902dXn1KY1hoYibqO3vd3a lbq6E/hXAx9nR+bo/ESpE4Tjbdb5JK5TeHIGK0imEfn9hrWFJ7BcUZ4lRXvhb/6BjR4/5Ly9B andNwPe5NqSuor64u42gk883/RJnDMXqBb7ooeG3b/ojuM77exZ1cwoPGwqzDfN+6ZIsBS594 DrSD0UsTPA5LMhiwcY0HsXqWpUa7DaZsUqFFDpRlrqMXBetv8f868d2yag0S28yFEkz1/bR3k POb1RAtTDoLXMkGlB81/BU19dT7gpYXchpQmS7rc3LpMJqM8IagzHJRVTnG9ZJo+uqagYixUR qXocWR9d0MQB09YW8WHHnpxltFBfO/EMLcByz3S8KKzMj9Ffu9oolAQOV/b7tA/VQtsVbOwVW XhHxzN3oq8NCsX0UDlcnSyAfa2QQ215Sd0HxRHYaqTvJ6Kp6P8rMAB73RTNTSnxZugYPgge3D NnOSVlN3GYYPcvZeo4rleTswzkJNKH3qZQUTXm8n2L71Yz70tG18BDKTUec6jGxXyBzoCWzib HtAcU7hgIHsHGYLOAqZYmdqALqjICAB2ChsmSNBE+0GmBeqC2yi/VuV0zIjX4OjfYEQ7DuFYt PxaHdqEH3yeWShd5YvrlA6TSiLEB98s/k5lYEQRxHBq7aosaZ2hIXcq1PVD9yuADRGBesDVhP GpF4Eoh X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 14:31:40 -0000 On 02/01/16 04:22, jceel@FreeBSD.org wrote: > Hello, > > I'm working on virtio-9p (so-called VirtFS) support in bhyve. Project consists of two parts: BSD-licensed lib9p library and actual virtio-9p driver. Right now it's able to do filesystem passthrough using 9P2000.u protocol to Linux guests. > > You can check it out here: https://github.com/jceel/freebsd/tree/virtfs > > Syntax: > bhyve side: append `-s ,virtio-9p,sharename=/host/path` > linux side: `mount -t 9p -o trans=virtio -o version=9p2000.u sharename /mnt/guest/path` > > Using 9p as root filesystem for Linux guests should work too. > > Plans: > - Definitely in-kernel 9pfs filesystem support for FreeBSD guests using same lib9p library > - 9P2000.L support (adds ACLs, extattrs, file locks, atomic reads/writes and so on) > - Filesystem backend using AIO > - Ability to export multiple trees for different "aname" values using one virtio-9p device (that's actually a low-hanging fruit) > > I'm looking forward to your feedback - keep in mind that's totally experimental/incomplete/nonworking code. > > Jakub. Hi Jakub, This is a very cool project! Does this apply to 10-STABLE also? Could you provide a patch for the people who are not familiar with github? Thanks, Nikos From owner-freebsd-virtualization@freebsd.org Tue Feb 2 18:30:53 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 9448CA99A8D for ; Tue, 2 Feb 2016 18:30:53 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A2D74119F for ; Tue, 2 Feb 2016 18:30:49 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 6EC872B5CF6; Tue, 2 Feb 2016 19:30:40 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01666-01; Tue, 2 Feb 2016 19:30:39 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id B756E2B5CEF; Tue, 2 Feb 2016 19:30:39 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Tue, 2 Feb 2016 19:28:17 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Tue, 2 Feb 2016 19:28:17 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMA== Date: Tue, 2 Feb 2016 18:28:16 +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: <4a98b41221ed4c3b84a8c733aa23f24d@HKXPR3004MB0088.064d.mgd.msft.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 02 Feb 2016 18:42: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: Tue, 02 Feb 2016 18:30:53 -0000 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" 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" From owner-freebsd-virtualization@freebsd.org Wed Feb 3 08:10:13 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 8A5E8A9A344 for ; Wed, 3 Feb 2016 08:10:13 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 032981F72 for ; Wed, 3 Feb 2016 08:10:08 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 1B9BF2B5C91; Wed, 3 Feb 2016 09:10:05 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 18758-01; Wed, 3 Feb 2016 09:10:04 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id 841FA2B5C85; Wed, 3 Feb 2016 09:10:04 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 3 Feb 2016 09:10:03 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Wed, 3 Feb 2016 09:10:03 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZA= Date: Wed, 3 Feb 2016 08:10:03 +0000 Message-ID: <5a09277abe094f5989fb145c12a511df@ORTELIUS.internal.bugworks.com> 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: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 03 Feb 2016 12:54:13 +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 08:10:13 -0000 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" 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" From owner-freebsd-virtualization@freebsd.org Wed Feb 3 16:02:59 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 7365DA9AAF0 for ; Wed, 3 Feb 2016 16:02:59 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 5E5C3120A for ; Wed, 3 Feb 2016 16:02:59 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 5A4CA106608; Wed, 3 Feb 2016 16:02:59 +0000 (UTC) Date: Wed, 3 Feb 2016 16:02:59 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5175+333+519ccacf1c2a3a95@reviews.freebsd.org Subject: [Differential] [Request, 19 lines] D5175: hyperv/hn: Add an option to always do transmission scheduling Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , Thread-Topic: D5175: hyperv/hn: Add an option to always do transmission scheduling X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk Thread-Index: OGFmNjgzYWFmZmVhMjQ0MTIwYzQ1OWJjZDg2 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_c3dca101931ab18808d7fff25e296480" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 16:02:59 -0000 --b1_c3dca101931ab18808d7fff25e296480 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit sepherosa_gmail.com created this revision. sepherosa_gmail.com added reviewers: network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com. sepherosa_gmail.com added subscribers: freebsd-net-list, freebsd-virtualization-list. REVISION SUMMARY It is off by default. This eases more experiment on hn(4). REVISION DETAIL https://reviews.freebsd.org/D5175 AFFECTED FILES sys/dev/hyperv/netvsc/hv_net_vsc.h sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c CHANGE DETAILS diff --git a/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c b/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c --- a/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c +++ b/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c @@ -534,6 +534,10 @@ SYSCTL_ADD_INT(ctx, child, OID_AUTO, "direct_tx_size", CTLFLAG_RW, &sc->hn_direct_tx_size, 0, "Size of the packet for direct transmission"); + SYSCTL_ADD_INT(ctx, child, OID_AUTO, "sched_tx", + CTLFLAG_RW, &sc->hn_sched_tx, 0, + "Always schedule transmission " + "instead of doing direct transmission"); if (unit == 0) { struct sysctl_ctx_list *dc_ctx; @@ -1602,26 +1606,31 @@ static void hn_start(struct ifnet *ifp) { - hn_softc_t *sc; + struct hn_softc *sc = ifp->if_softc; + + if (sc->hn_sched_tx) + goto do_sched; - sc = ifp->if_softc; if (NV_TRYLOCK(sc)) { int sched; sched = hn_start_locked(ifp, sc->hn_direct_tx_size); NV_UNLOCK(sc); if (!sched) return; } +do_sched: taskqueue_enqueue_fast(sc->hn_tx_taskq, &sc->hn_start_task); } static void hn_start_txeof(struct ifnet *ifp) { - hn_softc_t *sc; + struct hn_softc *sc = ifp->if_softc; + + if (sc->hn_sched_tx) + goto do_sched; - sc = ifp->if_softc; if (NV_TRYLOCK(sc)) { int sched; @@ -1633,6 +1642,7 @@ &sc->hn_start_task); } } else { +do_sched: /* * Release the OACTIVE earlier, with the hope, that * others could catch up. The task will clear the diff --git a/sys/dev/hyperv/netvsc/hv_net_vsc.h b/sys/dev/hyperv/netvsc/hv_net_vsc.h --- a/sys/dev/hyperv/netvsc/hv_net_vsc.h +++ b/sys/dev/hyperv/netvsc/hv_net_vsc.h @@ -1023,6 +1023,7 @@ int hn_txdesc_avail; int hn_txeof; + int hn_sched_tx; int hn_direct_tx_size; struct taskqueue *hn_tx_taskq; struct task hn_start_task; EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com Cc: freebsd-virtualization-list, freebsd-net-list --b1_c3dca101931ab18808d7fff25e296480 Content-Type: text/x-patch; charset=utf-8; name="D5175.12968.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D5175.12968.patch" ZGlmZiAtLWdpdCBhL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9uZXR2c2NfZHJ2X2ZyZWVic2Qu YyBiL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9uZXR2c2NfZHJ2X2ZyZWVic2QuYwotLS0gYS9z eXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNkLmMKKysrIGIvc3lzL2Rl di9oeXBlcnYvbmV0dnNjL2h2X25ldHZzY19kcnZfZnJlZWJzZC5jCkBAIC01MzQsNiArNTM0LDEw IEBACiAJU1lTQ1RMX0FERF9JTlQoY3R4LCBjaGlsZCwgT0lEX0FVVE8sICJkaXJlY3RfdHhfc2l6 ZSIsCiAJICAgIENUTEZMQUdfUlcsICZzYy0+aG5fZGlyZWN0X3R4X3NpemUsIDAsCiAJICAgICJT aXplIG9mIHRoZSBwYWNrZXQgZm9yIGRpcmVjdCB0cmFuc21pc3Npb24iKTsKKwlTWVNDVExfQURE X0lOVChjdHgsIGNoaWxkLCBPSURfQVVUTywgInNjaGVkX3R4IiwKKwkgICAgQ1RMRkxBR19SVywg JnNjLT5obl9zY2hlZF90eCwgMCwKKwkgICAgIkFsd2F5cyBzY2hlZHVsZSB0cmFuc21pc3Npb24g IgorCSAgICAiaW5zdGVhZCBvZiBkb2luZyBkaXJlY3QgdHJhbnNtaXNzaW9uIik7CiAKIAlpZiAo dW5pdCA9PSAwKSB7CiAJCXN0cnVjdCBzeXNjdGxfY3R4X2xpc3QgKmRjX2N0eDsKQEAgLTE2MDIs MjYgKzE2MDYsMzEgQEAKIHN0YXRpYyB2b2lkCiBobl9zdGFydChzdHJ1Y3QgaWZuZXQgKmlmcCkK IHsKLQlobl9zb2Z0Y190ICpzYzsKKwlzdHJ1Y3QgaG5fc29mdGMgKnNjID0gaWZwLT5pZl9zb2Z0 YzsKKworCWlmIChzYy0+aG5fc2NoZWRfdHgpCisJCWdvdG8gZG9fc2NoZWQ7CiAKLQlzYyA9IGlm cC0+aWZfc29mdGM7CiAJaWYgKE5WX1RSWUxPQ0soc2MpKSB7CiAJCWludCBzY2hlZDsKIAogCQlz Y2hlZCA9IGhuX3N0YXJ0X2xvY2tlZChpZnAsIHNjLT5obl9kaXJlY3RfdHhfc2l6ZSk7CiAJCU5W X1VOTE9DSyhzYyk7CiAJCWlmICghc2NoZWQpCiAJCQlyZXR1cm47CiAJfQorZG9fc2NoZWQ6CiAJ dGFza3F1ZXVlX2VucXVldWVfZmFzdChzYy0+aG5fdHhfdGFza3EsICZzYy0+aG5fc3RhcnRfdGFz ayk7CiB9CiAKIHN0YXRpYyB2b2lkCiBobl9zdGFydF90eGVvZihzdHJ1Y3QgaWZuZXQgKmlmcCkK IHsKLQlobl9zb2Z0Y190ICpzYzsKKwlzdHJ1Y3QgaG5fc29mdGMgKnNjID0gaWZwLT5pZl9zb2Z0 YzsKKworCWlmIChzYy0+aG5fc2NoZWRfdHgpCisJCWdvdG8gZG9fc2NoZWQ7CiAKLQlzYyA9IGlm cC0+aWZfc29mdGM7CiAJaWYgKE5WX1RSWUxPQ0soc2MpKSB7CiAJCWludCBzY2hlZDsKIApAQCAt MTYzMyw2ICsxNjQyLDcgQEAKIAkJCSAgICAmc2MtPmhuX3N0YXJ0X3Rhc2spOwogCQl9CiAJfSBl bHNlIHsKK2RvX3NjaGVkOgogCQkvKgogCQkgKiBSZWxlYXNlIHRoZSBPQUNUSVZFIGVhcmxpZXIs IHdpdGggdGhlIGhvcGUsIHRoYXQKIAkJICogb3RoZXJzIGNvdWxkIGNhdGNoIHVwLiAgVGhlIHRh c2sgd2lsbCBjbGVhciB0aGUKZGlmZiAtLWdpdCBhL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9u ZXRfdnNjLmggYi9zeXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0X3ZzYy5oCi0tLSBhL3N5cy9k ZXYvaHlwZXJ2L25ldHZzYy9odl9uZXRfdnNjLmgKKysrIGIvc3lzL2Rldi9oeXBlcnYvbmV0dnNj L2h2X25ldF92c2MuaApAQCAtMTAyMyw2ICsxMDIzLDcgQEAKIAlpbnQJCWhuX3R4ZGVzY19hdmFp bDsKIAlpbnQJCWhuX3R4ZW9mOwogCisJaW50CQlobl9zY2hlZF90eDsKIAlpbnQJCWhuX2RpcmVj dF90eF9zaXplOwogCXN0cnVjdCB0YXNrcXVldWUgKmhuX3R4X3Rhc2txOwogCXN0cnVjdCB0YXNr CWhuX3N0YXJ0X3Rhc2s7Cgo= --b1_c3dca101931ab18808d7fff25e296480-- 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" From owner-freebsd-virtualization@freebsd.org Wed Feb 3 21:09:59 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 91477A9A8A3 for ; Wed, 3 Feb 2016 21:09:59 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 7DABA1D52 for ; Wed, 3 Feb 2016 21:09:59 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 7CA0A106DB6; Wed, 3 Feb 2016 21:09:59 +0000 (UTC) Date: Wed, 3 Feb 2016 21:09:59 +0000 To: freebsd-virtualization@freebsd.org From: "adrian (Adrian Chadd)" Reply-to: D5175+333+519ccacf1c2a3a95@reviews.freebsd.org Subject: [Differential] [Accepted] D5175: hyperv/hn: Add an option to always do transmission scheduling Message-ID: <5da21ff805a214e396152d5ef093e1d4@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , Thread-Topic: D5175: hyperv/hn: Add an option to always do transmission scheduling X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: OGFmNjgzYWFmZmVhMjQ0MTIwYzQ1OWJjZDg2IFaybKc= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-Mailman-Approved-At: Wed, 03 Feb 2016 21:32:46 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 21:09:59 -0000 adrian accepted this revision. adrian added a comment. This revision has a positive review. Fine by me! REVISION DETAIL https://reviews.freebsd.org/D5175 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, adrian, network Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Wed Feb 3 23:17:57 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 3F7E3A9BA1A for ; Wed, 3 Feb 2016 23:17:57 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF4661DF5 for ; Wed, 3 Feb 2016 23:17:52 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id A6B7A2B9448; Thu, 4 Feb 2016 00:17:43 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01720-05; Thu, 4 Feb 2016 00:17:42 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id 331602B9447; Thu, 4 Feb 2016 00:17:42 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Thu, 4 Feb 2016 00:17:41 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Thu, 4 Feb 2016 00:17:41 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZAAANu3cAAenrMw Date: Wed, 3 Feb 2016 23:17:40 +0000 Message-ID: <53238096372f4362b436382a430bde57@ORTELIUS.internal.bugworks.com> 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: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] Content-Type: multipart/mixed; boundary="_007_53238096372f4362b436382a430bde57ORTELIUSinternalbugwork_" MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 03 Feb 2016 23:59:54 +0000 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 23:17:57 -0000 --_007_53238096372f4362b436382a430bde57ORTELIUSinternalbugwork_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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" --_007_53238096372f4362b436382a430bde57ORTELIUSinternalbugwork_ Content-Type: application/octet-stream; name="session001.log" Content-Description: session001.log Content-Disposition: attachment; filename="session001.log"; size=29592; creation-date="Wed, 03 Feb 2016 23:12:39 GMT"; modification-date="Wed, 03 Feb 2016 23:14:28 GMT" Content-Transfer-Encoding: base64 77u/ICMgY2F0IHN5cy9kZXYvaHlwZXJ2L3ZtYnVzL2h2X2NoYW5uZWxfbWdtdC5jDQovKi0NCiAq IENvcHlyaWdodCAoYykgMjAwOS0yMDEyIE1pY3Jvc29mdCBDb3JwLg0KICogQ29weXJpZ2h0IChj KSAyMDEyIE5ldEFwcCBJbmMuDQogKiBDb3B5cmlnaHQgKGMpIDIwMTIgQ2l0cml4IEluYy4NCiAq IEFsbCByaWdodHMgcmVzZXJ2ZWQuDQogKg0KICogUmVkaXN0cmlidXRpb24gYW5kIHVzZSBpbiBz b3VyY2UgYW5kIGJpbmFyeSBmb3Jtcywgd2l0aCBvciB3aXRob3V0DQogKiBtb2RpZmljYXRpb24s IGFyZSBwZXJtaXR0ZWQgcHJvdmlkZWQgdGhhdCB0aGUgZm9sbG93aW5nIGNvbmRpdGlvbnMNCiAq IGFyZSBtZXQ6DQogKiAxLiBSZWRpc3RyaWJ1dGlvbnMgb2Ygc291cmNlIGNvZGUgbXVzdCByZXRh aW4gdGhlIGFib3ZlIGNvcHlyaWdodA0KICogICAgbm90aWNlIHVubW9kaWZpZWQsIHRoaXMgbGlz dCBvZiBjb25kaXRpb25zLCBhbmQgdGhlIGZvbGxvd2luZw0KICogICAgZGlzY2xhaW1lci4NCiAq IDIuIFJlZGlzdHJpYnV0aW9ucyBpbiBiaW5hcnkgZm9ybSBtdXN0IHJlcHJvZHVjZSB0aGUgYWJv dmUgY29weXJpZ2h0DQogKiAgICBub3RpY2UsIHRoaXMgbGlzdCBvZiBjb25kaXRpb25zIGFuZCB0 aGUgZm9sbG93aW5nIGRpc2NsYWltZXIgaW4gdGhlDQogKiAgICBkb2N1bWVudGF0aW9uIGFuZC9v ciBvdGhlciBtYXRlcmlhbHMgcHJvdmlkZWQgd2l0aCB0aGUgZGlzdHJpYnV0aW9uLg0KICoNCiAq IFRISVMgU09GVFdBUkUgSVMgUFJPVklERUQgQlkgVEhFIEFVVEhPUiBgYEFTIElTJycgQU5EIEFO WSBFWFBSRVNTIE9SDQogKiBJTVBMSUVEIFdBUlJBTlRJRVMsIElOQ0xVRElORywgQlVUIE5PVCBM SU1JVEVEIFRPLCBUSEUgSU1QTElFRCBXQVJSQU5USUVTDQogKiBPRiBNRVJDSEFOVEFCSUxJVFkg QU5EIEZJVE5FU1MgRk9SIEEgUEFSVElDVUxBUiBQVVJQT1NFIEFSRSBESVNDTEFJTUVELg0KICog SU4gTk8gRVZFTlQgU0hBTEwgVEhFIEFVVEhPUiBCRSBMSUFCTEUgRk9SIEFOWSBESVJFQ1QsIElO RElSRUNULA0KICogSU5DSURFTlRBTCwgU1BFQ0lBTCwgRVhFTVBMQVJZLCBPUiBDT05TRVFVRU5U SUFMIERBTUFHRVMgKElOQ0xVRElORywgQlVUDQogKiBOT1QgTElNSVRFRCBUTywgUFJPQ1VSRU1F TlQgT0YgU1VCU1RJVFVURSBHT09EUyBPUiBTRVJWSUNFUzsgTE9TUyBPRiBVU0UsDQogKiBEQVRB LCBPUiBQUk9GSVRTOyBPUiBCVVNJTkVTUyBJTlRFUlJVUFRJT04pIEhPV0VWRVIgQ0FVU0VEIEFO RCBPTiBBTlkNCiAqIFRIRU9SWSBPRiBMSUFCSUxJVFksIFdIRVRIRVIgSU4gQ09OVFJBQ1QsIFNU UklDVCBMSUFCSUxJVFksIE9SIFRPUlQNCiAqIChJTkNMVURJTkcgTkVHTElHRU5DRSBPUiBPVEhF UldJU0UpIEFSSVNJTkcgSU4gQU5ZIFdBWSBPVVQgT0YgVEhFIFVTRSBPRg0KICogVEhJUyBTT0ZU V0FSRSwgRVZFTiBJRiBBRFZJU0VEIE9GIFRIRSBQT1NTSUJJTElUWSBPRiBTVUNIIERBTUFHRS4N CiAqLw0KDQojaW5jbHVkZSA8c3lzL2NkZWZzLmg+DQpfX0ZCU0RJRCgiJEZyZWVCU0Q6IHJlbGVu Zy8xMC4yL3N5cy9kZXYvaHlwZXJ2L3ZtYnVzL2h2X2NoYW5uZWxfbWdtdC5jIDI4MzI4MCAyMDE1 LTA1LTIyIDA5OjAzOjU1WiB3aHUgJCIpOw0KDQojaW5jbHVkZSA8c3lzL3BhcmFtLmg+DQojaW5j bHVkZSA8c3lzL21idWYuaD4NCg0KI2luY2x1ZGUgImh2X3ZtYnVzX3ByaXYuaCINCg0KLyoNCiAq IEludGVybmFsIGZ1bmN0aW9ucw0KICovDQoNCnN0YXRpYyB2b2lkIHZtYnVzX2NoYW5uZWxfb25f b2ZmZXIoaHZfdm1idXNfY2hhbm5lbF9tc2dfaGVhZGVyKiBoZHIpOw0Kc3RhdGljIHZvaWQgdm1i dXNfY2hhbm5lbF9vbl9vcGVuX3Jlc3VsdChodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIqIGhk cik7DQpzdGF0aWMgdm9pZCB2bWJ1c19jaGFubmVsX29uX29mZmVyX3Jlc2NpbmQoaHZfdm1idXNf Y2hhbm5lbF9tc2dfaGVhZGVyKiBoZHIpOw0Kc3RhdGljIHZvaWQgdm1idXNfY2hhbm5lbF9vbl9n cGFkbF9jcmVhdGVkKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2hlYWRlciogaGRyKTsNCnN0YXRpYyB2 b2lkIHZtYnVzX2NoYW5uZWxfb25fZ3BhZGxfdG9ybmRvd24oaHZfdm1idXNfY2hhbm5lbF9tc2df aGVhZGVyKiBoZHIpOw0Kc3RhdGljIHZvaWQgdm1idXNfY2hhbm5lbF9vbl9vZmZlcnNfZGVsaXZl cmVkKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2hlYWRlciogaGRyKTsNCnN0YXRpYyB2b2lkIHZtYnVz X2NoYW5uZWxfb25fdmVyc2lvbl9yZXNwb25zZShodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIq IGhkcik7DQpzdGF0aWMgdm9pZCB2bWJ1c19jaGFubmVsX3Byb2Nlc3Nfb2ZmZXIodm9pZCAqY29u dGV4dCk7DQpzdHJ1Y3QgaHZfdm1idXNfY2hhbm5lbCoNCiAgICB2bWJ1c19zZWxlY3Rfb3V0Z29p bmdfY2hhbm5lbChzdHJ1Y3QgaHZfdm1idXNfY2hhbm5lbCAqcHJvbWFyeSk7DQoNCi8qKg0KICog Q2hhbm5lbCBtZXNzYWdlIGRpc3BhdGNoIHRhYmxlDQogKi8NCmh2X3ZtYnVzX2NoYW5uZWxfbXNn X3RhYmxlX2VudHJ5DQogICAgZ19jaGFubmVsX21lc3NhZ2VfdGFibGVbSFZfQ0hBTk5FTF9NRVNT QUdFX0NPVU5UXSA9IHsNCiAgICAgICAgeyBIVl9DSEFOTkVMX01FU1NBR0VfSU5WQUxJRCwNCiAg ICAgICAgICAgICAgICAwLCBOVUxMIH0sDQogICAgICAgIHsgSFZfQ0hBTk5FTF9NRVNTQUdFX09G RkVSX0NIQU5ORUwsDQogICAgICAgICAgICAgICAgMCwgdm1idXNfY2hhbm5lbF9vbl9vZmZlciB9 LA0KICAgICAgICB7IEhWX0NIQU5ORUxfTUVTU0FHRV9SRVNDSU5EX0NIQU5ORUxfT0ZGRVIsDQog ICAgICAgICAgICAgICAgMCwgdm1idXNfY2hhbm5lbF9vbl9vZmZlcl9yZXNjaW5kIH0sDQogICAg ICAgIHsgSFZfQ0hBTk5FTF9NRVNTQUdFX1JFUVVFU1RfT0ZGRVJTLA0KICAgICAgICAgICAgICAg IDAsIE5VTEwgfSwNCiAgICAgICAgeyBIVl9DSEFOTkVMX01FU1NBR0VfQUxMX09GRkVSU19ERUxJ VkVSRUQsDQogICAgICAgICAgICAgICAgMSwgdm1idXNfY2hhbm5lbF9vbl9vZmZlcnNfZGVsaXZl cmVkIH0sDQogICAgICAgIHsgSFZfQ0hBTk5FTF9NRVNTQUdFX09QRU5fQ0hBTk5FTCwNCiAgICAg ICAgICAgICAgICAwLCBOVUxMIH0sDQogICAgICAgIHsgSFZfQ0hBTk5FTF9NRVNTQUdFX09QRU5f Q0hBTk5FTF9SRVNVTFQsDQogICAgICAgICAgICAgICAgMSwgdm1idXNfY2hhbm5lbF9vbl9vcGVu X3Jlc3VsdCB9LA0KICAgICAgICB7IEhWX0NIQU5ORUxfTUVTU0FHRV9DTE9TRV9DSEFOTkVMLA0K ICAgICAgICAgICAgICAgIDAsIE5VTEwgfSwNCiAgICAgICAgeyBIVl9DSEFOTkVMX01FU1NBR0VM X0dQQURMX0hFQURFUiwNCiAgICAgICAgICAgICAgICAwLCBOVUxMIH0sDQogICAgICAgIHsgSFZf Q0hBTk5FTF9NRVNTQUdFX0dQQURMX0JPRFksDQogICAgICAgICAgICAgICAgMCwgTlVMTCB9LA0K ICAgICAgICB7IEhWX0NIQU5ORUxfTUVTU0FHRV9HUEFETF9DUkVBVEVELA0KICAgICAgICAgICAg ICAgIDEsIHZtYnVzX2NoYW5uZWxfb25fZ3BhZGxfY3JlYXRlZCB9LA0KICAgICAgICB7IEhWX0NI QU5ORUxfTUVTU0FHRV9HUEFETF9URUFSRE9XTiwNCiAgICAgICAgICAgICAgICAwLCBOVUxMIH0s DQogICAgICAgIHsgSFZfQ0hBTk5FTF9NRVNTQUdFX0dQQURMX1RPUk5ET1dOLA0KICAgICAgICAg ICAgICAgIDEsIHZtYnVzX2NoYW5uZWxfb25fZ3BhZGxfdG9ybmRvd24gfSwNCiAgICAgICAgeyBI Vl9DSEFOTkVMX01FU1NBR0VfUkVMX0lEX1JFTEVBU0VELA0KICAgICAgICAgICAgICAgIDAsIE5V TEwgfSwNCiAgICAgICAgeyBIVl9DSEFOTkVMX01FU1NBR0VfSU5JVElBVEVEX0NPTlRBQ1QsDQog ICAgICAgICAgICAgICAgMCwgTlVMTCB9LA0KICAgICAgICB7IEhWX0NIQU5ORUxfTUVTU0FHRV9W RVJTSU9OX1JFU1BPTlNFLA0KICAgICAgICAgICAgICAgIDEsIHZtYnVzX2NoYW5uZWxfb25fdmVy c2lvbl9yZXNwb25zZSB9LA0KICAgICAgICB7IEhWX0NIQU5ORUxfTUVTU0FHRV9VTkxPQUQsDQog ICAgICAgICAgICAgICAgMCwgTlVMTCB9DQp9Ow0KDQoNCi8qKg0KICogSW1wbGVtZW50YXRpb24g b2YgdGhlIHdvcmsgYWJzdHJhY3Rpb24uDQogKi8NCnN0YXRpYyB2b2lkDQp3b3JrX2l0ZW1fY2Fs bGJhY2sodm9pZCAqd29yaywgaW50IHBlbmRpbmcpDQp7DQogICAgICAgIHN0cnVjdCBodl93b3Jr X2l0ZW0gKncgPSAoc3RydWN0IGh2X3dvcmtfaXRlbSAqKXdvcms7DQoNCiAgICAgICAgLyoNCiAg ICAgICAgICogU2VyaWFsaXplIHdvcmsgZXhlY3V0aW9uLg0KICAgICAgICAgKi8NCiAgICAgICAg aWYgKHctPndxLT53b3JrX3NlbWEgIT0gTlVMTCkgew0KICAgICAgICAgICAgICAgIHNlbWFfd2Fp dCh3LT53cS0+d29ya19zZW1hKTsNCiAgICAgICAgfQ0KDQogICAgICAgIHctPmNhbGxiYWNrKHct PmNvbnRleHQpOw0KDQogICAgICAgIGlmICh3LT53cS0+d29ya19zZW1hICE9IE5VTEwpIHsNCiAg ICAgICAgICAgICAgICBzZW1hX3Bvc3Qody0+d3EtPndvcmtfc2VtYSk7DQogICAgICAgIH0gDQoN CiAgICAgICAgZnJlZSh3LCBNX0RFVkJVRik7DQp9DQoNCnN0cnVjdCBodl93b3JrX3F1ZXVlKg0K aHZfd29ya19xdWV1ZV9jcmVhdGUoY2hhciogbmFtZSkNCnsNCiAgICAgICAgc3RhdGljIHVuc2ln bmVkIGludCAgICAgcWlkID0gMDsNCiAgICAgICAgY2hhciAgICAgICAgICAgICAgICAgICAgcW5h bWVbNjRdOw0KICAgICAgICBpbnQgICAgICAgICAgICAgICAgICAgICBwcmk7DQogICAgICAgIHN0 cnVjdCBodl93b3JrX3F1ZXVlKiAgIHdxOw0KDQogICAgICAgIHdxID0gbWFsbG9jKHNpemVvZihz dHJ1Y3QgaHZfd29ya19xdWV1ZSksIE1fREVWQlVGLCBNX05PV0FJVCB8IE1fWkVSTyk7DQogICAg ICAgIEtBU1NFUlQod3EgIT0gTlVMTCwgKCJFcnJvciBWTUJVUzogRmFpbGVkIHRvIGFsbG9jYXRl IHdvcmtfcXVldWVcbiIpKTsNCiAgICAgICAgaWYgKHdxID09IE5VTEwpDQogICAgICAgICAgICBy ZXR1cm4gKE5VTEwpOw0KDQogICAgICAgIC8qDQogICAgICAgICAqIFdlIHVzZSB3b3JrIGFic3Ry YWN0aW9uIHRvIGhhbmRsZSBtZXNzYWdlcw0KICAgICAgICAgKiBjb21pbmcgZnJvbSB0aGUgaG9z dCBhbmQgdGhlc2UgYXJlIHR5cGljYWxseSBvZmZlcnMuDQogICAgICAgICAqIFNvbWUgRnJlZUJz ZCBkcml2ZXJzIGFwcGVhciB0byBoYXZlIGEgY29uY3VycmVuY3kgaXNzdWUNCiAgICAgICAgICog d2hlcmUgcHJvYmUvYXR0YWNoIG5lZWRzIHRvIGJlIHNlcmlhbGl6ZWQuIFdlIGVuc3VyZSB0aGF0 DQogICAgICAgICAqIGJ5IGhhdmluZyBvbmx5IG9uZSB0aHJlYWQgcHJvY2VzcyB3b3JrIGVsZW1l bnRzIGluIGEgDQogICAgICAgICAqIHNwZWNpZmljIHF1ZXVlIGJ5IHNlcmlhbGl6aW5nIHdvcmsg ZXhlY3V0aW9uLg0KICAgICAgICAgKg0KICAgICAgICAgKi8NCiAgICAgICAgaWYgKHN0cmNtcChu YW1lLCAidm1idXNRIikgPT0gMCkgew0KICAgICAgICAgICAgcHJpID0gUElfRElTSzsNCiAgICAg ICAgfSBlbHNlIHsgLyogY29udHJvbCAqLw0KICAgICAgICAgICAgcHJpID0gUElfTkVUOw0KICAg ICAgICAgICAgLyoNCiAgICAgICAgICAgICAqIEluaXRpYWxpemUgc2VtYXBob3JlIGZvciB0aGlz IHF1ZXVlIGJ5IHBvaW50aW5nDQogICAgICAgICAgICAgKiB0byB0aGUgZ2xvYmFsZSBzZW1hcGhv cmUgdXNlZCBmb3Igc3luY2hyb25pemluZyBhbGwNCiAgICAgICAgICAgICAqIGNvbnRyb2wgbWVz c2FnZXMuDQogICAgICAgICAgICAgKi8NCiAgICAgICAgICAgIHdxLT53b3JrX3NlbWEgPSAmaHZf dm1idXNfZ19jb25uZWN0aW9uLmNvbnRyb2xfc2VtYTsNCiAgICAgICAgfQ0KDQogICAgICAgIHNw cmludGYocW5hbWUsICJodl8lc18ldSIsIG5hbWUsIHFpZCk7DQoNCiAgICAgICAgLyoNCiAgICAg ICAgICogRml4bWU6ICBGcmVlQlNEIDguMiBoYXMgYSBkaWZmZXJlbnQgcHJvdG90eXBlIGZvcg0K ICAgICAgICAgKiB0YXNrcXVldWVfY3JlYXRlKCksIGFuZCBmb3IgY2VydGFpbiBvdGhlciB0YXNr cXVldWUgZnVuY3Rpb25zLg0KICAgICAgICAgKiBXZSBuZWVkIHRvIHJlc2VhcmNoIHRoZSBpbXBs aWNhdGlvbnMgb2YgdGhlc2UgY2hhbmdlcy4NCiAgICAgICAgICogRml4bWU6ICBOb3Qgc3VyZSB3 aGVuIHRoZSBjaGFuZ2VzIHdlcmUgaW50cm9kdWNlZC4NCiAgICAgICAgICovDQogICAgICAgIHdx LT5xdWV1ZSA9IHRhc2txdWV1ZV9jcmVhdGUocW5hbWUsIE1fTk9XQUlULCB0YXNrcXVldWVfdGhy ZWFkX2VucXVldWUsDQogICAgICAgICAgICAmd3EtPnF1ZXVlDQogICAgICAgICAgICAjaWYgX19G cmVlQlNEX3ZlcnNpb24gPCA4MDAwMDANCiAgICAgICAgICAgICwgJndxLT5wcm9jDQogICAgICAg ICAgICAjZW5kaWYNCiAgICAgICAgICAgICk7DQoNCiAgICAgICAgaWYgKHdxLT5xdWV1ZSA9PSBO VUxMKSB7DQogICAgICAgICAgICBmcmVlKHdxLCBNX0RFVkJVRik7DQogICAgICAgICAgICByZXR1 cm4gKE5VTEwpOw0KICAgICAgICB9DQoNCiAgICAgICAgaWYgKHRhc2txdWV1ZV9zdGFydF90aHJl YWRzKCZ3cS0+cXVldWUsIDEsIHByaSwgIiVzIHRhc2txIiwgcW5hbWUpKSB7DQogICAgICAgICAg ICB0YXNrcXVldWVfZnJlZSh3cS0+cXVldWUpOw0KICAgICAgICAgICAgZnJlZSh3cSwgTV9ERVZC VUYpOw0KICAgICAgICAgICAgcmV0dXJuIChOVUxMKTsNCiAgICAgICAgfQ0KDQogICAgICAgIHFp ZCsrOw0KDQogICAgICAgIHJldHVybiAod3EpOw0KfQ0KDQp2b2lkDQpodl93b3JrX3F1ZXVlX2Ns b3NlKHN0cnVjdCBodl93b3JrX3F1ZXVlICp3cSkNCnsNCiAgICAgICAgLyoNCiAgICAgICAgICog S1lTOiBOZWVkIHRvIGRyYWluIHRoZSB0YXNrcXVldWUNCiAgICAgICAgICogYmVmb3JlIHdlIGNs b3NlIHRoZSBodl93b3JrX3F1ZXVlLg0KICAgICAgICAgKi8NCiAgICAgICAgLypLWVM6IHRhc2tx dWV1ZV9kcmFpbih3cS0+dHEsICk7ICovDQogICAgICAgIHRhc2txdWV1ZV9mcmVlKHdxLT5xdWV1 ZSk7DQogICAgICAgIGZyZWUod3EsIE1fREVWQlVGKTsNCn0NCg0KLyoqDQogKiBAYnJpZWYgQ3Jl YXRlIHdvcmsgaXRlbQ0KICovDQppbnQNCmh2X3F1ZXVlX3dvcmtfaXRlbSgNCiAgICAgICAgc3Ry dWN0IGh2X3dvcmtfcXVldWUgKndxLA0KICAgICAgICB2b2lkICgqY2FsbGJhY2spKHZvaWQgKiks IHZvaWQgKmNvbnRleHQpDQp7DQogICAgICAgIHN0cnVjdCBodl93b3JrX2l0ZW0gKncgPSBtYWxs b2Moc2l6ZW9mKHN0cnVjdCBodl93b3JrX2l0ZW0pLA0KICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIE1fREVWQlVGLCBNX05PV0FJVCB8IE1fWkVSTyk7DQogICAgICAgIEtB U1NFUlQodyAhPSBOVUxMLCAoIkVycm9yIFZNQlVTOiBGYWlsZWQgdG8gYWxsb2NhdGUgV29ya0l0 ZW1cbiIpKTsNCiAgICAgICAgaWYgKHcgPT0gTlVMTCkNCiAgICAgICAgICAgIHJldHVybiAoRU5P TUVNKTsNCg0KICAgICAgICB3LT5jYWxsYmFjayA9IGNhbGxiYWNrOw0KICAgICAgICB3LT5jb250 ZXh0ID0gY29udGV4dDsNCiAgICAgICAgdy0+d3EgPSB3cTsNCg0KICAgICAgICBUQVNLX0lOSVQo JnctPndvcmssIDAsIHdvcmtfaXRlbV9jYWxsYmFjaywgdyk7DQoNCiAgICAgICAgcmV0dXJuICh0 YXNrcXVldWVfZW5xdWV1ZSh3cS0+cXVldWUsICZ3LT53b3JrKSk7DQp9DQoNCg0KLyoqDQogKiBA YnJpZWYgQWxsb2NhdGUgYW5kIGluaXRpYWxpemUgYSB2bWJ1cyBjaGFubmVsIG9iamVjdA0KICov DQpodl92bWJ1c19jaGFubmVsKg0KaHZfdm1idXNfYWxsb2NhdGVfY2hhbm5lbCh2b2lkKQ0Kew0K ICAgICAgICBodl92bWJ1c19jaGFubmVsKiBjaGFubmVsOw0KDQogICAgICAgIGNoYW5uZWwgPSAo aHZfdm1idXNfY2hhbm5lbCopIG1hbGxvYygNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICBzaXplb2YoaHZfdm1idXNfY2hhbm5lbCksDQogICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgTV9ERVZCVUYsDQogICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgTV9OT1dBSVQgfCBNX1pFUk8pOw0KICAgICAgICBLQVNTRVJUKGNoYW5u ZWwgIT0gTlVMTCwgKCJFcnJvciBWTUJVUzogRmFpbGVkIHRvIGFsbG9jYXRlIGNoYW5uZWwhIikp Ow0KICAgICAgICBpZiAoY2hhbm5lbCA9PSBOVUxMKQ0KICAgICAgICAgICAgcmV0dXJuIChOVUxM KTsNCg0KICAgICAgICBtdHhfaW5pdCgmY2hhbm5lbC0+aW5ib3VuZF9sb2NrLCAiY2hhbm5lbCBp bmJvdW5kIiwgTlVMTCwgTVRYX0RFRik7DQogICAgICAgIG10eF9pbml0KCZjaGFubmVsLT5zY19s b2NrLCAidm1idXMgbXVsdGkgY2hhbm5lbCIsIE5VTEwsIE1UWF9ERUYpOw0KDQogICAgICAgIFRB SUxRX0lOSVQoJmNoYW5uZWwtPnNjX2xpc3RfYW5jaG9yKTsNCg0KICAgICAgICByZXR1cm4gKGNo YW5uZWwpOw0KfQ0KDQovKioNCiAqIEBicmllZiBSZWxlYXNlIHRoZSB2bWJ1cyBjaGFubmVsIG9i amVjdCBpdHNlbGYNCiAqLw0Kc3RhdGljIGlubGluZSB2b2lkDQpSZWxlYXNlVm1idXNDaGFubmVs KHZvaWQgKmNvbnRleHQpDQp7DQogICAgICAgIGh2X3ZtYnVzX2NoYW5uZWwqIGNoYW5uZWwgPSAo aHZfdm1idXNfY2hhbm5lbCopIGNvbnRleHQ7DQogICAgICAgIGZyZWUoY2hhbm5lbCwgTV9ERVZC VUYpOw0KfQ0KDQovKioNCiAqIEBicmllZiBSZWxlYXNlIHRoZSByZXNvdXJjZXMgdXNlZCBieSB0 aGUgdm1idXMgY2hhbm5lbCBvYmplY3QNCiAqLw0Kdm9pZA0KaHZfdm1idXNfZnJlZV92bWJ1c19j aGFubmVsKGh2X3ZtYnVzX2NoYW5uZWwqIGNoYW5uZWwpDQp7DQogICAgICAgIG10eF9kZXN0cm95 KCZjaGFubmVsLT5zY19sb2NrKTsNCiAgICAgICAgbXR4X2Rlc3Ryb3koJmNoYW5uZWwtPmluYm91 bmRfbG9jayk7DQogICAgICAgIC8qDQogICAgICAgICAqIFdlIGhhdmUgdG8gcmVsZWFzZSB0aGUg Y2hhbm5lbCdzIHdvcmtxdWV1ZS90aHJlYWQgaW4NCiAgICAgICAgICogIHRoZSB2bWJ1cydzIHdv cmtxdWV1ZS90aHJlYWQgY29udGV4dA0KICAgICAgICAgKiBpZSB3ZSBjYW4ndCBkZXN0cm95IG91 cnNlbHZlcw0KICAgICAgICAgKi8NCiAgICAgICAgaHZfcXVldWVfd29ya19pdGVtKGh2X3ZtYnVz X2dfY29ubmVjdGlvbi53b3JrX3F1ZXVlLA0KICAgICAgICAgICAgUmVsZWFzZVZtYnVzQ2hhbm5l bCwgKHZvaWQgKikgY2hhbm5lbCk7DQp9DQoNCi8qKg0KICogQGJyaWVmIFByb2Nlc3MgdGhlIG9m ZmVyIGJ5IGNyZWF0aW5nIGEgY2hhbm5lbC9kZXZpY2UNCiAqIGFzc29jaWF0ZWQgd2l0aCB0aGlz IG9mZmVyDQogKi8NCnN0YXRpYyB2b2lkDQp2bWJ1c19jaGFubmVsX3Byb2Nlc3Nfb2ZmZXIoaHZf dm1idXNfY2hhbm5lbCAqbmV3X2NoYW5uZWwpDQp7DQogICAgICAgIGJvb2xlYW5fdCAgICAgICAg ICAgICAgIGZfbmV3Ow0KICAgICAgICBodl92bWJ1c19jaGFubmVsKiAgICAgICBjaGFubmVsOw0K ICAgICAgICBpbnQgICAgICAgICAgICAgICAgICAgICByZXQ7DQoNCiAgICAgICAgZl9uZXcgPSBU UlVFOw0KICAgICAgICBjaGFubmVsID0gTlVMTDsNCg0KICAgICAgICAvKg0KICAgICAgICAgKiBN YWtlIHN1cmUgdGhpcyBpcyBhIG5ldyBvZmZlcg0KICAgICAgICAgKi8NCiAgICAgICAgbXR4X2xv Y2soJmh2X3ZtYnVzX2dfY29ubmVjdGlvbi5jaGFubmVsX2xvY2spOw0KDQogICAgICAgIFRBSUxR X0ZPUkVBQ0goY2hhbm5lbCwgJmh2X3ZtYnVzX2dfY29ubmVjdGlvbi5jaGFubmVsX2FuY2hvciwN CiAgICAgICAgICAgIGxpc3RfZW50cnkpDQogICAgICAgIHsNCiAgICAgICAgICAgICAgICBpZiAo bWVtY21wKCZjaGFubmVsLT5vZmZlcl9tc2cub2ZmZXIuaW50ZXJmYWNlX3R5cGUsDQogICAgICAg ICAgICAgICAgICAgICZuZXdfY2hhbm5lbC0+b2ZmZXJfbXNnLm9mZmVyLmludGVyZmFjZV90eXBl LA0KICAgICAgICAgICAgICAgICAgICBzaXplb2YoaHZfZ3VpZCkpID09IDAgJiYNCiAgICAgICAg ICAgICAgICAgICAgbWVtY21wKCZjaGFubmVsLT5vZmZlcl9tc2cub2ZmZXIuaW50ZXJmYWNlX2lu c3RhbmNlLA0KICAgICAgICAgICAgICAgICAgICAmbmV3X2NoYW5uZWwtPm9mZmVyX21zZy5vZmZl ci5pbnRlcmZhY2VfaW5zdGFuY2UsDQogICAgICAgICAgICAgICAgICAgIHNpemVvZihodl9ndWlk KSkgPT0gMCkgew0KICAgICAgICAgICAgICAgICAgICAgICAgZl9uZXcgPSBGQUxTRTsNCiAgICAg ICAgICAgICAgICAgICAgICAgIGJyZWFrOw0KICAgICAgICAgICAgICAgIH0NCiAgICAgICAgfQ0K DQogICAgICAgIGlmIChmX25ldykgew0KICAgICAgICAgICAgICAgIC8qIEluc2VydCBhdCB0YWls ICovDQogICAgICAgICAgICAgICAgVEFJTFFfSU5TRVJUX1RBSUwoDQogICAgICAgICAgICAgICAg ICAgICZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9hbmNob3IsDQogICAgICAgICAgICAg ICAgICAgIG5ld19jaGFubmVsLA0KICAgICAgICAgICAgICAgICAgICBsaXN0X2VudHJ5KTsNCiAg ICAgICAgfQ0KICAgICAgICBtdHhfdW5sb2NrKCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5l bF9sb2NrKTsNCg0KICAgICAgICAvKlhYWCBhZGQgbmV3IGNoYW5uZWwgdG8gcGVyY3B1X2xpc3Qg Ki8NCg0KICAgICAgICBpZiAoIWZfbmV3KSB7DQogICAgICAgICAgICAgICAgLyoNCiAgICAgICAg ICAgICAgICAgKiBDaGVjayBpZiB0aGlzIGlzIGEgc3ViIGNoYW5uZWwuDQogICAgICAgICAgICAg ICAgICovDQogICAgICAgICAgICAgICAgaWYgKG5ld19jaGFubmVsLT5vZmZlcl9tc2cub2ZmZXIu c3ViX2NoYW5uZWxfaW5kZXggIT0gMCkgew0KICAgICAgICAgICAgICAgICAgICAgICAgLyoNCiAg ICAgICAgICAgICAgICAgICAgICAgICAqIEl0IGlzIGEgc3ViIGNoYW5uZWwgb2ZmZXIsIHByb2Nl c3MgaXQuDQogICAgICAgICAgICAgICAgICAgICAgICAgKi8NCiAgICAgICAgICAgICAgICAgICAg ICAgIG5ld19jaGFubmVsLT5wcmltYXJ5X2NoYW5uZWwgPSBjaGFubmVsOw0KICAgICAgICAgICAg ICAgICAgICAgICAgbXR4X2xvY2soJmNoYW5uZWwtPnNjX2xvY2spOw0KICAgICAgICAgICAgICAg ICAgICAgICAgVEFJTFFfSU5TRVJUX1RBSUwoDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg JmNoYW5uZWwtPnNjX2xpc3RfYW5jaG9yLA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgIG5l d19jaGFubmVsLA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgIHNjX2xpc3RfZW50cnkpOw0K ICAgICAgICAgICAgICAgICAgICAgICAgbXR4X3VubG9jaygmY2hhbm5lbC0+c2NfbG9jayk7DQoN CiAgICAgICAgICAgICAgICAgICAgICAgIC8qIEluc2VydCBuZXcgY2hhbm5lbCBpbnRvIGNoYW5u ZWxfYW5jaG9yLiAqLw0KICAgICAgICAgICAgICAgICAgICAgICAgcHJpbnRmKCJTdG9ydnNjIGdl dCBtdWx0aS1jaGFubmVsIG9mZmVyLCByZWw9JXUuXG4iLA0KICAgICAgICAgICAgICAgICAgICAg ICAgICAgIG5ld19jaGFubmVsLT5vZmZlcl9tc2cuY2hpbGRfcmVsX2lkKTsNCiAgICAgICAgICAg ICAgICAgICAgICAgIG10eF9sb2NrKCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9sb2Nr KTsNCiAgICAgICAgICAgICAgICAgICAgICAgIFRBSUxRX0lOU0VSVF9UQUlMKCZodl92bWJ1c19n X2Nvbm5lY3Rpb24uY2hhbm5lbF9hbmNob3IsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg bmV3X2NoYW5uZWwsIGxpc3RfZW50cnkpOw0KICAgICAgICAgICAgICAgICAgICAgICAgbXR4X3Vu bG9jaygmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5uZWxfbG9jayk7DQoNCiAgICAgICAgICAg ICAgICAgICAgICAgIGlmKGJvb3R2ZXJib3NlKQ0KICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBwcmludGYoIlZNQlVTOiBuZXcgbXVsdGktY2hhbm5lbCBvZmZlciA8JXA+LlxuIiwNCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIG5ld19jaGFubmVsKTsNCg0KICAgICAg ICAgICAgICAgICAgICAgICAgLypYWFggYWRkIGl0IHRvIHBlcmNwdV9saXN0ICovDQoNCiAgICAg ICAgICAgICAgICAgICAgICAgIG5ld19jaGFubmVsLT5zdGF0ZSA9IEhWX0NIQU5ORUxfT1BFTl9T VEFURTsNCiAgICAgICAgICAgICAgICAgICAgICAgIGlmIChjaGFubmVsLT5zY19jcmVhdGlvbl9j YWxsYmFjayAhPSBOVUxMKSB7DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGNoYW5u ZWwtPnNjX2NyZWF0aW9uX2NhbGxiYWNrKG5ld19jaGFubmVsKTsNCiAgICAgICAgICAgICAgICAg ICAgICAgIH0NCiAgICAgICAgICAgICAgICAgICAgICAgIHJldHVybjsNCiAgICAgICAgICAgICAg ICB9DQoNCiAgICAgICAgICAgIGh2X3ZtYnVzX2ZyZWVfdm1idXNfY2hhbm5lbChuZXdfY2hhbm5l bCk7DQogICAgICAgICAgICByZXR1cm47DQogICAgICAgIH0NCg0KICAgICAgICBuZXdfY2hhbm5l bC0+c3RhdGUgPSBIVl9DSEFOTkVMX09QRU5fU1RBVEU7DQoNCiAgICAgICAgLyoNCiAgICAgICAg ICogU3RhcnQgdGhlIHByb2Nlc3Mgb2YgYmluZGluZyB0aGlzIG9mZmVyIHRvIHRoZSBkcml2ZXIN CiAgICAgICAgICogKFdlIG5lZWQgdG8gc2V0IHRoZSBkZXZpY2UgZmllbGQgYmVmb3JlIGNhbGxp bmcNCiAgICAgICAgICogaHZfdm1idXNfY2hpbGRfZGV2aWNlX2FkZCgpKQ0KICAgICAgICAgKi8N CiAgICAgICAgbmV3X2NoYW5uZWwtPmRldmljZSA9IGh2X3ZtYnVzX2NoaWxkX2RldmljZV9jcmVh dGUoDQogICAgICAgICAgICBuZXdfY2hhbm5lbC0+b2ZmZXJfbXNnLm9mZmVyLmludGVyZmFjZV90 eXBlLA0KICAgICAgICAgICAgbmV3X2NoYW5uZWwtPm9mZmVyX21zZy5vZmZlci5pbnRlcmZhY2Vf aW5zdGFuY2UsIG5ld19jaGFubmVsKTsNCg0KICAgICAgICAvKg0KICAgICAgICAgKiBBZGQgdGhl IG5ldyBkZXZpY2UgdG8gdGhlIGJ1cy4gVGhpcyB3aWxsIGtpY2sgb2ZmIGRldmljZS1kcml2ZXIN CiAgICAgICAgICogYmluZGluZyB3aGljaCBldmVudHVhbGx5IGludm9rZXMgdGhlIGRldmljZSBk cml2ZXIncyBBZGREZXZpY2UoKQ0KICAgICAgICAgKiBtZXRob2QuDQogICAgICAgICAqLw0KICAg ICAgICByZXQgPSBodl92bWJ1c19jaGlsZF9kZXZpY2VfcmVnaXN0ZXIobmV3X2NoYW5uZWwtPmRl dmljZSk7DQogICAgICAgIGlmIChyZXQgIT0gMCkgew0KICAgICAgICAgICAgICAgIG10eF9sb2Nr KCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9sb2NrKTsNCiAgICAgICAgICAgICAgICBU QUlMUV9SRU1PVkUoDQogICAgICAgICAgICAgICAgICAgICZodl92bWJ1c19nX2Nvbm5lY3Rpb24u Y2hhbm5lbF9hbmNob3IsDQogICAgICAgICAgICAgICAgICAgIG5ld19jaGFubmVsLA0KICAgICAg ICAgICAgICAgICAgICBsaXN0X2VudHJ5KTsNCiAgICAgICAgICAgICAgICBtdHhfdW5sb2NrKCZo dl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9sb2NrKTsNCiAgICAgICAgICAgICAgICBodl92 bWJ1c19mcmVlX3ZtYnVzX2NoYW5uZWwobmV3X2NoYW5uZWwpOw0KICAgICAgICB9DQp9DQoNCi8q Kg0KICogQXJyYXkgb2YgZGV2aWNlIGd1aWRzIHRoYXQgYXJlIHBlcmZvcm1hbmNlIGNyaXRpY2Fs LiBXZSB0cnkgdG8gZGlzdHJpYnV0ZQ0KICogdGhlIGludGVycnVwdCBsb2FkIGZvciB0aGVzZSBk ZXZpY2VzIGFjcm9zcyBhbGwgb25saW5lIGNwdXMuIA0KICovDQpzdGF0aWMgY29uc3QgaHZfZ3Vp ZCBoaWdoX3BlcmZfZGV2aWNlc1tdID0gew0KICAgICAgICB7SFZfTklDX0dVSUQsIH0sDQogICAg ICAgIHtIVl9JREVfR1VJRCwgfSwNCiAgICAgICAge0hWX1NDU0lfR1VJRCwgfSwNCn07DQoNCmVu dW0gew0KICAgICAgICBQRVJGX0NITl9OSUMgPSAwLA0KICAgICAgICBQRVJGX0NITl9JREUsDQog ICAgICAgIFBFUkZfQ0hOX1NDU0ksDQogICAgICAgIE1BWF9QRVJGX0NITiwNCn07DQoNCi8qDQog KiBXZSB1c2UgdGhpcyBzdGF0aWMgbnVtYmVyIHRvIGRpc3RyaWJ1dGUgdGhlIGNoYW5uZWwgaW50 ZXJydXB0IGxvYWQuDQogKi8NCnN0YXRpYyB1aW50MzJfdCBuZXh0X3ZjcHU7DQoNCi8qKg0KICog U3RhcnRpbmcgd2l0aCBXaW44LCB3ZSBjYW4gc3RhdGljYWxseSBkaXN0cmlidXRlIHRoZSBpbmNv bWluZw0KICogY2hhbm5lbCBpbnRlcnJ1cHQgbG9hZCBieSBiaW5kaW5nIGEgY2hhbm5lbCB0byBW Q1BVLiBXZQ0KICogaW1wbGVtZW50IGhlcmUgYSBzaW1wbGUgcm91bmQgcm9iaW4gc2NoZW1lIGZv ciBkaXN0cmlidXRpbmcNCiAqIHRoZSBpbnRlcnJ1cHQgbG9hZC4NCiAqIFdlIHdpbGwgYmluZCBj aGFubmVscyB0aGF0IGFyZSBub3QgcGVyZm9ybWFuY2UgY3JpdGljYWwgdG8gY3B1IDAgYW5kDQog KiBwZXJmb3JtYW5jZSBjcml0aWNhbCBjaGFubmVscyAoSURFLCBTQ1NJIGFuZCBOZXR3b3JrKSB3 aWxsIGJlIHVuaWZvcm1seQ0KICogZGlzdHJpYnV0ZWQgYWNyb3NzIGFsbCBhdmFpbGFibGUgQ1BV cy4NCiAqLw0Kc3RhdGljIHZvaWQNCnZtYnVzX2NoYW5uZWxfc2VsZWN0X2NwdShodl92bWJ1c19j aGFubmVsICpjaGFubmVsLCBodl9ndWlkICpndWlkKQ0Kew0KICAgICAgICB1aW50MzJfdCBjdXJy ZW50X2NwdTsNCiAgICAgICAgaW50IGk7DQogICAgICAgIGJvb2xlYW5fdCBpc19wZXJmX2NoYW5u ZWwgPSBGQUxTRTsNCg0KICAgICAgICBmb3IgKGkgPSBQRVJGX0NITl9OSUM7IGkgPCBNQVhfUEVS Rl9DSE47IGkrKykgew0KICAgICAgICAgICAgICAgIGlmIChtZW1jbXAoZ3VpZC0+ZGF0YSwgaGln aF9wZXJmX2RldmljZXNbaV0uZGF0YSwNCiAgICAgICAgICAgICAgICAgICAgc2l6ZW9mKGh2X2d1 aWQpKSA9PSAwKSB7DQogICAgICAgICAgICAgICAgICAgICAgICBpc19wZXJmX2NoYW5uZWwgPSBU UlVFOw0KICAgICAgICAgICAgICAgICAgICAgICAgYnJlYWs7DQogICAgICAgICAgICAgICAgfQ0K ICAgICAgICB9DQoNCiAgICAgICAgaWYgKChodl92bWJ1c19wcm90b2NhbF92ZXJzaW9uID09IEhW X1ZNQlVTX1ZFUlNJT05fV1MyMDA4KSB8fA0KICAgICAgICAgICAgKGh2X3ZtYnVzX3Byb3RvY2Fs X3ZlcnNpb24gPT0gSFZfVk1CVVNfVkVSU0lPTl9XSU43KSB8fA0KICAgICAgICAgICAgKCFpc19w ZXJmX2NoYW5uZWwpKSB7DQogICAgICAgICAgICAgICAgLyogSG9zdCdzIHZpZXcgb2YgZ3Vlc3Qg Y3B1ICovDQogICAgICAgICAgICAgICAgY2hhbm5lbC0+dGFyZ2V0X3ZjcHUgPSAwOw0KICAgICAg ICAgICAgICAgIC8qIEd1ZXN0J3Mgb3duIHZpZXcgb2YgY3B1ICovDQogICAgICAgICAgICAgICAg Y2hhbm5lbC0+dGFyZ2V0X2NwdSA9IDA7DQogICAgICAgICAgICAgICAgcmV0dXJuOw0KICAgICAg ICB9DQogICAgICAgIC8qIG1wX25jcHVzIHNob3VsZCBoYXZlIHRoZSBudW1iZXIgY3B1cyBjdXJy ZW50bHkgb25saW5lICovDQogICAgICAgIGN1cnJlbnRfY3B1ID0gKCsrbmV4dF92Y3B1ICUgbXBf bmNwdXMpOw0KICAgICAgICBjaGFubmVsLT50YXJnZXRfY3B1ID0gY3VycmVudF9jcHU7DQogICAg ICAgIGNoYW5uZWwtPnRhcmdldF92Y3B1ID0NCiAgICAgICAgICAgIGh2X3ZtYnVzX2dfY29udGV4 dC5odl92Y3B1X2luZGV4W2N1cnJlbnRfY3B1XTsNCiAgICAgICAgaWYgKGJvb3R2ZXJib3NlKQ0K ICAgICAgICAgICAgICAgIHByaW50ZigiVk1CVVM6IFRvdGFsIG9ubGluZSBjcHVzICVkLCBhc3Np Z24gcGVyZiBjaGFubmVsICVkICINCiAgICAgICAgICAgICAgICAgICAgInRvIHZjcHUgJWQsIGNw dSAlZFxuIiwgbXBfbmNwdXMsIGksIGNoYW5uZWwtPnRhcmdldF92Y3B1LA0KICAgICAgICAgICAg ICAgICAgICBjdXJyZW50X2NwdSk7DQp9DQoNCi8qKg0KICogQGJyaWVmIEhhbmRsZXIgZm9yIGNo YW5uZWwgb2ZmZXJzIGZyb20gSHlwZXItVi9BenVyZQ0KICoNCiAqIEhhbmRsZXIgZm9yIGNoYW5u ZWwgb2ZmZXJzIGZyb20gdm1idXMgaW4gcGFyZW50IHBhcnRpdGlvbi4gV2UgaWdub3JlDQogKiBh bGwgb2ZmZXJzIGV4Y2VwdCBuZXR3b3JrIGFuZCBzdG9yYWdlIG9mZmVycy4gRm9yIGVhY2ggbmV0 d29yayBhbmQgc3RvcmFnZQ0KICogb2ZmZXJzLCB3ZSBjcmVhdGUgYSBjaGFubmVsIG9iamVjdCBh bmQgcXVldWUgYSB3b3JrIGl0ZW0gdG8gdGhlIGNoYW5uZWwNCiAqIG9iamVjdCB0byBwcm9jZXNz IHRoZSBvZmZlciBzeW5jaHJvbm91c2x5DQogKi8NCnN0YXRpYyB2b2lkDQp2bWJ1c19jaGFubmVs X29uX29mZmVyKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2hlYWRlciogaGRyKQ0Kew0KICAgICAgICBo dl92bWJ1c19jaGFubmVsX29mZmVyX2NoYW5uZWwqIG9mZmVyOw0KICAgICAgICBodl92bWJ1c19j aGFubmVsKiBuZXdfY2hhbm5lbDsNCg0KICAgICAgICBvZmZlciA9IChodl92bWJ1c19jaGFubmVs X29mZmVyX2NoYW5uZWwqKSBoZHI7DQoNCiAgICAgICAgaHZfZ3VpZCAqZ3VpZFR5cGU7DQogICAg ICAgIGh2X2d1aWQgKmd1aWRJbnN0YW5jZTsNCg0KICAgICAgICBndWlkVHlwZSA9ICZvZmZlci0+ b2ZmZXIuaW50ZXJmYWNlX3R5cGU7DQogICAgICAgIGd1aWRJbnN0YW5jZSA9ICZvZmZlci0+b2Zm ZXIuaW50ZXJmYWNlX2luc3RhbmNlOw0KDQogICAgICAgIC8qIEFsbG9jYXRlIHRoZSBjaGFubmVs IG9iamVjdCBhbmQgc2F2ZSB0aGlzIG9mZmVyICovDQogICAgICAgIG5ld19jaGFubmVsID0gaHZf dm1idXNfYWxsb2NhdGVfY2hhbm5lbCgpOw0KICAgICAgICBpZiAobmV3X2NoYW5uZWwgPT0gTlVM TCkNCiAgICAgICAgICAgIHJldHVybjsNCg0KICAgICAgICAvKg0KICAgICAgICAgKiBCeSBkZWZh dWx0IHdlIHNldHVwIHN0YXRlIHRvIGVuYWJsZSBiYXRjaGVkDQogICAgICAgICAqIHJlYWRpbmcu IEEgc3BlY2lmaWMgc2VydmljZSBjYW4gY2hvb3NlIHRvDQogICAgICAgICAqIGRpc2FibGUgdGhp cyBwcmlvciB0byBvcGVuaW5nIHRoZSBjaGFubmVsLg0KICAgICAgICAgKi8NCiAgICAgICAgbmV3 X2NoYW5uZWwtPmJhdGNoZWRfcmVhZGluZyA9IFRSVUU7DQoNCiAgICAgICAgbmV3X2NoYW5uZWwt PnNpZ25hbF9ldmVudF9wYXJhbSA9DQogICAgICAgICAgICAoaHZfdm1idXNfaW5wdXRfc2lnbmFs X2V2ZW50ICopDQogICAgICAgICAgICAoSFZfQUxJR05fVVAoKHVuc2lnbmVkIGxvbmcpDQogICAg ICAgICAgICAgICAgJm5ld19jaGFubmVsLT5zaWduYWxfZXZlbnRfYnVmZmVyLA0KICAgICAgICAg ICAgICAgIEhWX0hZUEVSQ0FMTF9QQVJBTV9BTElHTikpOw0KDQogICAgICAgIG5ld19jaGFubmVs LT5zaWduYWxfZXZlbnRfcGFyYW0tPmNvbm5lY3Rpb25faWQuYXNfdWludDMyX3QgPSAwOw0KICAg ICAgICBuZXdfY2hhbm5lbC0+c2lnbmFsX2V2ZW50X3BhcmFtLT5jb25uZWN0aW9uX2lkLnUuaWQg PQ0KICAgICAgICAgICAgSFZfVk1CVVNfRVZFTlRfQ09OTkVDVElPTl9JRDsNCiAgICAgICAgbmV3 X2NoYW5uZWwtPnNpZ25hbF9ldmVudF9wYXJhbS0+ZmxhZ19udW1iZXIgPSAwOw0KICAgICAgICBu ZXdfY2hhbm5lbC0+c2lnbmFsX2V2ZW50X3BhcmFtLT5yc3ZkX3ogPSAwOw0KDQogICAgICAgIGlm IChodl92bWJ1c19wcm90b2NhbF92ZXJzaW9uICE9IEhWX1ZNQlVTX1ZFUlNJT05fV1MyMDA4KSB7 DQogICAgICAgICAgICAgICAgbmV3X2NoYW5uZWwtPmlzX2RlZGljYXRlZF9pbnRlcnJ1cHQgPQ0K ICAgICAgICAgICAgICAgICAgICAob2ZmZXItPmlzX2RlZGljYXRlZF9pbnRlcnJ1cHQgIT0gMCk7 DQogICAgICAgICAgICAgICAgbmV3X2NoYW5uZWwtPnNpZ25hbF9ldmVudF9wYXJhbS0+Y29ubmVj dGlvbl9pZC51LmlkID0NCiAgICAgICAgICAgICAgICAgICAgb2ZmZXItPmNvbm5lY3Rpb25faWQ7 DQogICAgICAgIH0NCg0KICAgICAgICAvKg0KICAgICAgICAgKiBCaW5kIHRoZSBjaGFubmVsIHRv IGEgY2hvc2VuIGNwdS4NCiAgICAgICAgICovDQogICAgICAgIHZtYnVzX2NoYW5uZWxfc2VsZWN0 X2NwdShuZXdfY2hhbm5lbCwNCiAgICAgICAgICAgICZvZmZlci0+b2ZmZXIuaW50ZXJmYWNlX3R5 cGUpOw0KDQogICAgICAgIG1lbWNweSgmbmV3X2NoYW5uZWwtPm9mZmVyX21zZywgb2ZmZXIsDQog ICAgICAgICAgICBzaXplb2YoaHZfdm1idXNfY2hhbm5lbF9vZmZlcl9jaGFubmVsKSk7DQogICAg ICAgIG5ld19jaGFubmVsLT5tb25pdG9yX2dyb3VwID0gKHVpbnQ4X3QpIG9mZmVyLT5tb25pdG9y X2lkIC8gMzI7DQogICAgICAgIG5ld19jaGFubmVsLT5tb25pdG9yX2JpdCA9ICh1aW50OF90KSBv ZmZlci0+bW9uaXRvcl9pZCAlIDMyOw0KDQogICAgICAgIHZtYnVzX2NoYW5uZWxfcHJvY2Vzc19v ZmZlcihuZXdfY2hhbm5lbCk7DQp9DQoNCi8qKg0KICogQGJyaWVmIFJlc2NpbmQgb2ZmZXIgaGFu ZGxlci4NCiAqDQogKiBXZSBxdWV1ZSBhIHdvcmsgaXRlbSB0byBwcm9jZXNzIHRoaXMgb2ZmZXIN CiAqIHN5bmNocm9ub3VzbHkNCiAqLw0Kc3RhdGljIHZvaWQNCnZtYnVzX2NoYW5uZWxfb25fb2Zm ZXJfcmVzY2luZChodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIqIGhkcikNCnsNCiAgICAgICAg aHZfdm1idXNfY2hhbm5lbF9yZXNjaW5kX29mZmVyKiByZXNjaW5kOw0KICAgICAgICBodl92bWJ1 c19jaGFubmVsKiAgICAgICAgICAgICAgIGNoYW5uZWw7DQoNCiAgICAgICAgcmVzY2luZCA9ICho dl92bWJ1c19jaGFubmVsX3Jlc2NpbmRfb2ZmZXIqKSBoZHI7DQoNCiAgICAgICAgY2hhbm5lbCA9 IGh2X3ZtYnVzX2dldF9jaGFubmVsX2Zyb21fcmVsX2lkKHJlc2NpbmQtPmNoaWxkX3JlbF9pZCk7 DQogICAgICAgIGlmIChjaGFubmVsID09IE5VTEwpIA0KICAgICAgICAgICAgcmV0dXJuOw0KDQog ICAgICAgIGh2X3ZtYnVzX2NoaWxkX2RldmljZV91bnJlZ2lzdGVyKGNoYW5uZWwtPmRldmljZSk7 DQp9DQoNCi8qKg0KICoNCiAqIEBicmllZiBJbnZva2VkIHdoZW4gYWxsIG9mZmVycyBoYXZlIGJl ZW4gZGVsaXZlcmVkLg0KICovDQpzdGF0aWMgdm9pZA0Kdm1idXNfY2hhbm5lbF9vbl9vZmZlcnNf ZGVsaXZlcmVkKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2hlYWRlciogaGRyKQ0Kew0KfQ0KDQovKioN CiAqIEBicmllZiBPcGVuIHJlc3VsdCBoYW5kbGVyLg0KICoNCiAqIFRoaXMgaXMgaW52b2tlZCB3 aGVuIHdlIHJlY2VpdmVkIGEgcmVzcG9uc2UNCiAqIHRvIG91ciBjaGFubmVsIG9wZW4gcmVxdWVz dC4gRmluZCB0aGUgbWF0Y2hpbmcgcmVxdWVzdCwgY29weSB0aGUNCiAqIHJlc3BvbnNlIGFuZCBz aWduYWwgdGhlIHJlcXVlc3RpbmcgdGhyZWFkLg0KICovDQpzdGF0aWMgdm9pZA0Kdm1idXNfY2hh bm5lbF9vbl9vcGVuX3Jlc3VsdChodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIqIGhkcikNCnsN CiAgICAgICAgaHZfdm1idXNfY2hhbm5lbF9vcGVuX3Jlc3VsdCogICByZXN1bHQ7DQogICAgICAg IGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2luZm8qICAgICAgbXNnX2luZm87DQogICAgICAgIGh2X3Zt YnVzX2NoYW5uZWxfbXNnX2hlYWRlciogICAgcmVxdWVzdEhlYWRlcjsNCiAgICAgICAgaHZfdm1i dXNfY2hhbm5lbF9vcGVuX2NoYW5uZWwqICBvcGVuTXNnOw0KDQogICAgICAgIHJlc3VsdCA9ICho dl92bWJ1c19jaGFubmVsX29wZW5fcmVzdWx0KikgaGRyOw0KDQogICAgICAgIC8qDQogICAgICAg ICAqIEZpbmQgdGhlIG9wZW4gbXNnLCBjb3B5IHRoZSByZXN1bHQgYW5kIHNpZ25hbC91bmJsb2Nr IHRoZSB3YWl0IGV2ZW50DQogICAgICAgICAqLw0KICAgICAgICBtdHhfbG9ja19zcGluKCZodl92 bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9tc2dfbG9jayk7DQoNCiAgICAgICAgVEFJTFFfRk9S RUFDSChtc2dfaW5mbywgJmh2X3ZtYnVzX2dfY29ubmVjdGlvbi5jaGFubmVsX21zZ19hbmNob3Is DQogICAgICAgICAgICBtc2dfbGlzdF9lbnRyeSkgew0KICAgICAgICAgICAgcmVxdWVzdEhlYWRl ciA9IChodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIqKSBtc2dfaW5mby0+bXNnOw0KDQogICAg ICAgICAgICBpZiAocmVxdWVzdEhlYWRlci0+bWVzc2FnZV90eXBlID09DQogICAgICAgICAgICAg ICAgICAgIEhWX0NIQU5ORUxfTUVTU0FHRV9PUEVOX0NIQU5ORUwpIHsNCiAgICAgICAgICAgICAg ICBvcGVuTXNnID0gKGh2X3ZtYnVzX2NoYW5uZWxfb3Blbl9jaGFubmVsKikgbXNnX2luZm8tPm1z ZzsNCiAgICAgICAgICAgICAgICBpZiAob3Blbk1zZy0+Y2hpbGRfcmVsX2lkID09IHJlc3VsdC0+ Y2hpbGRfcmVsX2lkDQogICAgICAgICAgICAgICAgICAgICYmIG9wZW5Nc2ctPm9wZW5faWQgPT0g cmVzdWx0LT5vcGVuX2lkKSB7DQogICAgICAgICAgICAgICAgICAgIG1lbWNweSgmbXNnX2luZm8t PnJlc3BvbnNlLm9wZW5fcmVzdWx0LCByZXN1bHQsDQogICAgICAgICAgICAgICAgICAgICAgICBz aXplb2YoaHZfdm1idXNfY2hhbm5lbF9vcGVuX3Jlc3VsdCkpOw0KICAgICAgICAgICAgICAgICAg ICBzZW1hX3Bvc3QoJm1zZ19pbmZvLT53YWl0X3NlbWEpOw0KICAgICAgICAgICAgICAgICAgICBi cmVhazsNCiAgICAgICAgICAgICAgICB9DQogICAgICAgICAgICB9DQogICAgICAgIH0NCiAgICAg ICAgbXR4X3VubG9ja19zcGluKCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9tc2dfbG9j ayk7DQoNCn0NCg0KLyoqDQogKiBAYnJpZWYgR1BBREwgY3JlYXRlZCBoYW5kbGVyLg0KICoNCiAq IFRoaXMgaXMgaW52b2tlZCB3aGVuIHdlIHJlY2VpdmVkIGEgcmVzcG9uc2UNCiAqIHRvIG91ciBn cGFkbCBjcmVhdGUgcmVxdWVzdC4gRmluZCB0aGUgbWF0Y2hpbmcgcmVxdWVzdCwgY29weSB0aGUN CiAqIHJlc3BvbnNlIGFuZCBzaWduYWwgdGhlIHJlcXVlc3RpbmcgdGhyZWFkLg0KICovDQpzdGF0 aWMgdm9pZA0Kdm1idXNfY2hhbm5lbF9vbl9ncGFkbF9jcmVhdGVkKGh2X3ZtYnVzX2NoYW5uZWxf bXNnX2hlYWRlciogaGRyKQ0Kew0KICAgICAgICBodl92bWJ1c19jaGFubmVsX2dwYWRsX2NyZWF0 ZWQqICAgICAgICAgZ3BhZGxfY3JlYXRlZDsNCiAgICAgICAgaHZfdm1idXNfY2hhbm5lbF9tc2df aW5mbyogICAgICAgICAgICAgIG1zZ19pbmZvOw0KICAgICAgICBodl92bWJ1c19jaGFubmVsX21z Z19oZWFkZXIqICAgICAgICAgICAgcmVxdWVzdF9oZWFkZXI7DQogICAgICAgIGh2X3ZtYnVzX2No YW5uZWxfZ3BhZGxfaGVhZGVyKiAgICAgICAgICBncGFkbF9oZWFkZXI7DQoNCiAgICAgICAgZ3Bh ZGxfY3JlYXRlZCA9IChodl92bWJ1c19jaGFubmVsX2dwYWRsX2NyZWF0ZWQqKSBoZHI7DQoNCiAg ICAgICAgLyogRmluZCB0aGUgZXN0YWJsaXNoIG1zZywgY29weSB0aGUgcmVzdWx0IGFuZCBzaWdu YWwvdW5ibG9jaw0KICAgICAgICAgKiB0aGUgd2FpdCBldmVudA0KICAgICAgICAgKi8NCiAgICAg ICAgbXR4X2xvY2tfc3BpbigmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5uZWxfbXNnX2xvY2sp Ow0KICAgICAgICBUQUlMUV9GT1JFQUNIKG1zZ19pbmZvLCAmaHZfdm1idXNfZ19jb25uZWN0aW9u LmNoYW5uZWxfbXNnX2FuY2hvciwNCiAgICAgICAgICAgICAgICBtc2dfbGlzdF9lbnRyeSkgew0K ICAgICAgICAgICAgcmVxdWVzdF9oZWFkZXIgPSAoaHZfdm1idXNfY2hhbm5lbF9tc2dfaGVhZGVy KikgbXNnX2luZm8tPm1zZzsNCiAgICAgICAgICAgIGlmIChyZXF1ZXN0X2hlYWRlci0+bWVzc2Fn ZV90eXBlID09DQogICAgICAgICAgICAgICAgICAgIEhWX0NIQU5ORUxfTUVTU0FHRUxfR1BBRExf SEVBREVSKSB7DQogICAgICAgICAgICAgICAgZ3BhZGxfaGVhZGVyID0NCiAgICAgICAgICAgICAg ICAgICAgKGh2X3ZtYnVzX2NoYW5uZWxfZ3BhZGxfaGVhZGVyKikgcmVxdWVzdF9oZWFkZXI7DQoN CiAgICAgICAgICAgICAgICBpZiAoKGdwYWRsX2NyZWF0ZWQtPmNoaWxkX3JlbF9pZCA9PSBncGFk bF9oZWFkZXItPmNoaWxkX3JlbF9pZCkNCiAgICAgICAgICAgICAgICAgICAgJiYgKGdwYWRsX2Ny ZWF0ZWQtPmdwYWRsID09IGdwYWRsX2hlYWRlci0+Z3BhZGwpKSB7DQogICAgICAgICAgICAgICAg ICAgIG1lbWNweSgmbXNnX2luZm8tPnJlc3BvbnNlLmdwYWRsX2NyZWF0ZWQsDQogICAgICAgICAg ICAgICAgICAgICAgICBncGFkbF9jcmVhdGVkLA0KICAgICAgICAgICAgICAgICAgICAgICAgc2l6 ZW9mKGh2X3ZtYnVzX2NoYW5uZWxfZ3BhZGxfY3JlYXRlZCkpOw0KICAgICAgICAgICAgICAgICAg ICBzZW1hX3Bvc3QoJm1zZ19pbmZvLT53YWl0X3NlbWEpOw0KICAgICAgICAgICAgICAgICAgICBi cmVhazsNCiAgICAgICAgICAgICAgICB9DQogICAgICAgICAgICB9DQogICAgICAgIH0NCiAgICAg ICAgbXR4X3VubG9ja19zcGluKCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9tc2dfbG9j ayk7DQp9DQoNCi8qKg0KICogQGJyaWVmIEdQQURMIHRvcm5kb3duIGhhbmRsZXIuDQogKg0KICog VGhpcyBpcyBpbnZva2VkIHdoZW4gd2UgcmVjZWl2ZWQgYSByZXNwb25zDQogKiB0byBvdXIgZ3Bh ZGwgdGVhcmRvd24gcmVxdWVzdC4gRmluZCB0aGUgbWF0Y2hpbmcgcmVxdWVzdCwgY29weSB0aGUN CiAqIHJlc3BvbnNlIGFuZCBzaWduYWwgdGhlIHJlcXVlc3RpbmcgdGhyZWFkDQogKi8NCnN0YXRp YyB2b2lkDQp2bWJ1c19jaGFubmVsX29uX2dwYWRsX3Rvcm5kb3duKGh2X3ZtYnVzX2NoYW5uZWxf bXNnX2hlYWRlciogaGRyKQ0Kew0KICAgICAgICBodl92bWJ1c19jaGFubmVsX2dwYWRsX3Rvcm5k b3duKiAgICAgICAgZ3BhZGxfdG9ybmRvd247DQogICAgICAgIGh2X3ZtYnVzX2NoYW5uZWxfbXNn X2luZm8qICAgICAgICAgICAgICBtc2dfaW5mbzsNCiAgICAgICAgaHZfdm1idXNfY2hhbm5lbF9t c2dfaGVhZGVyKiAgICAgICAgICAgIHJlcXVlc3RIZWFkZXI7DQogICAgICAgIGh2X3ZtYnVzX2No YW5uZWxfZ3BhZGxfdGVhcmRvd24qICAgICAgICBncGFkbFRlYXJkb3duOw0KDQogICAgICAgIGdw YWRsX3Rvcm5kb3duID0gKGh2X3ZtYnVzX2NoYW5uZWxfZ3BhZGxfdG9ybmRvd24qKWhkcjsNCg0K ICAgICAgICAvKg0KICAgICAgICAgKiBGaW5kIHRoZSBvcGVuIG1zZywgY29weSB0aGUgcmVzdWx0 IGFuZCBzaWduYWwvdW5ibG9jayB0aGUNCiAgICAgICAgICogd2FpdCBldmVudC4NCiAgICAgICAg ICovDQoNCiAgICAgICAgbXR4X2xvY2tfc3BpbigmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5u ZWxfbXNnX2xvY2spOw0KDQogICAgICAgIFRBSUxRX0ZPUkVBQ0gobXNnX2luZm8sICZodl92bWJ1 c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9tc2dfYW5jaG9yLA0KICAgICAgICAgICAgICAgIG1zZ19s aXN0X2VudHJ5KSB7DQogICAgICAgICAgICByZXF1ZXN0SGVhZGVyID0gKGh2X3ZtYnVzX2NoYW5u ZWxfbXNnX2hlYWRlciopIG1zZ19pbmZvLT5tc2c7DQoNCiAgICAgICAgICAgIGlmIChyZXF1ZXN0 SGVhZGVyLT5tZXNzYWdlX3R5cGUNCiAgICAgICAgICAgICAgICAgICAgPT0gSFZfQ0hBTk5FTF9N RVNTQUdFX0dQQURMX1RFQVJET1dOKSB7DQogICAgICAgICAgICAgICAgZ3BhZGxUZWFyZG93biA9 DQogICAgICAgICAgICAgICAgICAgIChodl92bWJ1c19jaGFubmVsX2dwYWRsX3RlYXJkb3duKikg cmVxdWVzdEhlYWRlcjsNCg0KICAgICAgICAgICAgICAgIGlmIChncGFkbF90b3JuZG93bi0+Z3Bh ZGwgPT0gZ3BhZGxUZWFyZG93bi0+Z3BhZGwpIHsNCiAgICAgICAgICAgICAgICAgICAgbWVtY3B5 KCZtc2dfaW5mby0+cmVzcG9uc2UuZ3BhZGxfdG9ybmRvd24sDQogICAgICAgICAgICAgICAgICAg ICAgICBncGFkbF90b3JuZG93biwNCiAgICAgICAgICAgICAgICAgICAgICAgIHNpemVvZihodl92 bWJ1c19jaGFubmVsX2dwYWRsX3Rvcm5kb3duKSk7DQogICAgICAgICAgICAgICAgICAgIHNlbWFf cG9zdCgmbXNnX2luZm8tPndhaXRfc2VtYSk7DQogICAgICAgICAgICAgICAgICAgIGJyZWFrOw0K ICAgICAgICAgICAgICAgIH0NCiAgICAgICAgICAgIH0NCiAgICAgICAgfQ0KICAgIG10eF91bmxv Y2tfc3BpbigmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5uZWxfbXNnX2xvY2spOw0KfQ0KDQov KioNCiAqIEBicmllZiBWZXJzaW9uIHJlc3BvbnNlIGhhbmRsZXIuDQogKg0KICogVGhpcyBpcyBp bnZva2VkIHdoZW4gd2UgcmVjZWl2ZWQgYSByZXNwb25zZQ0KICogdG8gb3VyIGluaXRpYXRlIGNv bnRhY3QgcmVxdWVzdC4gRmluZCB0aGUgbWF0Y2hpbmcgcmVxdWVzdCwgY29weSB0aA0KICogcmVz cG9uc2UgYW5kIHNpZ25hbCB0aGUgcmVxdWVzdGluZyB0aHJlYWQuDQogKi8NCnN0YXRpYyB2b2lk DQp2bWJ1c19jaGFubmVsX29uX3ZlcnNpb25fcmVzcG9uc2UoaHZfdm1idXNfY2hhbm5lbF9tc2df aGVhZGVyKiBoZHIpDQp7DQogICAgICAgIGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2luZm8qICAgICAg ICAgICAgICBtc2dfaW5mbzsNCiAgICAgICAgaHZfdm1idXNfY2hhbm5lbF9tc2dfaGVhZGVyKiAg ICAgICAgICAgIHJlcXVlc3RIZWFkZXI7DQogICAgICAgIGh2X3ZtYnVzX2NoYW5uZWxfaW5pdGlh dGVfY29udGFjdCogICAgICBpbml0aWF0ZTsNCiAgICAgICAgaHZfdm1idXNfY2hhbm5lbF92ZXJz aW9uX3Jlc3BvbnNlKiAgICAgIHZlcnNpb25SZXNwb25zZTsNCg0KICAgICAgICB2ZXJzaW9uUmVz cG9uc2UgPSAoaHZfdm1idXNfY2hhbm5lbF92ZXJzaW9uX3Jlc3BvbnNlKiloZHI7DQoNCiAgICAg ICAgbXR4X2xvY2tfc3BpbigmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5uZWxfbXNnX2xvY2sp Ow0KICAgICAgICBUQUlMUV9GT1JFQUNIKG1zZ19pbmZvLCAmaHZfdm1idXNfZ19jb25uZWN0aW9u LmNoYW5uZWxfbXNnX2FuY2hvciwNCiAgICAgICAgICAgIG1zZ19saXN0X2VudHJ5KSB7DQogICAg ICAgICAgICByZXF1ZXN0SGVhZGVyID0gKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2hlYWRlciopIG1z Z19pbmZvLT5tc2c7DQogICAgICAgICAgICBpZiAocmVxdWVzdEhlYWRlci0+bWVzc2FnZV90eXBl DQogICAgICAgICAgICAgICAgPT0gSFZfQ0hBTk5FTF9NRVNTQUdFX0lOSVRJQVRFRF9DT05UQUNU KSB7DQogICAgICAgICAgICAgICAgaW5pdGlhdGUgPQ0KICAgICAgICAgICAgICAgICAgICAoaHZf dm1idXNfY2hhbm5lbF9pbml0aWF0ZV9jb250YWN0KikgcmVxdWVzdEhlYWRlcjsNCiAgICAgICAg ICAgICAgICBtZW1jcHkoJm1zZ19pbmZvLT5yZXNwb25zZS52ZXJzaW9uX3Jlc3BvbnNlLA0KICAg ICAgICAgICAgICAgICAgICB2ZXJzaW9uUmVzcG9uc2UsDQogICAgICAgICAgICAgICAgICAgIHNp emVvZihodl92bWJ1c19jaGFubmVsX3ZlcnNpb25fcmVzcG9uc2UpKTsNCiAgICAgICAgICAgICAg ICBzZW1hX3Bvc3QoJm1zZ19pbmZvLT53YWl0X3NlbWEpOw0KICAgICAgICAgICAgfQ0KICAgICAg ICB9DQogICAgbXR4X3VubG9ja19zcGluKCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9t c2dfbG9jayk7DQoNCn0NCg0KLyoqDQogKiBAYnJpZWYgSGFuZGxlciBmb3IgY2hhbm5lbCBwcm90 b2NvbCBtZXNzYWdlcy4NCiAqDQogKiBUaGlzIGlzIGludm9rZWQgaW4gdGhlIHZtYnVzIHdvcmtl ciB0aHJlYWQgY29udGV4dC4NCiAqLw0Kdm9pZA0KaHZfdm1idXNfb25fY2hhbm5lbF9tZXNzYWdl KHZvaWQgKmNvbnRleHQpDQp7DQogICAgICAgIGh2X3ZtYnVzX21lc3NhZ2UqICAgICAgICAgICAg ICAgbXNnOw0KICAgICAgICBodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIqICAgIGhkcjsNCiAg ICAgICAgaW50ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzaXplOw0KDQogICAgICAgIG1z ZyA9IChodl92bWJ1c19tZXNzYWdlKikgY29udGV4dDsNCiAgICAgICAgaGRyID0gKGh2X3ZtYnVz X2NoYW5uZWxfbXNnX2hlYWRlciopIG1zZy0+dS5wYXlsb2FkOw0KICAgICAgICBzaXplID0gbXNn LT5oZWFkZXIucGF5bG9hZF9zaXplOw0KDQogICAgICAgIGlmIChoZHItPm1lc3NhZ2VfdHlwZSA+ PSBIVl9DSEFOTkVMX01FU1NBR0VfQ09VTlQpIHsNCiAgICAgICAgICAgIGZyZWUobXNnLCBNX0RF VkJVRik7DQogICAgICAgICAgICByZXR1cm47DQogICAgICAgIH0NCg0KICAgICAgICBpZiAoZ19j aGFubmVsX21lc3NhZ2VfdGFibGVbaGRyLT5tZXNzYWdlX3R5cGVdLm1lc3NhZ2VIYW5kbGVyKSB7 DQogICAgICAgICAgICBnX2NoYW5uZWxfbWVzc2FnZV90YWJsZVtoZHItPm1lc3NhZ2VfdHlwZV0u bWVzc2FnZUhhbmRsZXIoaGRyKTsNCiAgICAgICAgfQ0KDQogICAgICAgIC8qIEZyZWUgdGhlIG1z ZyB0aGF0IHdhcyBhbGxvY2F0ZWQgaW4gVm1idXNPbk1zZ0RQQygpICovDQogICAgICAgIGZyZWUo bXNnLCBNX0RFVkJVRik7DQp9DQoNCi8qKg0KICogIEBicmllZiBTZW5kIGEgcmVxdWVzdCB0byBn ZXQgYWxsIG91ciBwZW5kaW5nIG9mZmVycy4NCiAqLw0KaW50DQpodl92bWJ1c19yZXF1ZXN0X2No YW5uZWxfb2ZmZXJzKHZvaWQpDQp7DQogICAgICAgIGludCAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgcmV0Ow0KICAgICAgICBodl92bWJ1c19jaGFubmVsX21zZ19oZWFkZXIqICAgIG1zZzsN CiAgICAgICAgaHZfdm1idXNfY2hhbm5lbF9tc2dfaW5mbyogICAgICBtc2dfaW5mbzsNCg0KICAg ICAgICBtc2dfaW5mbyA9IChodl92bWJ1c19jaGFubmVsX21zZ19pbmZvICopDQogICAgICAgICAg ICBtYWxsb2Moc2l6ZW9mKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2luZm8pDQogICAgICAgICAgICAg ICAgICAgICsgc2l6ZW9mKGh2X3ZtYnVzX2NoYW5uZWxfbXNnX2hlYWRlciksIE1fREVWQlVGLCBN X05PV0FJVCk7DQoNCiAgICAgICAgaWYgKG1zZ19pbmZvID09IE5VTEwpIHsNCiAgICAgICAgICAg IGlmKGJvb3R2ZXJib3NlKQ0KICAgICAgICAgICAgICAgIHByaW50ZigiRXJyb3IgVk1CVVM6IG1h bGxvYyBmYWlsZWQgZm9yIFJlcXVlc3QgT2ZmZXJzXG4iKTsNCiAgICAgICAgICAgIHJldHVybiAo RU5PTUVNKTsNCiAgICAgICAgfQ0KDQogICAgICAgIG1zZyA9IChodl92bWJ1c19jaGFubmVsX21z Z19oZWFkZXIqKSBtc2dfaW5mby0+bXNnOw0KICAgICAgICBtc2ctPm1lc3NhZ2VfdHlwZSA9IEhW X0NIQU5ORUxfTUVTU0FHRV9SRVFVRVNUX09GRkVSUzsNCg0KICAgICAgICByZXQgPSBodl92bWJ1 c19wb3N0X21lc3NhZ2UobXNnLCBzaXplb2YoaHZfdm1idXNfY2hhbm5lbF9tc2dfaGVhZGVyKSk7 DQoNCiAgICAgICAgaWYgKG1zZ19pbmZvKQ0KICAgICAgICAgICAgZnJlZShtc2dfaW5mbywgTV9E RVZCVUYpOw0KDQogICAgICAgIHJldHVybiAocmV0KTsNCn0NCg0KLyoqDQogKiBAYnJpZWYgUmVs ZWFzZSBjaGFubmVscyB0aGF0IGFyZSB1bmF0dGFjaGVkL3VuY29ubmVjdGVkIChpLmUuLCBubyBk cml2ZXJzIGFzc29jaWF0ZWQpDQogKi8NCnZvaWQNCmh2X3ZtYnVzX3JlbGVhc2VfdW5hdHRhY2hl ZF9jaGFubmVscyh2b2lkKSANCnsNCiAgICAgICAgaHZfdm1idXNfY2hhbm5lbCAqY2hhbm5lbDsN Cg0KICAgICAgICBtdHhfbG9jaygmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5uZWxfbG9jayk7 DQoNCiAgICAgICAgd2hpbGUgKCFUQUlMUV9FTVBUWSgmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNo YW5uZWxfYW5jaG9yKSkgew0KICAgICAgICAgICAgY2hhbm5lbCA9IFRBSUxRX0ZJUlNUKCZodl92 bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9hbmNob3IpOw0KICAgICAgICAgICAgVEFJTFFfUkVN T1ZFKCZodl92bWJ1c19nX2Nvbm5lY3Rpb24uY2hhbm5lbF9hbmNob3IsDQogICAgICAgICAgICAg ICAgICAgICAgICAgICAgY2hhbm5lbCwgbGlzdF9lbnRyeSk7DQoNCiAgICAgICAgICAgIGh2X3Zt YnVzX2NoaWxkX2RldmljZV91bnJlZ2lzdGVyKGNoYW5uZWwtPmRldmljZSk7DQogICAgICAgICAg ICBodl92bWJ1c19mcmVlX3ZtYnVzX2NoYW5uZWwoY2hhbm5lbCk7DQogICAgICAgIH0NCiAgICAg ICAgbXR4X3VubG9jaygmaHZfdm1idXNfZ19jb25uZWN0aW9uLmNoYW5uZWxfbG9jayk7DQp9DQoN Ci8qKg0KICogQGJyaWVmIFNlbGVjdCB0aGUgYmVzdCBvdXRnb2luZyBjaGFubmVsDQogKiANCiAq IFRoZSBjaGFubmVsIHdob3NlIHZjcHUgYmluZGluZyBpcyBjbG9zZXN0IHRvIHRoZSBjdXJyZWN0 IHZjcHUgd2lsbA0KICogYmUgc2VsZWN0ZWQuDQogKiBJZiBubyBtdWx0aS1jaGFubmVsLCBhbHdh eXMgc2VsZWN0IHByaW1hcnkgY2hhbm5lbA0KICogDQogKiBAcGFyYW0gcHJpbWFyeSAtIHByaW1h cnkgY2hhbm5lbA0KICovDQpzdHJ1Y3QgaHZfdm1idXNfY2hhbm5lbCAqDQp2bWJ1c19zZWxlY3Rf b3V0Z29pbmdfY2hhbm5lbChzdHJ1Y3QgaHZfdm1idXNfY2hhbm5lbCAqcHJpbWFyeSkNCnsNCiAg ICAgICAgaHZfdm1idXNfY2hhbm5lbCAqbmV3X2NoYW5uZWwgPSBOVUxMOw0KICAgICAgICBodl92 bWJ1c19jaGFubmVsICpvdXRnb2luZ19jaGFubmVsID0gcHJpbWFyeTsNCiAgICAgICAgaW50IG9s ZF9jcHVfZGlzdGFuY2UgPSAwOw0KICAgICAgICBpbnQgbmV3X2NwdV9kaXN0YW5jZSA9IDA7DQog ICAgICAgIGludCBjdXJfdmNwdSA9IDA7DQogICAgICAgIGludCBzbXBfcHJvX2lkID0gUENQVV9H RVQoY3B1aWQpOw0KDQogICAgICAgIGlmIChUQUlMUV9FTVBUWSgmcHJpbWFyeS0+c2NfbGlzdF9h bmNob3IpKSB7DQogICAgICAgICAgICAgICAgcmV0dXJuIG91dGdvaW5nX2NoYW5uZWw7DQogICAg ICAgIH0NCg0KICAgICAgICBpZiAoc21wX3Byb19pZCA+PSBNQVhDUFUpIHsNCiAgICAgICAgICAg ICAgICByZXR1cm4gb3V0Z29pbmdfY2hhbm5lbDsNCiAgICAgICAgfQ0KDQogICAgICAgIGN1cl92 Y3B1ID0gaHZfdm1idXNfZ19jb250ZXh0Lmh2X3ZjcHVfaW5kZXhbc21wX3Byb19pZF07DQoNCiAg ICAgICAgVEFJTFFfRk9SRUFDSChuZXdfY2hhbm5lbCwgJnByaW1hcnktPnNjX2xpc3RfYW5jaG9y LCBzY19saXN0X2VudHJ5KSB7DQogICAgICAgICAgICAgICAgaWYgKG5ld19jaGFubmVsLT5zdGF0 ZSAhPSBIVl9DSEFOTkVMX09QRU5FRF9TVEFURSl7DQogICAgICAgICAgICAgICAgICAgICAgICBj b250aW51ZTsNCiAgICAgICAgICAgICAgICB9DQoNCiAgICAgICAgICAgICAgICBpZiAobmV3X2No YW5uZWwtPnRhcmdldF92Y3B1ID09IGN1cl92Y3B1KXsNCiAgICAgICAgICAgICAgICAgICAgICAg IHJldHVybiBuZXdfY2hhbm5lbDsNCiAgICAgICAgICAgICAgICB9DQoNCiAgICAgICAgICAgICAg ICBvbGRfY3B1X2Rpc3RhbmNlID0gKChvdXRnb2luZ19jaGFubmVsLT50YXJnZXRfdmNwdSA+IGN1 cl92Y3B1KSA/DQogICAgICAgICAgICAgICAgICAgIChvdXRnb2luZ19jaGFubmVsLT50YXJnZXRf dmNwdSAtIGN1cl92Y3B1KSA6DQogICAgICAgICAgICAgICAgICAgIChjdXJfdmNwdSAtIG91dGdv aW5nX2NoYW5uZWwtPnRhcmdldF92Y3B1KSk7DQoNCiAgICAgICAgICAgICAgICBuZXdfY3B1X2Rp c3RhbmNlID0gKChuZXdfY2hhbm5lbC0+dGFyZ2V0X3ZjcHUgPiBjdXJfdmNwdSkgPw0KICAgICAg ICAgICAgICAgICAgICAobmV3X2NoYW5uZWwtPnRhcmdldF92Y3B1IC0gY3VyX3ZjcHUpIDoNCiAg ICAgICAgICAgICAgICAgICAgKGN1cl92Y3B1IC0gbmV3X2NoYW5uZWwtPnRhcmdldF92Y3B1KSk7 DQoNCiAgICAgICAgICAgICAgICBpZiAob2xkX2NwdV9kaXN0YW5jZSA8IG5ld19jcHVfZGlzdGFu Y2UpIHsNCiAgICAgICAgICAgICAgICAgICAgICAgIGNvbnRpbnVlOw0KICAgICAgICAgICAgICAg IH0NCg0KICAgICAgICAgICAgICAgIG91dGdvaW5nX2NoYW5uZWwgPSBuZXdfY2hhbm5lbDsNCiAg ICAgICAgfQ0KDQogICAgICAgIHJldHVybihvdXRnb2luZ19jaGFubmVsKTsNCn0NCiAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAg --_007_53238096372f4362b436382a430bde57ORTELIUSinternalbugwork_-- From owner-freebsd-virtualization@freebsd.org Thu Feb 4 00:45:26 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 E1B83A9B8CE for ; Thu, 4 Feb 2016 00:45:26 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id CE4FF10BE for ; Thu, 4 Feb 2016 00:45:26 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id CA6D7106224; Thu, 4 Feb 2016 00:45:26 +0000 (UTC) Date: Thu, 4 Feb 2016 00:45:26 +0000 To: freebsd-virtualization@freebsd.org From: "honzhan_microsoft.com (hongjiangzhang)" Reply-to: D5175+333+519ccacf1c2a3a95@reviews.freebsd.org Subject: [Differential] [Accepted] D5175: hyperv/hn: Add an option to always do transmission scheduling Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , Thread-Topic: D5175: hyperv/hn: Add an option to always do transmission scheduling X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: OGFmNjgzYWFmZmVhMjQ0MTIwYzQ1OWJjZDg2IFaynyY= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-Mailman-Approved-At: Thu, 04 Feb 2016 00:53:59 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 00:45:27 -0000 honzhan_microsoft.com accepted this revision. honzhan_microsoft.com added a comment. Looks ok to me. REVISION DETAIL https://reviews.freebsd.org/D5175 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, howard0su_gmail.com, adrian, network, honzhan_microsoft.com Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Thu Feb 4 08:44:09 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 DBB8BA9B1AE for ; Thu, 4 Feb 2016 08:44:09 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id C4D1D1441 for ; Thu, 4 Feb 2016 08:44:09 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id C217C10755C; Thu, 4 Feb 2016 08:44:09 +0000 (UTC) Date: Thu, 4 Feb 2016 08:44:09 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Request, 117 lines] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdm MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_84755b6b2cef604cff3734dd97c0cd84" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 08:44:10 -0000 --b1_84755b6b2cef604cff3734dd97c0cd84 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit sepherosa_gmail.com created this revision. sepherosa_gmail.com added reviewers: network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, gallatin, hselasky, np. sepherosa_gmail.com added subscribers: freebsd-net-list, freebsd-virtualization-list. Herald added a reviewer: transport. REVISION SUMMARY It's append_cnt based. Unless the network driver sets these two limits, its an NO-OP. For hn(4): - Set TCP ACK append limit to 1, i.e. aggregate 2 ACKs at most. Aggregate anything more than 2 hurts TCP sending performance in hyperv. This significantly improves the TCP sending performance when the number of concurrent connetion is low (2~8). And greatly stabilize the TCP sending performance in other cases. - Set TCP data segments append limit to 25. Without this limitation, hn(4) could aggregate ~45 TCP data segments for each connection (even at 64 or more connections) before dispatching them to socket code; large aggregation slows down ACK sending and eventually hurts/destabilizes TCP reception performance. This setting stabilizes and improves TCP reception performance for >4 concurrent connections significantly. Make them sysctls so they could be adjusted. REVISION DETAIL https://reviews.freebsd.org/D5185 AFFECTED FILES sys/dev/hyperv/netvsc/hv_net_vsc.h sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c sys/netinet/tcp_lro.c sys/netinet/tcp_lro.h EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, transport, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, gallatin, hselasky, np Cc: freebsd-virtualization-list, freebsd-net-list --b1_84755b6b2cef604cff3734dd97c0cd84 Content-Type: text/x-patch; charset=utf-8; name="D5185.12995.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D5185.12995.patch" ZGlmZiAtLWdpdCBhL3N5cy9uZXRpbmV0L3RjcF9scm8uaCBiL3N5cy9uZXRpbmV0L3RjcF9scm8u aAotLS0gYS9zeXMvbmV0aW5ldC90Y3BfbHJvLmgKKysrIGIvc3lzL25ldGluZXQvdGNwX2xyby5o CkBAIC05MSw2ICs5MSw4IEBACiAJdW5zaWduZWQJbHJvX2NudDsKIAl1bnNpZ25lZAlscm9fbWJ1 Zl9jb3VudDsKIAl1bnNpZ25lZAlscm9fbWJ1Zl9tYXg7CisJdW5zaWduZWQgc2hvcnQJbHJvX2Fj a19hcHBlbmRfbGltOworCXVuc2lnbmVkIHNob3J0CWxyb19kYXRhX2FwcGVuZF9saW07CiAKIAlz dHJ1Y3QgbHJvX2hlYWQJbHJvX2FjdGl2ZTsKIAlzdHJ1Y3QgbHJvX2hlYWQJbHJvX2ZyZWU7CmRp ZmYgLS1naXQgYS9zeXMvbmV0aW5ldC90Y3BfbHJvLmMgYi9zeXMvbmV0aW5ldC90Y3BfbHJvLmMK LS0tIGEvc3lzL25ldGluZXQvdGNwX2xyby5jCisrKyBiL3N5cy9uZXRpbmV0L3RjcF9scm8uYwpA QCAtODgsNiArODgsOCBAQAogCWxjLT5scm9fbWJ1Zl9tYXggPSBscm9fbWJ1ZnM7CiAJbGMtPmxy b19jbnQgPSBscm9fZW50cmllczsKIAlsYy0+aWZwID0gaWZwOworCWxjLT5scm9fYWNrX2FwcGVu ZF9saW0gPSAwOworCWxjLT5scm9fZGF0YV9hcHBlbmRfbGltID0gMDsKIAlTTElTVF9JTklUKCZs Yy0+bHJvX2ZyZWUpOwogCVNMSVNUX0lOSVQoJmxjLT5scm9fYWN0aXZlKTsKIApAQCAtNjQ2LDYg KzY0OCwxNiBAQAogCiAJCWlmICh0Y3BfZGF0YV9sZW4gPT0gMCkgewogCQkJbV9mcmVlbShtKTsK KwkJCS8qCisJCQkgKiBGbHVzaCB0aGlzIExSTyBlbnRyeSwgaWYgdGhpcyBBQ0sgc2hvdWxkCisJ CQkgKiBub3QgYmUgZnVydGhlciBkZWxheWVkLgorCQkJICovCisJCQlpZiAobGMtPmxyb19hY2tf YXBwZW5kX2xpbSAmJgorCQkJICAgIGxlLT5hcHBlbmRfY250ID49IGxjLT5scm9fYWNrX2FwcGVu ZF9saW0pIHsKKwkJCQlTTElTVF9SRU1PVkUoJmxjLT5scm9fYWN0aXZlLCBsZSwgbHJvX2VudHJ5 LAorCQkJCSAgICBuZXh0KTsKKwkJCQl0Y3BfbHJvX2ZsdXNoKGxjLCBsZSk7CisJCQl9CiAJCQly ZXR1cm4gKDApOwogCQl9CiAKQEAgLTY2NCw5ICs2NzYsMTIgQEAKIAogCQkvKgogCQkgKiBJZiBh IHBvc3NpYmxlIG5leHQgZnVsbCBsZW5ndGggcGFja2V0IHdvdWxkIGNhdXNlIGFuCi0JCSAqIG92 ZXJmbG93LCBwcm8tYWN0aXZlbHkgZmx1c2ggbm93LgorCQkgKiBvdmVyZmxvdywgcHJvLWFjdGl2 ZWx5IGZsdXNoIG5vdy4gIEFuZCBpZiB3ZSBhcmUgYXNrZWQKKwkJICogdG8gbGltaXQgdGhlIGRh dGEgYWdncmVnYXRlLCBmbHVzaCB0aGlzIExSTyBlbnRyeSBub3cuCiAJCSAqLwotCQlpZiAobGUt PnBfbGVuID4gKDY1NTM1IC0gbGMtPmlmcC0+aWZfbXR1KSkgeworCQlpZiAobGUtPnBfbGVuID4g KDY1NTM1IC0gbGMtPmlmcC0+aWZfbXR1KSB8fAorCQkgICAgKGxjLT5scm9fZGF0YV9hcHBlbmRf bGltICYmCisJCSAgICAgbGUtPmFwcGVuZF9jbnQgPj0gbGMtPmxyb19kYXRhX2FwcGVuZF9saW0p KSB7CiAJCQlTTElTVF9SRU1PVkUoJmxjLT5scm9fYWN0aXZlLCBsZSwgbHJvX2VudHJ5LCBuZXh0 KTsKIAkJCXRjcF9scm9fZmx1c2gobGMsIGxlKTsKIAkJfSBlbHNlCmRpZmYgLS1naXQgYS9zeXMv ZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNkLmMgYi9zeXMvZGV2L2h5cGVy di9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNkLmMKLS0tIGEvc3lzL2Rldi9oeXBlcnYvbmV0 dnNjL2h2X25ldHZzY19kcnZfZnJlZWJzZC5jCisrKyBiL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9o dl9uZXR2c2NfZHJ2X2ZyZWVic2QuYwpAQCAtMTc2LDE0ICsxNzYsOCBAQAogI2RlZmluZSBITl9D U1VNX0FTU0lTVF9XSU44CShDU1VNX1RDUCkKICNkZWZpbmUgSE5fQ1NVTV9BU1NJU1QJCShDU1VN X0lQIHwgQ1NVTV9VRFAgfCBDU1VNX1RDUCkKIAotLyogWFhYIG1vdmUgdG8gbmV0aW5ldC90Y3Bf bHJvLmggKi8KLSNkZWZpbmUgSE5fTFJPX0hJV0FUX01BWAkJCQk2NTUzNQotI2RlZmluZSBITl9M Uk9fSElXQVRfREVGCQkJCUhOX0xST19ISVdBVF9NQVgKLS8qIFlZWSAyKk1UVSBpcyBhIGJpdCBy b3VnaCwgYnV0IHNob3VsZCBiZSBnb29kIGVub3VnaC4gKi8KLSNkZWZpbmUgSE5fTFJPX0hJV0FU X01UVUxJTShpZnApCQkJKDIgKiAoaWZwKS0+aWZfbXR1KQotI2RlZmluZSBITl9MUk9fSElXQVRf SVNWQUxJRChzYywgaGl3YXQpCQkJXAotICAgICgoaGl3YXQpID49IEhOX0xST19ISVdBVF9NVFVM SU0oKHNjKS0+aG5faWZwKSB8fAlcCi0gICAgIChoaXdhdCkgPD0gSE5fTFJPX0hJV0FUX01BWCkK KyNkZWZpbmUgSE5fTFJPX0FDS19BUFBFTkRfTElNCTEKKyNkZWZpbmUgSE5fTFJPX0RBVEFfQVBQ RU5EX0xJTQkyNQogCiAvKgogICogQmUgYXdhcmUgdGhhdCB0aGlzIHNsZWVwYWJsZSBtdXRleCB3 aWxsIGV4aGliaXQgV0lUTkVTUyBlcnJvcnMgd2hlbgpAQCAtMjUzLDI3ICsyNDcsMTYgQEAKIHN0 YXRpYyB2b2lkIGhuX3N0YXJ0X3R4ZW9mKHN0cnVjdCBpZm5ldCAqaWZwKTsKIHN0YXRpYyBpbnQg aG5faWZtZWRpYV91cGQoc3RydWN0IGlmbmV0ICppZnApOwogc3RhdGljIHZvaWQgaG5faWZtZWRp YV9zdHMoc3RydWN0IGlmbmV0ICppZnAsIHN0cnVjdCBpZm1lZGlhcmVxICppZm1yKTsKLSNpZmRl ZiBITl9MUk9fSElXQVQKLXN0YXRpYyBpbnQgaG5fbHJvX2hpd2F0X3N5c2N0bChTWVNDVExfSEFO RExFUl9BUkdTKTsKLSNlbmRpZgogc3RhdGljIGludCBobl90cnVzdF9oY3N1bV9zeXNjdGwoU1lT Q1RMX0hBTkRMRVJfQVJHUyk7CiBzdGF0aWMgaW50IGhuX3R4X2NoaW1uZXlfc2l6ZV9zeXNjdGwo U1lTQ1RMX0hBTkRMRVJfQVJHUyk7CitzdGF0aWMgaW50IGhuX2xyb19hcHBlbmRfbGltX3N5c2N0 bChTWVNDVExfSEFORExFUl9BUkdTKTsKIHN0YXRpYyBpbnQgaG5fY2hlY2tfaXBsZW4oY29uc3Qg c3RydWN0IG1idWYgKiwgaW50KTsKIHN0YXRpYyBpbnQgaG5fY3JlYXRlX3R4X3Jpbmcoc3RydWN0 IGhuX3NvZnRjICpzYyk7CiBzdGF0aWMgdm9pZCBobl9kZXN0cm95X3R4X3Jpbmcoc3RydWN0IGhu X3NvZnRjICpzYyk7CiBzdGF0aWMgdm9pZCBobl9zdGFydF90YXNrZnVuYyh2b2lkICp4c2MsIGlu dCBwZW5kaW5nKTsKIHN0YXRpYyB2b2lkIGhuX3R4ZW9mX3Rhc2tmdW5jKHZvaWQgKnhzYywgaW50 IHBlbmRpbmcpOwogc3RhdGljIGludCBobl9lbmNhcChzdHJ1Y3QgaG5fc29mdGMgKiwgc3RydWN0 IGhuX3R4ZGVzYyAqLCBzdHJ1Y3QgbWJ1ZiAqKik7CiAKLXN0YXRpYyBfX2lubGluZSB2b2lkCi1o bl9zZXRfbHJvX2hpd2F0KHN0cnVjdCBobl9zb2Z0YyAqc2MsIGludCBoaXdhdCkKLXsKLQlzYy0+ aG5fbHJvX2hpd2F0ID0gaGl3YXQ7Ci0jaWZkZWYgSE5fTFJPX0hJV0FUCi0Jc2MtPmhuX2xyby5s cm9faGl3YXQgPSBzYy0+aG5fbHJvX2hpd2F0OwotI2VuZGlmCi19Ci0KIHN0YXRpYyBpbnQKIGhu X2lmbWVkaWFfdXBkKHN0cnVjdCBpZm5ldCAqaWZwIF9fdW51c2VkKQogewpAQCAtMzU4LDcgKzM0 MSw2IEBACiAJYnplcm8oc2MsIHNpemVvZihobl9zb2Z0Y190KSk7CiAJc2MtPmhuX3VuaXQgPSB1 bml0OwogCXNjLT5obl9kZXYgPSBkZXY7Ci0Jc2MtPmhuX2xyb19oaXdhdCA9IEhOX0xST19ISVdB VF9ERUY7CiAJc2MtPmhuX2RpcmVjdF90eF9zaXplID0gaG5fZGlyZWN0X3R4X3NpemU7CiAJaWYg KGhuX3RydXN0X2hvc3R0Y3ApCiAJCXNjLT5obl90cnVzdF9oY3N1bSB8PSBITl9UUlVTVF9IQ1NV TV9UQ1A7CkBAIC00NDIsOSArNDI0LDggQEAKIAkvKiBEcml2ZXIgcHJpdmF0ZSBMUk8gc2V0dGlu Z3MgKi8KIAlzYy0+aG5fbHJvLmlmcCA9IGlmcDsKICNlbmRpZgotI2lmZGVmIEhOX0xST19ISVdB VAotCXNjLT5obl9scm8ubHJvX2hpd2F0ID0gc2MtPmhuX2xyb19oaXdhdDsKLSNlbmRpZgorCXNj LT5obl9scm8ubHJvX2Fja19hcHBlbmRfbGltID0gSE5fTFJPX0FDS19BUFBFTkRfTElNOworCXNj LT5obl9scm8ubHJvX2RhdGFfYXBwZW5kX2xpbSA9IEhOX0xST19EQVRBX0FQUEVORF9MSU07CiAj ZW5kaWYJLyogSU5FVCB8fCBJTkVUNiAqLwogCiAjaWYgX19GcmVlQlNEX3ZlcnNpb24gPj0gMTEw MDA0NQpAQCAtNDcxLDYgKzQ1MiwxMyBAQAogCSAgICBobl90eF9jaGltbmV5X3NpemUgPCBzYy0+ aG5fdHhfY2hpbW5leV9tYXgpCiAJCXNjLT5obl90eF9jaGltbmV5X3NpemUgPSBobl90eF9jaGlt bmV5X3NpemU7CiAKKwkvKgorCSAqIEFsd2F5cyBzY2hlZHVsZSB0cmFuc21pc3Npb24gaW5zdGVh ZCBvZiB0cnlpbmcKKwkgKiB0byBkbyBkaXJlY3QgdHJhbnNtaXNzaW9uLiAgVGhpcyBvbmUgZ2l2 ZXMgdGhlCisJICogYmVzdCBwZXJmb3JtYW5jZSBzbyBmYXIuCisJICovCisJc2MtPmhuX3NjaGVk X3R4ID0gMTsKKwogCWN0eCA9IGRldmljZV9nZXRfc3lzY3RsX2N0eChkZXYpOwogCWNoaWxkID0g U1lTQ1RMX0NISUxEUkVOKGRldmljZV9nZXRfc3lzY3RsX3RyZWUoZGV2KSk7CiAKQEAgLTQ4MCwx MSArNDY4LDYgQEAKIAkgICAgQ1RMRkxBR19SVywgJnNjLT5obl9scm8ubHJvX2ZsdXNoZWQsIDAs ICJMUk8gZmx1c2hlZCIpOwogCVNZU0NUTF9BRERfVUxPTkcoY3R4LCBjaGlsZCwgT0lEX0FVVE8s ICJscm9fdHJpZWQiLAogCSAgICBDVExGTEFHX1JXLCAmc2MtPmhuX2xyb190cmllZCwgIiMgb2Yg TFJPIHRyaWVzIik7Ci0jaWZkZWYgSE5fTFJPX0hJV0FUCi0JU1lTQ1RMX0FERF9QUk9DKGN0eCwg Y2hpbGQsIE9JRF9BVVRPLCAibHJvX2hpd2F0IiwKLQkgICAgQ1RMVFlQRV9JTlQgfCBDVExGTEFH X1JXLCBzYywgMCwgaG5fbHJvX2hpd2F0X3N5c2N0bCwKLQkgICAgIkkiLCAiTFJPIGhpZ2ggd2F0 ZXJtYXJrIik7Ci0jZW5kaWYKIAlTWVNDVExfQUREX1BST0MoY3R4LCBjaGlsZCwgT0lEX0FVVE8s ICJ0cnVzdF9ob3N0dGNwIiwKIAkgICAgQ1RMVFlQRV9JTlQgfCBDVExGTEFHX1JXLCBzYywgSE5f VFJVU1RfSENTVU1fVENQLAogCSAgICBobl90cnVzdF9oY3N1bV9zeXNjdGwsICJJIiwKQEAgLTUz OCw2ICs1MjEsMTQgQEAKIAkgICAgQ1RMRkxBR19SVywgJnNjLT5obl9zY2hlZF90eCwgMCwKIAkg ICAgIkFsd2F5cyBzY2hlZHVsZSB0cmFuc21pc3Npb24gIgogCSAgICAiaW5zdGVhZCBvZiBkb2lu ZyBkaXJlY3QgdHJhbnNtaXNzaW9uIik7CisJU1lTQ1RMX0FERF9QUk9DKGN0eCwgY2hpbGQsIE9J RF9BVVRPLCAibHJvX2Fja19hcHBlbmRfbGltIiwKKwkgICAgQ1RMVFlQRV9JTlQgfCBDVExGTEFH X1JXLCAmc2MtPmhuX2xyby5scm9fYWNrX2FwcGVuZF9saW0sCisJICAgIDAsIGhuX2xyb19hcHBl bmRfbGltX3N5c2N0bCwKKwkgICAgIkkiLCAiTFJPIEFDSyBhcHBlbmRpbmcgbGltaXRhdGlvbiIp OworCVNZU0NUTF9BRERfUFJPQyhjdHgsIGNoaWxkLCBPSURfQVVUTywgImxyb19kYXRhX2FwcGVu ZF9saW0iLAorCSAgICBDVExUWVBFX0lOVCB8IENUTEZMQUdfUlcsICZzYy0+aG5fbHJvLmxyb19k YXRhX2FwcGVuZF9saW0sCisJICAgIDAsIGhuX2xyb19hcHBlbmRfbGltX3N5c2N0bCwKKwkgICAg IkkiLCAiTFJPIGRhdGEgc2VnbWVudHMgYXBwZW5kaW5nIGxpbWl0YXRpb24iKTsKIAogCWlmICh1 bml0ID09IDApIHsKIAkJc3RydWN0IHN5c2N0bF9jdHhfbGlzdCAqZGNfY3R4OwpAQCAtMTQxMCwx MyArMTQwMSw2IEBACiAKIAkJLyogT2J0YWluIGFuZCByZWNvcmQgcmVxdWVzdGVkIE1UVSAqLwog CQlpZnAtPmlmX210dSA9IGlmci0+aWZyX210dTsKLQkJLyoKLQkJICogTWFrZSBzdXJlIHRoYXQg TFJPIGhpZ2ggd2F0ZXJtYXJrIGlzIHN0aWxsIHZhbGlkLAotCQkgKiBhZnRlciBNVFUgY2hhbmdl ICh0aGUgMipNVFUgbGltaXQpLgotCQkgKi8KLQkJaWYgKCFITl9MUk9fSElXQVRfSVNWQUxJRChz Yywgc2MtPmhuX2xyb19oaXdhdCkpCi0JCQlobl9zZXRfbHJvX2hpd2F0KHNjLCBITl9MUk9fSElX QVRfTVRVTElNKGlmcCkpOwotCiAJCWRvIHsKIAkJCU5WX0xPQ0soc2MpOwogCQkJaWYgKCFzYy0+ dGVtcF91bnVzYWJsZSkgewpAQCAtMTcyMiwyNyArMTcwNiw2IEBACiB9CiAjZW5kaWYKIAotI2lm ZGVmIEhOX0xST19ISVdBVAotc3RhdGljIGludAotaG5fbHJvX2hpd2F0X3N5c2N0bChTWVNDVExf SEFORExFUl9BUkdTKQotewotCXN0cnVjdCBobl9zb2Z0YyAqc2MgPSBhcmcxOwotCWludCBoaXdh dCwgZXJyb3I7Ci0KLQloaXdhdCA9IHNjLT5obl9scm9faGl3YXQ7Ci0JZXJyb3IgPSBzeXNjdGxf aGFuZGxlX2ludChvaWRwLCAmaGl3YXQsIDAsIHJlcSk7Ci0JaWYgKGVycm9yIHx8IHJlcS0+bmV3 cHRyID09IE5VTEwpCi0JCXJldHVybiBlcnJvcjsKLQotCWlmICghSE5fTFJPX0hJV0FUX0lTVkFM SUQoc2MsIGhpd2F0KSkKLQkJcmV0dXJuIEVJTlZBTDsKLQotCWlmIChzYy0+aG5fbHJvX2hpd2F0 ICE9IGhpd2F0KQotCQlobl9zZXRfbHJvX2hpd2F0KHNjLCBoaXdhdCk7Ci0JcmV0dXJuIDA7Ci19 Ci0jZW5kaWYJLyogSE5fTFJPX0hJV0FUICovCi0KIHN0YXRpYyBpbnQKIGhuX3RydXN0X2hjc3Vt X3N5c2N0bChTWVNDVExfSEFORExFUl9BUkdTKQogewpAQCAtMTc4Nyw2ICsxNzUwLDI0IEBACiB9 CiAKIHN0YXRpYyBpbnQKK2huX2xyb19hcHBlbmRfbGltX3N5c2N0bChTWVNDVExfSEFORExFUl9B UkdTKQoreworCXVuc2lnbmVkIHNob3J0ICpscm9fbGltID0gYXJnMTsKKwlpbnQgbGltLCBlcnJv cjsKKworCWxpbSA9ICpscm9fbGltOworCWVycm9yID0gc3lzY3RsX2hhbmRsZV9pbnQob2lkcCwg JmxpbSwgMCwgcmVxKTsKKwlpZiAoZXJyb3IgfHwgcmVxLT5uZXdwdHIgPT0gTlVMTCkKKwkJcmV0 dXJuIGVycm9yOworCisJaWYgKGxpbSA8IDAgfHwgbGltID4gNjU1MzUpCisJCXJldHVybiBFSU5W QUw7CisKKwkqbHJvX2xpbSA9IGxpbTsKKwlyZXR1cm4gMDsKK30KKworc3RhdGljIGludAogaG5f Y2hlY2tfaXBsZW4oY29uc3Qgc3RydWN0IG1idWYgKm0sIGludCBob2ZmKQogewogCWNvbnN0IHN0 cnVjdCBpcCAqaXA7CmRpZmYgLS1naXQgYS9zeXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0X3Zz Yy5oIGIvc3lzL2Rldi9oeXBlcnYvbmV0dnNjL2h2X25ldF92c2MuaAotLS0gYS9zeXMvZGV2L2h5 cGVydi9uZXR2c2MvaHZfbmV0X3ZzYy5oCisrKyBiL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9u ZXRfdnNjLmgKQEAgLTEwMzAsNyArMTAzMCw2IEBACiAJc3RydWN0IHRhc2sJaG5fdHhlb2ZfdGFz azsKIAogCXN0cnVjdCBscm9fY3RybAlobl9scm87Ci0JaW50CQlobl9scm9faGl3YXQ7CiAKIAkv KiBUcnVzdCBjc3VtIHZlcmlmaWNhdGlvbiBvbiBob3N0IHNpZGUgKi8KIAlpbnQJCWhuX3RydXN0 X2hjc3VtOwkvKiBITl9UUlVTVF9IQ1NVTV8gKi8KCg== --b1_84755b6b2cef604cff3734dd97c0cd84-- From owner-freebsd-virtualization@freebsd.org Thu Feb 4 08:46: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 CE6BCA9B3AB for ; Thu, 4 Feb 2016 08:46:58 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id B9428180F for ; Thu, 4 Feb 2016 08:46:58 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id B69A21076C0; Thu, 4 Feb 2016 08:46:58 +0000 (UTC) Date: Thu, 4 Feb 2016 08:46:58 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Updated] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <4b6952c13cf30262ee62b024bbb85065@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFazEAI= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 08:46:58 -0000 sepherosa_gmail.com updated the summary for this revision. REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, gallatin, hselasky, np, transport Cc: freebsd-virtualization-list, freebsd-net-list 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" From owner-freebsd-virtualization@freebsd.org Thu Feb 4 15:57:30 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 BEA63A9BE12 for ; Thu, 4 Feb 2016 15:57:30 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id A9A991F15 for ; Thu, 4 Feb 2016 15:57:30 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id A82911070E4; Thu, 4 Feb 2016 15:57:30 +0000 (UTC) Date: Thu, 4 Feb 2016 15:57:30 +0000 To: freebsd-virtualization@freebsd.org From: "gallatin (Andrew Gallatin)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Updated] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <556e744da692c1f062ea302fef94111d@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFazdOo= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 15:57:30 -0000 gallatin added a comment. It might be nice to make these general tunables that could be done centrally and apply to all drivers, but that's probably outside the scope of the review. INLINE COMMENTS sys/netinet/tcp_lro.c:655 Can you just initialize ack_append_limit to the max value for whatever type it is and eliminate the check for a 0 ack_append_limit? That would eliminate one clause from this conditional. sys/netinet/tcp_lro.c:684 Rather than adding more clauses to this condition, how would to feel about setting an append limit in bytes, and replacing the hard-coded 65535 with this new limit? The default lro init would initialize the new limit to 65535. And hn(4) would initialize it in terms of multiples of its MTU. REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Thu Feb 4 16:02:04 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 3DD6DA73297 for ; Thu, 4 Feb 2016 16:02:04 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 290BF8FF for ; Thu, 4 Feb 2016 16:02:04 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 270E31073FD; Thu, 4 Feb 2016 16:02:04 +0000 (UTC) Date: Thu, 4 Feb 2016 16:02:04 +0000 To: freebsd-virtualization@freebsd.org From: "adrian (Adrian Chadd)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Commented On] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <3bcd6f0e514da6e40d3d030a98a07083@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFazdfw= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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 16:02:04 -0000 adrian added inline comments. INLINE COMMENTS sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c:455 this should be a separate commit REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Thu Feb 4 17:00:43 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 03E55A9BD21; Thu, 4 Feb 2016 17:00:43 +0000 (UTC) (envelope-from gerd.hafenbrack@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 955F813C3; Thu, 4 Feb 2016 17:00:42 +0000 (UTC) (envelope-from gerd.hafenbrack@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id 78so40394986lfy.3; Thu, 04 Feb 2016 09:00:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=CvPqgwDgVFXy5/1A50KaO3wDd+Q/zFSud6lzREAOfiQ=; b=OnZwhSIjx8s/8ybABIiXYMMQa5BRE9U0RMvpEs+5AM46SlLo1ENcaCMCHwANeznnM/ f0EJ/WfsS1/KE76B3m6gAzB7pOt6b11Bwx/eQwr2Dj8unx9XGT3Wkwe0zsr1zKbTkHOX Cwajw1+84nOD+BCaxtbFic1zn/KisV/tIWogDGsj1u6sR0Musn5w26t7P//OqtAuflPz dcKKEdmV3I92NMdQFvMIG/9oJUpb+dweSPBaPChDQhWxUbJUvE7xdJMStpecXWMlrASp WYojp/2LW825S2XTNxu1hnXt89xEb5T8v6NbJ8Dcv/qwvbPB8EFdBZB3U/h6kXG/fxfO 0tYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=CvPqgwDgVFXy5/1A50KaO3wDd+Q/zFSud6lzREAOfiQ=; b=YY6ruPZtH60xS4VPptzQNi/rFIkCzzzcfd0Rn+XhPRu2+uJ/oLO4cx7IqpUbId4D+h QIzNpSr4FNbghQTkzhRAy8v/i5fMGw1vSr+oeTXGA/fdAb9LRqT9gj+dkvtnbBnwR3Li jyROoD7DFtz6S6wEbLrsc35/T0y4seMaVf9N76dpFD/SWAodvjLfOgbrZvoQpfERPxbN WqojJPYtLz9w4KGX9hjbLG1MvUJso9FfPVWMdtF8c8XyyLcLibE+pF1g+xOX7gLW1o9K fCD7Sufyt7+95kOwPVNA0HMysLJ1G5wfDL2VzhJUbB0AXvMUNDiu05AwOyy0RB46kdgz 5EgQ== X-Gm-Message-State: AG10YOSweucJIU80/BytxVAcF4UEGBKSBx2fQKD4csBbcyg/p6WbJcWUGhZIda4pb9kBJA== X-Received: by 10.25.39.134 with SMTP id n128mr4172509lfn.54.1454605240733; Thu, 04 Feb 2016 09:00:40 -0800 (PST) Received: from [192.168.2.103] (ipservice-092-209-164-142.092.209.pools.vodafone-ip.de. [92.209.164.142]) by smtp.googlemail.com with ESMTPSA id k3sm1659424lbp.9.2016.02.04.09.00.39 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Feb 2016 09:00:40 -0800 (PST) Subject: Re: AMD CPUs To: freebsd-xen@freebsd.org, freebsd-virtualization@freebsd.org References: <56B32F11.7050100@gmail.com> <56B34238.2070804@citrix.com> From: Gerd Hafenbrack Message-ID: <56B383B6.20100@gmail.com> Date: Thu, 4 Feb 2016 18:00:38 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56B34238.2070804@citrix.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 17:00:43 -0000 On 2016-02-04 13:21, Roger Pau Monné wrote: > El 4/2/16 a les 11:59, Gerd Hafenbrack ha escrit: >> Hello, >> >> I read on http://wiki.xen.org/wiki/FreeBSD_Dom0 the following: >>> ... to run a FreeBSD PVH Dom0 an Intel box with EPT and a working IOMMU is required. >> >> Why only intel and not an AMD CPU with Rapid Virtualization Indexing >> (RVI) and IOMMU as well? > > There's no technical reason on why this was done this way. It's just > that the original PVH implementation inside of Xen was badly designed, > and one of the results is the lack of support on AMD hardware. This is > not related to FreeBSD at all, Linux has the same exact problem. > > I'm (together with other people) currently working on removing this (and > other) stupid limitation by doing a proper implementation of PVH inside > of Xen. This new implementation is ATM called HVMlite. Sadly I can not > yet provide an ETA on when this is going to be finished. Once HVMlite is > finished inside of Xen FreeBSD will hopefully be able to run on AMD > hardware just like it does on Intel one. I will do a HEADS UP once this > is in testing state. > > Roger. Thx. I have to use an AMD box. In the meantime: bhyve? Already mature enough? or VirtualBox? From owner-freebsd-virtualization@freebsd.org Thu Feb 4 18:37:51 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 EC828A9B4D4; Thu, 4 Feb 2016 18:37:50 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B84B71D52; Thu, 4 Feb 2016 18:37:50 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-io0-x229.google.com with SMTP id f81so102560713iof.0; Thu, 04 Feb 2016 10:37:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=hNyEnWDSppDZwxp+/EkYFAHHP/YGUxP3BFTHS+F0+6s=; b=fUvcbnE5G+XbiSxYTClsKUsJ8zrOP40Jwp5UlGrRjiHStrNvA6dMoqfFdWmqS1lllZ hRmyTmj4pZRF+vWn9OqYEBeIEZQLcxbdUso4UMqAPFVojl3woMeR4E5OvfKE26RfOY89 1RrllBTPXUrOUL38s+5+S/y2/7xTthj3ap5q/tIHwqktuEhuEMQQ7bV0g0nroCqzTZ0t 2/VtYVOndp4PBRvozVWydt0KO3Vl4rfLCDtP4cYBv4x7BJfm2FKeTT3injwVTeR3tWRt 0IHBmtK8ShIhKJR+Dh1If8CuE5FG4fnT+6wCxCmzxbuY9zov3pDimxDKFsOg9jYKqSGM KgRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hNyEnWDSppDZwxp+/EkYFAHHP/YGUxP3BFTHS+F0+6s=; b=TzRsO+76B3Ow2RCZThtenOpx781KjdPzx2w3SU7eTKV9ROAqiZgFm7yK1EdHBv9Wdu yR3a1zsnE3e3QnK2LAi9YwFoFwpIk/RxH8QaxJH+n/PlHHZBfHs3yYTjC5Rk+3SK3v4p gZrGAnloETJ+zFfedsi+Z3BfRDLnFwLElVUiCSYgxCPlhl2QdCy7pz4+FS63f6WEIvUV ZZcCn1NsgxMU62CTP5qEQrFcaC30bUHgTULozEbh6FzGQWdwtDKWGCZEbz+La8dqqUiu CBr1NW20TvNgXCg1kx1ivOBlSDdvy45DDkqIggULY/0KvS63S18r230Ync0eEYJlWWF6 cAQQ== X-Gm-Message-State: AG10YORoDdfoJdRLaqbF9BOt5ME9Zg3tMPlEV/lZ1FHnQKDTfmfXmh7UhSCz6F3nVl1hrrinZKQGB3/tIauqhw== MIME-Version: 1.0 X-Received: by 10.107.154.80 with SMTP id c77mr10743215ioe.162.1454611069964; Thu, 04 Feb 2016 10:37:49 -0800 (PST) Received: by 10.107.143.193 with HTTP; Thu, 4 Feb 2016 10:37:49 -0800 (PST) In-Reply-To: <56B383B6.20100@gmail.com> References: <56B32F11.7050100@gmail.com> <56B34238.2070804@citrix.com> <56B383B6.20100@gmail.com> Date: Thu, 4 Feb 2016 12:37:49 -0600 Message-ID: Subject: Re: AMD CPUs From: Dustin Marquess To: Gerd Hafenbrack Cc: freebsd-xen@freebsd.org, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 18:37:51 -0000 I'm using bhyve on my AMD box because of this exact reason. It's working well enough for me! -Dustin On Thu, Feb 4, 2016 at 11:00 AM, Gerd Hafenbrack wrote: > On 2016-02-04 13:21, Roger Pau Monn=C3=A9 wrote: >> El 4/2/16 a les 11:59, Gerd Hafenbrack ha escrit: >>> Hello, >>> >>> I read on http://wiki.xen.org/wiki/FreeBSD_Dom0 the following: >>>> ... to run a FreeBSD PVH Dom0 an Intel box with EPT and a working IOMM= U is required. >>> >>> Why only intel and not an AMD CPU with Rapid Virtualization Indexing >>> (RVI) and IOMMU as well? >> >> There's no technical reason on why this was done this way. It's just >> that the original PVH implementation inside of Xen was badly designed, >> and one of the results is the lack of support on AMD hardware. This is >> not related to FreeBSD at all, Linux has the same exact problem. >> >> I'm (together with other people) currently working on removing this (and >> other) stupid limitation by doing a proper implementation of PVH inside >> of Xen. This new implementation is ATM called HVMlite. Sadly I can not >> yet provide an ETA on when this is going to be finished. Once HVMlite is >> finished inside of Xen FreeBSD will hopefully be able to run on AMD >> hardware just like it does on Intel one. I will do a HEADS UP once this >> is in testing state. >> >> Roger. > > Thx. > > I have to use an AMD box. > > In the meantime: > bhyve? Already mature enough? > or > VirtualBox? > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org" From owner-freebsd-virtualization@freebsd.org Fri Feb 5 01:08:30 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 E9155A9D4C9 for ; Fri, 5 Feb 2016 01:08:30 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id D537A757 for ; Fri, 5 Feb 2016 01:08:30 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id D0AD1107603; Fri, 5 Feb 2016 01:08:30 +0000 (UTC) Date: Fri, 5 Feb 2016 01:08:30 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Commented On] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <4d7a07ec20d03ae758aea62419269bc9@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFaz9g4= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 01:08:31 -0000 sepherosa_gmail.com added inline comments. INLINE COMMENTS sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c:455 OK, I will split it out. REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Fri Feb 5 01:14:03 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 67646A9D770 for ; Fri, 5 Feb 2016 01:14:03 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 53DA5B14 for ; Fri, 5 Feb 2016 01:14:03 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 5046F10799C; Fri, 5 Feb 2016 01:14:03 +0000 (UTC) Date: Fri, 5 Feb 2016 01:14:03 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Commented On] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <044574270dbd32d7174e62a2b5fed4c6@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFaz91s= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 01:14:03 -0000 sepherosa_gmail.com added a comment. I will adjust the patch accordingly. INLINE COMMENTS sys/netinet/tcp_lro.c:655 Sure :) sys/netinet/tcp_lro.c:684 Sounds fine to me. I did the byte limit before (https://reviews.freebsd.org/D4825). But it turns out the ACKs need seperate limit (append count based). To make them consistent, I changed the original patch to use append count too. REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Fri Feb 5 03:00:28 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 BAEA7A9D6E8 for ; Fri, 5 Feb 2016 03:00:28 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 9DB8F1A25 for ; Fri, 5 Feb 2016 03:00:28 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 9B34610742B; Fri, 5 Feb 2016 03:00:28 +0000 (UTC) Date: Fri, 5 Feb 2016 03:00:28 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Updated, 114 lines] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa0EEw= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_d01dabc12de4f5773c51a2be5901ed4e" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 03:00:28 -0000 --b1_d01dabc12de4f5773c51a2be5901ed4e Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit sepherosa_gmail.com updated the summary for this revision. sepherosa_gmail.com updated this revision to Diff 13028. sepherosa_gmail.com added a comment. Address gallatin and adrian's concern. CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D5185?vs=12995&id=13028 REVISION DETAIL https://reviews.freebsd.org/D5185 AFFECTED FILES sys/dev/hyperv/netvsc/hv_net_vsc.h sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c sys/netinet/tcp_lro.c sys/netinet/tcp_lro.h EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, gallatin, transport Cc: freebsd-virtualization-list, freebsd-net-list --b1_d01dabc12de4f5773c51a2be5901ed4e Content-Type: text/x-patch; charset=utf-8; name="D5185.13028.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D5185.13028.patch" ZGlmZiAtLWdpdCBhL3N5cy9uZXRpbmV0L3RjcF9scm8uaCBiL3N5cy9uZXRpbmV0L3RjcF9scm8u aAotLS0gYS9zeXMvbmV0aW5ldC90Y3BfbHJvLmgKKysrIGIvc3lzL25ldGluZXQvdGNwX2xyby5o CkBAIC05MSwxMSArOTEsMTYgQEAKIAl1bnNpZ25lZAlscm9fY250OwogCXVuc2lnbmVkCWxyb19t YnVmX2NvdW50OwogCXVuc2lnbmVkCWxyb19tYnVmX21heDsKKwl1bnNpZ25lZCBzaG9ydAlscm9f YWNrY250X2xpbTsJCS8qIG1heCAjIG9mIGFnZ3JlZ2F0ZWQgQUNLcyAqLworCXVuc2lnbmVkIHNo b3J0CWxyb19sZW5ndGhfbGltOwkJLyogbWF4IGxlbiBvZiBhZ2dyZWdhdGVkIGRhdGEgKi8KIAog CXN0cnVjdCBscm9faGVhZAlscm9fYWN0aXZlOwogCXN0cnVjdCBscm9faGVhZAlscm9fZnJlZTsK IH07CiAKKyNkZWZpbmUJVENQX0xST19MRU5HVEhfTUFYCTY1NTM1CisjZGVmaW5lCVRDUF9MUk9f QUNLQ05UX01BWAk2NTUzNQkJLyogdW5saW1pdGVkICovCisKIGludCB0Y3BfbHJvX2luaXQoc3Ry dWN0IGxyb19jdHJsICopOwogaW50IHRjcF9scm9faW5pdF9hcmdzKHN0cnVjdCBscm9fY3RybCAq LCBzdHJ1Y3QgaWZuZXQgKiwgdW5zaWduZWQsIHVuc2lnbmVkKTsKIHZvaWQgdGNwX2xyb19mcmVl KHN0cnVjdCBscm9fY3RybCAqKTsKZGlmZiAtLWdpdCBhL3N5cy9uZXRpbmV0L3RjcF9scm8uYyBi L3N5cy9uZXRpbmV0L3RjcF9scm8uYwotLS0gYS9zeXMvbmV0aW5ldC90Y3BfbHJvLmMKKysrIGIv c3lzL25ldGluZXQvdGNwX2xyby5jCkBAIC04Nyw2ICs4Nyw4IEBACiAJbGMtPmxyb19tYnVmX2Nv dW50ID0gMDsKIAlsYy0+bHJvX21idWZfbWF4ID0gbHJvX21idWZzOwogCWxjLT5scm9fY250ID0g bHJvX2VudHJpZXM7CisJbGMtPmxyb19hY2tjbnRfbGltID0gVENQX0xST19BQ0tDTlRfTUFYOwor CWxjLT5scm9fbGVuZ3RoX2xpbSA9IFRDUF9MUk9fTEVOR1RIX01BWDsKIAlsYy0+aWZwID0gaWZw OwogCVNMSVNUX0lOSVQoJmxjLT5scm9fZnJlZSk7CiAJU0xJU1RfSU5JVCgmbGMtPmxyb19hY3Rp dmUpOwpAQCAtNjA4LDcgKzYxMCw3IEBACiAJCX0KIAogCQkvKiBGbHVzaCBub3cgaWYgYXBwZW5k aW5nIHdpbGwgcmVzdWx0IGluIG92ZXJmbG93LiAqLwotCQlpZiAobGUtPnBfbGVuID4gKDY1NTM1 IC0gdGNwX2RhdGFfbGVuKSkgeworCQlpZiAobGUtPnBfbGVuID4gKGxjLT5scm9fbGVuZ3RoX2xp bSAtIHRjcF9kYXRhX2xlbikpIHsKIAkJCVNMSVNUX1JFTU9WRSgmbGMtPmxyb19hY3RpdmUsIGxl LCBscm9fZW50cnksIG5leHQpOwogCQkJdGNwX2xyb19mbHVzaChsYywgbGUpOwogCQkJYnJlYWs7 CkBAIC02NDYsNiArNjQ4LDE1IEBACiAKIAkJaWYgKHRjcF9kYXRhX2xlbiA9PSAwKSB7CiAJCQlt X2ZyZWVtKG0pOworCQkJLyoKKwkJCSAqIEZsdXNoIHRoaXMgTFJPIGVudHJ5LCBpZiB0aGlzIEFD SyBzaG91bGQgbm90CisJCQkgKiBiZSBmdXJ0aGVyIGRlbGF5ZWQuCisJCQkgKi8KKwkJCWlmIChs ZS0+YXBwZW5kX2NudCA+PSBsYy0+bHJvX2Fja2NudF9saW0pIHsKKwkJCQlTTElTVF9SRU1PVkUo JmxjLT5scm9fYWN0aXZlLCBsZSwgbHJvX2VudHJ5LAorCQkJCSAgICBuZXh0KTsKKwkJCQl0Y3Bf bHJvX2ZsdXNoKGxjLCBsZSk7CisJCQl9CiAJCQlyZXR1cm4gKDApOwogCQl9CiAKQEAgLTY2Niw3 ICs2NzcsNyBAQAogCQkgKiBJZiBhIHBvc3NpYmxlIG5leHQgZnVsbCBsZW5ndGggcGFja2V0IHdv dWxkIGNhdXNlIGFuCiAJCSAqIG92ZXJmbG93LCBwcm8tYWN0aXZlbHkgZmx1c2ggbm93LgogCQkg Ki8KLQkJaWYgKGxlLT5wX2xlbiA+ICg2NTUzNSAtIGxjLT5pZnAtPmlmX210dSkpIHsKKwkJaWYg KGxlLT5wX2xlbiA+IChsYy0+bHJvX2xlbmd0aF9saW0gLSBsYy0+aWZwLT5pZl9tdHUpKSB7CiAJ CQlTTElTVF9SRU1PVkUoJmxjLT5scm9fYWN0aXZlLCBsZSwgbHJvX2VudHJ5LCBuZXh0KTsKIAkJ CXRjcF9scm9fZmx1c2gobGMsIGxlKTsKIAkJfSBlbHNlCmRpZmYgLS1naXQgYS9zeXMvZGV2L2h5 cGVydi9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNkLmMgYi9zeXMvZGV2L2h5cGVydi9uZXR2 c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNkLmMKLS0tIGEvc3lzL2Rldi9oeXBlcnYvbmV0dnNjL2h2 X25ldHZzY19kcnZfZnJlZWJzZC5jCisrKyBiL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9uZXR2 c2NfZHJ2X2ZyZWVic2QuYwpAQCAtMTc2LDE0ICsxNzYsMTEgQEAKICNkZWZpbmUgSE5fQ1NVTV9B U1NJU1RfV0lOOAkoQ1NVTV9UQ1ApCiAjZGVmaW5lIEhOX0NTVU1fQVNTSVNUCQkoQ1NVTV9JUCB8 IENTVU1fVURQIHwgQ1NVTV9UQ1ApCiAKLS8qIFhYWCBtb3ZlIHRvIG5ldGluZXQvdGNwX2xyby5o ICovCi0jZGVmaW5lIEhOX0xST19ISVdBVF9NQVgJCQkJNjU1MzUKLSNkZWZpbmUgSE5fTFJPX0hJ V0FUX0RFRgkJCQlITl9MUk9fSElXQVRfTUFYCisjZGVmaW5lIEhOX0xST19MRU5MSU1fREVGCQko MjUgKiBFVEhFUk1UVSkKIC8qIFlZWSAyKk1UVSBpcyBhIGJpdCByb3VnaCwgYnV0IHNob3VsZCBi ZSBnb29kIGVub3VnaC4gKi8KLSNkZWZpbmUgSE5fTFJPX0hJV0FUX01UVUxJTShpZnApCQkJKDIg KiAoaWZwKS0+aWZfbXR1KQotI2RlZmluZSBITl9MUk9fSElXQVRfSVNWQUxJRChzYywgaGl3YXQp CQkJXAotICAgICgoaGl3YXQpID49IEhOX0xST19ISVdBVF9NVFVMSU0oKHNjKS0+aG5faWZwKSB8 fAlcCi0gICAgIChoaXdhdCkgPD0gSE5fTFJPX0hJV0FUX01BWCkKKyNkZWZpbmUgSE5fTFJPX0xF TkxJTV9NSU4oaWZwKQkJKDIgKiAoaWZwKS0+aWZfbXR1KQorCisjZGVmaW5lIEhOX0xST19BQ0tD TlRfREVGCQkxCiAKIC8qCiAgKiBCZSBhd2FyZSB0aGF0IHRoaXMgc2xlZXBhYmxlIG11dGV4IHdp bGwgZXhoaWJpdCBXSVRORVNTIGVycm9ycyB3aGVuCkBAIC0yNTMsOSArMjUwLDggQEAKIHN0YXRp YyB2b2lkIGhuX3N0YXJ0X3R4ZW9mKHN0cnVjdCBpZm5ldCAqaWZwKTsKIHN0YXRpYyBpbnQgaG5f aWZtZWRpYV91cGQoc3RydWN0IGlmbmV0ICppZnApOwogc3RhdGljIHZvaWQgaG5faWZtZWRpYV9z dHMoc3RydWN0IGlmbmV0ICppZnAsIHN0cnVjdCBpZm1lZGlhcmVxICppZm1yKTsKLSNpZmRlZiBI Tl9MUk9fSElXQVQKLXN0YXRpYyBpbnQgaG5fbHJvX2hpd2F0X3N5c2N0bChTWVNDVExfSEFORExF Ul9BUkdTKTsKLSNlbmRpZgorc3RhdGljIGludCBobl9scm9fbGVubGltX3N5c2N0bChTWVNDVExf SEFORExFUl9BUkdTKTsKK3N0YXRpYyBpbnQgaG5fbHJvX2Fja2NudF9zeXNjdGwoU1lTQ1RMX0hB TkRMRVJfQVJHUyk7CiBzdGF0aWMgaW50IGhuX3RydXN0X2hjc3VtX3N5c2N0bChTWVNDVExfSEFO RExFUl9BUkdTKTsKIHN0YXRpYyBpbnQgaG5fdHhfY2hpbW5leV9zaXplX3N5c2N0bChTWVNDVExf SEFORExFUl9BUkdTKTsKIHN0YXRpYyBpbnQgaG5fY2hlY2tfaXBsZW4oY29uc3Qgc3RydWN0IG1i dWYgKiwgaW50KTsKQEAgLTI2NSwxNSArMjYxLDYgQEAKIHN0YXRpYyB2b2lkIGhuX3R4ZW9mX3Rh c2tmdW5jKHZvaWQgKnhzYywgaW50IHBlbmRpbmcpOwogc3RhdGljIGludCBobl9lbmNhcChzdHJ1 Y3QgaG5fc29mdGMgKiwgc3RydWN0IGhuX3R4ZGVzYyAqLCBzdHJ1Y3QgbWJ1ZiAqKik7CiAKLXN0 YXRpYyBfX2lubGluZSB2b2lkCi1obl9zZXRfbHJvX2hpd2F0KHN0cnVjdCBobl9zb2Z0YyAqc2Ms IGludCBoaXdhdCkKLXsKLQlzYy0+aG5fbHJvX2hpd2F0ID0gaGl3YXQ7Ci0jaWZkZWYgSE5fTFJP X0hJV0FUCi0Jc2MtPmhuX2xyby5scm9faGl3YXQgPSBzYy0+aG5fbHJvX2hpd2F0OwotI2VuZGlm Ci19Ci0KIHN0YXRpYyBpbnQKIGhuX2lmbWVkaWFfdXBkKHN0cnVjdCBpZm5ldCAqaWZwIF9fdW51 c2VkKQogewpAQCAtMzU4LDcgKzM0NSw2IEBACiAJYnplcm8oc2MsIHNpemVvZihobl9zb2Z0Y190 KSk7CiAJc2MtPmhuX3VuaXQgPSB1bml0OwogCXNjLT5obl9kZXYgPSBkZXY7Ci0Jc2MtPmhuX2xy b19oaXdhdCA9IEhOX0xST19ISVdBVF9ERUY7CiAJc2MtPmhuX2RpcmVjdF90eF9zaXplID0gaG5f ZGlyZWN0X3R4X3NpemU7CiAJaWYgKGhuX3RydXN0X2hvc3R0Y3ApCiAJCXNjLT5obl90cnVzdF9o Y3N1bSB8PSBITl9UUlVTVF9IQ1NVTV9UQ1A7CkBAIC00NDIsOSArNDI4LDggQEAKIAkvKiBEcml2 ZXIgcHJpdmF0ZSBMUk8gc2V0dGluZ3MgKi8KIAlzYy0+aG5fbHJvLmlmcCA9IGlmcDsKICNlbmRp ZgotI2lmZGVmIEhOX0xST19ISVdBVAotCXNjLT5obl9scm8ubHJvX2hpd2F0ID0gc2MtPmhuX2xy b19oaXdhdDsKLSNlbmRpZgorCXNjLT5obl9scm8ubHJvX2xlbmd0aF9saW0gPSBITl9MUk9fTEVO TElNX0RFRjsKKwlzYy0+aG5fbHJvLmxyb19hY2tjbnRfbGltID0gSE5fTFJPX0FDS0NOVF9ERUY7 CiAjZW5kaWYJLyogSU5FVCB8fCBJTkVUNiAqLwogCiAjaWYgX19GcmVlQlNEX3ZlcnNpb24gPj0g MTEwMDA0NQpAQCAtNDgwLDExICs0NjUsMTIgQEAKIAkgICAgQ1RMRkxBR19SVywgJnNjLT5obl9s cm8ubHJvX2ZsdXNoZWQsIDAsICJMUk8gZmx1c2hlZCIpOwogCVNZU0NUTF9BRERfVUxPTkcoY3R4 LCBjaGlsZCwgT0lEX0FVVE8sICJscm9fdHJpZWQiLAogCSAgICBDVExGTEFHX1JXLCAmc2MtPmhu X2xyb190cmllZCwgIiMgb2YgTFJPIHRyaWVzIik7Ci0jaWZkZWYgSE5fTFJPX0hJV0FUCi0JU1lT Q1RMX0FERF9QUk9DKGN0eCwgY2hpbGQsIE9JRF9BVVRPLCAibHJvX2hpd2F0IiwKLQkgICAgQ1RM VFlQRV9JTlQgfCBDVExGTEFHX1JXLCBzYywgMCwgaG5fbHJvX2hpd2F0X3N5c2N0bCwKLQkgICAg IkkiLCAiTFJPIGhpZ2ggd2F0ZXJtYXJrIik7Ci0jZW5kaWYKKwlTWVNDVExfQUREX1BST0MoY3R4 LCBjaGlsZCwgT0lEX0FVVE8sICJscm9fbGVuZ3RoX2xpbSIsCisJICAgIENUTFRZUEVfSU5UIHwg Q1RMRkxBR19SVywgc2MsIDAsIGhuX2xyb19sZW5saW1fc3lzY3RsLCAiSSIsCisJICAgICJNYXgg IyBvZiBkYXRhIGJ5dGVzIHRvIGJlIGFnZ3JlZ2F0ZWQgYnkgTFJPIik7CisJU1lTQ1RMX0FERF9Q Uk9DKGN0eCwgY2hpbGQsIE9JRF9BVVRPLCAibHJvX2Fja2NudF9saW0iLAorCSAgICBDVExUWVBF X0lOVCB8IENUTEZMQUdfUlcsIHNjLCAwLCBobl9scm9fYWNrY250X3N5c2N0bCwgIkkiLAorCSAg ICAiTWF4ICMgb2YgQUNLcyB0byBiZSBhZ2dyZWdhdGVkIGJ5IExSTyIpOwogCVNZU0NUTF9BRERf UFJPQyhjdHgsIGNoaWxkLCBPSURfQVVUTywgInRydXN0X2hvc3R0Y3AiLAogCSAgICBDVExUWVBF X0lOVCB8IENUTEZMQUdfUlcsIHNjLCBITl9UUlVTVF9IQ1NVTV9UQ1AsCiAJICAgIGhuX3RydXN0 X2hjc3VtX3N5c2N0bCwgIkkiLApAQCAtMTQxMCwxMiArMTM5NiwxMyBAQAogCiAJCS8qIE9idGFp biBhbmQgcmVjb3JkIHJlcXVlc3RlZCBNVFUgKi8KIAkJaWZwLT5pZl9tdHUgPSBpZnItPmlmcl9t dHU7CisKIAkJLyoKLQkJICogTWFrZSBzdXJlIHRoYXQgTFJPIGhpZ2ggd2F0ZXJtYXJrIGlzIHN0 aWxsIHZhbGlkLAotCQkgKiBhZnRlciBNVFUgY2hhbmdlICh0aGUgMipNVFUgbGltaXQpLgorCQkg KiBNYWtlIHN1cmUgdGhhdCBMUk8gYWdncmVnYXRpb24gbGVuZ3RoIGxpbWl0IGlzIHN0aWxsCisJ CSAqIHZhbGlkLCBhZnRlciB0aGUgTVRVIGNoYW5nZS4KIAkJICovCi0JCWlmICghSE5fTFJPX0hJ V0FUX0lTVkFMSUQoc2MsIHNjLT5obl9scm9faGl3YXQpKQotCQkJaG5fc2V0X2xyb19oaXdhdChz YywgSE5fTFJPX0hJV0FUX01UVUxJTShpZnApKTsKKwkJaWYgKHNjLT5obl9scm8ubHJvX2xlbmd0 aF9saW0gPCBITl9MUk9fTEVOTElNX01JTihpZnApKQorCQkJc2MtPmhuX2xyby5scm9fbGVuZ3Ro X2xpbSA9IEhOX0xST19MRU5MSU1fTUlOKGlmcCk7CiAKIAkJZG8gewogCQkJTlZfTE9DSyhzYyk7 CkBAIC0xNzIyLDI2ICsxNzA5LDUwIEBACiB9CiAjZW5kaWYKIAotI2lmZGVmIEhOX0xST19ISVdB VAogc3RhdGljIGludAotaG5fbHJvX2hpd2F0X3N5c2N0bChTWVNDVExfSEFORExFUl9BUkdTKQor aG5fbHJvX2xlbmxpbV9zeXNjdGwoU1lTQ1RMX0hBTkRMRVJfQVJHUykKK3sKKwlzdHJ1Y3QgaG5f c29mdGMgKnNjID0gYXJnMTsKKwlpbnQgbGVubGltLCBlcnJvcjsKKworCWxlbmxpbSA9IHNjLT5o bl9scm8ubHJvX2xlbmd0aF9saW07CisJZXJyb3IgPSBzeXNjdGxfaGFuZGxlX2ludChvaWRwLCAm bGVubGltLCAwLCByZXEpOworCWlmIChlcnJvciB8fCByZXEtPm5ld3B0ciA9PSBOVUxMKQorCQly ZXR1cm4gZXJyb3I7CisKKwlpZiAobGVubGltIDwgSE5fTFJPX0xFTkxJTV9NSU4oc2MtPmhuX2lm cCkgfHwKKwkgICAgbGVubGltID4gVENQX0xST19MRU5HVEhfTUFYKQorCQlyZXR1cm4gRUlOVkFM OworCisJc2MtPmhuX2xyby5scm9fbGVuZ3RoX2xpbSA9IGxlbmxpbTsKKwlyZXR1cm4gMDsKK30K Kworc3RhdGljIGludAoraG5fbHJvX2Fja2NudF9zeXNjdGwoU1lTQ1RMX0hBTkRMRVJfQVJHUykK IHsKIAlzdHJ1Y3QgaG5fc29mdGMgKnNjID0gYXJnMTsKLQlpbnQgaGl3YXQsIGVycm9yOworCWlu dCBhY2tjbnQsIGVycm9yOwogCi0JaGl3YXQgPSBzYy0+aG5fbHJvX2hpd2F0OwotCWVycm9yID0g c3lzY3RsX2hhbmRsZV9pbnQob2lkcCwgJmhpd2F0LCAwLCByZXEpOworCS8qCisJICogbHJvX2Fj a2NudF9saW0gaXMgYXBwZW5kIGNvdW50IGxpbWl0LAorCSAqICsxIHRvIHR1cm4gaXQgaW50byBh Z2dyZWdhdGlvbiBsaW1pdC4KKwkgKi8KKwlhY2tjbnQgPSBzYy0+aG5fbHJvLmxyb19hY2tjbnRf bGltICsgMTsKKwllcnJvciA9IHN5c2N0bF9oYW5kbGVfaW50KG9pZHAsICZhY2tjbnQsIDAsIHJl cSk7CiAJaWYgKGVycm9yIHx8IHJlcS0+bmV3cHRyID09IE5VTEwpCiAJCXJldHVybiBlcnJvcjsK IAotCWlmICghSE5fTFJPX0hJV0FUX0lTVkFMSUQoc2MsIGhpd2F0KSkKKwlpZiAoYWNrY250IDwg MiB8fCBhY2tjbnQgPiAoVENQX0xST19BQ0tDTlRfTUFYICsgMSkpCiAJCXJldHVybiBFSU5WQUw7 CiAKLQlpZiAoc2MtPmhuX2xyb19oaXdhdCAhPSBoaXdhdCkKLQkJaG5fc2V0X2xyb19oaXdhdChz YywgaGl3YXQpOworCS8qCisJICogQ29udmVydCBhZ2dyZWdhdGlvbiBsaW1pdCBiYWNrIHRvIGFw cGVuZAorCSAqIGNvdW50IGxpbWl0LgorCSAqLworCXNjLT5obl9scm8ubHJvX2Fja2NudF9saW0g PSBhY2tjbnQgLSAxOwogCXJldHVybiAwOwogfQotI2VuZGlmCS8qIEhOX0xST19ISVdBVCAqLwog CiBzdGF0aWMgaW50CiBobl90cnVzdF9oY3N1bV9zeXNjdGwoU1lTQ1RMX0hBTkRMRVJfQVJHUykK ZGlmZiAtLWdpdCBhL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9uZXRfdnNjLmggYi9zeXMvZGV2 L2h5cGVydi9uZXR2c2MvaHZfbmV0X3ZzYy5oCi0tLSBhL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9o dl9uZXRfdnNjLmgKKysrIGIvc3lzL2Rldi9oeXBlcnYvbmV0dnNjL2h2X25ldF92c2MuaApAQCAt MTAzMCw3ICsxMDMwLDYgQEAKIAlzdHJ1Y3QgdGFzawlobl90eGVvZl90YXNrOwogCiAJc3RydWN0 IGxyb19jdHJsCWhuX2xybzsKLQlpbnQJCWhuX2xyb19oaXdhdDsKIAogCS8qIFRydXN0IGNzdW0g dmVyaWZpY2F0aW9uIG9uIGhvc3Qgc2lkZSAqLwogCWludAkJaG5fdHJ1c3RfaGNzdW07CS8qIEhO X1RSVVNUX0hDU1VNXyAqLwoK --b1_d01dabc12de4f5773c51a2be5901ed4e-- From owner-freebsd-virtualization@freebsd.org Fri Feb 5 05:51:23 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 649DCA9A454 for ; Fri, 5 Feb 2016 05:51:23 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 4F1071EC5 for ; Fri, 5 Feb 2016 05:51:23 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 4E6E1107296; Fri, 5 Feb 2016 05:51:23 +0000 (UTC) Date: Fri, 5 Feb 2016 05:51:23 +0000 To: freebsd-virtualization@freebsd.org From: Phabricator Reply-to: D5175+333+519ccacf1c2a3a95@reviews.freebsd.org Subject: [Differential] [Closed] D5175: hyperv/hn: Add an option to always do transmission scheduling Message-ID: <68411d8e22aef06adf3480219cafe460@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D5175: hyperv/hn: Add an option to always do transmission scheduling X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: OGFmNjgzYWFmZmVhMjQ0MTIwYzQ1OWJjZDg2IFa0OFs= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_68411d8e22aef06adf3480219cafe460" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 05:51:23 -0000 --b1_68411d8e22aef06adf3480219cafe460 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit This revision was automatically updated to reflect the committed changes. Closed by commit rS295306: hyperv/hn: Add an option to always do transmission scheduling (authored by sephe). CHANGED PRIOR TO COMMIT https://reviews.freebsd.org/D5175?vs=12968&id=13040#toc REPOSITORY rS FreeBSD src repository CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D5175?vs=12968&id=13040 REVISION DETAIL https://reviews.freebsd.org/D5175 AFFECTED FILES head/sys/dev/hyperv/netvsc/hv_net_vsc.h head/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c CHANGE DETAILS diff --git a/head/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c b/head/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c --- a/head/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c +++ b/head/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c @@ -534,6 +534,10 @@ SYSCTL_ADD_INT(ctx, child, OID_AUTO, "direct_tx_size", CTLFLAG_RW, &sc->hn_direct_tx_size, 0, "Size of the packet for direct transmission"); + SYSCTL_ADD_INT(ctx, child, OID_AUTO, "sched_tx", + CTLFLAG_RW, &sc->hn_sched_tx, 0, + "Always schedule transmission " + "instead of doing direct transmission"); if (unit == 0) { struct sysctl_ctx_list *dc_ctx; @@ -1602,26 +1606,31 @@ static void hn_start(struct ifnet *ifp) { - hn_softc_t *sc; + struct hn_softc *sc = ifp->if_softc; + + if (sc->hn_sched_tx) + goto do_sched; - sc = ifp->if_softc; if (NV_TRYLOCK(sc)) { int sched; sched = hn_start_locked(ifp, sc->hn_direct_tx_size); NV_UNLOCK(sc); if (!sched) return; } +do_sched: taskqueue_enqueue_fast(sc->hn_tx_taskq, &sc->hn_start_task); } static void hn_start_txeof(struct ifnet *ifp) { - hn_softc_t *sc; + struct hn_softc *sc = ifp->if_softc; + + if (sc->hn_sched_tx) + goto do_sched; - sc = ifp->if_softc; if (NV_TRYLOCK(sc)) { int sched; @@ -1633,6 +1642,7 @@ &sc->hn_start_task); } } else { +do_sched: /* * Release the OACTIVE earlier, with the hope, that * others could catch up. The task will clear the diff --git a/head/sys/dev/hyperv/netvsc/hv_net_vsc.h b/head/sys/dev/hyperv/netvsc/hv_net_vsc.h --- a/head/sys/dev/hyperv/netvsc/hv_net_vsc.h +++ b/head/sys/dev/hyperv/netvsc/hv_net_vsc.h @@ -1023,6 +1023,7 @@ int hn_txdesc_avail; int hn_txeof; + int hn_sched_tx; int hn_direct_tx_size; struct taskqueue *hn_tx_taskq; struct task hn_start_task; EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, howard0su_gmail.com, adrian, network, honzhan_microsoft.com Cc: freebsd-virtualization-list, freebsd-net-list --b1_68411d8e22aef06adf3480219cafe460 Content-Type: text/x-patch; charset=utf-8; name="D5175.13040.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D5175.13040.patch" ZGlmZiAtLWdpdCBhL2hlYWQvc3lzL2Rldi9oeXBlcnYvbmV0dnNjL2h2X25ldHZzY19kcnZfZnJl ZWJzZC5jIGIvaGVhZC9zeXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNk LmMKLS0tIGEvaGVhZC9zeXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNk LmMKKysrIGIvaGVhZC9zeXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0dnNjX2Rydl9mcmVlYnNk LmMKQEAgLTUzNCw2ICs1MzQsMTAgQEAKIAlTWVNDVExfQUREX0lOVChjdHgsIGNoaWxkLCBPSURf QVVUTywgImRpcmVjdF90eF9zaXplIiwKIAkgICAgQ1RMRkxBR19SVywgJnNjLT5obl9kaXJlY3Rf dHhfc2l6ZSwgMCwKIAkgICAgIlNpemUgb2YgdGhlIHBhY2tldCBmb3IgZGlyZWN0IHRyYW5zbWlz c2lvbiIpOworCVNZU0NUTF9BRERfSU5UKGN0eCwgY2hpbGQsIE9JRF9BVVRPLCAic2NoZWRfdHgi LAorCSAgICBDVExGTEFHX1JXLCAmc2MtPmhuX3NjaGVkX3R4LCAwLAorCSAgICAiQWx3YXlzIHNj aGVkdWxlIHRyYW5zbWlzc2lvbiAiCisJICAgICJpbnN0ZWFkIG9mIGRvaW5nIGRpcmVjdCB0cmFu c21pc3Npb24iKTsKIAogCWlmICh1bml0ID09IDApIHsKIAkJc3RydWN0IHN5c2N0bF9jdHhfbGlz dCAqZGNfY3R4OwpAQCAtMTYwMiwyNiArMTYwNiwzMSBAQAogc3RhdGljIHZvaWQKIGhuX3N0YXJ0 KHN0cnVjdCBpZm5ldCAqaWZwKQogewotCWhuX3NvZnRjX3QgKnNjOworCXN0cnVjdCBobl9zb2Z0 YyAqc2MgPSBpZnAtPmlmX3NvZnRjOworCisJaWYgKHNjLT5obl9zY2hlZF90eCkKKwkJZ290byBk b19zY2hlZDsKIAotCXNjID0gaWZwLT5pZl9zb2Z0YzsKIAlpZiAoTlZfVFJZTE9DSyhzYykpIHsK IAkJaW50IHNjaGVkOwogCiAJCXNjaGVkID0gaG5fc3RhcnRfbG9ja2VkKGlmcCwgc2MtPmhuX2Rp cmVjdF90eF9zaXplKTsKIAkJTlZfVU5MT0NLKHNjKTsKIAkJaWYgKCFzY2hlZCkKIAkJCXJldHVy bjsKIAl9Citkb19zY2hlZDoKIAl0YXNrcXVldWVfZW5xdWV1ZV9mYXN0KHNjLT5obl90eF90YXNr cSwgJnNjLT5obl9zdGFydF90YXNrKTsKIH0KIAogc3RhdGljIHZvaWQKIGhuX3N0YXJ0X3R4ZW9m KHN0cnVjdCBpZm5ldCAqaWZwKQogewotCWhuX3NvZnRjX3QgKnNjOworCXN0cnVjdCBobl9zb2Z0 YyAqc2MgPSBpZnAtPmlmX3NvZnRjOworCisJaWYgKHNjLT5obl9zY2hlZF90eCkKKwkJZ290byBk b19zY2hlZDsKIAotCXNjID0gaWZwLT5pZl9zb2Z0YzsKIAlpZiAoTlZfVFJZTE9DSyhzYykpIHsK IAkJaW50IHNjaGVkOwogCkBAIC0xNjMzLDYgKzE2NDIsNyBAQAogCQkJICAgICZzYy0+aG5fc3Rh cnRfdGFzayk7CiAJCX0KIAl9IGVsc2UgeworZG9fc2NoZWQ6CiAJCS8qCiAJCSAqIFJlbGVhc2Ug dGhlIE9BQ1RJVkUgZWFybGllciwgd2l0aCB0aGUgaG9wZSwgdGhhdAogCQkgKiBvdGhlcnMgY291 bGQgY2F0Y2ggdXAuICBUaGUgdGFzayB3aWxsIGNsZWFyIHRoZQpkaWZmIC0tZ2l0IGEvaGVhZC9z eXMvZGV2L2h5cGVydi9uZXR2c2MvaHZfbmV0X3ZzYy5oIGIvaGVhZC9zeXMvZGV2L2h5cGVydi9u ZXR2c2MvaHZfbmV0X3ZzYy5oCi0tLSBhL2hlYWQvc3lzL2Rldi9oeXBlcnYvbmV0dnNjL2h2X25l dF92c2MuaAorKysgYi9oZWFkL3N5cy9kZXYvaHlwZXJ2L25ldHZzYy9odl9uZXRfdnNjLmgKQEAg LTEwMjMsNiArMTAyMyw3IEBACiAJaW50CQlobl90eGRlc2NfYXZhaWw7CiAJaW50CQlobl90eGVv ZjsKIAorCWludAkJaG5fc2NoZWRfdHg7CiAJaW50CQlobl9kaXJlY3RfdHhfc2l6ZTsKIAlzdHJ1 Y3QgdGFza3F1ZXVlICpobl90eF90YXNrcTsKIAlzdHJ1Y3QgdGFzawlobl9zdGFydF90YXNrOwoK --b1_68411d8e22aef06adf3480219cafe460-- From owner-freebsd-virtualization@freebsd.org Fri Feb 5 07:54:52 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 BA92A9D93D4 for ; Fri, 5 Feb 2016 07:54:52 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7AE111EDF for ; Fri, 5 Feb 2016 07:54:47 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 591252B944A; Fri, 5 Feb 2016 08:54:38 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 18529-10; Fri, 5 Feb 2016 08:54:37 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id EF9C72B9448; Fri, 5 Feb 2016 08:54:36 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Fri, 5 Feb 2016 08:54:36 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Fri, 5 Feb 2016 08:54:36 +0100 From: Jac Backus To: 'Dexuan Cui' , "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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZAAANu3cAAenrMwAA2JiMAANmckAA== Date: Fri, 5 Feb 2016 07:54:35 +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: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.101] MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 05 Feb 2016 12:16:28 +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: Fri, 05 Feb 2016 07:54:52 -0000 Hello Dexuan, I build a new kernel and the problem is gone. I tried to understand your description of the patch. What I find remarkable= is, that there is apparently no fixed relation between the virtual nics de= fined in Hyper-V (with a fixed mac address) and the devices, hn0, hn1, etc = in the guest, and is the order determined at boot time. Something completely different: maybe you can point me to an explanation o= f these messages when I boot: calcru: runtime went backwards from 1672 usec to 845 usec for pid 144 (adjk= erntz) calcru: runtime went backwards from 5 usec to 2 usec for pid 7 (pagezero) calcru: runtime went backwards from 126 usec to 63 usec for pid 4 (sctp_ite= rator) calcru: runtime went backwards from 6920 usec to 3743 usec for pid 3 (fdc0) calcru: runtime went backwards from 33080 usec to 16732 usec for pid 13 (ge= om) calcru: runtime went backwards from 12117 usec to 6318 usec for pid 1 (init= ) calcru: runtime went backwards from 155335 usec to 104098 usec for pid 0 (k= ernel) I happens since I virtualized the server. Again, I thank you very much for the help. And, of course, especially for t= he fix! With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: donderdag 4 februari 2016 7:01 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, 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 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, 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" From owner-freebsd-virtualization@freebsd.org Fri Feb 5 12:55:35 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 E86CCA77EA4 for ; Fri, 5 Feb 2016 12:55:34 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0145.outbound.protection.outlook.com [207.46.100.145]) (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 300CAD4 for ; Fri, 5 Feb 2016 12:55:33 +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=HRyHMgtSXMGtZVS5leHrKXRAr06CzDHVgfNj1DNutC4=; b=Fq25VxqlMy+xKZHgAD+47zLBtz1KFe0ieyR2aN5PbvXwg8WL0JclbQf+KthzsI2f9Zsrg8rCCcV4POyAgVUDyjUC7hfM9rzQgIBkyd7Wywax4ZeU6f6Hx5/I8AJZngpMLbbaYfR4pYMYERMTAyPlsl5GJ2duwqRtDH1hO4zmid0= Received: from BN3PR0301CA0025.namprd03.prod.outlook.com (10.160.180.163) by CY1PR0301MB0842.namprd03.prod.outlook.com (10.160.163.148) with Microsoft SMTP Server (TLS) id 15.1.403.16; Fri, 5 Feb 2016 08:23:03 +0000 Received: from BY2FFO11FD015.protection.gbl (2a01:111:f400:7c0c::111) by BN3PR0301CA0025.outlook.office365.com (2a01:111:e400:4000::35) with Microsoft SMTP Server (TLS) id 15.1.403.16 via Frontend Transport; Fri, 5 Feb 2016 08:23:03 +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 BY2FFO11FD015.mail.protection.outlook.com (10.1.14.131) with Microsoft SMTP Server (TLS) id 15.1.409.7 via Frontend Transport; Fri, 5 Feb 2016 08:23:02 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) by HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) with Microsoft SMTP Server (TLS) id 15.1.409.10; Fri, 5 Feb 2016 08:22:57 +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.0409.010; Fri, 5 Feb 2016 08:22:57 +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/D1AASYVK4AAUkXXgABTfDnAAFm9KUAAPGOaQAADXxAAARLesMAAMBcNAABCbgZAAANu3cAAenrMwAA2JiMAANmckAAABL75w Date: Fri, 5 Feb 2016 08:22:56 +0000 Message-ID: <2cdde8e104d04875a3e2614686426375@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> <17b639f383df4f42b1e050f6e40d1ad2@HKXPR3004MB0088.064d.mgd.msft.net> <53238096372f4362b436382a430bde57@ORTELIUS.internal.bugworks.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [141.251.56.4] X-MS-Office365-Filtering-Correlation-Id: 223a8e23-752a-47fa-94dc-08d32e0590c0 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD015; 1:4Tkbs9+gEv/c9GhVOgOTrHXu6KhSE2P7AOEVPQTbGiGXtr+IOb21s5gCQAjpeegyddYX1UxoG1hGV1RIitZ5IKWZVME+03nVxQ6liqc3u6TlBfwE6MNYivF2mgwtmc35oyamhk+PY2wFhDay30BbwM7mM9SsWGohFz84inSt1pFSB9ZhrOWXqsFpWfBM9SPJcnx2yWsOLzR2FTmh9aeE2ImI6xtn3VIJv8JCUYmCCgsJH2CvAdiKEhaqBSe09HvBciqlw+YoZl5c7ZFrwyR3NI4uRBp+LLEPTtHpJbuof9MoJ3yoCzUOcpU9SgtOHsQQi9lvfcFhJ1f6xDe4WbhLEQ== 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)(52604005)(199003)(3905003)(45984002)?= =?us-ascii?Q?(164054003)(51914003)(189002)(71364002)(13464003)(377424004)?= =?us-ascii?Q?(377454003)(5008740100001)(76176999)(24736003)(50986999)(589?= =?us-ascii?Q?0100001)(15975445007)(19627595001)(5001770100001)(2561002)(9?= =?us-ascii?Q?9936001)(2900100001)(18206015028)(3900700001)(106466001)(108?= =?us-ascii?Q?616004)(5003600100002)(5001960100002)(54356999)(107886002)(8?= =?us-ascii?Q?6146001)(6806005)(5005710100001)(11100500001)(189998001)(512?= =?us-ascii?Q?954002)(2906002)(19300405004)(19617315012)(2950100001)(10400?= =?us-ascii?Q?500002)(16236675004)(87936001)(5004730100002)(92566002)(1776?= =?us-ascii?Q?0045003)(66066001)(67866002)(300700001)(33646002)(1958040500?= =?us-ascii?Q?1)(19580395003)(1511001)(3846002)(102836003)(86362001)(58600?= =?us-ascii?Q?3)(10290500002)(2421001)(1096002)(66926002)(575784001)(12207?= =?us-ascii?Q?00001)(6116002)(19625215002)(16796002)(84326002)(40014501000?= =?us-ascii?Q?02)(10090500001)(790700001)(93886004)(260700001)(7099028)(49?= =?us-ascii?Q?1001)(559001)(579004)(562774006);DIR:OUT;SFP:1102;SCL:1;SRVR?= =?us-ascii?Q?:CY1PR0301MB0842;H:064-smtp-out.microsoft.com;FPR:;SPF:Pass;?= =?us-ascii?Q?MLV:sfv;A:1;MX:1;LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0842; 2:gvxgFq7rP0IvcbHh/zMDn28qNrqy84zkNt9XFywSe329zNcdZbt5nRY52lWAjq9/UlUBzqIlwM32fOksOXbhcMy/DOjSSs6WhXBiVci7oNjOoYGDKfMDIvTGuiLHBqKLKvbloOEhJBweA+LPJFLzJHJVysiUKkcGXM6TFbpTSuRoTJuh/oPmqbsG27evNwcw; 3:IhiyLqrlbuK69Tlh3EG7pprP5aayzI03y3bmk3PPngVbSPOrAM66TqHRRm43mwAjSmlXW4R5rVNafx8FCPJ3PGIPgD0kMshZ00D9ovA7MRtIzV7g811AfzV8/I8rz6N5JqmyxDsuAGo94d+VHw41L/tWFtVy9l1Jwa6uk3WCwnBfP1rCx186ISfz9rDNTmg8P14C1nUcae2udV64eAYwROFvOjTw7I8G5GK0bOD36ID3E9f56rociBKI/zzc+tCT43R4v/90ip/yDGRpLTzofQ==; 25:DbQQqkC2RzK5a0LpkFDpyUp1fTzgDIhRdR2ZXrhrOxQwk7b74g/syIIVTfnDd8c4SSZDSp6y0F0YrAVwMuP7fiVRCB/pH6V6CZUyP5lIm7SAJB6HnXcc9m3rnRI1LjkRXj+UPex2N45d217gEEEfW5jw/Mo5VtHO7R2h/79oonxFpKw7UhWg1fSz5xCNVSpBUduQAkM3UF2UI5GmJnpWRD0QDFngMSvlYge/mlgO0ouUFld0mkG+163I88GBsKiqA4XIz5GG4C3CnBsWWaAeogC5/shKQcMgeeRtPbiwho+e8iKWg4D2mEUCkiQXdl04izEJcB8lzk79HCAYuWZkMbfkjBtZM6wbBMhSx7DWCK8= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:CY1PR0301MB0842; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0842; 20:75VMNnMSgdn27o1NHjg/I4QXHPYCckckIDd02M5Fg1OSxXP3qQVx4hH/3QTFAFIvExmZgMlIOZdMCKutA5+UDnajcCK+mMK7U+LHy//AfCsjs9Pen9JxULV1DPB+Rpb1Sh2oWe+XQ6HocCrBELH1l2sSQNPNO+HT6Y9oWaN73TZSchhDRt/E52Ec5nsPyxHa9osKtcHNF/2v7V2fpZBsHl8hnuTsLreF1eVxY24wDxGjhxuQnJyYPtkt1s8ElHM9r+mPeiN1w/iWZYT3fkPBPzvZgExuPwSwTi7E05ACdSQ/9+1cfwgi5RdXkbCqU0rrCt2L0Z6xFb4G1WOgOhjoyboqa/kV/VpVMrPlZbOajZP3vPYX+8H9mw96Lf2jQePc4yYcL2azi7N3C9KOmZ8IG4JOmNMqLcljjjEns4/73ZJ+K+TtR0BLG1qBFB3EexIZDoOkpzqzz1qXdnhHAD4g1uUBgP8JgscPbgUDnwjawHoWatmFyMkBku+QTJCnxreBA1n+9kuCUKUKHifQZV9tULRMJqXbQOeEG+gUZmom1r0JhNhl6LwvKdwqo/hLpOsZLU/hdoPp7+/PWJaLRLxqYgddE90cMAId5rtbizWPB5c= 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)(13018025)(5005006)(13016025)(3002001)(10201501046)(61426038)(61427038); SRVR:CY1PR0301MB0842; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB0842; X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0842; 4:w0R4L+fGyRVGHx5GjQ/tk4liRSDZzoa1L2BNNwaIw8FoKtiycnTG9O5dyh+17gQBJW4FCAIiw48cbwOSP2eygkP54/cHuRpBIMEom36eSKOWZyMRBBFno0ZnrH+6yjSTfDLBIQcnI7tzaE1Ml9FCyXikbO3txerWfWhLjTZTq4tbvgie30GLHyiv9Hno2eb76R1fCttf58I4Vm05ELAahhxHHeaztuP9JL98RHTqgqjvAJ/6jKS3POa5z9RCCKR6wEaH0WPcYHFauCRfqo89+nvrPlOAuuC8aVEdFjzqj7PECAQB1lDSizJ7T8aJBzdKv6p832oN78ahTC56FNITnwcfSsi8oK0TQTZWrIStE78h7kSWRNG/7CR0mJZ/ebF6k/fdXtZExobHlTVSm8BNCHmlxEKgk1Bko9Ai0EKyme4+HV8qYMbY/xoWufKeM3stvtT5jRPdhv1KoPdlU4a1fMtEHOr7bJQUWIwz32rTyZuEUHdKlYn4WosAGo2so7ZC X-Forefront-PRVS: 0843C17679 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR0301MB0842; 23:i6cEpr242sHVjyp96k1+M03fsiKQZUemigTtKyj?= =?us-ascii?Q?LnW7K7N30T2V8OVrDlSm0nKucP3h/lyK9VIBTcju6VGMWjR1n4uGVETIV8Xx?= =?us-ascii?Q?nw5N/h+r3u6Ys4xaGUrq9JrUsLUx98ZnPso+7L4hmYFHao3BLelFTKpQQW/r?= =?us-ascii?Q?8dbJgvyAq/i0bQQWeqkdS874QSlXa5uH9+rL0of9FXglMs3z2X3dsKVN/41l?= =?us-ascii?Q?YO5BsaSvdtBg58E3/mrdWKAeIZBEYhSNK+bengLaCUNAQSeRnOVn/9rK5rNs?= =?us-ascii?Q?j2XdPjlMhKex1RqcfTJp5E/sgLm4FLDu3SCjr9PLd6/S2o0s+kKjhg5UUfGN?= =?us-ascii?Q?XwVgNEc6rbb3glW0jXtFl8erMh7nZkY0jK/3g1oXPh8m64Nav7Wz42KaWeR5?= =?us-ascii?Q?CgKuunRxSWV4fpUaT8Fr0nm/CD1C4BgyvP386wxc+lBhu0pweC3HHOFBhSQS?= =?us-ascii?Q?uC4MWrsFWcZMmYVhhKwCUz+ryPAo4NV2ozjOie6ZbgS7OWthOPb/hBXOEFYH?= =?us-ascii?Q?sOJC5rtKUZTLsehDsNe9nS+Do9zsnbNv4u0FxcI/sFlZNPEA/ns1FBvOyYt6?= =?us-ascii?Q?+4eTd4GCw8dU2tqtEAsSAfOILvoT5JgGk63yNb3Lbjx7ArEeVcSXkebiNxB/?= =?us-ascii?Q?lXLhR9KSVVCW+402tbIby0yw2CSufRS7YhTiBA/taKPuxvNb5VJNBU1R/PhB?= =?us-ascii?Q?/W5d+H9aqGaey39P/iniaavNuQS1Ma2VVWMG35tFoWYjF29kxDcl+3h8KHD+?= =?us-ascii?Q?v7igeEPLipBnkjWf7XpX56rTqsCtFacWEIDiT9ZayBfzvR3aLdqlHYceHtTH?= =?us-ascii?Q?xuvheqWdlpVReb+5x5KVSXC+Ok81pjcCrogr8jXW874zRaBb2X5qQJklIvjw?= =?us-ascii?Q?3VnXqHHqUvdmcXYkvl6lr7N17nqm33deLu81CfxOk6G4t4+6uadsz+LZtdRu?= =?us-ascii?Q?VmNP1UWBkd/H2fN+IuIECVEpRQj/vgDCl/LhVR9YpyrfeRN8Ix7Ul0KS4+Zb?= =?us-ascii?Q?aclSD2eTFviNeU6DQrjdwavaNJoXn46Ho0Izu/OmrqlNHcTD7yDZt+wHE/Xx?= =?us-ascii?Q?FuqO7yv8H6IGW9BBQQHDAQIro3Q7i82L+1Rfjw9VJce/TUa2hZYsBTsC9Xmd?= =?us-ascii?Q?PP2lAz3o64B+KeCUmUqLkGwPDcDOlPYRTn3nZa0G0oARJ5HRMRbMAjRHmNDi?= =?us-ascii?Q?Ghm/E2dXHKgzJba/kqYVoq3BSDijbzNUpNSvnnb3D2OjOgDRjoX1QDtY7eTh?= =?us-ascii?Q?ZzdSvylUw6BTA2dDJwcsc008AA3uPiz/k4KQ+vH1o1Qf7yigWjm16vqxDxg3?= =?us-ascii?Q?tyj/B/tAwcuKYSPfWYWqmToX8PvzCIXjCN+Xiys/gwtNtCdi8Rx3KMOtVpCe?= =?us-ascii?Q?IG9DrtTHHOL0zGNTS7hac0l2nUXK4a+hyE8Md62G7ZolDP5rY+puLngwQVEl?= =?us-ascii?Q?D9w0EH4aQTtvb/8FgvldmXSg8P1Dxqy0QS9x2UCU8XqVZzSdz+uOlcLDORpe?= =?us-ascii?Q?+dZqQzMI4rU7Tx+tP1WDCK/18nhJwhpqVyzl/GeBUJqk2JbYhOCDtKMWlRPr?= =?us-ascii?Q?VLQj1yO7rKZm2LnnBCiICEK0yMyBlqUgNGwa4EJWKvk/3FTZFHTl3A9bj7Tn?= =?us-ascii?Q?KPFJ0Xxcfvu6ePnXwc07nBtXxhJPIINxOGPGUlt7S5Xqi3s0OyMzgq82JM0o?= =?us-ascii?Q?cs8W3JRX3mXPFbw4NqJanBGOTayuFZL/4CXtWnO3AjqquNNsW7hkem+Za+n2?= =?us-ascii?Q?arHvF+CGxdZgXU9ZYdrlijciBmv+llZkYTYilknqZRUXDIZKLZbRypPkYiBn?= =?us-ascii?Q?GBzFgzn4MKuHM0gY/C8PDzC65UK4EG8KEZGPaBy/kHEuD3Pn6ioCNp72yWaI?= =?us-ascii?Q?Uz6ywcUdj1cYnO9VyvW2f1Ep8dkIQSRFY7IUzsInt9mWTGqOImeTM3pVHUs+?= =?us-ascii?Q?IA7B3P6/4PbnR0JRmDkYGTSW+/9obLhUEKnq77bHdFhpb0AXPYpsOrqQEZxy?= =?us-ascii?Q?XwtGpaS0LEeaQimW82yFJEf+i52DlLeiOpn/P+8/KnOGrOQ=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0842; 5:/RcXa+qev/XqrXTgJWwPWueQTUwOTofpaujf/wrqFzuMIUuZSk12Uk6WqEZc0M2Zq3NCeCjzYc+f/icD0R01RJH4+3NXbjGIirIelOAg4pYkuWdmENWVK/3GLtpy3T0PH3nkwV/gZM978r79qY4ulg==; 24:13KsOXEnOPB8PfpcgHaT7q0IBqwkR2/KAvRxGraoaptUjBwnivVVroaFicJwLzoJUXWCnrywA8B96HQabp4MICdOYkCqXKFnZxKRGdJQiK4= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Feb 2016 08:23:02.4506 (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: CY1PR0301MB0842 X-Mailman-Approved-At: Fri, 05 Feb 2016 13:04:43 +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: Fri, 05 Feb 2016 12:55:35 -0000 Hi Jac, Thanks for confirming the fixes! Please let me explain the issue a little more. The issue exists in the VMBu= s driver. Since the network driver depends on the VMBus driver, we have the= issue. The issue is: the VMBus doesn't guarantee the serialization of registering = multiple NICs, e.g., supposing the VM has 2 NICs (NIC1 with MAC1 and NIC2 w= ith MAC2), 2 kernel threads (FreeBSD's taskqueues) are created to register = the NICs concurrently; if sometimes NIC1 is registered first, NIC1 will be = "hn0"and sometimes if NIC2 is registered first, NIC2 will be "hn0"... My fixes make sure the proper serialization, so now we can make sure NIC1 i= s always registered before NIC2. About another issue ("calcru: runtime went backwards"), I made a fix recent= ly: https://reviews.freebsd.org/D5174. Please try it. I'm trying to push this fix to the Head branch. Thanks, -- Dexuan From: Jac Backus [mailto:j.backus@bugworks.com] Sent: Friday, February 5, 2016 15:55 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, I build a new kernel and the problem is gone. I tried to understand your description of the patch. What I find remarkable= is, that there is apparently no fixed relation between the virtual nics de= fined in Hyper-V (with a fixed mac address) and the devices, hn0, hn1, etc = in the guest, and is the order determined at boot time. Something completely different: maybe you can point me to an explanation o= f these messages when I boot: calcru: runtime went backwards from 1672 usec to 845 usec for pid 144 (adjk= erntz) calcru: runtime went backwards from 5 usec to 2 usec for pid 7 (pagezero) calcru: runtime went backwards from 126 usec to 63 usec for pid 4 (sctp_ite= rator) calcru: runtime went backwards from 6920 usec to 3743 usec for pid 3 (fdc0) calcru: runtime went backwards from 33080 usec to 16732 usec for pid 13 (ge= om) calcru: runtime went backwards from 12117 usec to 6318 usec for pid 1 (init= ) calcru: runtime went backwards from 155335 usec to 104098 usec for pid 0 (k= ernel) I happens since I virtualized the server. Again, I thank you very much for the help. And, of course, especially for t= he fix! With kind regards, Jac Van: Dexuan Cui [mailto:decui@microsoft.com] Verzonden: donderdag 4 februari 2016 7:01 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, 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 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, 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" From owner-freebsd-virtualization@freebsd.org Fri Feb 5 16:17:13 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 AE3D0A9B822 for ; Fri, 5 Feb 2016 16:17:13 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 990E532C for ; Fri, 5 Feb 2016 16:17:13 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 979096C01; Fri, 5 Feb 2016 16:17:13 +0000 (UTC) Date: Fri, 5 Feb 2016 16:17:13 +0000 To: freebsd-virtualization@freebsd.org From: "gallatin (Andrew Gallatin)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Accepted] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <5c8ff24d18615a9282eea036a148ca21@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa0ywk= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 16:17:13 -0000 gallatin accepted this revision. gallatin added a comment. Thanks for addressing my concerns.. Does anybody else want to comment? REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Fri Feb 5 16:22: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 36331A9BAA3 for ; Fri, 5 Feb 2016 16:22:58 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 212A791F for ; Fri, 5 Feb 2016 16:22:58 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 1E8B96F5B; Fri, 5 Feb 2016 16:22:58 +0000 (UTC) Date: Fri, 5 Feb 2016 16:22:58 +0000 To: freebsd-virtualization@freebsd.org From: "adrian (Adrian Chadd)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Accepted] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa0zGI= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 16:22:58 -0000 adrian accepted this revision. adrian added a comment. Nice! Thanks for all this work! REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin, adrian, network Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Fri Feb 5 16:47:20 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 63B3DA77578 for ; Fri, 5 Feb 2016 16:47:20 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 4F4A81CD7 for ; Fri, 5 Feb 2016 16:47:20 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 4CCE76412; Fri, 5 Feb 2016 16:47:20 +0000 (UTC) Date: Fri, 5 Feb 2016 16:47:20 +0000 To: freebsd-virtualization@freebsd.org From: "hselasky (Hans Petter Selasky)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Commented On] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <054a1629e2d36e7d8aac07ae3650bb0d@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa00hg= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 16:47:20 -0000 hselasky added inline comments. INLINE COMMENTS sys/netinet/tcp_lro.h:94 Might be worth set this limit to unsigned instead of unsigned short. Technically we can LRO more than 64KBytes worth of data! REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin, adrian, network Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Sat Feb 6 01:12:31 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 6F8BBA9EEA9 for ; Sat, 6 Feb 2016 01:12:31 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 5A690DC3 for ; Sat, 6 Feb 2016 01:12:31 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 56AE76B86; Sat, 6 Feb 2016 01:12:31 +0000 (UTC) Date: Sat, 6 Feb 2016 01:12:31 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Commented On] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa1SH8= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 01:12:31 -0000 sepherosa_gmail.com added inline comments. INLINE COMMENTS sys/netinet/tcp_lro.h:94 My intention here is too keep the size of lro_ctrl unchanged on amd64 (I think there is an implicit 4 bytes padding after lro_mbuf_max :). But I am fine to change them into unsigned int. Does anyone know any drawbacks to change these two fields into unsigned int? If not, I would change them into unsigned int after Chinese New Year :) REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, hselasky, np, transport, gallatin, adrian, network Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Sat Feb 6 08:59:40 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 C38A6A9E341 for ; Sat, 6 Feb 2016 08:59:40 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id AF7CC1EF2 for ; Sat, 6 Feb 2016 08:59:40 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id ABB4B653C; Sat, 6 Feb 2016 08:59:40 +0000 (UTC) Date: Sat, 6 Feb 2016 08:59:40 +0000 To: freebsd-virtualization@freebsd.org From: "hselasky (Hans Petter Selasky)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Updated] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa1tfw= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 08:59:40 -0000 hselasky added a comment. The size of lro_ctrl already changed when the statistics was made 64-bit. Just remember to bump the FreeBSD_version. Might not be possible to MFC. REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, np, transport, gallatin, adrian, network, hselasky Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Sat Feb 6 09:02:09 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 4845AA9E777 for ; Sat, 6 Feb 2016 09:02:09 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from phabric-backend.rbsd.freebsd.org (unknown [IPv6:2607:fc50:2000:101::1bb:73]) by mx1.freebsd.org (Postfix) with ESMTP id 3456E662 for ; Sat, 6 Feb 2016 09:02:09 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by phabric-backend.rbsd.freebsd.org (Postfix, from userid 1346) id 3079F6736; Sat, 6 Feb 2016 09:02:09 +0000 (UTC) Date: Sat, 6 Feb 2016 09:02:09 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5185+333+b2354430ad09b93f@reviews.freebsd.org Subject: [Differential] [Commented On] D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit Message-ID: <8b97ad868325f98e4e6ca090cd950cd9@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5185: tcp/lro: Allow network drivers to set the limit for TCP ACK/data segment aggregation limit X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NTU0NmM0Mjk2NjdmNzVhNmM3MzlkMWQyNTdmIFa1tpE= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 09:02:09 -0000 sepherosa_gmail.com added a comment. In https://reviews.freebsd.org/D5185#110952, @hselasky wrote: > The size of lro_ctrl already changed when the statistics was made 64-bit. Just remember to bump the FreeBSD_version. Might not be possible to MFC. OK, let's wait for others inputs (I will be away next week). If no objection comes, I will change the limits to unsigned int. REVISION DETAIL https://reviews.freebsd.org/D5185 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, np, transport, gallatin, adrian, network, hselasky Cc: freebsd-virtualization-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Sat Feb 6 22:10:18 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 5DA9CA9F413 for ; Sat, 6 Feb 2016 22:10:18 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id BE98ADD6 for ; Sat, 6 Feb 2016 22:10:17 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sat, 06 Feb 2016 23:09:31 +0100 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 21F68757-309E-487A-B08A-77C11EDAE9C4.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Sat, 06 Feb 2016 23:09:25 +0100 From: Rainer Duffner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Question about bhyve disk images Message-Id: Date: Sat, 6 Feb 2016 23:09:00 +0100 To: freebsd-virtualization@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=13 total_conn=2 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 54, bad: 0, connections: 213, history: 54, asn_score: 59, asn_connections: 230, asn_good: 59, asn_bad: 0, pass:all_good, asn, asn_all_good, relaying 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: Sat, 06 Feb 2016 22:10:18 -0000 Hi, is it possible to increase the size of these images (after creation, and = while the guest OS is running)? How large can they be? I may have a use-case where I would need to have images in the size of = tens of terabytes. Or is there a way to delegate a ZFS (or a pool) to a bhyve guest?