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"