From owner-freebsd-virtualization@freebsd.org Sun Jan 24 21:00:50 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 E60757A2C for ; Sun, 24 Jan 2016 21:00:50 +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 C53BF1DD2 for ; Sun, 24 Jan 2016 21:00:50 +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 u0OL01fD036435 for ; Sun, 24 Jan 2016 21:00:50 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201601242100.u0OL01fD036435@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, 24 Jan 2016 21:00:50 +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, 24 Jan 2016 21:00:51 -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 Jan 25 22:05: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 95702A45D22 for ; Mon, 25 Jan 2016 22:05:40 +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 1E265D44 for ; Mon, 25 Jan 2016 22:05:39 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 0A4E12B9BA4 for ; Mon, 25 Jan 2016 22:55:48 +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 01933-06 for ; Mon, 25 Jan 2016 22:55:47 +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 C05EA2B9BA8 for ; Mon, 25 Jan 2016 22:55:47 +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, 25 Jan 2016 22:55:47 +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, 25 Jan 2016 22:55:47 +0100 From: Jac Backus To: "'freebsd-virtualization@freebsd.org'" Subject: Hyper-V networking: problem after upgrade to 10.2 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2A== Date: Mon, 25 Jan 2016 21:55:46 +0000 Message-ID: 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="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, 25 Jan 2016 22:05:40 -0000 Dear reader, Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a full pa= tched 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 vmb= us0 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/204= 8 Jan 25 21:02:01 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11:08 Jan 25 21:02:01 mercurius kernel: hn1: on vmb= us0 Jan 25 21:02:01 mercurius kernel: hn1: unknown 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/204= 8 Jan 25 21:02:01 mercurius kernel: hn1: Ethernet address: 00:15:5d:ac:11:09 Jan 25 21:02:01 mercurius kernel: hn2: on vmb= us0 Jan 25 21:02:01 mercurius kernel: hn2: unknown 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/204= 8 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 vmb= us0 Jan 25 22:20:02 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11:07 Jan 25 22:20:02 mercurius kernel: hn1: on vmb= us0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet address: 00:15:5d:ac:11:08 Jan 25 22:20:02 mercurius kernel: hn2: on vmb= us0 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 From owner-freebsd-virtualization@freebsd.org Tue Jan 26 02:26:47 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 994FBA46F0F for ; Tue, 26 Jan 2016 02:26:47 +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 88EE1D0B for ; Tue, 26 Jan 2016 02:26:47 +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 u0Q2QkGv092632 for ; Tue, 26 Jan 2016 02:26:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 206630] [Hyper-V]FreeBSD 10.2 on Windows 10 & 2016 server may not boot due to multiple invalid disks issue Date: Tue, 26 Jan 2016 02:26:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: kyliel@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 26 Jan 2016 02:26:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206630 Kylie changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |delphij@FreeBSD.org, | |freebsd-virtualization@Free | |BSD.org, | |kyliel@microsoft.com, | |royger@freebsd.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jan 26 06:11:00 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 C5854A46AE7 for ; Tue, 26 Jan 2016 06:11:00 +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 B5B6AE13 for ; Tue, 26 Jan 2016 06:11:00 +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 u0Q6AxnO057657 for ; Tue, 26 Jan 2016 06:11:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 206630] [Hyper-V]FreeBSD 10.2 on Windows 10 & 2016 server may not boot due to multiple invalid disks issue Date: Tue, 26 Jan 2016 06:10:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: emulation@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 26 Jan 2016 06:11:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206630 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Assignee|freebsd-bugs@FreeBSD.org |emulation@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jan 26 06:49: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 B48AFA476D9 for ; Tue, 26 Jan 2016 06:49:20 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0138.outbound.protection.outlook.com [207.46.100.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 58A08185C for ; Tue, 26 Jan 2016 06:49:19 +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=tWraPv/vlIaqSJHz5/xblSmIW3UTVrRDk2X3UHQcgOI=; b=PaIW88hz7pOfxs9ZTZGEgW5sz1ORi0mGciaQ2umOjc6TwVJRjAzpU15OXCrQ1ZDv+5Lz0PFxlYawr7wO3H2gOnEn2nguYYANnAJGTMm1NiuJoPkr4yK8EHlyODHu66KkdsEuZ7Y5F2NGR7rqGro8ts6SQ9atDFBD2Ls9jDjNQAE= Received: from BLUPR03CA010.namprd03.prod.outlook.com (10.255.124.27) by BL2PR03MB209.namprd03.prod.outlook.com (10.255.230.140) with Microsoft SMTP Server (TLS) id 15.1.365.19; Tue, 26 Jan 2016 06:49:09 +0000 Received: from BN1AFFO11FD022.protection.gbl (10.255.124.4) by BLUPR03CA010.outlook.office365.com (10.255.124.27) with Microsoft SMTP Server (TLS) id 15.1.390.13 via Frontend Transport; Tue, 26 Jan 2016 06:49:09 +0000 Authentication-Results: spf=pass (sender IP is 206.191.229.100) 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 206.191.229.100 as permitted sender) receiver=protection.outlook.com; client-ip=206.191.229.100; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (206.191.229.100) by BN1AFFO11FD022.mail.protection.outlook.com (10.58.52.82) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Tue, 26 Jan 2016 06:49:07 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) by SIXPR3002MB0110.064d.mgd.msft.net (141.251.56.82) with Microsoft SMTP Server (TLS) id 15.1.396.8; Tue, 26 Jan 2016 06:49:03 +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.0396.010; Tue, 26 Jan 2016 06:49:03 +0000 From: Dexuan Cui To: Kylie Liang , Jac Backus , "'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/xyLaKrOi2AAEaGnQAA5R0WA= Date: Tue, 26 Jan 2016 06:49:03 +0000 Message-ID: References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> In-Reply-To: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [141.251.197.5] X-MS-Office365-Filtering-Correlation-Id: 5133ccb5-597f-48e0-edce-08d3261cca30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD022; 1:ASgEieerm2yjQ/49wLjpyxYhf9wJbpFjPR1yUe4/HFP9pMBvaL61/p6b/JbmpIpa/HrWZjTqFNQFXKZ4ILUKZD6tK+kuQmDVdxOp6c7/7Jce+cLk/v94Ft2+LnAvWH5GL74G2bFWGZSBaML4M45pg8SnA762mzine2lxdJTSgxV1/OYmSwQneEp9PyEunAH16DLiflcddhYt8aXSpFY3t/U6x5Ie+T5mv6BLvp6Wbx9g9A/yUi2yNep5cMKOxUZSulo8d4gHudfiTfVORnSlPnZjy5veZ0rTT2hJxZZRjMWpFB1+D1RSQLPpGSXr6AfnU4FJQdLk4ldgGrdg38uY9QrW/A2NSyAuXo4q7no+PA7NuuTuFJz2a5qiJOy7K3rH X-Forefront-Antispam-Report: CIP:206.191.229.100; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(2980300002)(438002)(71364002)(51914003)(164054003)(377454003)(189002)(3905003)(199003)(13464003)(5001960100002)(15975445007)(106466001)(3846002)(54356999)(2950100001)(1096002)(23726003)(1220700001)(2900100001)(107886002)(102836003)(11100500001)(2561002)(1511001)(189998001)(50986999)(5003600100002)(586003)(97736004)(10090500001)(5008740100001)(6116002)(76176999)(66066001)(81156007)(5001770100001)(2421001)(19580395003)(47776003)(6806005)(50466002)(97756001)(5005710100001)(87936001)(2906002)(19580405001)(4001450100002)(24736003)(10290500002)(10400500002)(108616004)(16796002)(86146001)(46406003)(5004730100002)(92566002)(575784001)(86362001)(33646002)(69596002)(86612001)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR03MB209; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; PTR:ErrorRetry; MX:1; A:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB209; 2:fvHrar2hrErYQuNSyVxwXZAXdVZOS4Fyrl8ImQ0e3ZiHybSUvY20i+5gR54kPaDIr9rtIqBvPWNSHhbYKGmtwsbq+zz2SEFFrqrczN2b76zVmAughtkQV3J8HshwZZ4tKFBR+zafPXwkAF52iZdyd9/Kz6BXKlQSLcNQf868+TjWmZIhuILFF8wXM7o+A+rb; 3:81HsMtmZoCDvmQSatY/lganfKvz4syjG//reMU9DeixH3GdFOcqTUvgpYD/nU2Z+CsQ4SMZc6bz0p8ewOcpgO2AQWUtr50E4O361puEIzhT8biM5/EJSZVcNWyA0q2JDOvqeb3KCKqV2C/p0dPN3bEt+WGIRA/PT957r7PprGgha7sBkiPRSpZhbAVQN1ef/jheum3fQZcNwX3WzlHjmRh/yTNkE5KTznnxB6u4WDgW5BqCLroZEldjFdYdwqkQ0hmOk6USAK3x1l+ee799BRA==; 25:wBSLWxAfJLdHlHFvpd/TVNQa7S9Nl1OSmYMk20ncyx3IyOqNeRn4oHtvx3kAfUY7GHkQzEiV0fT+ZBB3Aehq2nbBiDmYjWptr7QgEy1lJ8XexH37GFVMtRgERdTNOPn0MsmPdDLX/8rWo/LBxxQskh3FrPUn5afECBLpHNqkhupl9Feka9Nz1Rrrvmw74Cy9g2U83GemYcEqF27F5u1OD2Hnk+FRyemHTUKNLfS18SMVYYxBYCL8IfcRlre57kEEzN1mcCiBVkSEipydrOhEIJ3ak7DJiAqCiAbTdB1Mlgs= X-Exchange-Antispam-Report-Test: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BL2PR03MB209; UriScan:; X-O365EOP-Header: O365_EOP: AllowList from IP - set SCL to -1 X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB209; 20:HjiMkfC8Do04NdrVOuQV3kxAsHDR6uuyjDLGwL0P38dvpl/aHjAYjM2KW2LutbiWtNHnrA+7/WMqrXnLeUA6d15gcIkThPkiwlorPxjl62VL5VwO5h3y7zqzICCz94frSakkuL9412smEJsGt+LFz5QOHWk3CcyeFzB3ZHtdV0jw7y8MLykPMLEAQGyuV1Q1G8pzjOOgOMoOIc9TG5kS9ye3Ek/ahj7PESs7B953maolbYqTeKV0M0V8KqpvlR0W1aejLxVzDHQwwtOIMNL835TQo5eRVu1ky3HJaZQkAZeKpv1rq+iYwPnN7MiWvcbKYHM2Vtfk1Y39z/UM2QztFyk5p28lse8Al9NBVt2jtn4UfdUSU4n48k+ErWSTZxyrqJyZ8tDtZL3wu9FOt0APZNvKc9VbrUXzvY15+bAiKApsBK7fDYrvHCPitSVENaT+b0NsWJAkk4jO5jZhVHDYLYp6j2Agm3orFDZFPDlAuqOTAdUNGGp4QCCzgORXC4a3AJvWQX/HSUAr1PCDrL0r6BdbdiqIv0abcUqIw0frjJCs7/bWuKrrJPApYbP9Qg+TOXPqsw9TLQgwEpg+btpOpu+TggopxWUZK5EbKVwaXo8= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(520078)(5005006)(13018025)(13016025)(8121501046)(10201501046)(3002001)(61426038)(61427038); SRVR:BL2PR03MB209; BCL:0; PCL:0; RULEID:; SRVR:BL2PR03MB209; X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB209; 4:kSCvjaU7uy7vO8LxVjL2K9KcoqlTqI1UNAoWGl1c4R1fI98QQb5JGRppoe1zIfOeAuWkmpQx8EKOcLXAINO2qjPdIu0Jm54YUEUw6fxKglaNoWUhYL7+l0wfi3M5f4mj7SMntzecR5ITzacV7kQWDsHqiaAEKTkUhfTfjLTvHpFOh2AKjXb54NoXtO4tOTYvVDXpqAckd2bDxGYvvj81H1mX/aHWs1rMEhpomKB3CUUYVybH/ZOhj3/Is0VK01nHw5oZr+AYxaFVf5foaHZUerCvmApaqvmMhS3jxGRpq/xgLJyTd9UUOYYOskYhVO5IFi7qkt3HQyKi1dB5ohUEf0AQAeso432FypB9X92C0TW/oOMafASKAVbRgiRLAA5CEDt5vvUeI/UxtENi7hiNA9vs9B78uE33GFBCIhLAilDFG7dznaXf0oL9ZONiBtqHgaw1c5NNB2AwuD8umnntPvNWN6qVrmNQgA0XiK6ubUE= X-Forefront-PRVS: 08331F819E X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BL2PR03MB209; 23:Y+KWGUEL5NIEU/AMobrQVsAYfRPYHalHaxCmQVkgrR?= =?us-ascii?Q?U0qxAOKJEXw/IHgoic6PIn/eOIXLL3whIHs04CgBsqnFvAUJGl2K2OcUmwz4?= =?us-ascii?Q?MAHcizoLPmI1MD9XflXO8Cs52CuNUq4mPUgJIPxQ+e4g5AH4IZibGrjVSXoL?= =?us-ascii?Q?l6L+T4tpV2rYbTu0Vomm4V9IvwRKt+j0nJYfK/g/xD8DFoifIs2KswMuP0xB?= =?us-ascii?Q?WH9/JHy8HgOY+SwEGhOoYUgFu99ux8OqoYkf3upmoDNufAJMRVzniHo3COYT?= =?us-ascii?Q?gIx0KKPjNKiktyFrdJNNdJnwYlvaf+jRa19cqVWtK4TWg9Rdw55aRdTAeQ1Y?= =?us-ascii?Q?S1UOrhly0qJYOrXIn6ApbKPtCFQL0toaqqTSnVOnBBUFrDOc10shDDIaPnx2?= =?us-ascii?Q?nxS4Gy23yv9eoACHxf5d+W+QX8NnC8xhUBW7iOXq1N2ECWMDvKnOTpR+lzfE?= =?us-ascii?Q?8FPbMsKez+aLlGc3kz8yxcy/25yKlKXY244oArY11tiZKFuAD8wgYbb8tcJg?= =?us-ascii?Q?Gnd+059NSq/vtLREeKMz7CxkxyXQ3HGTwBHnYWjVlx4Ov+KoZdF8+4LfUCXo?= =?us-ascii?Q?86WTmk2uf5GwuvkK4GUpjfmRBmzMGazc5yOioocqTc6eog8BOuHu1uFh8MMz?= =?us-ascii?Q?oTNDRmUSoyVIeFNsHZY4FRSf5wlMlsFLvqo1h2T4ZjBSQaKdaMO8DQTG3VO7?= =?us-ascii?Q?d3OZ3s5+FZ+LZw0BquUePFULPzpGQ4kvgkr6QxHuAcigU1qStUNet24mJjq3?= =?us-ascii?Q?H7E/HFJR8XDmzLz4GlpCMjjHOIkCRwNsukRhzZUJk15JDhtoqhMginXFpeuW?= =?us-ascii?Q?eGpdWZTrroHKt4/J1yrXJkYUuL/GgzyC2kJ1MgJ2UxdEyBMuk78XcwOkWiN3?= =?us-ascii?Q?s9TKzrFK+Tw5je1SgrPJ9XLnjeOjxgHWFSZgzFr1uS+L6VrEHz+CLkS2pGOJ?= =?us-ascii?Q?v9dCfHNiMKZ6Ne/ks0bqX1/Ma+lXKtSlo8wKn2kNeiAf3jS5boh2pTCZCztO?= =?us-ascii?Q?yqwUEtSB0oI9+8260eBj0uGw+6Wdl/Y5rMVCtuZvC58cSBDf6/tN3KiKsZ4E?= =?us-ascii?Q?vuKApB3INMS1lAgJE7wrYGWEjMNHETjvLpJWw5tdepLlyGlM5tj7KGWRY9bA?= =?us-ascii?Q?bdTQ4Bo0d7GELcs1fVLGQSH78p4dU2tUzLiad83ZyQGNxr0nEUoPijYJYsdU?= =?us-ascii?Q?z4kCHtzXdn/vZlfUiHkA6JEBIhNsYHghSyxHGycij5m9FC6WCjFSShpKp2ma?= =?us-ascii?Q?Hoipx9bPjVb018oJtlrKM4JhjiJH5bNfWXk7OtZ+sZitz8q/jy0lSbdOey3G?= =?us-ascii?Q?rdLThoyDDoHkT8ZFjrEL+ZK8aa6FuEoWDKsSKHI3+s+5IF48vkJBCuxZcWvk?= =?us-ascii?Q?M/aR6IXwOe4mieK8Ro0BJv/WcIYcrKvvR3H/IQ4+29EBRkx0yzEAR505RHAD?= =?us-ascii?Q?8kPdcEqtQceotvjQHiE6tEf6rovQI1EgJLM6mO57VaW8LX+iwP44Yz01CP1O?= =?us-ascii?Q?79MMGLAvjkiTreoJZ+RFuau6W5pLS6IcM2Ji0esp1xmQGafkIBYkuy7wTd0s?= =?us-ascii?Q?5waBeSa6K+PEd95TkQEK8Okjt87ZC98RpoBouagYaeFyfryTA53hYwVOqMfQ?= =?us-ascii?Q?wAJzlMHe8GPbp/fPentIN/E5unKVoqHAMBLz8v1z4=3D?= X-Microsoft-Exchange-Diagnostics: 1; BL2PR03MB209; 5:y7/Iz149nHjI1qJoHD0BoqYWn48R4jXMnm1/xzRgyNojJks0nhP3DlgUr79cZKCJ2HXkNjm6UNAWvKcfBMLJR6A1Wx8+fElumdN39ijwEZnblWLwdAXR9KsNObNwy3Uc4qNfr2B3QjjiwpAhsJF43w==; 24:y69oj5BIXnOGqLW8Y0mba755pgjsNxFMOCq6Vb4CHZ6owkoUKDGjmRMRlhPx7AL3fMde2qVDnFrhP5fihAdNRfZC6Ex8ZyCEdpfhZovFeIE= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Jan 2016 06:49:07.8147 (UTC) X-MS-Exchange-CrossTenant-Id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=72f988bf-86f1-41af-91ab-2d7cd011db47; Ip=[206.191.229.100]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR03MB209 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, 26 Jan 2016 06:49:20 -0000 Hi Jac, Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso"). The message " hn0: unknown status 1073872902 received" should be an unneces= sary 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.o= rg' > ; BSD Integration Components for Hype= r-V > > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 >=20 > Hi Jac, >=20 > Thank you for asking. To isolate your issue, could you please try disabli= ng SO on > your 10.2 system first? Thank you. >=20 > 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 >=20 > Right? And add our engineers in the list. >=20 > Thanks, > Kylie Liang >=20 > -----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 >=20 > Dear reader, >=20 > Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a full = patched > Windows Server 2012 R2 x64 version. >=20 > After the update, networking does not work anymore. >=20 > In /var/log/messages is this: >=20 > 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: Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown statu= s > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send offloa= d > request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using defaults f= or 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: Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown statu= s > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send offloa= d > request succeeded Jan 25 21:02:01 mercurius kernel: hn2: Using defaults f= or TSO: > 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn2: Ethernet address: > 00:15:5d:ac:11:07 >=20 > It worked fine with the 10.1 kernel, and when I boot this kernel, it work= s again: >=20 > 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: Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet addr= ess: > 00:15:5d:ac:11:08 Jan 25 22:20:02 mercurius kernel: hn2: Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn2: Ethernet addr= ess: > 00:15:5d:ac:11:09 >=20 > So I am running a 10.2 system on a 10.1 kernel at the moment. >=20 > I found nothing in /usr/src/UPDATING and not really anything on the net. >=20 > So, could you tell why does this happen, and how can I solve this? >=20 > Thanks for the help! >=20 > With kind regards, >=20 > Jac Backus >=20 >=20 >=20 > _______________________________________________ > 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 Tue Jan 26 06:54: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 EF1F1A478AE for ; Tue, 26 Jan 2016 06:54:57 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0113.outbound.protection.outlook.com [157.56.110.113]) (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 7FCE51ADC for ; Tue, 26 Jan 2016 06:54:56 +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=OgRGER0u5s4ymZh90qfkhPad7SB0AX8Qd1e1g0enttM=; b=CLhlf8SUCox7wECB8pO2GWgqNmjg0qSX2bBOIsidiNqEqPwFbjzlVByfbBx6Wy3Tj3ww4GNwuhJtjBNZIEdwtt38RpbFhFfqzoW9kyxHts6+NViDvjVzcv9oodyg6DYhPagkv1b5mkYRI1ISPpNoo/p0GoUckpOhzHQ+oFHpoNk= Received: from BLUPR0301CA0027.namprd03.prod.outlook.com (10.162.113.165) by SN1PR0301MB1597.namprd03.prod.outlook.com (10.162.130.19) with Microsoft SMTP Server (TLS) id 15.1.409.1; Tue, 26 Jan 2016 06:54:53 +0000 Received: from BN1BFFO11FD028.protection.gbl (2a01:111:f400:7c10::1:167) by BLUPR0301CA0027.outlook.office365.com (2a01:111:e400:5259::37) with Microsoft SMTP Server (TLS) id 15.1.390.13 via Frontend Transport; Tue, 26 Jan 2016 06:54:53 +0000 Authentication-Results: spf=pass (sender IP is 206.191.228.180) 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 206.191.228.180 as permitted sender) receiver=protection.outlook.com; client-ip=206.191.228.180; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (206.191.228.180) by BN1BFFO11FD028.mail.protection.outlook.com (10.58.144.91) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Tue, 26 Jan 2016 06:54:51 +0000 Received: from HKXPR3004MB0088.064d.mgd.msft.net (141.251.197.88) by SG2PR3002MB0106.064d.mgd.msft.net (141.251.56.18) with Microsoft SMTP Server (TLS) id 15.1.390.9; Tue, 26 Jan 2016 06:54:48 +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.0396.010; Tue, 26 Jan 2016 06:54:48 +0000 From: Dexuan Cui To: Kylie Liang , Jac Backus , "'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/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIA== Date: Tue, 26 Jan 2016 06:54:47 +0000 Message-ID: <1430812ff38c4e08a4b91ea25fdb5a7b@HKXPR3004MB0088.064d.mgd.msft.net> References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [141.251.197.5] X-MS-Office365-Filtering-Correlation-Id: 5540b5cb-f2d1-48eb-d1e6-08d3261d9734 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1BFFO11FD028; 1:M/JGWtDRpVP9s5U+nOXh7mtI1+DT0Zs10Q1Y13nQjH5NP3oVnsu6jv4LhlzcPlJHbWw90MGrBnXUJd+tRFGZNu3GyzzkQpRo45njodtA4lY+2bHjzinRSaXmYdUIQYTc8v4BFFOHw1DwgqRkZ/yODBqmSzX+WeeYEomqtay0hUqqsKqi23KjKAqq5f54zfd5LnTg8qCBjih8iw8PAP1PoxQVlRLEqx4OdyU+Pjp+XPNqWQxh7Qcvwum+WA3qRlrqKBCqyY0t9+Tz5aix/MQAAOlpyXThKhfcmgNlPHZQ7W7VYdnaZZDvVPQi2GutVLXhfjwSTGuRGP85vOVCbfYj6LbGCMdIatdnXHLM1y1fPXSKzlKW9Ka7Butxkhg05NNY X-Forefront-Antispam-Report: CIP:206.191.228.180; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(2980300002)(438002)(199003)(189002)(13464003)(51914003)(164054003)(71364002)(3905003)(377454003)(1511001)(11100500001)(24736003)(1096002)(10090500001)(54356999)(76176999)(50986999)(2421001)(5008740100001)(189998001)(97736004)(6806005)(69596002)(10400500002)(106466001)(5001960100002)(5005710100001)(2906002)(5004730100002)(19580395003)(2561002)(19580405001)(4001450100002)(1220700001)(10290500002)(2900100001)(66066001)(586003)(2950100001)(15975445007)(107886002)(102836003)(23726003)(6116002)(5001770100001)(81156007)(47776003)(3846002)(33646002)(108616004)(86612001)(86146001)(86362001)(97756001)(92566002)(575784001)(87936001)(50466002)(5003600100002)(16796002)(46406003)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0301MB1597; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; PTR:ErrorRetry; A:1; MX:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1597; 2:0venD+CvZlVY6ivb+FXtG8EriHVPc+69/ucduLjNGPzckVoQ5G/251bte6sw0L4UFc83O+Z5i6Xx8WuljfDZUo6zoXk0UvI7ix93k4IHIrCQyHm3r1eXtjKS7W6CECNXVNxNBLlNFDT6268y1qKlS8XNeS9vO9l2AAK0HPvFu/fhrrfUNgdVuFJ8yH1fEAGy; 3:8LJ3Tv0V/LcjVlzhoZZw9b35ypfnqGQWQfxg9C2rbNMZtDbAUYdHshlrne6o0rCoSiUa44hVDwvQl1PrXMutL3ijTdmvdkWoEXGVFoj3gnL7D4jj6mdhzpzaP7sobORgd8t0bhMcFLjs+0sfYA8aFvgBasHZzrYA1onmtSblplCIphAVenxjxHm/Hl0sI2Klt/c5HUYB+GkzEtKlaHght/1pFl3YCggyG5SV2CJXiDztkB2laeawMvyHfX/Xf/nba4ZyOhlnhVVcJ2Faql1j3A==; 25:iaZYM2tZ9JFxeXolnms99YlCOq7UkrdfKf6zZaUhTJuVLD4+DSkpDu3Q++eiqlnN8ixFb4g3sqtW6mQ4arYMTTt5Ov/KEn6oeYi6gwn//fTliaq7oSG4bCwqAE7YLZmJ62SuOaE6nHYvOkcEIn3c3vkGILAj72wEOclUuR2i/izbWj201z4n5Wr+2akSUb4bTsbhTMoKOllARz3pdXPQLqDGBNDGTS/cwX3eiPdUc/0bR5QnPRzOxJIyXz7N+Tp5/V7Iudtd+YxBk8UyvMMTN7ijVq4LzWl/cGR5n/SwCqM= X-Exchange-Antispam-Report-Test: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:SN1PR0301MB1597; UriScan:; X-O365EOP-Header: O365_EOP: AllowList from IP - set SCL to -1 X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1597; 20:0nQRpbSEIqO7HG9lf4GD+khFZvG6GKZNduibSvG3e+xTD9HEB/ggSRyOJWy/9FvQEra+sOzFjRB3k2SsKN9KBETLgsrUQtADgpeSSrwbi43eQ4SblQ3mq/G7wsdn07oexAEExNKeJnI4U6lN/g6kHxXQ6YCQIoyS3vTqudzkiS4c+ZLPHi9X9Kl54heZ02bCWpHZP8urPxUzfm/wHrdKwRt/VjoplPH29YT2Lynh9Vxu7bkxQMXmv+T1Xv6PFPoDkd+Kmxzsi9qilNy6/J3mSGMoLU89Na0WpqC0nSUmeJPRLpIV1iZXKmTrzH3+/i1Z1FKVyYH85VMoe0g4ZZeUNJk5Pn5iBPuvu/QnVLVVPAI4ZBVUmJJ4WVSm9Hmqnqfl22Y5l/2qCAuEmq1nYRUz0uszefgyWVAqzTDemWuAH/nJmvo+FLK2JWBYeP3bdf5VIQHWx+NJdLa8d+UikAIg89Ab6zK9Lx31Cs+Hsnd4o4BjK/595CZcV/onfg4BAAA2vJvAdrRBghrejA7uxpn4DUvA0VxpkPopdKny/C5v8wxgy8dinrx0IcWhJTXMQY9Wks9i9HKR1v/jdvQtHU1+nUG4lEOZrW4QqTRWZ6oHc2E= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(61425038)(123027)(601004)(2401047)(13018025)(8121501046)(13016025)(5005006)(520078)(10201501046)(3002001)(61426038)(61427038); SRVR:SN1PR0301MB1597; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0301MB1597; X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1597; 4:SALtcvlN3nlNkEWAg2CFim1pB3RpAybHa/ZyujUym/QSvLX76PDBxcExkepJv6Sb12T1FeZ/HQnudNVO4sw1jguGssLAL+1nqqZjh4BqF4u+JXZTjS/3/B1f68+t/VyZMcRRiDppaDE/ea/Ns9h8UMr4JBgdNbRqfeCIxRIVMArXFLi9SnarlvyzW5Nt/+DxBuQfek35KixHe4vCOyopW94oi/NvxZShfGtEq1e2Is6K9mrseYIGhHUw6ORRxbzOkCTHmQCsEopdb+xKUp0iO5AB5U55Ek7igQ4EzNjgLaBr/cwdPNLoubBzXI5KsEXtIkwMZ2xWix1j/CPaVC0e/25JemARzn0YZ6jvFNGPAYN1NGnRA9uvEfmTGSVD5ieBMrcYSJIeKhMkP0TR7uXkQ+gvquI1bgG78GrbfRjTaJhTOZL7TZqOA1rugbtokEq+nLYM2+zlrVIbPxZa0XFznpOW19/+9cFMyJ/rY2FjqeS+W8t4GSGXShvfjn8DBdoP X-Forefront-PRVS: 08331F819E X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; SN1PR0301MB1597; 23:g1YXqQDw3uKRbSdp+usy7NlQl1VGOpCqUJeUn4K?= =?us-ascii?Q?7iuysQH5cEiqkWR8TIW32fyUSjDmZPedcb5MSem+5VspOBSosQiuTy3pQLSe?= =?us-ascii?Q?6VFULICG7GEfPAsoklr4H/y/9+amya2RFPm0yBfcyb7R54QFwjWlaLF/Bre3?= =?us-ascii?Q?Ko06h2hepaQVdET0WMSVs4XPzvX6cVK8UN6HjXJbTGt4MtJDX8g9VqE2Bru2?= =?us-ascii?Q?ED2t/IfbGC4H7uMunNJd6tz1eYxekSwQ4P1duPzk7z1zqF4ESJ8B25SKD0pU?= =?us-ascii?Q?oiM7hwRA41r4nz8YN2AR5kvefhYNCJe/E8dG7lT9+I9ZYGu3iaEd9i790t1+?= =?us-ascii?Q?ESq3b8YF383bY8omroPjypsaSlHDLnrfhvK5i4qaIJoRMuEgFX/z5sVvOoDT?= =?us-ascii?Q?UmXxOZ14QKLFV1hFWpPyv4uls1EovEqhh3nJnwXDIHv9K9agKSWEI0WN4o5d?= =?us-ascii?Q?HS5zuo22pdXNYH5iXDMe57buPtwhuwtaiZDTGc89vFOq+AwFiXI86VG8NetB?= =?us-ascii?Q?x1pdkoYKOoYzUig4ja/WyDG2tvLpusCmMs/wz/9W8vmB984XJU9FoSbxttXh?= =?us-ascii?Q?50yZBWlMCbxvjS1tA1qWnpb4w0Isldh7S3fyeFKQnLGAZ6XRbM6DHSe5iLcD?= =?us-ascii?Q?RKQPNHOEYvx7SKuDuaFOLNQwtExgmknQk8TBljcpB09MuiW9lwomVLGDCYti?= =?us-ascii?Q?iPwavj2raDi/EuFq57SF0ztpsd34bQnIB/M4Fo0rJazmcclbo5N0T8cyGQUp?= =?us-ascii?Q?ve8uGremyxigfvPNvAoVPn/b5LDTHD1fNZrERHli7c2sjc4F22h0HL8/JFDs?= =?us-ascii?Q?h5FGCoFXVTk5OKMUom9uNX8A0C1EjJZXZxfEgCaQTqN1yiwI+ZNhM6OOMk4k?= =?us-ascii?Q?XNz6cQUvpO+ZMB4MYC6AATJoSMnRGbW1Lh8CK/PDtgskr1Rl7GCRsqEAzs1b?= =?us-ascii?Q?zpbJlu6rD17pKIEPEZnbz6SZXkRsaDqw9GpXl9u6ebPFnueWTpZTLKlHkc3O?= =?us-ascii?Q?N/OgE92RfEJboWLKbhckAiJ8fFEnTT/V0zL30jtQkon0opAt5einoRH+2uNf?= =?us-ascii?Q?PWLfEUEukUwvMFe+U8ERVNxX+L2odWfkjK1QsXk2w+hfVrVeHBOJ68z8litD?= =?us-ascii?Q?pICTEDm8m9vI67wFYPv/EgrZcCDL7AmMpbEbF06RA9CBBJMMO7bcFK/ApnjC?= =?us-ascii?Q?ok2EFBycC+k/pTnoAR82OF06Suw5QnpnUXgaBZr1kpgcfevoAnXYHX/FdIeG?= =?us-ascii?Q?Xk32Sicsw1h1tFylg3znQp+7oWea2vmmGp/OF/+trjsO6glStHGjcvy/2OX6?= =?us-ascii?Q?RafX00OQhursY9aiaobdaHNwDHKnfODtee4U6dOpyYu4aOkyW5WVU7gt+kGl?= =?us-ascii?Q?bLYYjPKAbetys40I1EGYxyYaV1ZwzEIbX4FSkl1c1+RV6IFaS7WQGqqLOVRO?= =?us-ascii?Q?oWRkek39wjoVz+IhlMNU9y6GrtNLH38UimA63IanFyox1dsRGaSqHmfl1VLg?= =?us-ascii?Q?K41AApo43duHXOyv5y3h+STLmRIhNfgwYQ75xWKeC5re1l31zihCN6qothJo?= =?us-ascii?Q?0w9/icDXVuNaptOi8WN9UURmaZQHko9j/zqDYmN/xRKiZXVRv3/7ODv/Vx6Z?= =?us-ascii?Q?53cZ8uiev8Mbj4g34EBZ4Z9qO8YhXV6dTEiRG8W+hojc=3D?= X-Microsoft-Exchange-Diagnostics: 1; SN1PR0301MB1597; 5:3thY3rbNhthXRJHtm8+zB9J8zDhO2I+l5xdxFAksr4DQFraE1nKFxwfrtauKI+qarC/FgTZ0mui8igYsioP1TfHfez7Ier2Hq7EValMV6s+fwayRci/cQi+r5OEKj7DGOOhN6N8cSP4gxQ8cLB53hg==; 24:bwEln2wN4gOkWeMLVz6v/4r3k1e8ZyFHCCy6pYEyejtx+gNS10igbAJQmTKWfq18NfaAdgqdSuXnqrdDYtVOUbAlpx4yqENoQjZIjbO83Os= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Jan 2016 06:54:51.7576 (UTC) X-MS-Exchange-CrossTenant-Id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=72f988bf-86f1-41af-91ab-2d7cd011db47; Ip=[206.191.228.180]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0301MB1597 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, 26 Jan 2016 06:54:58 -0000 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-virtualization@freebsd.org' = ; BSD > Integration Components for Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 >=20 > Hi Jac, > Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso"). >=20 > 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. >=20 > Can you please install a 10.2 VM from the 10.2 .ISO file directly as I di= d and see if > it works for you? >=20 > 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 sa= me > steps. >=20 > Thanks, > -- Dexuan >=20 > > -----Original Message----- > > From: Kylie Liang > > Sent: Tuesday, January 26, 2016 8:01 > > To: Jac Backus ; 'freebsd- > virtualization@freebsd.org' > > ; BSD Integration Components for Hy= per- > 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 disab= ling 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 ful= l > 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 10738729= 02 > > 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: > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown sta= tus > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown stat= us > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send offl= oad > > 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: > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown sta= tus > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown stat= us > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send offl= oad > > 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: > 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: > 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 Tue Jan 26 09:58: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 0A56FA46938 for ; Tue, 26 Jan 2016 09:58: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 2DE9A8EF for ; Tue, 26 Jan 2016 09:58: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 A15262B9BDD; Tue, 26 Jan 2016 10:58:04 +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 01692-08; Tue, 26 Jan 2016 10:58: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 600562B9BA4; Tue, 26 Jan 2016 10:58: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; Tue, 26 Jan 2016 10:58: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; Tue, 26 Jan 2016 10:58:03 +0100 From: Jac Backus To: 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/xyLaKrOi2AAEaGnQABSV3xA= Date: Tue, 26 Jan 2016 09:58:02 +0000 Message-ID: References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> In-Reply-To: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> 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.126] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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, 26 Jan 2016 09:58:10 -0000 Hello Kylie, Thanks for the quick response! I disabled tso, but it makes no difference. I can ping the interface address itself, but no host on the subnet with the= 10.2 kernel.=20 1, 2 and 3 are completely correct. With kind regards, Jac -----Oorspronkelijk bericht----- Van: Kylie Liang [mailto:kyliel@microsoft.com]=20 Verzonden: dinsdag 26 januari 2016 1:01 Aan: Jac Backus; 'freebsd-virtualization@freebsd.org'; BSD Integration Comp= onents for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac,=20 Thank you for asking. To isolate your issue, could you please try disabling= SO on your 10.2 system first? Thank you.=20 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.=20 Thanks, Kylie Liang=20 -----Original Message----- From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-virtua= lization@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 pa= tched 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 vmb= us0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 receiv= ed Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 receive= d 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/204= 8 Jan 25 21:02:01 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11:0= 8 Jan 25 21:02:01 mercurius kernel: hn1: on v= mbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 rece= ived Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 recei= ved Jan 25 21:02:01 mercurius kernel: hn1: hv send offload request succeede= d Jan 25 21:02:01 mercurius kernel: hn1: Using defaults for TSO: 65518/35/2= 048 Jan 25 21:02:01 mercurius kernel: hn1: Ethernet address: 00:15:5d:ac:11= :09 Jan 25 21:02:01 mercurius kernel: hn2: on= vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 re= ceived Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 rec= eived Jan 25 21:02:01 mercurius kernel: hn2: hv send offload request succee= ded 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 vmb= us0 Jan 25 22:20:02 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11= :07 Jan 25 22:20:02 mercurius kernel: hn1: on= vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet address: 00:15:5d:a= c:11:08 Jan 25 22:20:02 mercurius kernel: hn2: 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 mailing list https://na01.safelinks.prot= ection.outlook.com/?url=3Dhttps%3a%2f%2flists.freebsd.org%2fmailman%2flisti= nfo%2ffreebsd-virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.c= om%7cc9ca2e0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c= 1&sdata=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org" From owner-freebsd-virtualization@freebsd.org Tue Jan 26 10:16: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 39E9EA6E003 for ; Tue, 26 Jan 2016 10:16:43 +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 C2C5CEC1 for ; Tue, 26 Jan 2016 10:16:42 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 4F9382B9BDD; Tue, 26 Jan 2016 11:16: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 02192-05; Tue, 26 Jan 2016 11:16:40 +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 07C4B2B9BD7; Tue, 26 Jan 2016 11:16:40 +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, 26 Jan 2016 11:16:39 +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, 26 Jan 2016 11:16:39 +0100 From: Jac Backus 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 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQAA5R0WAABtKIEA== Date: Tue, 26 Jan 2016 10:16:38 +0000 Message-ID: <60e0cabb7bd4495a88bc392594a16614@ORTELIUS.internal.bugworks.com> References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.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.126] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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, 26 Jan 2016 10:16:43 -0000 Hello Dexuan, You too, thanks for the reply! I disabled TSO, but it makes no difference. I disable VMQ I mentioned the message because it was the only difference I saw. I will do this installation later today. I'll let you know. I did the upgrade according to 2.2 Upgrading FreeBSD from https://www.fre= ebsd.org/releases/10.2R/installation.html So, essentially I did run: freebsd-update upgrade -r 10.2-RELEASE It went without a problem, as far as I can see. With kind regards, Jac -----Oorspronkelijk bericht----- Van: Dexuan Cui [mailto:decui@microsoft.com]=20 Verzonden: dinsdag 26 januari 2016 7:49 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, Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso"). The message " hn0: unknown status 1073872902 received" should be an unneces= sary 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.o= rg' > ; BSD Integration Components for=20 > Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 >=20 > Hi Jac, >=20 > Thank you for asking. To isolate your issue, could you please try=20 > disabling SO on your 10.2 system first? Thank you. >=20 > 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 >=20 > Right? And add our engineers in the list. >=20 > Thanks, > Kylie Liang >=20 > -----Original Message----- > From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-=20 > virtualization@freebsd.org] On Behalf Of Jac Backus > Sent: Tuesday, January 26, 2016 5:56 AM > To: 'freebsd-virtualization@freebsd.org'=20 > > Subject: Hyper-V networking: problem after upgrade to 10.2 >=20 > Dear reader, >=20 > Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a=20 > full patched Windows Server 2012 R2 x64 version. >=20 > After the update, networking does not work anymore. >=20 > In /var/log/messages is this: >=20 > Jan 25 21:02:01 mercurius kernel: hn0: =20 > on > vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status=20 > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: unknown=20 > status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: hv=20 > send offload request succeeded Jan 25 21:02:01 mercurius kernel: hn0: Usi= ng 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=20 > Interface> status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown=20 > status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send=20 > offload request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using de= faults 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=20 > Interface> status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown=20 > status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send=20 > offload request succeeded Jan 25 21:02:01 mercurius kernel: hn2: Using de= faults for TSO: > 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn2: Ethernet address: > 00:15:5d:ac:11:07 >=20 > It worked fine with the 10.1 kernel, and when I boot this kernel, it work= s again: >=20 > Jan 25 22:20:02 mercurius kernel: hn0: =20 > 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 addr= ess: > 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 addr= ess: > 00:15:5d:ac:11:09 >=20 > So I am running a 10.2 system on a 10.1 kernel at the moment. >=20 > I found nothing in /usr/src/UPDATING and not really anything on the net. >=20 > So, could you tell why does this happen, and how can I solve this? >=20 > Thanks for the help! >=20 > With kind regards, >=20 > Jac Backus >=20 >=20 >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list=20 > 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-=20 > unsubscribe@freebsd.org" From owner-freebsd-virtualization@freebsd.org Tue Jan 26 10: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 010CAA460B8 for ; Tue, 26 Jan 2016 10:50:29 +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 2F5C6968 for ; Tue, 26 Jan 2016 10:50:24 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 1FA892B9F0A; Tue, 26 Jan 2016 11:50:21 +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 01722-02; Tue, 26 Jan 2016 11:50:20 +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 3CD6A2B9BE2; Tue, 26 Jan 2016 11:50:20 +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, 26 Jan 2016 11:36:45 +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, 26 Jan 2016 11:36:45 +0100 From: Jac Backus 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 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQ Date: Tue, 26 Jan 2016 10:36:44 +0000 Message-ID: <1fdbb9b939c54e31ac00329f61bf6f41@ORTELIUS.internal.bugworks.com> References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> <1430812ff38c4e08a4b91ea25fdb5a7b@HKXPR3004MB0088.064d.mgd.msft.net> In-Reply-To: <1430812ff38c4e08a4b91ea25fdb5a7b@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 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, 26 Jan 2016 10:50:29 -0000 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@01D1582C.39CF7E80] 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@01D1582D.D4B9BD10] 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 Tue Jan 26 12:35: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 A7FD4A6E124 for ; Tue, 26 Jan 2016 12:35:38 +0000 (UTC) (envelope-from kyliel@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0137.outbound.protection.outlook.com [207.46.100.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 31AC8985 for ; Tue, 26 Jan 2016 12:35:37 +0000 (UTC) (envelope-from kyliel@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=TUDswHruAgVkQ95mT7+psxfgKX8JrDd+FCkS384vz90=; b=YYxxn548B8ihcHcam/qgnRlnHQBuhh2XyfdkLRLh1toAR5LvupkI8HRX54+fkYAWy2NLv98iGpHNCuuDvkR8HgSqQtsTO1dsmlEpJtvrTnr9ANGFzgvGhsJgRueHYwWzWEaFhmDMiQ485zDck4qws5W2VxQKJZ4U4WbnIiFcMFQ= Received: from BLUPR0301CA0015.namprd03.prod.outlook.com (10.162.113.153) by BLUPR0301MB1587.namprd03.prod.outlook.com (10.162.214.21) with Microsoft SMTP Server (TLS) id 15.1.409.1; Tue, 26 Jan 2016 00:00:57 +0000 Received: from BY2FFO11FD004.protection.gbl (2a01:111:f400:7c0c::157) by BLUPR0301CA0015.outlook.office365.com (2a01:111:e400:5259::25) with Microsoft SMTP Server (TLS) id 15.1.390.13 via Frontend Transport; Tue, 26 Jan 2016 00:00:57 +0000 Authentication-Results: spf=pass (sender IP is 206.191.228.180) 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 206.191.228.180 as permitted sender) receiver=protection.outlook.com; client-ip=206.191.228.180; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (206.191.228.180) by BY2FFO11FD004.mail.protection.outlook.com (10.1.14.158) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Tue, 26 Jan 2016 00:00:55 +0000 Received: from SG2PR3002MB0107.064d.mgd.msft.net (141.251.56.19) by SG2PR3002MB0107.064d.mgd.msft.net (141.251.56.19) with Microsoft SMTP Server (TLS) id 15.1.390.9; Tue, 26 Jan 2016 00:00:52 +0000 Received: from SG2PR3002MB0107.064d.mgd.msft.net ([141.251.56.19]) by SG2PR3002MB0107.064d.mgd.msft.net ([141.251.56.19]) with mapi id 15.01.0390.013; Tue, 26 Jan 2016 00:00:52 +0000 From: Kylie Liang To: Jac Backus , "'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/xyLaKrOi2AAEaGnQ Date: Tue, 26 Jan 2016 00:00:52 +0000 Message-ID: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [141.251.197.132] X-MS-Office365-Filtering-Correlation-Id: 64f75c18-5ad0-487f-a76a-08d325e3c3af Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD004; 1:3xJYkC2zhGGlfdHxpmwqRXWQzpAVQntFt4ZRAbo6/aJH3VRYGgGXQp3j0wo9ciCfJgJgeGRvC6Dq+CC4uM2fMmRvA0ZrNbB+X+oDks4sjlN+xYEJ4XJ4RnuJ5ykssCMCWxvYbhpvAIEIWJBUlhEdGqD6Ze29Nep5KfdywRl5zFd2Ibw/6DUN8XhN/q2YxIYpDrHKSAVPJhSCpGbhuO6mhPgmP/wNB5U8qfPse/ojQjlTdgalbZ0m5M9xz9D1mBNuQ39KZYilothnHtLZMI5BFSvOL4RaJHunHUqqqpM9hkXvYu+y0HT0WqmLtcu7COs6PrWGeFKGETu7ehE8ajAl1A== X-Forefront-Antispam-Report: CIP:206.191.228.180; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(2980300002)(438002)(3905003)(71364002)(377454003)(13464003)(199003)(189002)(51914003)(164054003)(50466002)(189998001)(92566002)(575784001)(97756001)(86362001)(108616004)(33646002)(86146001)(46406003)(97736004)(87936001)(5003600100002)(16796002)(50986999)(54356999)(1511001)(5008740100001)(10090500001)(1096002)(24736003)(11100500001)(15975445007)(6806005)(2421001)(86612001)(81156007)(47776003)(102836003)(2950100001)(66066001)(586003)(23726003)(2900100001)(3846002)(107886002)(5001770100001)(5001960100002)(4001450100002)(10400500002)(2561002)(6116002)(5005710100001)(19580395003)(69596002)(19580405001)(106466001)(10290500002)(1220700001)(2906002)(5004730100002)(76176999)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0301MB1587; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; PTR:ErrorRetry; A:1; MX:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB1587; 2:J+1xspZ37bSPxXYSg37jaS9SSJBsG8haK02O57/TVCYGWLePNrUsIxusHmEhiNww5MzeCfgrxw9GT61uioFjYPe5l5F7h5UFrNpGf7QaPsomZ71+uubhfrUywzvJ2IlO/qf9BJPd8XZiIlOD1uMnMYrytZHSdN8M6nuTfFO/y6C0OsJ17HXJljtvdGfW/m3e; 3:mmoUrBpqn9nK8hvWfTRaHoL+hDTPVzhVA56imYD5JmThXO5s+spc1yLaxXiZvhC6Px3PBF83TSNMqVDe28dysj/Ie6n+Etn55dZsrHthlqrlVqa+WBbsvlznpfcemPW+blGNWGId6g5vHKKB9jr8O0iLF34gnv6Zo/AwZSFWk2g5/Swby1NFwzlo/MjCuw6S1iKPj8FVjz1Wd/SFQ/y9/C1TlxgtTj+mhsferHVCGSJCwqnoKZfIEt2REiAf4aFFGtRxYP4XNGZhCW6Zi5ZmRQ==; 25:l75xYHJLZbcgHWWpe2GYTU0t1AHc2ztuVGecvoTEdyottxZdueDYld7T9lo/BdwRO9uQyNjCs92DNazKKxHn3sjWedGYC3Iyl4fvmw0I1eCti7hVSby8sJEsjvxgf90a30NyuQIo4QYVVG3nz0oUiljtsnmudcuXwd6ad3DUya8S+5nW7L9+KbIuQCtttcqGDUl5rNiDeJDWf4p3plJQfUyPc6F03AkDKXSAa73taO9gnjLeimHsmXvTZrpoyuaHxjeg/CUZ9S4fBQd+Q4VxazgqQqpwcvXZuz5o3SUJh6Y= X-Exchange-Antispam-Report-Test: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BLUPR0301MB1587; UriScan:; X-O365EOP-Header: O365_EOP: AllowList from IP - set SCL to -1 X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB1587; 20:9GuGFUpBaRKSAkPcfb0gIGqr3nNGkl/70tzaSKqvErxq6jWcDFyW2flWCq0R/GoJvQhn+t6Rsq1BftkPWJ+4fLihDszTEqND/Ymt03qu7635E749tIVcHCUZAKpO7VHseQwpHFzagVuydpCZRGVZaTUlx659cRXU5RqtS49JqsxaenymjZT2GWgfz+kwOH/FdhwDIdKgG93tK2iIJ47QOFptNojKLuDD9u+FoVTFLFuCYLMGzwGwz0I7qumbO6uTuGiPUgGjf3lFnlL5FfED/rxYbPBoZAqe1a6n83WTP4yznISmT9VSDsZh97Et3sSa4vQCJ8E6uHdvpSEgh8RgJerOPq5AwKO5cVvVYK4uSMxaCNVOumWA2NdGYw4Ux8m8GrIEswrWkie2A3sLFRUDnwx3H/V9c9AqTQyN228Zm+YDPXk+IGtU+qoVryVYlg8pgZi0jm8MuWmczI9UGCcVMeZzj9SXQtdPP5FYC93hFf44MqSFzYHDQIFtwhq9jXjEoKVHg4F7UgErWp75msvNkpy/fII/JujHMCa5jWyp4lKZNfAPyhlIzvLxgfEzeZOnPyfyQvrY15H12FgnhSM56+XsCaf9t7u0tXHc+HdzGsc= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(61425038)(123027)(601004)(2401047)(13016025)(8121501046)(13018025)(5005006)(520078)(3002001)(10201501046)(61426038)(61427038); SRVR:BLUPR0301MB1587; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0301MB1587; X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB1587; 4:iYxvgue0k5Cs8oq55o7lOKny/h584tfeGrIQ9pEv/gib2eT+JtxTS1XiMBNzeyFXaZgevQ6uLD75aeO94eGwuTps92AS7Js1lxZnjVW+1YBBZ8Y/WhoMi4M7XOurHU1jxLxW4mK6BxI6Q0SnVEznb/rjFarJsFtqzJluRX7xoYmpVvbMuNTjtHcGQpsW8LXKW519fNL1e/FMHsVYr4HSmU7DZr3mEnGU1ykfNJns1yFfuBGTCLTimHQjYYMr8iCPq2VWKpUi4S6O9Z0htKMYuSyswikKNm4svWuaxZrqVtWVueJRV8gjsE4ujwsYCza2igRCXQLRunxzf7k/4B5zcIqdP1HYhHyjeCjvJ/0d77e7RwvrVCWzQu4JC6S/qmEboZYejaX5v0rOOjN8e1dhBdC9BlIoTmdjI+Qoz1vFg04n8feQuHJ9K+NT+S2lupDQEmKETw0Lnl83icoPyEQy2kSRX7RRY2+LM5Mb1pVqekF3zuhGNcTyAS/grRbPcOBF X-Forefront-PRVS: 08331F819E X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR0301MB1587; 23:QPQXb/ghTe1GfOydWt66FF+qPXGi3kzK3iWHxur?= =?us-ascii?Q?VDt1Ky7BbUMXj0Bccjyk4aoX8gupC2fo8IjyRmQhdz1zsXFpAgtMMYWAB70J?= =?us-ascii?Q?K9APBRJfvcPCs87ukpopr3VQonCPIVFpf7+W9fQtmNZ6Xd/oMeBEtq6uet9D?= =?us-ascii?Q?D1+37IMyvfrOhoh6lLWGy/97/vYFyF0DZAEGkN54FRqWo3kkB+fbVOmV1gGQ?= =?us-ascii?Q?8JcEyuCHZh+bE/zi3yPpScVLczPv6neCiRuGz8LXiNmE73X/ypWNOMNJAfjg?= =?us-ascii?Q?9PhId0SzcqINTmmJrRXTPA/WvVc33SfZAWHqbp/fsFJIHFs41jGei1b95ran?= =?us-ascii?Q?Fx39RXaZTsmOT0NonZG76w7eVCBoeER6grYVNgPAOBvL+HWelvRvTjZehojX?= =?us-ascii?Q?iPmTHhY+fC1xRmfmoGRAayKIguAWs7AMYUB8XRW29FqOcivHB8yxepItQxMt?= =?us-ascii?Q?m3u0OplKNnG1+98nZq9622EMgG9sWCjibtuZqXA+5L5lJeAsc5m16m484xK+?= =?us-ascii?Q?PspvxEdL2ruMuz6axgjyxhNELZ4evDwj3lASBd8ICtI1J9VvffxJ6wegE2Pr?= =?us-ascii?Q?bFUDXsZXMSxfhXYQ4WBNDFR+sxJ1gi0feCN4rIrkxn52njWmajjJC9+fP1Se?= =?us-ascii?Q?o+7EPog8VByuQRTCkIUOypHJX3m/qjXOgRuEhpmNLcE67gqSkHpYe3MRTWBq?= =?us-ascii?Q?3HULvBVYo6b2ggZTTOUlhUBbWZb2NPalikOn4jAg+yvObE7jLyiNe2FjUQ7c?= =?us-ascii?Q?5LAZfBHIqKv73zHPnW7hCoBbJ2LEy3jCjl+ZY9Bk5rIe15KDHRCPup0gqQYx?= =?us-ascii?Q?EU1SapSakrzeNn0LR54iJm7crObNlmGMppB3qwBtSh/pTmrYSdKHJJ5PXboX?= =?us-ascii?Q?TVf7f6aUf9BD32+kCnHnq8Q1YMMCoLlgLFkRN4QmWM2HTb27KLXEt1+DbG7k?= =?us-ascii?Q?xa+WInODnAqQOFqhf72F7qqyS6mgpFxF0bBBefcDB9PSMaY9WGbhjhG39Oes?= =?us-ascii?Q?emCQwnjQJvBKPQLZTb7YQSG8SCaVqia2UES4GusZ6R0MFHnZF96sXV6ntjTC?= =?us-ascii?Q?AMLwFvgJIFc23QXVuh1ihexDktjvXgEiglb0oCezrj0q0mMHr1cBhwH+iR1L?= =?us-ascii?Q?SEwHmCfedbm8UzujEGTzXWfS3PoW4/uMJNe+bCEZe2B1f0UAjzjHaDXDKpnr?= =?us-ascii?Q?9PufSxKyrfOaY1eVBxzj6nXownR7pMY5bJNuUm30U0Dxj9HHsv4vb9faJXHE?= =?us-ascii?Q?rKk3dcYYPgQ/zK1Tirley0xwJeSKq+nQjVu16mjZhYMbJux+jv1kKgq32oCx?= =?us-ascii?Q?oN/fpg6P1ZKT8Km+bONJ7Td/FLMa3nS4wMPB3v8kgawmR2/62Wr6kocGJmjR?= =?us-ascii?Q?KRja3p8CqUih4BDnK5LMStS/OPVGpiqhtbZn8yzXRYBtldA11VH1XIaPtm9H?= =?us-ascii?Q?zXKz206Obt6FEGrp8+FJWc/O3yDdbkWWXTPoZ9WrG4YsZRMozYr+cBYfmgFI?= =?us-ascii?Q?sHal9Zhl8KblVks1Ruk+l/FjQwoiApx0oKZugOYkhso3JY+kgew+g56Recp6?= =?us-ascii?Q?WTeuWFtlaZjTbLVnJEXlBs4xLosacoFe7QivCyHEdrEQwN0HCkGUaso5cuL9?= =?us-ascii?Q?vgl1XxApYW1oiCe7UO/cc8R9HJ9GbtFx8NTI+zEqrJz0=3D?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB1587; 5:EFbL6m2G6e1Qf97xcW5JNGBibQqiQIRXkqoqFUguVLD0dEQ7pRdANY+s0d0lc5XR2482vXJO0OUTMZAss9Cj4hlNT1FmolorRc7IRZjt9PiALWneBGLe+WlW8XHbCqbbhKB2lI6FHd7afO8YoNZk8g==; 24:iUqO2rW67mqbVufzRoiM/A9ZLEFzJ9CyVaFBgfNlMwcw3QfQMoLyi9TCHQZUYjQLU54dDvXjetc8JqxZRAm1XmmC6+j6SWtW9wDPisBWCjk=; 23:Zc7GEqHWs7T8s/KecgJxaEgLTiD57WyYOKZwTGHQIuaVCgsg3QjIbEl5F6gypm8CzxinqMFPHe5wGctqUmMJcbVUf+Sfe7LpUTnWnfbXYPZtVGaG1NVncblp4KhGCRhAIKxslwioH88NeuO6OUW9tj5XTUWMt1N8zGDjHxY0LxnfVGvCYM/kMEWroVk0xDJq; 23:BNH81WdK07ZCexvTk9K3EQ02v9KDJ49u+3CiutTD3Ib3mYUi1l5Cq11mDdsequzKhb/p/zWQudTdm9aUQTDM6Stx7i6rrNNX8zQvFmQzJ/Sqfqh7Zt8jnGyiKWmLt1/L+LE0oHPtRgCvS2UDaUhVe7RKhextvkqij+X8/Ol5X7pakMBgc8BJUdDkSstonKhY SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Jan 2016 00:00:55.6812 (UTC) X-MS-Exchange-CrossTenant-Id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=72f988bf-86f1-41af-91ab-2d7cd011db47; Ip=[206.191.228.180]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0301MB1587 X-OriginatorOrg: microsoft.com 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, 26 Jan 2016 12:35:38 -0000 Hi Jac,=20 Thank you for asking. To isolate your issue, could you please try disabling= SO on your 10.2 system first? Thank you.=20 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.=20 Thanks, Kylie Liang=20 -----Original Message----- From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-virtua= lization@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 pa= tched 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 vmb= us0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 receiv= ed Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 receive= d 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/204= 8 Jan 25 21:02:01 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11:0= 8 Jan 25 21:02:01 mercurius kernel: hn1: on v= mbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 rece= ived Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 recei= ved Jan 25 21:02:01 mercurius kernel: hn1: hv send offload request succeede= d Jan 25 21:02:01 mercurius kernel: hn1: Using defaults for TSO: 65518/35/2= 048 Jan 25 21:02:01 mercurius kernel: hn1: Ethernet address: 00:15:5d:ac:11= :09 Jan 25 21:02:01 mercurius kernel: hn2: on= vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 re= ceived Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 rec= eived Jan 25 21:02:01 mercurius kernel: hn2: hv send offload request succee= ded 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 vmb= us0 Jan 25 22:20:02 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11= :07 Jan 25 22:20:02 mercurius kernel: hn1: on= vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet address: 00:15:5d:a= c:11:08 Jan 25 22:20:02 mercurius kernel: hn2: 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 mailing list https://na01.safelinks.prot= ection.outlook.com/?url=3Dhttps%3a%2f%2flists.freebsd.org%2fmailman%2flisti= nfo%2ffreebsd-virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.c= om%7cc9ca2e0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c= 1&sdata=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org" From owner-freebsd-virtualization@freebsd.org Tue Jan 26 14:26:12 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 5E64AA6ECA8 for ; Tue, 26 Jan 2016 14:26:12 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (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 2E5521637 for ; Tue, 26 Jan 2016 14:26:11 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.local (localhost [192.168.5.2]) by webmail.dweimer.net (8.15.2/8.15.2) with ESMTPS id u0QEQ3Bo027976 (version=TLSv1.2 cipher=DHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO) for ; Tue, 26 Jan 2016 08:26:04 -0600 (CST) (envelope-from dweimer@dweimer.net) Received: (from www@localhost) by webmail.dweimer.local (8.15.2/8.15.2/Submit) id u0QEQ3Xw027975; Tue, 26 Jan 2016 08:26:03 -0600 (CST) (envelope-from dweimer@dweimer.net) X-Authentication-Warning: webmail.dweimer.local: www set sender to dweimer@dweimer.net using -f To: freebsd-virtualization@freebsd.org Subject: bhyve with Linux guest, how to safely handle updates? X-PHP-Script: www.dweimer.net/webmail/index.php for 71.86.41.122, 192.168.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Jan 2016 08:26:03 -0600 From: dweimer Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net Message-ID: <790acf0350e0f10e79b4120e564a553c@dweimer.net> X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.1.4 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, 26 Jan 2016 14:26:12 -0000 I am currently running VirtualBox with a Debian Linux guest to run Ubiquiti Unifi-Video server. I had it briefly running on a byhve VM, but after about 10 days of running fine. I installed some updates using Aptitude within the Debian guest which promptly broke the VM. I am currently running a beta version of the UniFi-Video server software, and as such planning to do a fresh install when the release comes out of Beta. I would like to go back to a byhve VM, instead of VirtualBox. But before I can make the switch I need to find a safe way to install updates. I believe that the issue was one of the updates updated the kernel, which broke the byhve to grub boot loader setup. What is the proper method of handling this so that the byhve to grub setup gets updated? Does this issue go away on the current build with UEFI setup that's in development? Perhaps its best for me to wait until then? -- Thanks, Dean E. Weimer http://www.dweimer.net/ From owner-freebsd-virtualization@freebsd.org Tue Jan 26 15:31: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 75053A6E932 for ; Tue, 26 Jan 2016 15:31:35 +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 0D11F1344 for ; Tue, 26 Jan 2016 15:31:34 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id BA09F2B9BDE; Tue, 26 Jan 2016 16:31:31 +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 06652-10; Tue, 26 Jan 2016 16:31:31 +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 72AD32B9BA4; Tue, 26 Jan 2016 16:31:31 +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, 26 Jan 2016 16:31:31 +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, 26 Jan 2016 16:31:31 +0100 From: Jac Backus 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 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQAA5R0WAAEltbYA== Date: Tue, 26 Jan 2016 15:31:30 +0000 Message-ID: References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.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.126] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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, 26 Jan 2016 15:31:35 -0000 Hello Dexuan, I did fresh installation with the current FreeBSD-10.2-RELEASE-amd64-dvd1.i= so and this works. Even with the message, as you already mentioned. With kind regards, Jac -----Oorspronkelijk bericht----- Van: Dexuan Cui [mailto:decui@microsoft.com]=20 Verzonden: dinsdag 26 januari 2016 7:49 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, Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso"). The message " hn0: unknown status 1073872902 received" should be an unneces= sary 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.o= rg' > ; BSD Integration Components for=20 > Hyper-V > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 >=20 > Hi Jac, >=20 > Thank you for asking. To isolate your issue, could you please try=20 > disabling SO on your 10.2 system first? Thank you. >=20 > 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 >=20 > Right? And add our engineers in the list. >=20 > Thanks, > Kylie Liang >=20 > -----Original Message----- > From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-=20 > virtualization@freebsd.org] On Behalf Of Jac Backus > Sent: Tuesday, January 26, 2016 5:56 AM > To: 'freebsd-virtualization@freebsd.org'=20 > > Subject: Hyper-V networking: problem after upgrade to 10.2 >=20 > Dear reader, >=20 > Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a=20 > full patched Windows Server 2012 R2 x64 version. >=20 > After the update, networking does not work anymore. >=20 > In /var/log/messages is this: >=20 > Jan 25 21:02:01 mercurius kernel: hn0: =20 > on > vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status=20 > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: unknown=20 > status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: hv=20 > send offload request succeeded Jan 25 21:02:01 mercurius kernel: hn0: Usi= ng 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=20 > Interface> status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown=20 > status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send=20 > offload request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using de= faults 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=20 > Interface> status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown=20 > status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send=20 > offload request succeeded Jan 25 21:02:01 mercurius kernel: hn2: Using de= faults for TSO: > 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn2: Ethernet address: > 00:15:5d:ac:11:07 >=20 > It worked fine with the 10.1 kernel, and when I boot this kernel, it work= s again: >=20 > Jan 25 22:20:02 mercurius kernel: hn0: =20 > 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 addr= ess: > 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 addr= ess: > 00:15:5d:ac:11:09 >=20 > So I am running a 10.2 system on a 10.1 kernel at the moment. >=20 > I found nothing in /usr/src/UPDATING and not really anything on the net. >=20 > So, could you tell why does this happen, and how can I solve this? >=20 > Thanks for the help! >=20 > With kind regards, >=20 > Jac Backus >=20 >=20 >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list=20 > 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-=20 > unsubscribe@freebsd.org" From owner-freebsd-virtualization@freebsd.org Tue Jan 26 23:03:42 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 5659FA6EEDD for ; Tue, 26 Jan 2016 23:03:42 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::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 26376C92 for ; Tue, 26 Jan 2016 23:03:42 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: by mail-ob0-x233.google.com with SMTP id is5so154349544obc.0 for ; Tue, 26 Jan 2016 15:03:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=FgrN60wc2iU/PDtUZGV+KxFtpDNuVpRyVpNORP85dKg=; b=EZo+oy84zlnBxAQqrKZ6MnnpHkKowCt9UfK6eDrllBzM3s44RZDCMxNiM140QVD90D 3RfudtvG2q0Cs5JGjs6UZ9V3NWWukrBU0az9m/Cb2KpKDuHkOXg1ua+8EDNsaRH1hE5F v/NfCSIqUiG9FyCRjrfjAWOlp8sO2y4n27bJ4COZbhP+XhYCtAsKD7cPMXvn9frh+pIj hUlkDN4sl96jAhr1IZP6Dll+ZD8sm9RAgZO2RFtaCLtDcCm2FIFGWQDfzt+DnoyC/tbe /B8QSBJHWo9Dsvc3xsOARotoMfWekC21quXrWmTt3PmeS7XodhoI2thinZgPhPwDjLss wKqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=FgrN60wc2iU/PDtUZGV+KxFtpDNuVpRyVpNORP85dKg=; b=bAq1WIOdP+e8WCJ7r5ZvWMO0wtPuGlKAyGm0jR4YqVEwrCltlQ+XZcwTibmlVTB4a7 thmcy1oBcuPy5vJFcnh9TEcseH8dnZXoNv95S4dD0xDRJg6GnSkF3+X6KDsWOfAIHlVg t0kcUEGVFY+N+DPnAp88byc1kObgayI3A5LJ+cZ7ctBR8Tgmj52LIbIQ3H62qHH4r9yj lPwIEZuEPNhLhjOoLwU0stXlLbX59/IbcF+Z64u1cYnDN5O195wMrujBOFs6d7QMPGul 2tlM/JNNc2DsfIqY59HvT4rB1cWOwVQ3S1276e1rkS4uNHSxgOv9+JwFIrkLSonqKrXK qYCw== X-Gm-Message-State: AG10YOSUV1vdbu0M88zBtsEsnpGYDkjBccoqVgw17GyO6SzN2HdiheQIeZld9e/nyEf71g== X-Received: by 10.182.20.238 with SMTP id q14mr16900381obe.33.1453849421254; Tue, 26 Jan 2016 15:03:41 -0800 (PST) Received: from debian.ara-ler.com ([50.243.135.133]) by smtp.gmail.com with ESMTPSA id bi2sm505921obb.24.2016.01.26.15.03.40 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jan 2016 15:03:40 -0800 (PST) Date: Tue, 26 Jan 2016 16:03:38 -0700 From: Sergey Manucharian To: freebsd-virtualization@freebsd.org Subject: Re: bhyve with Linux guest, how to safely handle updates? Message-ID: <20160126230338.GM4109@debian.ara-ler.com> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <790acf0350e0f10e79b4120e564a553c@dweimer.net> User-Agent: Mutt/1.5.23 (2014-03-12) 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, 26 Jan 2016 23:03:42 -0000 Hi Dean, Excerpts from dweimer's message from Tue 26-Jan-16 08:26: > I installed some updates using Aptitude within the > Debian guest which promptly broke the VM. Additional info is needed to help: - bhyve command line you use to start the VM - what error messages do you see stating that it's broken? Sergey From owner-freebsd-virtualization@freebsd.org Wed Jan 27 01:08:02 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 41FA0A6EF4C for ; Wed, 27 Jan 2016 01:08:02 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (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 EFA2A1C7E for ; Wed, 27 Jan 2016 01:08:01 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.local (localhost [192.168.5.2]) by webmail.dweimer.net (8.15.2/8.15.2) with ESMTPS id u0R17wrW097787 (version=TLSv1.2 cipher=DHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO); Tue, 26 Jan 2016 19:07:58 -0600 (CST) (envelope-from dweimer@dweimer.net) Received: (from www@localhost) by webmail.dweimer.local (8.15.2/8.15.2/Submit) id u0R17wvJ097786; Tue, 26 Jan 2016 19:07:58 -0600 (CST) (envelope-from dweimer@dweimer.net) X-Authentication-Warning: webmail.dweimer.local: www set sender to dweimer@dweimer.net using -f To: Sergey Manucharian Subject: Re: bhyve with Linux guest, how to safely handle updates? X-PHP-Script: www.dweimer.net/webmail/index.php for 192.168.5.1, 192.168.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Jan 2016 19:07:58 -0600 From: dweimer Cc: freebsd-virtualization@freebsd.org Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net In-Reply-To: <20160126230338.GM4109@debian.ara-ler.com> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> Message-ID: <9ee895854c862cccc0bcc84c16eee063@dweimer.net> X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.1.4 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, 27 Jan 2016 01:08:02 -0000 On 2016-01-26 5:03 pm, Sergey Manucharian wrote: > Hi Dean, > > Excerpts from dweimer's message from Tue 26-Jan-16 08:26: >> I installed some updates using Aptitude within the >> Debian guest which promptly broke the VM. > > Additional info is needed to help: > - bhyve command line you use to start the VM > - what error messages do you see stating that it's broken? > > Sergey It was a while back I was running it, so I am not quite sure which method I had finally stuck with I worked through multiple different management scripts at the time before settling on the one I liked best. I tried at the time to manually run the VM without using the management script to no avail. It would start with no bhyve error on FreeBSD side, but when connecting to the console the grub boot loader couldn't find the kernel. It appeared to be a disconnect between the kernel upgrade within Linux updating grub configuration and the grub2-bhyve setup. Maybe it was just a one off issue and something went wrong during the Linux update and nothing to do with byhve. However at the time, I didn't have time to play with it and new I could get it working with VirtualBox. Is there anything that normally needs to be done after a Linux kernel update to refresh the grub2-bhyve setup? Its winter now, so I have some time to play with it again. Unfortunately the old external hard drive I wrote a backup of the data to save until I had time to work on it again was too old, and doesn't want to spin up now, or I could provide the exact error information. -- Thanks, Dean E. Weimer http://www.dweimer.net/ From owner-freebsd-virtualization@freebsd.org Wed Jan 27 01:10: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 A234AA6F004 for ; Wed, 27 Jan 2016 01:10:26 +0000 (UTC) (envelope-from v-yanqia@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0107.outbound.protection.outlook.com [207.46.100.107]) (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 41B1C1CF8 for ; Wed, 27 Jan 2016 01:10:25 +0000 (UTC) (envelope-from v-yanqia@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=UmVeLMT5wVfAveW+IOKpEKpoECRb+iUYMQHwCvwLns0=; b=SLNIsGPJoDFATP1s4VrdOP5ggtUuMXIetGoARcvycTW4d6tmLO0xEtjipTscpL28qyTRJ8gpmMJ3PsLw2mo22xfnTobdZbWzkAi4b/qif7t0w97TVtLLiqlQAeZCRAi95utQ0bcdKo2TbiziavxYwTTJArROK786n4cE8xNHA3Y= Received: from BLUPR03CA009.namprd03.prod.outlook.com (10.255.124.26) by BN1PR03MB023.namprd03.prod.outlook.com (10.255.224.41) with Microsoft SMTP Server (TLS) id 15.1.390.13; Wed, 27 Jan 2016 01:10:17 +0000 Received: from BY2FFO11FD054.protection.gbl (10.255.124.4) by BLUPR03CA009.outlook.office365.com (10.255.124.26) with Microsoft SMTP Server (TLS) id 15.1.390.13 via Frontend Transport; Wed, 27 Jan 2016 01:10:17 +0000 Authentication-Results: spf=pass (sender IP is 23.103.252.4) 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.252.4 as permitted sender) receiver=protection.outlook.com; client-ip=23.103.252.4; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (23.103.252.4) by BY2FFO11FD054.mail.protection.outlook.com (10.1.15.191) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Wed, 27 Jan 2016 01:10:16 +0000 Received: from SG2PR3004MB0090.064d.mgd.msft.net (141.251.197.150) by SG2PR3004MB0090.064d.mgd.msft.net (141.251.197.150) with Microsoft SMTP Server (TLS) id 15.1.396.8; Wed, 27 Jan 2016 01:10:12 +0000 Received: from SG2PR3004MB0090.064d.mgd.msft.net ([141.251.197.150]) by SG2PR3004MB0090.064d.mgd.msft.net ([141.251.197.150]) with mapi id 15.01.0396.010; Wed, 27 Jan 2016 01:10:12 +0000 From: "Sephe Qiao (Wicresoft)" 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 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pA= Date: Wed, 27 Jan 2016 01:10:12 +0000 Message-ID: <2323532a95934cdfae0142a9d6f88fd8@SG2PR3004MB0090.064d.mgd.msft.net> References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> <1430812ff38c4e08a4b91ea25fdb5a7b@HKXPR3004MB0088.064d.mgd.msft.net> <1fdbb9b939c54e31ac00329f61bf6f41@ORTELIUS.internal.bugworks.com> In-Reply-To: <1fdbb9b939c54e31ac00329f61bf6f41@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.197.132] X-MS-Office365-Filtering-Correlation-Id: 8389a708-f75b-4639-ad72-08d326b69dfd MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD054; 1:DdKmJjdP0GyxOGK8FZCYoh97gowLU8spNAKsbws0IMMfsRWU21ktk66qF4jiegGJuJ9WB2ML0sgWO2//gl+puhDIYSm2QrkRd9wsl/Jj36ts23qNLpys6ycTrFEb7m0caleLqpHi81g7EEla7QMDGXLCJ/Nksg0ZuOZjjc2aq0196l5F7MItkrHhmTr16TFyJk1o2pkvY/WCLAmEZcQrFFolyEHwh8oOA0pd9g0XsXDecEdabq47t4afZfMC7rqTV7g+TR9EX8hL77/B5xa3irHZyH8dNgj378bzQVM4eCCodejfzaa/7cARAsZvIuGJVb5jKzfH8sLrFp6ftnnKgQ== X-Forefront-Antispam-Report: =?us-ascii?Q?CIP:23.103.252.4; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(1001902?= =?us-ascii?Q?0)(2980300002)(438002)(189002)(377454003)(164054003)(5191400?= =?us-ascii?Q?3)(13464003)(199003)(3905003)(71364002)(108616004)(16796002)?= =?us-ascii?Q?(10400500002)(19580405001)(2906002)(67866002)(10290500002)(5?= =?us-ascii?Q?12954002)(86362001)(575784001)(93886004)(92566002)(33646002)?= =?us-ascii?Q?(5004730100002)(5005710100001)(6116002)(81156007)(24736003)(?= =?us-ascii?Q?19617315012)(4001450100002)(86146001)(86612001)(69596002)(18?= =?us-ascii?Q?206015028)(87936001)(2900100001)(1220700001)(11100500001)(10?= =?us-ascii?Q?96002)(2561002)(102836003)(107886002)(15975445007)(500196010?= =?us-ascii?Q?0002)(260700001)(19625215002)(3846002)(2950100001)(54356999)?= =?us-ascii?Q?(99936001)(106466001)(19627595001)(6806005)(16236675004)(500?= =?us-ascii?Q?1770100001)(19580395003)(97736004)(5008740100001)(189998001)?= =?us-ascii?Q?(2421001)(50986999)(790700001)(66066001)(84326002)(76176999)?= =?us-ascii?Q?(1511001)(19300405004)(66926002)(5003600100002)(586003)(1009?= =?us-ascii?Q?0500001)(17760045003)(300700001)(7099028)(491001)(562774006)?= =?us-ascii?Q?;DIR:OUT;SFP:1102;SCL:1;SRVR:BN1PR03MB023;H:064-smtp-out.mic?= =?us-ascii?Q?rosoft.com;FPR:;SPF:Pass;PTR:InfoDomainNonexistent;MX:1;A:1;?= =?us-ascii?Q?LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; BN1PR03MB023; 2:sHllCGCwqIIpWN12PoAL4M2N/iMyyFGrZWRu1xs5vV+x8ZoAmUBEmoqdXmKmZgZUKt1Vnb7Z9DQYwuDE0DQE0rd9We5mXO0HL6CJFAD8JcqKBusmWJqcsjwTYMVAJhlBauGZoPi6hSb0GpYDKLZrVOCcqpFfIJ9x1krIcdaa4+1X1NuQwZ2gyrSl7CGic7Ic; 3:wvuJLQBUGE04EsnPY2wZem7A1/CzZZlKT9t32ftRBJpMd8ATS4z/6S8g17ifjojNeRqXXNdgpIL8HSw10/a65eb6TLC/8/jK5EeSq77/5MQ5aiCZhhYy6wkmMtuq//w8fQTgbAlrDm6Loil7uyow38DdFjE20T7I4lmAUIrUhMz8MRqV5uTj+HP2ktXh+em4n7ozgL7ykGnEL7FqREQcajwwzY3+fEU7sBL7Z+aAa69YtnLuhpkA6LK9jzIT0e89; 25:/gEYT7dszg1cyGEMnMTBWGDXs++klX+hlNYD/AJNv5KOKFcSOEhv97z3iRhlcBDh7ub7x032qW5KgQdjRWMHuNJme7ZpdASBzjsCPZoqY7Ss/YMa6SfkwUfCrvpkKEJ2hLDKScapla6lebsx/977+tfrHi/BxDOkvkkNREV8+aBdvXlWnIHOjhl64SgguB9EgvytzHgG9VPAN7EuVb/9sHXKAP21hADhkeD4hJqlqkdZgd/53e/86GNF47KMJfWtuuCXiNQNfWBCyWpde4l/Ia89FoOywdVTzIaMk5hdEJA= X-Exchange-Antispam-Report-Test: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BN1PR03MB023; UriScan:; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BN1PR03MB023; 20:8uYKXB61fg8/mCXjWpop3nlsHZtGzJ1wOh35jIUqA6KuQ1LJnwhndEVYoIk5um3ecPSFDFf1b8xUwKW3r+iWJ6lSinOdKd1HVo7FfqtnN8yF3/d/rp34iKlqU7MhPWQtsPYcJ7KgESbLD85XijZe6a+meSj4kHlnIz0OwCIMqXUNxd7jQey9kYI8vQ7RaCkkkZgSIb1yBNVV8rooJP2Gpuqhit9buQuK9erM36FGO4HF8tdc3bOpYWSepHdwK2isiCyhhL2kP0ZlpMSueC43EZG588T+suK2qYB6yM2ui/KSRHn4JnFRHHJb2hKoEOZo4TixNTdwGfLr2hAJCpGKO1+ZttnRV1wmPkeREUHgVvlPdLBpkCBF3T6CT/O74T0XkgJifNw9tx8FZBHCduuKhqQdbwTSrZe2TOWDwmg2WYUuMQZcGp2GgT2J5W30sjS/PReNjP+/YuDrPp5Hx4DdfHc/7AZWiEXlDrpjfmr0jtr0tVFVtLSrrIwNFN72x6xaRSeb681qBEUo9Ecw4NKf0VaANnqMWRkC4qDQtpqnWUfkzpOgRIce/yJnxzCYTZMDTvgmkF4w3x/J5vOvGGXA7Xt+FtNpVGWN17MJjkiRAqY= X-Microsoft-Antispam-PRVS: 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:BN1PR03MB023; BCL:0; PCL:0; RULEID:; SRVR:BN1PR03MB023; X-Microsoft-Exchange-Diagnostics: 1; BN1PR03MB023; 4:tCBQGparIksUOHTrIWeDXb0fm2n7xwW3LYCvDbrokX2Twea640GiU98BD+XQWyUz2ZHT1u2c57n9sM5pCBjdJLYgAlPyflR6zgNrcdJJKY7Ye+RX4ziiX5OS8Wxs2GvAXQqYVfZKad1etGOm+CHdKl3vDtXsifOggFipAq5km80nRTQQ1hEnk42dDIIQr5MevsQZrxT25l07dxexK9g9nvE7o0rypQGfPMpeoukb9I9zbii2+gbD9jiG0YbzVDyYCvvQP5xQacsoHwcu/VBdQILqtvcpfDugzdI9+TyrPKm5UyEeIeqCBJ5AagRW7qfZP9P3Iyet9Fe7brClfxGnpsFdpvKWZZRvMG1ucJifPmzoMK3jDWR5gFO7uiSP8Y806T60MHcIdEZ34b2J0AbX8+xjt4R6WeY1IzOp1R23Tud8uFs1PmU7+bkb1vplTzcgUhHEtFir7X7swWEIqzWiMAsRdSC4k6SIJrNTKHZQuc9u4M6toGQVp4fY/CA2YeqI X-Forefront-PRVS: 0834BAF534 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN1PR03MB023; 23:pchambWhH5pUdsC+0TL+BEnJOobEVqlTg9bjwZSp9D?= =?us-ascii?Q?COw5tjR5oRsXea1k+GrRRlcDHzS+UUWDAKdLElqeCorBUcJuoJQAV85qjp0S?= =?us-ascii?Q?+Ch98mKU4f0D7VRd9nhdQwAtnSza4pAB6AjD4upI1wJrbWGMGi8w2J43+9jF?= =?us-ascii?Q?+GrJTfuv6hO/zhpGbjBgGSqtB99rMOZmEQyHLLJB3FHYMysA4DXfqGbh46zC?= =?us-ascii?Q?jCqeie3Hx7Zk05dKxFiL1a/B/v4adfK/EFv5xCuDZGeuZWcTPVd1YLxZ1z6P?= =?us-ascii?Q?nzV14SbbsiUZYPYgHvJEWaOgS1bqJT/llgd4ZPlvg4G/OcdBE+LrIOTSgrd3?= =?us-ascii?Q?OIFsMGjZj7KPxKejPWUwHSbvEp5OADq3ycjrQXpYrCPKvWGs05GBxd4LGQg+?= =?us-ascii?Q?W9wS2vbBYU+y8JQ5xK0uG3Ue0Ko3WSZBnWRnbMXf86pODGo2FbG0hdw5uc65?= =?us-ascii?Q?EobqFBQ37NToLYTt53UC1dQ+azi4J53KRiOUE4gak3pkajmX5FTgT9rygj2/?= =?us-ascii?Q?Cza9b9KCZUC0zJX+zABYtgdnKwD3W9H8n7hyXiR2SL7ipXkGKaWiLOlOid5v?= =?us-ascii?Q?1vjLfqjOSr+qtv98dF0jeoBymcSNCBqduexjen+d+/EBA9zfdsrl+N460F5d?= =?us-ascii?Q?sm/1Pq0M4Ac3bCPPInwTQeqsR8xU7egsg33P6pwwzPTXr0nmfaWPEX/CcLjT?= =?us-ascii?Q?tWVjBuNY/lnRBguKjZlCw7RFnc+tAFdjh82QnpJp3uOG0qETxllR5GMTVZvj?= =?us-ascii?Q?w0dyLiS5eccDbtKxF2geC7pj+BvIii9aNsXavb9+5fltZuOjY4L3zZRe1PWi?= =?us-ascii?Q?aDJ/Dqiw2+HU/Ts631Gyp0A7YEb6AwMPlx89QpFqG93WeNa6NGZDbNOaZwE5?= =?us-ascii?Q?p/d+Sm/+aln91lik8OhSd2HIcpSo2CZK43D4zaq7yZ3v7nvZPaKIW5bLxiNk?= =?us-ascii?Q?BLgMRG4FF5BKuwxjVC+XyZ2RVGLbQjXm6sM47KO4g4qDryhDjV9xSxS/EgDR?= =?us-ascii?Q?L4AHCue6kiaD/5jfDzTE6y3n2oyGaI67X9kKUjC0u+yCUWT6mWmQWRn0IZEn?= =?us-ascii?Q?KKBEe21XgvaSjUyV9H+m1+sMagK26RIh0khWgoy36cWiIWl60pD8pSa96a/d?= =?us-ascii?Q?riwVSPamimtNnZGid4r4IaHemlrH4axxwnacKkcJVgoGNGqtwKzg3DZP2cEB?= =?us-ascii?Q?6iz5ufPRJmlnLfdUJ09gQuaZ9waFMefMXajTka6lUkRO/UoUibPQ5Lb2yEQg?= =?us-ascii?Q?/4W8ATdbRU6h1vpTDnq25Y7WS9OKiU7pgUrU72vk03yvP2f1UY6sqzJJlnv+?= =?us-ascii?Q?0pb3JQpBxXrJ9YVxb6wpuCJJcafEJWgtzQHVgVTx1Tk/+wNukL3j4d/SKwqt?= =?us-ascii?Q?L/PSsIm/eWLUOQ4mcgBSlBIfxxw8geadO7myKABBqT+9BqurkrD31VmXlYSe?= =?us-ascii?Q?g0qpOif1XRUwjrMnOujla1mP1VMpkYQdoKYhyzpXDHqWREYVa5DqtgMKmEmT?= =?us-ascii?Q?aUGKLov6c04cRNkQG1V9+OUJFmm0hH8cbyHif75q5xT9N6+TNRo79NGdXKwM?= =?us-ascii?Q?UbDmzUE7boDFfI3JSHRHG78UrwpcXqX0zbpTyMiNHQxN78xNr8R4sqQxVZza?= =?us-ascii?Q?e7UEsEszF5164ryqZ4soxPvgJLCc81ewWUx33VP2qWAiFAVemONYBszE/gxs?= =?us-ascii?Q?5QPDlgk3eLt5p3M/6Dc+IrUUKzMvK6JTianscW5EL86ATC/3u997SIGXOJoS?= =?us-ascii?Q?tblOszJTvsv1hNaBYGV1UChnyxUkmVFaIYfjKcLs4rFsqhpp8R5Egm2dW90Q?= =?us-ascii?Q?ScSAyLsprXUPexy+pMryWWHo0c9aiUx/mlwU8nKICYqdesuOb4x5wcjQWix2?= =?us-ascii?Q?nMYfb++x/KHBveFK0dQFuSCL8DG0Dp8AwYfdOAtLDWBKjFeP88u9IB1gWa6D?= =?us-ascii?Q?fWl7mo76Ly0xiKiQQOX48LStMbRdwxZz95EpNvFw=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; BN1PR03MB023; 5:jBtvSOHWy6qSwR4HlShTjhEYnNLFeAoIkaZxNLEHBWFvAn/gudn3m6HtjL+JW/AFKbLhBs3a3RjLv1yvy/y12kuO3jKiC6keBLNyaxtgZkvM8Z/ANzJD2zkoHvK0JhbginXKG91aXBQZUcQOD6FvLA==; 24:9s00ViRBOaHYl2a68C8+7s/KwYUd6oSb7JdsY4Bl51qBAo66V7YSNG7A5wyG0wM2wNxNQVqHs/uHfjJILI0FSTwdrNSGJePA6KL3Pic/SG8= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jan 2016 01:10:16.2179 (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.252.4]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR03MB023 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, 27 Jan 2016 01:10:26 -0000 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' ; B= SD 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@01D158E2.863D42F0] 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@01D158E2.863D42F0] 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 Jan 27 01:13: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 82A3AA6F14A for ; Wed, 27 Jan 2016 01:13:07 +0000 (UTC) (envelope-from v-yanqia@microsoft.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0137.outbound.protection.outlook.com [207.46.100.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 1691F1F38 for ; Wed, 27 Jan 2016 01:13:06 +0000 (UTC) (envelope-from v-yanqia@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=3gnoxgZEsJfI/kQUPj0RaKuYbuZV4lFMokWYlRtzHjM=; b=EPeC9ZBW5HLEmfWe6LcmRl9EuPHSm/UQw83wFSGP4IpRuxUFFFbv/Ep4WjWdnS5NVy+BT/9wJOORuRZbO3SvGwgOGSZNNwIFAnFGDHR2/YnmtF36yKbMlpeQd341b08Eoj+3BtTkFmKIJp8VQRdVH76KcanWfkOviN3RdCOAxyQ= Received: from CH1PR03CA012.namprd03.prod.outlook.com (10.255.156.157) by CH1PR03MB598.namprd03.prod.outlook.com (10.255.156.163) with Microsoft SMTP Server (TLS) id 15.1.390.13; Wed, 27 Jan 2016 01:12:57 +0000 Received: from BL2FFO11FD007.protection.gbl (10.255.156.132) by CH1PR03CA012.outlook.office365.com (10.255.156.157) with Microsoft SMTP Server (TLS) id 15.1.390.13 via Frontend Transport; Wed, 27 Jan 2016 01:12:57 +0000 Authentication-Results: spf=pass (sender IP is 23.103.252.4) 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.252.4 as permitted sender) receiver=protection.outlook.com; client-ip=23.103.252.4; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (23.103.252.4) by BL2FFO11FD007.mail.protection.outlook.com (10.173.161.3) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Wed, 27 Jan 2016 01:12:56 +0000 Received: from SG2PR3004MB0090.064d.mgd.msft.net (141.251.197.150) by SG2PR3004MB0091.064d.mgd.msft.net (141.251.197.151) with Microsoft SMTP Server (TLS) id 15.1.396.8; Wed, 27 Jan 2016 01:12:55 +0000 Received: from SG2PR3004MB0090.064d.mgd.msft.net ([141.251.197.150]) by SG2PR3004MB0090.064d.mgd.msft.net ([141.251.197.150]) with mapi id 15.01.0396.010; Wed, 27 Jan 2016 01:12:55 +0000 From: "Sephe Qiao (Wicresoft)" 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 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pAAABp5MA== Date: Wed, 27 Jan 2016 01:12:54 +0000 Message-ID: <2b22a9544c6c4ff3b017133a346e75e2@SG2PR3004MB0090.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> In-Reply-To: <2323532a95934cdfae0142a9d6f88fd8@SG2PR3004MB0090.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.197.132] X-MS-Office365-Filtering-Correlation-Id: 32ed0be0-c683-4486-7801-08d326b6fdc2 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BL2FFO11FD007; 1:IDvPB4d4cgBonY2zc3sn4b5YP43GfL+/ivf837GYxouofG4yfODHzf4+6AGgP2rD8e5oFDIjqenEwKvT3xklKYOXDsXp3nFvvwK/DNn4O2msoMr0GRKp38hPoMbB/jDW3iHgymehbKshfur8TuM2qQY0Bc525vvfC/yxHUWiCsimKYp1qzWb/rrEEtly0a9kElJxFZ9qsi6cSd5qe4SvzdoSvfzgKaet9NW9JOCuH2/nL8tbyI11bdmsG1LnHMXi0JKzZc4dKyNJPxdeZqUdyskkJ0GuvscMebTd7nAWALOYVTnLVJ4q1S3yG6rchhVWbgZESkdaU+KR68l6U+DkSQ== X-Forefront-Antispam-Report: =?us-ascii?Q?CIP:23.103.252.4; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(1001902?= =?us-ascii?Q?0)(2980300002)(438002)(71364002)(51914003)(164054003)(189002?= =?us-ascii?Q?)(377454003)(199003)(3905003)(13464003)(54356999)(1597544500?= =?us-ascii?Q?7)(5001960100002)(19625215002)(260700001)(106466001)(3846002?= =?us-ascii?Q?)(99936001)(2950100001)(1220700001)(102836003)(1096002)(8115?= =?us-ascii?Q?6007)(2561002)(107886002)(2900100001)(11100500001)(6806005)(?= =?us-ascii?Q?66926002)(1511001)(50986999)(19617315012)(5008740100001)(500?= =?us-ascii?Q?3600100002)(17760045003)(76176999)(586003)(10090500001)(1958?= =?us-ascii?Q?0395003)(6116002)(2421001)(19300405004)(300700001)(182060150?= =?us-ascii?Q?28)(84326002)(97736004)(189998001)(66066001)(24736003)(87936?= =?us-ascii?Q?001)(5005710100001)(512954002)(10290500002)(67866002)(290600?= =?us-ascii?Q?2)(108616004)(19580405001)(10400500002)(16796002)(5001770100?= =?us-ascii?Q?001)(86612001)(790700001)(5004730100002)(19627595001)(400145?= =?us-ascii?Q?0100002)(16236675004)(92566002)(93886004)(69596002)(57578400?= =?us-ascii?Q?1)(86362001)(86146001)(33646002)(7099028)(491001)(562774006)?= =?us-ascii?Q?;DIR:OUT;SFP:1102;SCL:1;SRVR:CH1PR03MB598;H:064-smtp-out.mic?= =?us-ascii?Q?rosoft.com;FPR:;SPF:Pass;PTR:InfoDomainNonexistent;MX:1;A:1;?= =?us-ascii?Q?LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; CH1PR03MB598; 2:Qckz9uddNoeTXKhbgxzIpBHbqi5yrRkOCna/BSOKqI5gRP9tSHx8RBs1lquyHyQ6ZAaI0UyHf4ZHz5vHmnLtAHpWF7BAPnGLzDAxLFaheLR6yWoCVEMkbweG1hSWuPCBwgJbZwLOKXx3lYIJxu7uIljIeOKR0z7BSEVwmd+dfPC1H7ZeS+9tKr+C4Cwtf1vS; 3:60NbrK5NYFyJBEFpMTV1zb4TKhZpKLvL/xG5w16BWshaIi3M+9Q9vPUttEWGLR1HYzXkbS4ls6thdbDbKfWr6nlqs4C7WpMT+RO+T+aezq5oXe8s4d35HvnU371cIZWpABxozO5NyozKgxeV8kGcWLBiwzf7tIiVWpi84m9wOkOBwMhcRd6eM38NlU5LS0BIhZAPIk8vvpdquXaW2vq9QeLHur5UfEyNvVEoAMw8VRIkhPaG51eDifH5YmHNvjFD; 25:nGeBbZXBmu1vb3qR+Emi/vZdBOym65wbmp6MwErHAPFyM265OdlLLrW7HE8LRAyMlLtQY9H9Y2uYDYnT1t0/rAEOgY0+5YEKExIbWisd/CsdS/eX86jUOpIRBx2CxKKmNjwWE7ToiNdFEkZ6+TR7TRHSght89s/HAQ3NkynvZ0JDZT7sEVQxWEOPBSd7daPLERsFnTBYE2cYYabXuMdgYYghhmyYVA1zaAlwY3gY2bc8Lk9AaTcYvCO36TxZTBVKQV5SoNL7N89HeiCTpO69nthmrrLPtylObHsF/36wMOQ= X-Exchange-Antispam-Report-Test: BCL:0; PCL:0; RULEID:(8251501002); SRVR:CH1PR03MB598; UriScan:; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; CH1PR03MB598; 20:T6wLdLsAj6+Txz5Qvo4GyTDcmsSosFVlF8KzweKLgBRBOChbiruSfJazqnE6NWQVOhwyzA2QMay+20oD7oXBDSoG0DhxiYHRJYMozO2rIIOwoYlgFxC4rDf08NzV4Lsb+DtR+tlKEtL5SDo4rA2WnoBHB2bEj5yEDeyIBcO/ZTGaZYiWXK7USRrI2jZViP2J74+KxGZSAn5KKxIdZvtz9r/T8J7xe/X/FSA03oC1XireqCC58eeQOmvtcN94XmMLiWWpcPKtMGZPj2Fz7p5DQ8T8AanutDcFHX4sZ9bCEWE8pqixV0FUGsObSXeMaECSMmcoUYiHVRW1p/BWzRxTPpm+kK7FwXimcR01BqBQYI2VA+nSKHHjiup4QR6aA5V1f00BRwOa1ceFPUPjAwaj84ETkaGMj/C6eq87mMMLPYnRc+fWUqMpIRgWhqNWisqztE9V9N+yT2s0sG3VBPfuwXFUBnIyukYwGgoRcCCy8BDtRCTu5V2opVG+UFr1tpegZN/uNRw1INYVFFHQIqhNClpMk1ElM5hjQ1ag0jQore9dERtDwSl2Qwbrp0KM+eDGE0+0xM1x3JZozETcOJkAE7GZuOA0O3s88kwh0Xva4Sc= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(102415267)(61425038)(102615245)(601004)(2401047)(13016025)(8121501046)(5005006)(13018025)(3002001)(10201501046)(61426038)(61427038); SRVR:CH1PR03MB598; BCL:0; PCL:0; RULEID:; SRVR:CH1PR03MB598; X-Microsoft-Exchange-Diagnostics: 1; CH1PR03MB598; 4:3T68rbhXPV4Rq6gMfrvQSg204jS0cCQw3ZG+rZUCf1vv0Jcs9mtgQLIR1UULLoREcEYuP4dwjaXWSenZOmovN/CiP++jKGAFml5zA3S9j1LWpTsrMfXEuAPBL4LJOrybrrY4toJ05f/O4UUD2EI5iJmK7FkNfieXL2MJ5vbX5R8QB/GtnYl33HzNghPnpsNa79n1emZghVuh1vO+bzqo2DXXuG+zgJySRvtcGiAAfE0fHodqGS26CskspMGKYErh6ofT5uhTGIkqLPpPH1Mkwk0uzhQZg9rWory3IMWSwmNuyK9yOaIEo8akNf2vCEIQy3N4wD+q7PyvxL+Yd/eC2faouOGpNkn6UCo9U7w1iCCEPwI5ZUQLnvTfsVKnsYeOhHvcz4H8IKKGLKs63482IP4lGN7Rpzt4FxMD+hcrVB3q6M5IJQb+sNdd9PzJKQhdDRHMG9ZyEZGNLkkPoVhcWMnEsJseTJ/v9mhe73GIbdhRBPHGcWZGPqm9o2Y9UkWW X-Forefront-PRVS: 0834BAF534 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CH1PR03MB598; 23:FOMaEMVJu8cPkXEZctHS4+e75mt8l8hU2xyqVu+KO5?= =?us-ascii?Q?0QoLXopBXqJU/DieahvGn6oFgj/OonDTr4ej/GdmOgjMcHDaMktRXJYBAmkV?= =?us-ascii?Q?LPcDkr+3PTgL/igKLMkEN9zK4Gyky6n1xwY7/0zPxUzr3QIixeFOToeNV7gS?= =?us-ascii?Q?7KhZKJcfpi1TmqlxLijN8W2IF0UPtVNubY+Rg7DuyLJatAm0My6GrcdD+Nsr?= =?us-ascii?Q?RzYoa7MRyHtN10me7Zwxl/g3a2pGVSsypSWvsGbmBQiAoeX6zZ4FXiMzqs2O?= =?us-ascii?Q?vUNqDpHxYqPADQuEcJFfUxpj9Tw0HS/E/lJI6H96bEHY2NVxKreCWruBhrnx?= =?us-ascii?Q?hCs5RRlN62gefacBS8Fb5hWWzvQELDqlPZw2d7JFGuQq6ZGk74y5GAuMq1NA?= =?us-ascii?Q?F5bcOmanq/f5SNyTWphSosMdKn8D9VR+kaZEQV5JdWO8/5m+wpmtrsOKxrbR?= =?us-ascii?Q?Bx8nFkcmFXnjAdhq3trB5bnXPhfjcs/hdSCFJYGxz3vWGhBfFmVZM3EXCJpE?= =?us-ascii?Q?uOlx5AE9+A7iavLhgI+gomu7fdlACebhdRGH1mGo9lyW738AW6gVulpiEaOH?= =?us-ascii?Q?PPjDYa88V4LXjM05G2IsGSLnepPr5X9QjhKdM/mNPe5ws508Vrf0JMWyreWr?= =?us-ascii?Q?gcaQn4iG/k4rBjc1PjRyJuWKopkwRU8ZuH1OnrpjYqHsweZB9fNs2p5FbRju?= =?us-ascii?Q?EuNkeU3YljLyaOrFYJbGDAYtBh/GSfjHiFoQxviglbejC1ds6aPzLNUXtpB4?= =?us-ascii?Q?c2zFhfmM/57vXxzwFf8KNDq/qaSSwZry1SLpYNB1Q9JomaehNiMbVRsQQ3zT?= =?us-ascii?Q?WzRFFO+61mvr7Qo6k2do8qI/lQzxCS06gf6iRrKVK25RGyiSrv/j9Z66g2gD?= =?us-ascii?Q?/W/lWFpSCzzE8xGQ80b48FUrCWn9HOlelesqh2hIbixCIJPMyurBQF+JoM4x?= =?us-ascii?Q?3PDrc2Sr11HkEqa0PWRsPgBOvs9MZMUpDMDr3GqxvU+bhzHq8vcJtau4h9VG?= =?us-ascii?Q?lMcidZSH/vATTyFDYCU4JloRviTUO46yYzFgw3EzdOYaarAlLySk/ZKk2RQJ?= =?us-ascii?Q?gOXD3qW5pkFP8UsdHU3ZriibX+AQw1CtzMkj5a9oNF14hcN6OAPZkHO7TQMQ?= =?us-ascii?Q?QzPomunqA/Kb6DqR2zn5gN+SO+UUQ0rqKGcACf0fbSfhqYSZjJD2KoQ1kpSH?= =?us-ascii?Q?E+DKNG9OGT5MWcBnrNtRXdf9eY0fbWFg149U3b0ClYanFenOJlV2VY+13r8/?= =?us-ascii?Q?KXpB7HlYO9q0DBioJV4l9oe0U+mdQGT/pMM1x4oORUQ8bXehbBq+gOH6Bawq?= =?us-ascii?Q?feYIAHDx+os2rjz6zmLPrN3hOstxoQKiStQETTRvKleeaEvNSTBEFU+2l/qx?= =?us-ascii?Q?OyLlop83wtf6QRxAEGUhDVr3Lp8KSFNeNKSP9KV1pwjOByPG5+VRC+MMs8si?= =?us-ascii?Q?k1kbxokzUsw6/9QIGSPbeGENuLZIStk5eNNL473VWM2NxbA5z7VKChTPcOt6?= =?us-ascii?Q?+nqcD5w5fB+foPcG7Kx/XOWirkRbODIMKDHipVQESa+M1m6uf/9OwY0DooyM?= =?us-ascii?Q?0R/TZS/Yuj3OLqPcR+7Fb1fk1/EdODNUoELla7V+N6vYrFmwvSvy+DaSt6Kp?= =?us-ascii?Q?n1zzc2kFxKXEjZ+zrJ8DaUp8S8+SXva26dvcPKOmRhPEFFEXqZSGxh5HbtEe?= =?us-ascii?Q?f6a31V9B+6Vtpjb9IrhvLYJtp/Xf6e1rw3paj1upqQ4hzKg7FsQhMxnwIn8J?= =?us-ascii?Q?2e5DuEP8XRmTKY78wX90SPY4mX53z9LR0yVMiBzDuRHUmMeczK4cB5uRuwBN?= =?us-ascii?Q?tLa0hjYhY+QzT8G51nFd7vkEODJjS1urjNFR8nf9jl93RMtWFl1nJnDKZorQ?= =?us-ascii?Q?LAVOYhuBA4SKRBQaidpLo3a5xnkSj6uLjcmwriAvuPRpRL/JrYiCeehnVwhC?= =?us-ascii?Q?JJ9G6iNdJ7aMgxeg1ZoEXLeigN1ODV2atOI8kb+g=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; CH1PR03MB598; 5:xo6Pyo3h+2/N2J0H+YCBTNe5LfLZWoBttrcci4Ine8WhltJIzcDCqvflqOOu0UJ7mwDlhO3NAWykNmbRSQxJ8tKI+rablQQ5TFpw4ODC5uQEx+VI0liqYU7fOnZ9HMykj7RDMdfsERdmxB6wW4yskg==; 24:C64hPlB0jYB2O4bRe3ML3YDbkikIx9zOlKi3XS82kExsfYh2IFkS7lDqPV2zbXPjihVkOG8gMwlHq5o3DWg14HKTAz4xLXEY5YCFzORW248= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jan 2016 01:12:56.7819 (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.252.4]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH1PR03MB598 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, 27 Jan 2016 01:13:07 -0000 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 ; K= ylie Liang ; 'freebsd-virtualization@freebsd.org' ; BSD Integration Components for Hyper-V <= bsdic@microsoft.com> 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@01D158E2.E7296D00] 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@01D158E2.E7296D00] 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 Jan 27 01:51:32 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 ED05FA6FE5B for ; Wed, 27 Jan 2016 01:51:31 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 7667D1C3A for ; Wed, 27 Jan 2016 01:51:30 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: by mail-lf0-x231.google.com with SMTP id c192so117240861lfe.2 for ; Tue, 26 Jan 2016 17:51:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olevole-ru.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:user-agent:mime-version :content-transfer-encoding:content-type; bh=pG8fnj4Ni6tWm0SUdwdUDeTHS2FDHaWv3K4sFg3wQ7A=; b=PieZA65fhRb7SCY9TMtEhHF/3Jq21SPrvPQSZHUzv4kCZkGLwyFRVBceypWjv7gK/c WyxRylovj0ZUFSGNHdsk8KSP8nHD0k1kxSjaAqxYOM6fG8MXJq9CyFVeN8T073LSze+/ lxH+XqGeGjdxi26+LLJlnORt318iWwt+Te1fgq3/RoxlPuSGupIkPq4YS99jaR5x176x fAK/oXsnOTr9UpK/BtXYEGUEWDN+Mkg15OOBBUioHnCtfZ+G3d0znp1NKdY6lJr/k4aX dhHUOG1pzKtf3/zSnmK4m52EIZChTMAF6uPu4qTXGTm33QaVZ5E3xZb2cx26sxIQsSdC uFlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :mime-version:content-transfer-encoding:content-type; bh=pG8fnj4Ni6tWm0SUdwdUDeTHS2FDHaWv3K4sFg3wQ7A=; b=m6nRHpQbE7ftSEv80awQ8D/39dAsl5av5Bw4O48D6LZ2Wsfb33VZmy3OQb2LIzUSJn ITGxF+lJotRjiPJg6SsGZIuJSBW+8C8k5rJHTUlainyzmonrL3fBsRNmtpPBSGRg8HWE 07yFSremeUQJgLoDHaLTvpY/X5CsXouKhOk29dDBk9kpeG6C22UNuh6BJk6Cq0YIwsP5 sUtplF84G/25Zb0RAJjLu7jMNggjk16ArtyIBwLFwpuKWahI7x3XacZn7ra4XanKUFR8 WUVBs6ijknkO703pQCJ9rCFGdnlvDkhw3AP46FsMQZwwDJGNjsRHzu2AXl6FTfZMKlFa q0Ug== X-Gm-Message-State: AG10YOTFJr5i/QiBfmtaP0FS5Tv5sI1sPsUQxXPIxVeqagFxfPSwJfibKj/F0p0Nvuwt4w== X-Received: by 10.25.20.221 with SMTP id 90mr9792163lfu.98.1453859488663; Tue, 26 Jan 2016 17:51:28 -0800 (PST) Received: from gizmo.my.domain (95-55-91-16.dynamic.avangarddsl.ru. [95.55.91.16]) by smtp.gmail.com with ESMTPSA id um4sm506689lbb.1.2016.01.26.17.51.27 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 26 Jan 2016 17:51:28 -0800 (PST) From: Oleg Ginzburg To: users@dragonflybsd.org, freebsd-virtualization@freebsd.org Subject: VirtIO Ethernet driver in DragonFlyBSD under FreeBSD bhyve Date: Wed, 27 Jan 2016 04:51:28 +0300 Message-ID: <9893747.yFCcEWVR7f@gizmo.my.domain> User-Agent: KMail/4.14.3 (FreeBSD/11.0-CURRENT; KDE/4.14.3; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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, 27 Jan 2016 01:51:32 -0000 Hello, I do not know whose it is a problem - DragonFlyBSD vtnet(4) driver or FreeBSD bhyve(4), so I decided to send on both maillist. I've try to boot DragonFlyBSD 4.4 in bhyve. All goes well, however, there is no network interface. During boot i see: -- virtio_pci0: port 0x2000-0x201f mem 0xc0000000-0xc0001fff irq 5 at device 2.0 on pci0 virtio_pci1: port 0x2020-0x203f mem 0xc0002000-0xc0003fff irq 6 at device 3.0 on pci0 vtnet0: on virtio_pci1 virtio_pci1: host features: 0x11018020 virtio_pci1: negotiated features: 0x11018020 virtio_pci1: cannot allocate interrupts vtnet0: cannot allocate virtqueues device_probe_and_attach: vtnet0 attach returned 6 -- pciconf inside DFLY: -- virtio_pci1@pci0:0:3:0: class=0x020000 card=0x00011af4 chip=0x10001af4 rev=0x00 hdr=0x00 vendor = 'Red Hat, Inc' device = 'Virtio network device' class = network subclass = ethernet -- Boot processing : https://youtu.be/iV1eZxEvj0c bhyve executed with follow settings: /usr/sbin/bhyve -c 1 -m 4294967296 -A -H -P -s 0:0,hostbridge -s 2:0,virtio- rnd -s 3:0,virtio-net,tap0 ... What can be done to correct this error ? From owner-freebsd-virtualization@freebsd.org Wed Jan 27 02:13: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 9950AA6E6D5 for ; Wed, 27 Jan 2016 02:13:52 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (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 687C3B79 for ; Wed, 27 Jan 2016 02:13:52 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: by mail-ob0-x22a.google.com with SMTP id ba1so158755676obb.3 for ; Tue, 26 Jan 2016 18:13:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=tgKvnINpVZwp9KqM2ArSx2biJrnRFxQu9t1NpcRjE+8=; b=mwpAD9Wp33dGVNVM6wciuPQfW7IT0YdQG3AWi9kjOSJSa4iAB8GGW2vCheT14Hz2rj SlLwWG1dvg7V0cN5kqBt/r5OwHlNziFNRvDlXa4hyK5e5Du0GV042ziMnzi2wGB36qu/ VJr2qZcMk0uc6C/o+q805mrCfnDVeopPwwO9J+CJqWc5BDMzgLdG9DFFM/MhDS13c2VD w1NaulEDe3SJi0B4PNDaS3Rgg3ZgAMdgK0ajleLzRpX+rxaRAnDh/W6hlcNbVfFPNNic B8+v2lTOTIrMKdGbg8/qJvlF4wHzh+/nbDiBaImrollLsSv96sQLYcSxO0bBV8OEk/na VOkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=tgKvnINpVZwp9KqM2ArSx2biJrnRFxQu9t1NpcRjE+8=; b=KYkwn0XtmOiU/JlwOx/slrEcPQBrxmljJLlkB/hFAxDva8MRFvDPsmhCDoeUdz5Qvc EZ8CRHNITyZUgRkWH33X/bHtKBw4ZhpL1ykDiYfy6DYBki0Hypc09m61MkHM6T5yN+Ek POcUNumO+1zkyEyRRZQcD4LnnY5d8EWKnljxlyi4rmwhZl4VjIirJJur6TEa0+0qIW+O dlCxmHYdSy8/P7RKBs0VBX0d0UmhNZaqxn5uCc10THST3GSlvFpymueWVpqud4K5PpZH oV9LyxyER9X9J1ODVlNePJvTMf95WMAmy85OBBGyvNnzRRVgN5/ryqQh6VSvY6TSM+hd MG9Q== X-Gm-Message-State: AG10YOS63JOIbrJaPArWYYOhcYk0GEmhoKVTu+AO3OuUN0uw93DLaqv8qZDa2JieuGoDxA== X-Received: by 10.60.58.6 with SMTP id m6mr19170973oeq.47.1453860831351; Tue, 26 Jan 2016 18:13:51 -0800 (PST) Received: from dendrobates.araler.com (75-166-211-166.hlrn.qwest.net. [75.166.211.166]) by smtp.gmail.com with ESMTPSA id px4sm2037895oec.7.2016.01.26.18.13.50 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jan 2016 18:13:50 -0800 (PST) Date: Tue, 26 Jan 2016 19:13:48 -0700 From: Sergey Manucharian To: dweimer Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve with Linux guest, how to safely handle updates? Message-ID: <20160127021348.GE1799@dendrobates.araler.com> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9ee895854c862cccc0bcc84c16eee063@dweimer.net> User-Agent: Mutt/1.5.24 (2015-08-30) 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, 27 Jan 2016 02:13:52 -0000 Excerpts from dweimer's message from Tue 26-Jan-16 19:07: > > Is there anything that normally needs to be done after a Linux kernel > update to refresh the grub2-bhyve setup? The kernel update should not have any effect since grub-bhyve uses the virtual disk mapping file, which should point to your linux drive. I'm using the following command: $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian where "device.map" contains the following: (hd0) /dev/zvol/zroot/linuxdisk1 (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in my case it's a ZFS volume). How do you use that VM in VBox? If it's a .vdi file, bhyve will not be able to recognize it. You should use a raw HDD image file. To make it compatible with VBox you can create a .vmdk file pointing to that raw image. -- Sergey From owner-freebsd-virtualization@freebsd.org Wed Jan 27 03:42: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 D9B4EA6E595 for ; Wed, 27 Jan 2016 03:42:52 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0112.outbound.protection.outlook.com [65.55.169.112]) (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 E9F251F9F for ; Wed, 27 Jan 2016 03:42:51 +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=kEeFNwWOxSZjXPL0SrZwLttx4X4v+QhhL+4pz7jj1EU=; b=kL2fom7Ty1LeXJMtjKqH30AqyCRWEesnWlFaHEY188pJP7NiS2a/E3eEhmmNfGY1Efbmci4aVMCXnSrB8tC6GNpYKfquSmsyHbLLLq5UKyeNOWVRsMGvDnGKLhgdmM7qBjKQ5fbU0CEPstgrvvn9D9gXhB3YgQZVLfgfyOmS5Iw= Received: from BY2PR03CA056.namprd03.prod.outlook.com (10.141.249.29) by BY2PR0301MB1592.namprd03.prod.outlook.com (10.163.28.22) with Microsoft SMTP Server (TLS) id 15.1.409.1; Wed, 27 Jan 2016 03:09:29 +0000 Received: from BN1AFFO11FD017.protection.gbl (2a01:111:f400:7c10::142) by BY2PR03CA056.outlook.office365.com (2a01:111:e400:2c5d::29) with Microsoft SMTP Server (TLS) id 15.1.390.13 via Frontend Transport; Wed, 27 Jan 2016 03:09:29 +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 BN1AFFO11FD017.mail.protection.outlook.com (10.58.52.77) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Wed, 27 Jan 2016 03:09:28 +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.396.8; Wed, 27 Jan 2016 03:09:26 +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.0396.010; Wed, 27 Jan 2016 03:09:26 +0000 From: Dexuan Cui To: "Sephe Qiao (Wicresoft)" , Jac Backus , 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/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pAAABp5MAAD39gw Date: Wed, 27 Jan 2016 03:09:25 +0000 Message-ID: <7df41cc958ee408297487d4ffbb91903@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> In-Reply-To: <2b22a9544c6c4ff3b017133a346e75e2@SG2PR3004MB0090.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.4] X-MS-Office365-Filtering-Correlation-Id: bbf49e04-6d03-4d9b-2ea9-08d326c7453d MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD017; 1:40M9q+NcnqBsT3aTVbVhiyEoZrG0jP54zjmo1DX7tiBnEHx7eJM3Hxd8J0XG1bmrBiz9nYu35WjsO8VkMLn8RbsQl9DOFYBtgyxItafCGpNHYjgi9o4w6sY82VxRcxvkCDwoyMK4IDGn0BipRHdTSM1rLbbr2yW/slxo9UFk1XzXzpxfqjvC+mKtD0ASnyd1ANwre/zbGbKki88x+469A9uJjkjbfGrw8/oIyP9q/USkzZIYdFWVcYgd7b88UW41kA+uHoPbp3ueXQQqm+hQyib69FJyugQ6d/gM/I6ztdq1dPg4ciEBP52a5PQKvMOecYi59n3L3vpNpmrfsueci18x5G4oJ5W/kksx1vV4N+0e5Y+8GVBjgcaZSHXgXcgx 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)(71364002)(189002)(37745400?= =?us-ascii?Q?3)(164054003)(3905003)(199003)(13464003)(86362001)(92566002)?= =?us-ascii?Q?(10290500002)(19625215002)(93886004)(5008740100001)(24736003?= =?us-ascii?Q?)(19580405001)(19580395003)(575784001)(4001450100002)(695960?= =?us-ascii?Q?02)(18206015028)(2906002)(108616004)(97736004)(86146001)(512?= =?us-ascii?Q?954002)(3470700001)(66066001)(5001770100001)(5003600100002)(?= =?us-ascii?Q?107886002)(5001960100002)(5005710100001)(84326002)(500473010?= =?us-ascii?Q?0002)(87936001)(16796002)(3846002)(6116002)(586003)(79070000?= =?us-ascii?Q?1)(102836003)(10090500001)(10400500002)(86612001)(2561002)(1?= =?us-ascii?Q?9627595001)(260700001)(11100500001)(300700001)(81156007)(669?= =?us-ascii?Q?26002)(1220700001)(1096002)(2900100001)(2950100001)(99936001?= =?us-ascii?Q?)(1511001)(6806005)(19300405004)(67866002)(54356999)(1776004?= =?us-ascii?Q?5003)(106466001)(15975445007)(16236675004)(19617315012)(1899?= =?us-ascii?Q?98001)(50986999)(33646002)(76176999)(2421001)(7099028)(49100?= =?us-ascii?Q?1)(579004)(562774006);DIR:OUT;SFP:1102;SCL:1;SRVR:BY2PR0301M?= =?us-ascii?Q?B1592;H:064-smtp-out.microsoft.com;FPR:;SPF:Pass;PTR:InfoDom?= =?us-ascii?Q?ainNonexistent;MX:1;A:1;LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB1592; 2:q6d7F3c2TF/hTTU6y/ItFNRslkZcg7sB6iYb6XOcDzuryeJvFzmSSbK5y74xPKMl/8GYlF3k/nJrkty5gbB7nLwifAS0+VhJWu62sw6O1G4CWwbL/LnSo/J16szpRzwtyw7j6/KriJN8Vl0a+8Y1rMyc3cHObaGF9pqz1TkOG3Vv5DJLytvTP7p85xcGNbu+; 3:aawJOGouuaJxOmM9JeEeIXNp6ew6/wSXysehlBqwd2jXNnZ1jnaITsv27DT+tM2WQJpNj2MjyyLP1eTYN2zlLjvAjSTWwrgQqHTdi8OXc2W4PeivPs0n1kAKz7CNjosO27b+aneoTIMJCdHc/HYQA74nBrK7u+H9zBDXApE/CvXZQszbA0xgQtw54hX8b+uQ20RBqGKDKQTL2/DCj3up1OdB8X5hvkSGYsRE6wop4FuYISJkWyHy+BjXoI1LaKNp3sDGopF531jfs8igyR+esA==; 25:SCBfVjfth/FZ6aY37kpaoxAnYRjmIiDCfyK161WX9GI3RsolInaETVHRlB6Um+A6eKhFmBBUErwVSFvUThmcO5WG5UlBhodaA/N99eLbwR9gYBDrt7lAH49AzUplU+HLRY216P6qSUuoZZGu/r/NsH/4oOyyyydzimdG+5AfQHvbev7js0GJb0rKqzgv6CB3nroA3mDvu/XVfRueU8IR7PanIWXw3iXGVt+7pJVCBjAl1hNaiDp8Tiz+E5CSQopFfc4kWFTnQJKz5JHM3rtLzaxyElScpEXk5DBBCLWCijc= X-Exchange-Antispam-Report-Test: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BY2PR0301MB1592; UriScan:; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB1592; 20:L25C9zUe4d7C17mMGooHPKndFVsGjBsa5ndhWiR8MgPaC0ToambhJxYqMwrWZ9Iz14XDk7bXMpt4JKXz6vUU8oKhhbNVir2WbwUq7DIxauBjd/MLhCRjjx4TyO1biQCL0NTZ0DbJ4PhJgrJiCKb8nx6YbKT6EHezl8R+zzXnAhvM0WJzp4SZZ3JjICQjq3w2QnTRdHAaKtsGMRRwyoV5yvhaBombJu1Sb+icu6i5Zhm4J07J4g1d97MW05qJpOWd7QrDQsQyJ6X5zGoC5iCthbLhiIvdH4C5+9hJAf1ooH69gqNrgUEYeS414txDaflIKhUJy/49jSYXqrBOCnYev5PiL/0WSn3KRZ3TpgHtAxTDJynWqglzxH5j76HdIIXEROy1fCBzp9vMxwFTN7iU3z2J1v7j1vJQcN8HhpyVMBoLGnJEjFZp6JAYvIFb4VzrFDq/9jkckL4xw99rAK8qOei1h9E2eLGlPyl2HPwHB0uaaE8CmotC0AwH2lFAtFy6oYmkEmutopDLxfpWOWnKt+SecHvLrPD/eUhrL/qXCPcbMOOGovgKPvWHROAFOrvdzQ5h1rnW5dhPbZA3DhlwGNAmyW4DmiSnaKuXesPXOEg= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(102415267)(61425038)(102615245)(601004)(2401047)(13016025)(8121501046)(13018025)(5005006)(10201501046)(3002001)(61426038)(61427038); SRVR:BY2PR0301MB1592; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0301MB1592; X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB1592; 4:mn69PAs6fi2DUpXvz9G+lOjxVEuIpoyuIVx/wavPR8IEN7lGrCcuYSUQcV8vYfxVVeY1vxb5rtEPH1nblICjzSTQCRJRhmQEzJiGMFkRHYGeS8P0SXalz+jV/M3BiExhrMYWRQeNg1FcENubGaGeem3cUG36byqWFtqQaVXjIFTGc9j8U0XA5fusqbvBIca7R0MMkTcBapVY9nsU/VvZsqnq4kPXSNTIqVY62p03Q5RNbcjO49MMCqqjdW0+1totzXdPl5lUd2HjhxA6oxVWyUF4Qiiq+qaAnjhu3ws0m58iSQf2ZGUMN9KborJvvA5Et558fKVdvUixR9HkeDD0gixT76R0KEzKbect0YL3LGbX70exKQMSjjdq1NzDUUv0vu/nWhRlHkbirlvHQS5xxKN6LmHqQYTQF8Y4SapA9OZWg53vFm8knD+B7xRiCBm+WAvGeeZucyyR9w/uc2SLQoaTQtuIh/ZHHMP/NPxfIbfXf2r7FaI62AB9Eyj6qymp X-Forefront-PRVS: 0834BAF534 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY2PR0301MB1592; 23:dnJRzW5wmgd/b+M2jCH4A1yH+iWgLiMrPI4ZMvV?= =?us-ascii?Q?NPvkYCMHmtwPmlSCmVxP+RI3xbJgwbrhKfeLI6zePQFkPdVCJGIVfSq6BpuR?= =?us-ascii?Q?z3y+ZEJM/p1KDMRyJJVnFvIIBTRhyY0HWUZqEtezOJB7GdDYkBLSKP0er/fz?= =?us-ascii?Q?J1Kied/AYmHMpdRvmkCpeQIUJegQMLomz993QensVIs/dDsZUX8GHM0rR9Eg?= =?us-ascii?Q?mhyhG1xbtcw90fr5Ps3gyIXMxXtNVpDkkhyQPUirSb0jqLNpPoo7Vr/tdZII?= =?us-ascii?Q?17M72Jb6O3XX5O0UKfPxdlhT5C7Hg0LK7y2yKXc1poVb6A/mMzSLEDoZ71QT?= =?us-ascii?Q?lfVj7rCW0IRIlVluCz6ETb2DGM4bqK2h+FBR/tHu8wsVTUJWFH4HGvg+ZLuY?= =?us-ascii?Q?AOQYp+pBQ8uB9GCEPTGPhHrp4bXNfJXZMu1ksvRrvSzItTLgCdcb1C5xFDA4?= =?us-ascii?Q?ypBfU4KDhhAaCOvkwCaRKz0Zobb5UlPa4v6GSG9mOjmlSpzYpiTveknpWeOs?= =?us-ascii?Q?ZS0qm/t957Ei/MOOB2W+pItVVsREWleDG6flSzpdY2cXHVKqSH3+YNZl0GLC?= =?us-ascii?Q?DNfckwXO9msF/orn0IN6sZtn3rxn5rqsBUnM6eHbs5jMGA+Hj98K265IYu8C?= =?us-ascii?Q?bTKHmKecL7zhG6jXH37UVsxmCCDcsD4kh/u853Mx6fX6+LFIufOYzifxt3G8?= =?us-ascii?Q?vrsjCJgxW3cLzHrsKdJ5Q1f8scv8GopLuvkEPxCcuzdrAZD4wzJDbEZgMhEY?= =?us-ascii?Q?stSMIkEiH/LqvwLPZIPM0hM/svt3jLwQaJab25SnZ/T0/SDnaZssr/yzxpBO?= =?us-ascii?Q?J1JVVIulG/Q7K4PCYjUQmJzpitL+BjYAOAretTdXZrXVke2tZPRnP3eVSdgO?= =?us-ascii?Q?dCL9td0jJvbQyz8TnI44tob+kCF0gjOaPSNYQps98/MmGd1vc6dWtOlKj4w5?= =?us-ascii?Q?ujp/v1G9teKubPAHb7xepgm7KzWKFS9emktoDAV673oJVKDABcg5e3GoDfY0?= =?us-ascii?Q?1kdenNQvdIUK0pmE4Mz46ai1KZaPvNUVGTfrzZJLTdjTSYndsRE7DPcf/+XK?= =?us-ascii?Q?YcoyWvhRV7t+CFQ6cHLA4q47l99CU/J1+O+bS/F08AXSVR/x8XNsP9g6gFOl?= =?us-ascii?Q?F4m5wbIvx85cKHV7tZjbZ+eCyydJUymI1pIAebG5wa7FMlRqS9qsTBF6aDpk?= =?us-ascii?Q?4D2n68X3jPafXcKzix3RI7fEL7plPgz/SJQ/1NbuT1e+/9g1yJyvSlED4Cup?= =?us-ascii?Q?mYiXRr4SdMUs8OWDqtDFply6pZh8YrJdii/2emWMWGH3o2CGihK1V6R5iRUt?= =?us-ascii?Q?n7P0V/qZgb358XU+PJnx6mpVnmaW+rz07CH4xU6Vp14uYpiDEz2SwlGj7f7T?= =?us-ascii?Q?GuBGFT2vyEuGErjNX5dwv4Icv9/mYya8YsykurkRZWx5GNKaFH3lezfMW6R9?= =?us-ascii?Q?aLI3kEgTHAdKvQJ1E5rAqoLm6KzMrTQyyM7dwuuqVzZZZM5iHnrBAvVyk/7a?= =?us-ascii?Q?P6ngy0iDbjqqNu79evvFS/Npktizm7EVIPPqrI7mMGbH0EjVAwdnLy/zQHAC?= =?us-ascii?Q?HIYt2WhbbxFlBpg3pevVo8bxyBiNPNy/SCbPF9Em2loioNlOWRQT1Cbd6pZd?= =?us-ascii?Q?f2mB+U3mGkbnOsO3SspoVuatxv9fBVC9YTbcBCy9n2dWoCdArQKtyYdBuEZv?= =?us-ascii?Q?/n1tV4/GXEKWXqEQnIVEM052Xkw1jOjXCqWE3uxiKxRo6LCijPOTXJPGJuLP?= =?us-ascii?Q?kYA4ELsVAZHP1XRWeMHPCzkq3hKxdH1ndsTE2SQVVeMQ/iIii4ampoRT9o7e?= =?us-ascii?Q?2P6MJH6tsp/hXAhdCVKC9xSd8tsckc/3V0n3YwUwpM3M9DQCEmvyRn0lWZJL?= =?us-ascii?Q?SK5TilNRgrYSyqV/7rOomuXYwjZpGqEHcJMzjUOksJ1ZPc00VDrghCu42eQx?= =?us-ascii?Q?zlRPCcls86kESFESlqso+EK3rZRl2gaXPdcHyA/3N53/fG9a+eqOztCSn0TL?= =?us-ascii?Q?Vs2l6uYRdgqx+NufSn9dB2Qpi?= X-Microsoft-Exchange-Diagnostics: 1; BY2PR0301MB1592; 5:fUg+BEsvLMqWLKXHsxiQuUn77te4Onr4dCv2W48MHo6U77TkYId2ypiXAm5+aHCy8bedPdQXkTbfEP12wVX+D5E93Ir602Q4G4SQ2a24TIRJKQXEn7bsOYg5AxjuzeEAZSOTKt0ctaRufve/ujsRyQ==; 24:l2wZ7Y8GDTI3DnAu6dHoA1jerr9Bh3rw9Qp6f51R/bEDHejdxUWS0l1vl9AyxHdAhksoHX4G63Wj9GP6T/SEewC2DgLgScPAcwGMjEEXBVI= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jan 2016 03:09:28.7144 (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: BY2PR0301MB1592 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, 27 Jan 2016 03:42:52 -0000 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 ; Dexuan Cui ; K= ylie Liang ; 'freebsd-virtualization@freebsd.org' ; BSD Integration Components for Hyper-V <= bsdic@microsoft.com> 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@01D158F3.2E0CC0E0] 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@01D158F3.2E0CC0E0] 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 Jan 27 09:35: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 D5CBBA6F2D6 for ; Wed, 27 Jan 2016 09:35: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 120FF13B2 for ; Wed, 27 Jan 2016 09:35: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 B19B52B9BE2; Wed, 27 Jan 2016 10:34:59 +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 02061-06; Wed, 27 Jan 2016 10:34:59 +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 488FB2B9BA9; Wed, 27 Jan 2016 10:34:59 +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, 27 Jan 2016 10:34:58 +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, 27 Jan 2016 10:34:58 +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/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pAAABp5MAAD39gwAAxCoKA= Date: Wed, 27 Jan 2016 09:34:58 +0000 Message-ID: <4e85ad234a0b4618ae5862fbcd266e3d@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> In-Reply-To: <7df41cc958ee408297487d4ffbb91903@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 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, 27 Jan 2016 09:35:10 -0000 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@01D158E9.38DFF280] 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@01D158E9.38DFF280] 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 Jan 28 01:37:00 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 A81F3A70B77 for ; Thu, 28 Jan 2016 01:37:00 +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 958CB15EB for ; Thu, 28 Jan 2016 01:37:00 +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 u0S1b0kc032517 for ; Thu, 28 Jan 2016 01:37:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 206699] [Hyper-V]FreeBSD potential NULL pointer dereference in storage bounce buffer Date: Thu, 28 Jan 2016 01:37:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: honzhan@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 28 Jan 2016 01:37:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206699 Hongjiang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-virtualization@Free | |BSD.org, | |kyliel@microsoft.com, | |royger@freebsd.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jan 28 10:18:02 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 2FEACA70790 for ; Thu, 28 Jan 2016 10:18:02 +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 2223E1E08 for ; Thu, 28 Jan 2016 10:18:02 +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 u0SAI1YZ083927 for ; Thu, 28 Jan 2016 10:18:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 206699] [Hyper-V]FreeBSD potential NULL pointer dereference in storage bounce buffer Date: Thu, 28 Jan 2016 10:18:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 28 Jan 2016 10:18:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206699 --- Comment #1 from Roger Pau Monn=C3=83=C2=A9 --- I've already told Wei that creating your own bounce buffer is a bad idea. Instead you should use the BUSDMA API and let it take care of the bouncing = when necessary: https://reviews.freebsd.org/D1964 IIRC something was missing in BUSDMA so that the HyperV storage driver could use it, we should look into adding what's needed and then removing this cus= tom bounce buffering. Please upload the patch to the review system. Roger. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jan 28 10:40:01 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 D65E2A70E5A for ; Thu, 28 Jan 2016 10:40:01 +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 C88511635 for ; Thu, 28 Jan 2016 10:40:01 +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 u0SAe1jF034631 for ; Thu, 28 Jan 2016 10:40:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 206699] [Hyper-V]FreeBSD potential NULL pointer dereference in storage bounce buffer Date: Thu, 28 Jan 2016 10:40:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: honzhan@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 28 Jan 2016 10:40:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206699 --- Comment #2 from Hongjiang --- Yes, the final fix should be using BUSDMA. Temporarily we still used the customized bounce buffer. The code review for this patch: https://reviews.freebsd.org/D5097 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jan 28 18:55:42 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 AF46BA70CBC for ; Thu, 28 Jan 2016 18:55:42 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (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 7378F174C for ; Thu, 28 Jan 2016 18:55:41 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.local (localhost [192.168.5.2]) by webmail.dweimer.net (8.15.2/8.15.2) with ESMTPS id u0SItXrt003937 (version=TLSv1.2 cipher=DHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO); Thu, 28 Jan 2016 12:55:33 -0600 (CST) (envelope-from dweimer@dweimer.net) Received: (from www@localhost) by webmail.dweimer.local (8.15.2/8.15.2/Submit) id u0SItWYb003936; Thu, 28 Jan 2016 12:55:32 -0600 (CST) (envelope-from dweimer@dweimer.net) X-Authentication-Warning: webmail.dweimer.local: www set sender to dweimer@dweimer.net using -f To: Sergey Manucharian Subject: Re: bhyve with Linux guest, how to safely handle updates? X-PHP-Script: www.dweimer.net/webmail/index.php for 71.86.41.122, 192.168.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 28 Jan 2016 12:55:32 -0600 From: dweimer Cc: freebsd-virtualization@freebsd.org Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net In-Reply-To: <20160127021348.GE1799@dendrobates.araler.com> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> <20160127021348.GE1799@dendrobates.araler.com> Message-ID: <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.1.4 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, 28 Jan 2016 18:55:42 -0000 On 2016-01-26 8:13 pm, Sergey Manucharian wrote: > Excerpts from dweimer's message from Tue 26-Jan-16 19:07: >> >> Is there anything that normally needs to be done after a Linux kernel >> update to refresh the grub2-bhyve setup? > > The kernel update should not have any effect since grub-bhyve uses the > virtual disk mapping file, which should point to your linux drive. > > I'm using the following command: > > $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian > > where "device.map" contains the following: > > (hd0) /dev/zvol/zroot/linuxdisk1 > (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso > > "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in > my case it's a ZFS volume). > > How do you use that VM in VBox? If it's a .vdi file, bhyve will not be > able to recognize it. You should use a raw HDD image file. To make it > compatible with VBox you can create a .vmdk file pointing to that raw > image. > > -- > Sergey I am back to testing again, copied my ZFS Boot Environment over to a VMware virtual machine, renamed it and changed IPs, removed the virtual box stuff, and enabled bhyve. I did some searching and found out that I was using https://github.com/churchers/vm-bhyve to manage the bhyve virtual machines starting and stopping. Sticking with zvol for disk backing, I know its less portable. I have been able to install a couple of debian virtual machines and play around with them. So far I have been unable to duplicate the issue I had before. My current issue which maybe related to running inside a VMware virtual machine. Is the Linux hwclock and system clock sync issues. If I power off the vm and reboot it it believes that the disk was modified in the future and appears to hang. Its actually doing a fsck I just don't see status if you wait long enough it finally does come up. Has anyone else ran into this issue? I have actually ran the hwclock -systohc --utc prior to powering down and still had the issue. Tried changing the hwclock to system time by excluding the --utc from the command no change. Incidentally whether I use the --utc or not the hwclock --show always displays the local time. I couldn't seem to find any documentation on bhyve whether or not I should tell the guests that the hwclock is in utc or local time. -- Thanks, Dean E. Weimer http://www.dweimer.net/ From owner-freebsd-virtualization@freebsd.org Thu Jan 28 19:13:37 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 89180A712ED for ; Thu, 28 Jan 2016 19:13:37 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 22EC8113C for ; Thu, 28 Jan 2016 19:13:37 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id r129so38994700wmr.0 for ; Thu, 28 Jan 2016 11:13:37 -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; bh=hFxpIS+6xk/rem9k5gaLpUcMSluf0zVi2ePNYeTZEgU=; b=HSFP/yj6Hp899M7wLcD4S+bv/x6CSBDlwSNTJahLSbzFvaDdhWKjXHag71oBg76HPx KcTVVuFZRXL1uNKzlG1/0fRTrtlUpcSFciP+8vvVjvGOjreCxztnFPXj/6xjRThR8/24 ei+/MumwTTsIzEwX6J7VnrVPhWu3pFTQicgt3jzY3VtPFToRsRyUuoPdZo70irIl3ek7 9tiwVO2lyn9LVjVulUqLSV8g7LeTA4XopbEzXwMVaCWgruYjzTeEHMvOJa+IWRswGIST nIhAaYBEJ4aSlMqEG/hpWYd3k9Nj0/qwadRm2SmOpS+wUw+QrjlVBx1O5rOJmVujiCv6 ivyg== 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; bh=hFxpIS+6xk/rem9k5gaLpUcMSluf0zVi2ePNYeTZEgU=; b=hPeu3+26tT7FOmCro3BSRI+7QUVzZpP66jSH2qu/KP4zEZtdkxz5zHkmgAS6QVFt+a X/oQeTdBeB9CbQvEm7+13e9cuOh5kgQI4DdQJXVCb9tcHQZSv7cN4+UbxQrh5bzd4+Lg jbU/Hf1NCbiytfG0WqeegM/MGdh/fphkdhgyL2luwwO+LDL8T4/K8FgzwoXeLt3NdTyw QupK14zQJvKP/dKlSM/xfeUpok88dhXs5vaaS5RIQGYi04QW94pVtTb1mzAMDb6XuIBm at5Wg4f+G4c7HX5uhupOoAjrS+DwJ/hUEaCaWCXcgK6cN7K9UrvAX6nqchWJEoFatVem RBtA== X-Gm-Message-State: AG10YORKJt8eM78c17vPdyeIGGco8h8034k+GhfO1VY5rZuXb9HrsLZSHCEjJhq0gfXcXasGQM9NJCrBZz1dzg== MIME-Version: 1.0 X-Received: by 10.28.35.6 with SMTP id j6mr5045378wmj.80.1454008415612; Thu, 28 Jan 2016 11:13:35 -0800 (PST) Received: by 10.27.81.84 with HTTP; Thu, 28 Jan 2016 11:13:35 -0800 (PST) In-Reply-To: <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> <20160127021348.GE1799@dendrobates.araler.com> <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> Date: Thu, 28 Jan 2016 11:13:35 -0800 Message-ID: Subject: Re: bhyve with Linux guest, how to safely handle updates? From: Neel Natu To: dweimer@dweimer.net Cc: Sergey Manucharian , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 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, 28 Jan 2016 19:13:37 -0000 Hi Dean, On Thu, Jan 28, 2016 at 10:55 AM, dweimer wrote: > On 2016-01-26 8:13 pm, Sergey Manucharian wrote: >> >> Excerpts from dweimer's message from Tue 26-Jan-16 19:07: >>> >>> >>> Is there anything that normally needs to be done after a Linux kernel >>> update to refresh the grub2-bhyve setup? >> >> >> The kernel update should not have any effect since grub-bhyve uses the >> virtual disk mapping file, which should point to your linux drive. >> >> I'm using the following command: >> >> $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian >> >> where "device.map" contains the following: >> >> (hd0) /dev/zvol/zroot/linuxdisk1 >> (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso >> >> "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in >> my case it's a ZFS volume). >> >> How do you use that VM in VBox? If it's a .vdi file, bhyve will not be >> able to recognize it. You should use a raw HDD image file. To make it >> compatible with VBox you can create a .vmdk file pointing to that raw >> image. >> >> -- >> Sergey > > > I am back to testing again, copied my ZFS Boot Environment over to a VMware > virtual machine, renamed it and changed IPs, removed the virtual box stuff, > and enabled bhyve. > > I did some searching and found out that I was using > https://github.com/churchers/vm-bhyve to manage the bhyve virtual machines > starting and stopping. Sticking with zvol for disk backing, I know its less > portable. > > I have been able to install a couple of debian virtual machines and play > around with them. So far I have been unable to duplicate the issue I had > before. My current issue which maybe related to running inside a VMware > virtual machine. Is the Linux hwclock and system clock sync issues. If I > power off the vm and reboot it it believes that the disk was modified in the > future and appears to hang. Its actually doing a fsck I just don't see > status if you wait long enough it finally does come up. > > Has anyone else ran into this issue? I have actually ran the hwclock > -systohc --utc prior to powering down and still had the issue. Tried > changing the hwclock to system time by excluding the --utc from the command > no change. Incidentally whether I use the --utc or not the hwclock --show > always displays the local time. I couldn't seem to find any documentation on > bhyve whether or not I should tell the guests that the hwclock is in utc or > local time. > The "-u" option of bhyve(8) will configure the RTC to present UTC time to the guest (default is localtime). best Neel > -- > Thanks, > Dean E. Weimer > http://www.dweimer.net/ > _______________________________________________ > 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 Fri Jan 29 05:05: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 09820A70C04 for ; Fri, 29 Jan 2016 05:05:49 +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 EE42217EA for ; Fri, 29 Jan 2016 05:05:48 +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 u0T55mvk077738 for ; Fri, 29 Jan 2016 05:05:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 206699] [Hyper-V]FreeBSD potential NULL pointer dereference in storage bounce buffer Date: Fri, 29 Jan 2016 05:05:48 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 29 Jan 2016 05:05:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206699 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Jan 29 05:24:15 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 96CA8A71489 for ; Fri, 29 Jan 2016 05:24:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C44E11AD for ; Fri, 29 Jan 2016 05:24:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-229-231.lns20.per1.internode.on.net [121.45.229.231]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u0T5MliL008151 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 28 Jan 2016 21:22:50 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: bhyve with Linux guest, how to safely handle updates? To: Neel Natu , dweimer@dweimer.net References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> <20160127021348.GE1799@dendrobates.araler.com> <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> Cc: "freebsd-virtualization@freebsd.org" From: Julian Elischer Message-ID: <56AAF721.4080009@freebsd.org> Date: Fri, 29 Jan 2016 13:22:41 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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, 29 Jan 2016 05:24:15 -0000 On 29/01/2016 3:13 AM, Neel Natu wrote: > Hi Dean, > > On Thu, Jan 28, 2016 at 10:55 AM, dweimer wrote: >> On 2016-01-26 8:13 pm, Sergey Manucharian wrote: >>> Excerpts from dweimer's message from Tue 26-Jan-16 19:07: >>>> >>>> Is there anything that normally needs to be done after a Linux kernel >>>> update to refresh the grub2-bhyve setup? >>> >>> The kernel update should not have any effect since grub-bhyve uses the >>> virtual disk mapping file, which should point to your linux drive. >>> >>> I'm using the following command: >>> >>> $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian >>> >>> where "device.map" contains the following: >>> >>> (hd0) /dev/zvol/zroot/linuxdisk1 >>> (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso >>> >>> "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in >>> my case it's a ZFS volume). >>> >>> How do you use that VM in VBox? If it's a .vdi file, bhyve will not be >>> able to recognize it. You should use a raw HDD image file. To make it >>> compatible with VBox you can create a .vmdk file pointing to that raw >>> image. >>> >>> -- >>> Sergey >> >> I am back to testing again, copied my ZFS Boot Environment over to a VMware >> virtual machine, renamed it and changed IPs, removed the virtual box stuff, >> and enabled bhyve. >> >> I did some searching and found out that I was using >> https://github.com/churchers/vm-bhyve to manage the bhyve virtual machines >> starting and stopping. Sticking with zvol for disk backing, I know its less >> portable. >> >> I have been able to install a couple of debian virtual machines and play >> around with them. So far I have been unable to duplicate the issue I had >> before. My current issue which maybe related to running inside a VMware >> virtual machine. Is the Linux hwclock and system clock sync issues. If I >> power off the vm and reboot it it believes that the disk was modified in the >> future and appears to hang. Its actually doing a fsck I just don't see >> status if you wait long enough it finally does come up. >> >> Has anyone else ran into this issue? I have actually ran the hwclock >> -systohc --utc prior to powering down and still had the issue. Tried >> changing the hwclock to system time by excluding the --utc from the command >> no change. Incidentally whether I use the --utc or not the hwclock --show >> always displays the local time. I couldn't seem to find any documentation on >> bhyve whether or not I should tell the guests that the hwclock is in utc or >> local time. >> > The "-u" option of bhyve(8) will configure the RTC to present UTC time > to the guest (default is localtime). wouldn't it be best if the -u option had an argument to give the offsett? I had this problem with two windows hosts that were supposed to be in different timezones. I worked around it but... > > best > Neel > >> -- >> Thanks, >> Dean E. Weimer >> http://www.dweimer.net/ >> _______________________________________________ >> 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" > _______________________________________________ > 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 Fri Jan 29 05:53: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 31000A71E79 for ; Fri, 29 Jan 2016 05:53:28 +0000 (UTC) (envelope-from neelnatu@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 E351C1CB9; Fri, 29 Jan 2016 05:53:27 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id p63so53729783wmp.1; Thu, 28 Jan 2016 21:53:27 -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; bh=H2ApXLU4VaGaBEznXUvl/aMa7CSPLegNCmx7SvgHoS8=; b=skPAFtodUl6BGNAlxzwkgScNVBtKge7znxeK0VBp/c18sBPiMeTlhC4VHhKfIXcLSV ZeYUEwDzlMTVeE3Ue/vL9BXnAJQMe+8KBP3zlm6BsrSjQ8zdx29gC8QW+JVq0yvClpzs MYYccK5y+zVGlboS/Wjnx9j3DhS4i1EaQM719fZhyq5qv72WRZjoMjynpUcB8PemieRe WibHXdbvqm1ySTMaU1UDLGvFn2au2Ie15PWO/ReAuFt6kr9FGVGKkIjwnupIXqKx59n5 VguJ+scpCOgYOvEqJCT/p+1e7Hg14bGplWezZYw7kJnhr4jgFDz1WXlT2IDWjfGCjtKQ n++Q== 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; bh=H2ApXLU4VaGaBEznXUvl/aMa7CSPLegNCmx7SvgHoS8=; b=dLfVa5VfAVg4IvlmQE9mw/g+ZTnlf6v7FOirkwF70bD6IrMyoGI45gNg5ss9+Tgezh wsu57lS5vPzJkjWfx60Gxg+//chPRp6Ar8RlnPO7mrmtIlADCOmqBo8mVDgBv+DtVj+1 5x8VWF/jnj+yvF58/iOiF+rgwkWEz3QWFAcW41qcoQBUODN1MTspzFLh1yThBz7R4p1y ZImwaifF0sgDHW02RdBKgzJUQ9sxvL8bz+DOEfAnpSU1HaohpBmTF/7U++dfaVOp6lJ7 XTCIqE8NvbFo8ge9bho+sZjLNYRrpIC/l2XBKQlL2pnQBfaTE+RYrBb28ZZtu4yQ8SR6 mkqA== X-Gm-Message-State: AG10YOS4t17hY2Yu4lut6R2YwHPhg2zA4JEutJlPsWvD4ZiSoFDMr2msiXWAxghvCmYlFtstwWsIdy8zJ3MTbA== MIME-Version: 1.0 X-Received: by 10.28.57.214 with SMTP id g205mr6556893wma.20.1454046806312; Thu, 28 Jan 2016 21:53:26 -0800 (PST) Received: by 10.27.81.84 with HTTP; Thu, 28 Jan 2016 21:53:26 -0800 (PST) In-Reply-To: <56AAF721.4080009@freebsd.org> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> <20160127021348.GE1799@dendrobates.araler.com> <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> <56AAF721.4080009@freebsd.org> Date: Thu, 28 Jan 2016 21:53:26 -0800 Message-ID: Subject: Re: bhyve with Linux guest, how to safely handle updates? From: Neel Natu To: Julian Elischer Cc: dweimer@dweimer.net, "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 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, 29 Jan 2016 05:53:28 -0000 Hi Julian, On Thu, Jan 28, 2016 at 9:22 PM, Julian Elischer wrote: > On 29/01/2016 3:13 AM, Neel Natu wrote: >> >> Hi Dean, >> >> On Thu, Jan 28, 2016 at 10:55 AM, dweimer wrote: >>> >>> On 2016-01-26 8:13 pm, Sergey Manucharian wrote: >>>> >>>> Excerpts from dweimer's message from Tue 26-Jan-16 19:07: >>>>> >>>>> >>>>> Is there anything that normally needs to be done after a Linux kernel >>>>> update to refresh the grub2-bhyve setup? >>>> >>>> >>>> The kernel update should not have any effect since grub-bhyve uses the >>>> virtual disk mapping file, which should point to your linux drive. >>>> >>>> I'm using the following command: >>>> >>>> $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian >>>> >>>> where "device.map" contains the following: >>>> >>>> (hd0) /dev/zvol/zroot/linuxdisk1 >>>> (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso >>>> >>>> "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in >>>> my case it's a ZFS volume). >>>> >>>> How do you use that VM in VBox? If it's a .vdi file, bhyve will not be >>>> able to recognize it. You should use a raw HDD image file. To make it >>>> compatible with VBox you can create a .vmdk file pointing to that raw >>>> image. >>>> >>>> -- >>>> Sergey >>> >>> >>> I am back to testing again, copied my ZFS Boot Environment over to a >>> VMware >>> virtual machine, renamed it and changed IPs, removed the virtual box >>> stuff, >>> and enabled bhyve. >>> >>> I did some searching and found out that I was using >>> https://github.com/churchers/vm-bhyve to manage the bhyve virtual >>> machines >>> starting and stopping. Sticking with zvol for disk backing, I know its >>> less >>> portable. >>> >>> I have been able to install a couple of debian virtual machines and play >>> around with them. So far I have been unable to duplicate the issue I had >>> before. My current issue which maybe related to running inside a VMware >>> virtual machine. Is the Linux hwclock and system clock sync issues. If I >>> power off the vm and reboot it it believes that the disk was modified in >>> the >>> future and appears to hang. Its actually doing a fsck I just don't see >>> status if you wait long enough it finally does come up. >>> >>> Has anyone else ran into this issue? I have actually ran the hwclock >>> -systohc --utc prior to powering down and still had the issue. Tried >>> changing the hwclock to system time by excluding the --utc from the >>> command >>> no change. Incidentally whether I use the --utc or not the hwclock --show >>> always displays the local time. I couldn't seem to find any documentation >>> on >>> bhyve whether or not I should tell the guests that the hwclock is in utc >>> or >>> local time. >>> >> The "-u" option of bhyve(8) will configure the RTC to present UTC time >> to the guest (default is localtime). > > wouldn't it be best if the -u option had an argument to give the offsett? > I had this problem with two windows hosts that were supposed to be in > different timezones. > I worked around it but... > Yes, it would be more flexible. FWIW the underlying vmmapi call and the ioctl don't need to change (i.e. the changes would be limited to bhyve(9)). best Neel > >> >> best >> Neel >> >>> -- >>> Thanks, >>> Dean E. Weimer >>> http://www.dweimer.net/ >>> _______________________________________________ >>> 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" >> >> _______________________________________________ >> 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 Fri Jan 29 06:51:45 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 3BFDAA72DB9 for ; Fri, 29 Jan 2016 06:51:45 +0000 (UTC) (envelope-from doublef.mobile@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 C69E213DA for ; Fri, 29 Jan 2016 06:51:44 +0000 (UTC) (envelope-from doublef.mobile@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id p63so54777685wmp.1 for ; Thu, 28 Jan 2016 22:51:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5+3pGAIh14EuCcLFwxC+e8IBjvbwMRs18gZgwgowqx8=; b=hiHq8JIUfbOvVnadyFkjh4CqKBgrIzhuwqStHT0XqhcBfHd2W5e6dcs4UBxsOJEaix yoToU77sOZaJlMLmVPm7wcyLitMW5CVpr9Vdt18B+bVYS0/SEf8CIfVuyvVmQcaN4797 UZIje9leO7vAeDXhgWCdTmWKwynUZsWY4eGwA+OI1fCXplOSd3rwgp2cYBgsKX/zxqX3 +h4BcgmzXqyA4TwZeAcpWbAHPa8qorn8ePbYvggYTjwBfjYSOmPH64J0lt6VyRWkIvzM KuFaxAqwSkINDLPKOiSqs8gudizWvw33+QQlNLygfoQUvKgnVGMxYE8+TVwg6lrRlUC7 dfpA== 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:from:date :message-id:subject:to:cc:content-type; bh=5+3pGAIh14EuCcLFwxC+e8IBjvbwMRs18gZgwgowqx8=; b=ONZIMOipccGh2pTS9adVWJ1NGfkrNkZ0GzW13CvyVFqtpTzu9VXi4VUjOUx7dcIj9J uB0puiVEyUtlwT6bEtI2yd9mMlNWzlQLS1Fef2cIXFJh1wVyKvs1KlvmFl1M8SPR/MC/ x+LbJa8SIg/fsxGowwsQzJAQ5lHkAcC/sxGjACXknHIxZCdeiB1bgaKqsVBmmlFp9evS 3+iga0nW94wI0c6Htp+uKyDHv000FrnsVbf9ujiRBZuqm2FBwxGs6ynDOL5QgH4jdVZR GFzi23pjM4C+O6pAnevZ1jDl0qcYF2/hlILGB/prehRXfwG7vKHzUOWvWs/xkQw0xeS9 BYrA== X-Gm-Message-State: AG10YOTVvm+g0442ArqGpnyBApMGXupbc4+Dnq3CmQzsK9dspiZe1aHyAqIRgi0DEnjWldvY9YtF96hdCxB6JA== X-Received: by 10.28.187.67 with SMTP id l64mr6730726wmf.39.1454050302971; Thu, 28 Jan 2016 22:51:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.93.6 with HTTP; Thu, 28 Jan 2016 22:51:23 -0800 (PST) In-Reply-To: References: From: Sergey Zakharchenko Date: Fri, 29 Jan 2016 09:51:23 +0300 Message-ID: Subject: Re: Docker on FreeBSD To: Ryan Holt Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 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, 29 Jan 2016 06:51:45 -0000 Hello Ryan, 2016-01-21 23:15 GMT+03:00 Ryan Holt : > Finished building a FreeBSD Head system today with the intent of using Docker. My condolences. > Is there a workaround to getting DNS inside of a container aside from manually building each image? The basic reason is no volume support in FreeBSD Docker port. The workaround is one of: - hacking the Docker port yourself, https://github.com/kvasdopil/docker/ is *a bit* incomplete and stale; - building a custom complicated and evil system around Docker that works around its design deficiencies and FreeBSD port incompleteness; - using Docker for building images only, and running them using vanilla jails + a custom complicated and evil system; - using jetpack instead and exposing yourself to a whole different set of problems ;) It's doable, but it is not for the faint of heart. I could share some improvements for the Docker port but kvasdopil@ seems too reluctant to make even the simplest changes (e.g. working around https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204897 :) ), #freebsd-docker is also rather apathetic and there's no way I'm going to hack on Go (yuck) alone and then just give it away (I'm in the 'custom complicated and evil system' camp). Best regards, -- DoubleF From owner-freebsd-virtualization@freebsd.org Fri Jan 29 07:45: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 5F02CA71D4F for ; Fri, 29 Jan 2016 07:45:30 +0000 (UTC) (envelope-from mveety@gmail.com) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (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 17D8A1A56 for ; Fri, 29 Jan 2016 07:45:30 +0000 (UTC) (envelope-from mveety@gmail.com) Received: by mail-qg0-x231.google.com with SMTP id e32so59720503qgf.3 for ; Thu, 28 Jan 2016 23:45:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:subject:in-reply-to:message-id:references:user-agent :mime-version:content-type; bh=U+a5E8YJCoLUc+nXfZbrth8dCF4EdsFRCVLC04R/i3w=; b=kLwvTdxuPgsxr40w4UTPg8AZcKqVdKNGft6RSg6yjWyW8Au4mZEcl0QNGSpUgGi9pU 2UbDn/Wa00WAeACDBy+NR+vXCAy3RZZ2c5+bBk5N7tv7kVP8qaSE5/a4NuS3mi8NhfEi RmBMTFpC355T0bIY/kEm0rmrwcTUYNh9dPM1EM+ow0GQ9rXiTxQHLieUgnsTCgUc1Dbn JiN4yPpeVrZnBXFyGq2zwFVNJFIGmgKnIoIR1mPFcPdNNGF+Xyj4xGJbpGDLDDSeWeVa xJoHgL6M6ZeQsveZY2fX28B5MW4XDjimwsjJM2THqIPc1q9bg0XsP9W773ng2dOg5gLr Sdow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:subject:in-reply-to:message-id :references:user-agent:mime-version:content-type; bh=U+a5E8YJCoLUc+nXfZbrth8dCF4EdsFRCVLC04R/i3w=; b=inPFYK5C0uKg9jxoHY5F+G49fyMe/pOxebbJA3Ocv/2B7B3D63s00zMd0D7ZL9mQpy 1H+Wqc3vef8tYwxRbSKlMehuHUPPsBlTb6blDP0yjHlPYmX1Uw+IzJ+uMjyU4mqJONdw FM11ru0GHLaFq84mju9B04FYIPzX+jmVtN4ZTkwr4vBWP/a+yXls2IqBEXrVxCSKYfbH u3zTcOBxBxSLP8qxjyR/fsr31H721MhuhBYo/y9oV6inbTSYjo4f8Kbztzg7rANX//f7 EWtDmPoDrwqmLWO7xcxDu9YyUBlueY3VB713v23rYfudoBOE5qJFRPo4RhKTl8a0nbeB 7bbw== X-Gm-Message-State: AG10YOQKhB6MA3ZWGoq5S8SErlB7g3ODc/qT+yI2sBKdFQAOtPHbVxCXXhGh85TCS5dtlw== X-Received: by 10.140.249.68 with SMTP id u65mr9326154qhc.53.1454053529156; Thu, 28 Jan 2016 23:45:29 -0800 (PST) Received: from localhost ([50.32.141.60]) by smtp.gmail.com with ESMTPSA id a89sm3330236qkj.21.2016.01.28.23.45.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jan 2016 23:45:28 -0800 (PST) From: Matthew Veety X-Google-Original-From: Matthew Veety Received: from localhost (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id 8c696f3d for ; Fri, 29 Jan 2016 02:45:24 -0500 (EST) Date: Fri, 29 Jan 2016 02:45:24 -0500 (EST) To: freebsd-virtualization@freebsd.org Subject: Re: Docker on FreeBSD In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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, 29 Jan 2016 07:45:30 -0000 On Fri, 29 Jan 2016, Sergey Zakharchenko wrote: > Hello Ryan, > > 2016-01-21 23:15 GMT+03:00 Ryan Holt : >> Finished building a FreeBSD Head system today with the intent of using Docker. > > My condolences. > >> Is there a workaround to getting DNS inside of a container aside from manually building each image? > > The basic reason is no volume support in FreeBSD Docker port. The > workaround is one of: > > - hacking the Docker port yourself, > https://github.com/kvasdopil/docker/ is *a bit* incomplete and stale; > - building a custom complicated and evil system around Docker that > works around its design deficiencies and FreeBSD port incompleteness; > - using Docker for building images only, and running them using > vanilla jails + a custom complicated and evil system; > - using jetpack instead and exposing yourself to a whole different set > of problems ;) > > It's doable, but it is not for the faint of heart. I could share some > improvements for the Docker port but kvasdopil@ seems too reluctant to > make even the simplest changes (e.g. working around > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204897 :) ), > #freebsd-docker is also rather apathetic and there's no way I'm going > to hack on Go (yuck) alone and then just give it away (I'm in the > 'custom complicated and evil system' camp). > > Best regards, > > -- > DoubleF What needs to be done with docker to get it running better on FreeBSD? Is there any place with a list of bugs or a todo list? I would be interested in getting it working better. -- Veety From owner-freebsd-virtualization@freebsd.org Fri Jan 29 11:48: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 E7B73A72302 for ; Fri, 29 Jan 2016 11:48:28 +0000 (UTC) (envelope-from doublef.mobile@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 84A251E97 for ; Fri, 29 Jan 2016 11:48:28 +0000 (UTC) (envelope-from doublef.mobile@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id 128so49412448wmz.1 for ; Fri, 29 Jan 2016 03:48:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=ZHRM2AbhvL304XgNXkHds4g5M4/TUb3DpaltFkKwJH4=; b=YXP9xTZ7/9CX8mrMeOsirZ3Q53MT3YL0/KB7xJB5BKhA49K0DkTOkVI0CMiWZ5tGFC DM8/7W9rq4caTUuyKXfEMi7USBspFdd2vQvYSXykhbiuGRkmLKp1vp+xSdpC/J4fx5cR wYmBdeohKAc9pgkj6iJoClYCOCZgmbMR5F9739P0kVjORNeM1UyYiK6YQGpvfHEs8hZH fIBwZB+YO7CKLs1DnKfn6eORMUwaN4PWS1S72a2fxHA6SDB/28ipQdQoTTe6cXGZTeFR BtB/ZkRE/TEkrbc87m154BtwL29LCV4cMHOPBSzuBowSwslpVJrHKzz9deIqn0fA59xV H5JQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=ZHRM2AbhvL304XgNXkHds4g5M4/TUb3DpaltFkKwJH4=; b=IxAyfMqnfnpU1BF/Ye9bHEIjOxYDt+68o1aBb+WqxIAWxLUcXZuKajQfcXTPYjbmAi S5wZ8NkPJ/MdDgcfwmymEXE3qxA7rjdofXFbzzS49I87DxLq+5CBJ/nMtJ7aFCFaSPzW 8uGYA1odqME/LAJR3iS2p+HnWi+VF8L3MfK8KZox4kR46zKIudI9sz5/vY+LJU5pCumo 1eBLNa9TaOHSX18uZhnXEs0NonH2TuKlkxDZTOkAaVJqSshi9UKrRsWKZza9KwmbJyto l/+YblmT3PdZLzPSHG2Me/vOpAubTw1bXyy4zyVvWys1v77djUDdL51Rm8yGUpLrDQws EGpw== X-Gm-Message-State: AG10YOQRj7sdJMMKuVKc6rNhx9Afe9oB7jj7fIOkIfip+E/OZa8qyLPJzM5qJVsYCyzUO67qfjSVQuXhmj/sNg== X-Received: by 10.194.203.99 with SMTP id kp3mr8295572wjc.3.1454068107096; Fri, 29 Jan 2016 03:48:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.93.6 with HTTP; Fri, 29 Jan 2016 03:48:07 -0800 (PST) From: Sergey Zakharchenko Date: Fri, 29 Jan 2016 14:48:07 +0300 Message-ID: Subject: ATTN Docker, Jetpack users (was: Re: Docker on FreeBSD) To: Matthew Veety , Ryan Holt Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 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, 29 Jan 2016 11:48:29 -0000 Hi Matthew, > What needs to be done with docker to get it running better on FreeBSD? Is > there any place with a list of bugs or a todo list? I would be interested in > getting it working better. It's more like a list of things which work, many things that don't, and a sea of things which 'sorta' work. Mainly because of this one entry in https://github.com/kvasdopil/docker/blob/freebsd-compat/FREEBSD-PORTING.md : >>> volumes - not working It's a small benign-looking entry. Not in bold, not highlighted, hidden deeply from those unaware. Image building doesn't *really* work because of that, because the resolver configuration and hosts file are, like, 'single-file mounts'. So when you do a pkg install in the image-building container, you get no address record. Jumping through some hoops, including custom-generated Dockerfiles (what a crappy file format BTW), can still get things done. You're left with jumping more hoops with adding the volumes when you instantiate and start a container. Problems indicated by kvasdopil: Docker is too much of a moving target and his patches no longer apply to the latest, they change everything all the time (e.g. network config revamping, etc.). That is a valid concern. Should I contribute to the whole thing? Too few people seem to care. My questions are: Is anyone here interested in a patch which improves container-building performance (I'm patching Docker but a similar approach should benefit Jetpack)? Now, is anyone interested and *competent enough* in fixing the volume problem? Oh, and there's the whole port forwarding thing... >>> port forward - ok OK would be native support of a FreeBSD firewall, e.g. PF. Please don't tell me you like the userland proxy. That's partial support, and the container access logs become useless... P.S. Ryan wrote: > I've since moved to Gentoo, ZFS for Linux, and Docker. Works really well. That's exactly the attitude the current state of things provoke. Not blaming you in any way. Docker in general sounds like 'run it anywhere and pray it's the latest 64-bit Ubuntu' :) Best regards, -- DoubleF From owner-freebsd-virtualization@freebsd.org Fri Jan 29 11:52: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 2DCC5A72465 for ; Fri, 29 Jan 2016 11:52:30 +0000 (UTC) (envelope-from ryan@ryanholt.net) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0144.outbound.protection.outlook.com [157.56.111.144]) (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 CC2B510EA for ; Fri, 29 Jan 2016 11:52:29 +0000 (UTC) (envelope-from ryan@ryanholt.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=holt.onmicrosoft.com; s=selector1-ryanholt-net; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GP/eKTi8DB77C4pm4AX1Iu+vLSQDQIdoDwTMV0wN2SU=; b=FLiX50NeoKfbY5n6D2TwYm7xNAxpzF4Bhr2/g/HqgTZHq2QJqC+OfUfZkeHn81MUf1WOP/6Wk2hDmahK7r+NkGcxLZuOW6WNzFMBVgrE1XufghZ+OpoqTdYbPGyW891fXpDMBDMYD8fnD+C2uBCcDcn0pPg8KNQpNvSEz3WNB78= Received: from BLUPR08MB1170.namprd08.prod.outlook.com (10.163.86.151) by BLUPR08MB1171.namprd08.prod.outlook.com (10.163.86.152) with Microsoft SMTP Server (TLS) id 15.1.396.15; Fri, 29 Jan 2016 11:19:31 +0000 Received: from BLUPR08MB1170.namprd08.prod.outlook.com ([10.163.86.151]) by BLUPR08MB1170.namprd08.prod.outlook.com ([10.163.86.151]) with mapi id 15.01.0396.017; Fri, 29 Jan 2016 11:19:31 +0000 From: Ryan Holt To: Sergey Zakharchenko CC: "freebsd-virtualization@freebsd.org" Subject: RE: Docker on FreeBSD Thread-Topic: Docker on FreeBSD Thread-Index: AdFUiDsH2GfXLkQjSNyYQAbJADTuVwF2TxCAAAldXy4= Date: Fri, 29 Jan 2016 11:19:31 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=ryanholt.net; x-originating-ip: [2600:1003:b002:8b:a5cf:c770:3d10:f638] x-microsoft-exchange-diagnostics: 1; BLUPR08MB1171; 5:RAuuAFY5J389sgH0z2mFSUIX2830+GJtlu5HcC51Kjrc0Fj6MFHgLLvGypJK8bieAQocoKMiiaQc8/QiRlEl+qAQ7hze+sQgTE6PGieCSmMWJ4We0SNMUnmLsB50E763Lvb7mo1CQX5l1XUOcvSz+A==; 24:C2RLOCMymh+loZF9mLlkN1cL4KN/bHxB/wTo2ZPLY6xWDrBds/jcLbNV8Mp+vd/WTJ71oYKiCAiC3oEor6FmD5L8plyh3fQxNY5XelmLizA= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR08MB1171; x-ms-office365-filtering-correlation-id: ab5c5be8-0a2a-4da8-92ce-08d3289e0f7b x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:BLUPR08MB1171; BCL:0; PCL:0; RULEID:; SRVR:BLUPR08MB1171; x-forefront-prvs: 083691450C x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(3905003)(377424004)(51914003)(377454003)(3470700001)(3480700001)(50986999)(76176999)(19580405001)(19580395003)(92566002)(3280700002)(54356999)(2906002)(99286002)(19625215002)(76576001)(19617315012)(106356001)(4326007)(10400500002)(5003600100002)(77096005)(102836003)(6116002)(15975445007)(74316001)(87936001)(3660700001)(189998001)(2900100001)(5002640100001)(2950100001)(16236675004)(586003)(33656002)(5008740100001)(1220700001)(11100500001)(5001960100002)(110136002)(122556002)(1096002)(5004730100002)(86362001)(40100003)(3826002)(19627235001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR08MB1171; H:BLUPR08MB1170.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: ryanholt.net X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2016 11:19:31.6103 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: c11cb874-8bea-4982-9978-8e6b35a3679b X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR08MB1171 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, 29 Jan 2016 11:52:30 -0000 Hi Sergey, Thanks for the response. I've since moved to Gentoo, ZFS for Linux, and Do= cker. Works really well. Sent from Outlook Mail for= Windows 10 phone From: Sergey Zakharchenko Sent: Friday, January 29, 2016 1:51 AM To: Ryan Holt Cc: freebsd-virtualization@freebsd.org Subject: Re: Docker on FreeBSD Hello Ryan, 2016-01-21 23:15 GMT+03:00 Ryan Holt : > Finished building a FreeBSD Head system today with the intent of using Do= cker. My condolences. > Is there a workaround to getting DNS inside of a container aside from man= ually building each image? The basic reason is no volume support in FreeBSD Docker port. The workaround is one of: - hacking the Docker port yourself, https://github.com/kvasdopil/docker/ is *a bit* incomplete and stale; - building a custom complicated and evil system around Docker that works around its design deficiencies and FreeBSD port incompleteness; - using Docker for building images only, and running them using vanilla jails + a custom complicated and evil system; - using jetpack instead and exposing yourself to a whole different set of problems ;) It's doable, but it is not for the faint of heart. I could share some improvements for the Docker port but kvasdopil@ seems too reluctant to make even the simplest changes (e.g. working around https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204897 :) ), #freebsd-docker is also rather apathetic and there's no way I'm going to hack on Go (yuck) alone and then just give it away (I'm in the 'custom complicated and evil system' camp). Best regards, -- DoubleF From owner-freebsd-virtualization@freebsd.org Fri Jan 29 03:40:37 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 309C6A71E56 for ; Fri, 29 Jan 2016 03:40:37 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0134.outbound.protection.outlook.com [65.55.169.134]) (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 0BBFB13B1 for ; Fri, 29 Jan 2016 03:40:35 +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=kOAdzNQA0JsOLwLtEPiSPElsQnpPM2Gc0ioYdHeRhU4=; b=CHNZaX9WxUHOiYbIPN4wxrDnO87N06/qXVKVTOHYQTVc1QcemratHOzCTvQ6e85V/rDVNH93PGOD0C8qstZdplKsyfgAVrOHyIn4f+NNE5sweU2LeYXHiiwqnsCbXuUavILgL1YMTOG7tSaZIC7EAl3T9G8WqumSoeqBiAe8wDk= Received: from DM2PR03CA0006.namprd03.prod.outlook.com (10.141.96.16) by BLUPR03MB149.namprd03.prod.outlook.com (10.255.212.17) with Microsoft SMTP Server (TLS) id 15.1.365.19; Fri, 29 Jan 2016 03:24:42 +0000 Received: from BY2FFO11FD044.protection.gbl (2a01:111:f400:7c0c::163) by DM2PR03CA0006.outlook.office365.com (2a01:111:e400:2428::16) with Microsoft SMTP Server (TLS) id 15.1.396.15 via Frontend Transport; Fri, 29 Jan 2016 03:24:42 +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 BY2FFO11FD044.mail.protection.outlook.com (10.1.14.229) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Fri, 29 Jan 2016 03:24:41 +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; Fri, 29 Jan 2016 03:24:37 +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; Fri, 29 Jan 2016 03:24: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/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pAAABp5MAAD39gwAAxCoKAALasVEA== Date: Fri, 29 Jan 2016 03:24:36 +0000 Message-ID: <0f761afc10864ad3aeb89ee7c9b6e8ac@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> In-Reply-To: <4e85ad234a0b4618ae5862fbcd266e3d@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.197.68] X-MS-Office365-Filtering-Correlation-Id: 97e93f1a-6576-440e-8607-08d3285bb9c7 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD044; 1:+i3P8mcQTVNeUZNXLaJxjsNKTjqLBtLjbOASL3LeH6GrMQhOIktitjhSmsIooSNHSBzdsIhQii2+Pi/osU+jy3auEVgHinEfgn6n2iS5o7xIUTW1X84F/nZudT9Uo8iDMgiRLAG13ixyTpnT4YvAF8NHVTHSRD/862ryvJh1+TgrkWrsEw28Yj4wRbukq5fYZGisNJVK4Q53xkmwxbJmces1EIhuHMTYCOPXp0oljsEjlHSWXg0Vc9Ss4DosX2MIFPWqgoaKhZSPdopHJ3i3wMzyAkf2Q3TX0khj+tT8+N8Z5Su2HBe0U4ZokMU/0wFZyhNX+EXRBTuOYpV+O3zugw== X-Forefront-Antispam-Report: CIP:23.103.249.84; CTRY:; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(2980300002)(438002)(13464003)(3905003)(189002)(164054003)(71364002)(377454003)(199003)(51914003)(11100500001)(6806005)(5008740100001)(67866002)(33646002)(5003600100002)(1220700001)(3470700001)(19300405004)(102836003)(3846002)(1096002)(790700001)(6116002)(92566002)(18206015028)(586003)(108616004)(16796002)(2906002)(512954002)(50986999)(300700001)(93886004)(2561002)(76176999)(1511001)(19580395003)(4001450100002)(107886002)(19580405001)(54356999)(86146001)(84326002)(99936001)(10290500002)(87936001)(10090500001)(16236675004)(17760045003)(260700001)(5005710100001)(19625215002)(86612001)(15975445007)(86362001)(2950100001)(106466001)(189998001)(575784001)(2900100001)(5001960100002)(10400500002)(66066001)(66926002)(24736003)(19617315012)(19627595001)(5004730100002)(7099028)(491001)(579004)(562774006); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB149; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; MLV:sfv; MX:1; A:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB149; 2:9D6PMXV9DErA3yBjlcQr66iVPvs8dvBqyKUbyuq5ose2OiLT5XEpKyusg9wUYj6dyZf7rCaeGH4dHCo/7bC6Tkw0d9h5Yol65BscZ85NKSXX1IPA4kD44e6W3SHK68CSxbSmOPnDf0d5WKNMrrXnTiluWUOqLkHFKgVMgdGnnbnWaTLGH0zL5IKV1mRSkhMg; 3:GUCWapowH7Azsci3WaE6Acw4BXnursnkbRjyLkLi1lvuEgL3858uxSXPg7A9HkNvg0dnyfsQj29RQw5ZLlZjlVlKz+iPN46YNUbYBQb7cEHx4lJZSZsajnYB1fztSMr9nF3nBfw3jjPbcM6fMhN6hmLZD3WPZU5L5lmYkTQdJoQfjjSPzG8jtNUnysiuI3ar7rSoyEk1Fy98K/MHaRW4wdrXuNCjQmE4kPT+E2rrSO0RHDtu5ctxeW5RdOzFykeqQIZCCJWAjc4370nbGpxB1A==; 25:Ypu/B04PifsOl3BN7YDEjFfPCbDQAlXgcBxIGjCekzD5nLi4/FmLwKVhmFdSN0th+P4oulcLjTLXJousIF/Tc7wXg1N2z4ErAFfKxA5pTrMsaN+dvlDnGYMUsNVD0hdQBE1lLjqskGo2zFaEtBPjLMb+pHfp/uKitpAogaZolS9Mqib40Vx64jBTrUfUpXAWQ5JyLbg5Yl7QaNiCFmkM4TO8AIheODlLtntpL0iAEm22UeIQBtiHFsHTVvyNU2W0ChPfAzbDESbMdYSWKlYLZnVaph+9xCmEFspbTBQt3H8= X-Exchange-Antispam-Report-Test: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BLUPR03MB149; UriScan:; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB149; 20:Z+6Gm7ZIewtlCe6axiiqflBckILXQvsw+wfRaUC2PoOLtvXSxGaiTzHUKf4WqudcdRh+LngMKarbd8nY529Y09gkXOLQmxSC/OHoJ9CYfOuSMvIYUNzKkIwDrMQLVAgXy94X17SRBtMAvXwcLxY2jKmzscOX2QDAcX7Cj/GhKhFR8SeGYGzl9xF4zwZYekcoodnF8zwoVipGS4QXfW/xNZBzgD8op1NYBvpjZuv3ufSX3RGgo/7exTqL2IGwVxREMrhOaIQc3hD4PFu1ZA10YM2GUtXxMqWwUXsuEcoBvcs1QaoGuaciZZa5/Rdr7SRCRFiHpGVxw79Qes/2EX6OJGWJRFFQWMfMR3Dus2X6htBeBdg/hVmNKyHWiLIII7pp7peUql4/JVKh8GolH6joUlV9mHUV0klSUjRZB8ewzQF7Hvh8Il86ysgwR5uhF57sfJ7K6KRwLRR+YA7n2fePE89RPcyjnYAWj7oRKJu/K9IEuvDm0RwFaLXysayXEHT0H+P/9dc9c7EhND/jMFS7j0inExl5E+9KQdVTRH3v1VfEUsvTjSsJiTUSxOrxXLbqccH7FMRAa32ouaJvA3Eh6j4YdECojNUg+aSxQGajysk= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(102415267)(61425038)(102615245)(601004)(2401047)(13018025)(5005006)(13016025)(8121501046)(10201501046)(3002001)(61426038)(61427038); SRVR:BLUPR03MB149; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB149; X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB149; 4:KheUfP6yLbr0RZQCWqaoFK4NlJJ0jbB3nQPGUe+Oy0j2L0anqOzmung2dcbdxLiMBvc5ekMgSMCsnsESXWvi6rGbVsm/OnqLjbj5wd1yDdkO9ZoQOJTXf8n5o8ai43F9vE6s87IDtqciw3tOiFWJGz6VArEYDwVEp0cJnhpFNpPmwCUhhtPbZo/fRYwRawRccTs5EZ5LDqsQu2EEK8UJcHnlbN4eMIUtGod0oQV5wvoxG9PD8MaZdaUGegbujY84Gbj4Pso7xUN+S65GVMWck3eDqMuOTo4zrDXTr87CHd4baoZr+jpvaKakUrkS5NA/zSph/9fgPfAkzkvSWP5o9y7HOZG+T7XFRDplzHkI6aAAOU/dY5CdpQ9QTX46R2PiubPFSK0IBLXbKFc8i6n49mi+UgSmaXxqF2RJyngbQNrorrFj+LOuzVuCSUsnAwIzTlG7XXKxy8qa2lh0qdR3fQ7h0Gd9I8xC9iTKYfVX7/qOxUq5RRh7ThGw+sDaN8wV5aEfGoy+jNQ0d1GMAyAQ6Q== X-Forefront-PRVS: 083691450C X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR03MB149; 23:fATJgOPvbu2c46xj1S7c8tXbaz8Gfx7Dbp8hZXGz11?= =?us-ascii?Q?ocIpaxviHSroOUhuEdyg6NtMrGt9ewaXik3UkwIF+iyajq2tbap/6Zl5trXq?= =?us-ascii?Q?rpWsabyLzcb4CFyFo59oY2nQgr7TaX7j2calCoA6tckeX4ZyJ+UTaBeY4YrN?= =?us-ascii?Q?oQI6tZ+e+XBt6n2sBVh15iNzszyWuU7IC+WKbQdB9Y/1TXucpgmcuv5lwH4S?= =?us-ascii?Q?Yt9leCYjw9Dmqkq75TRI3xGFAeLEh4i1UwBRrf9DTPijvxqJlngqPm6b3doj?= =?us-ascii?Q?J/QPjPlFYaoTlk11PlutFdcaDo7q7tQ5GXMbT9yohDvwB8F9O85sKIs/43MJ?= =?us-ascii?Q?RUExlUUTPPuIXq6qUl7CmGATHD91780naQ05XV1o8uZUCT3wO3ygvlS3f1PN?= =?us-ascii?Q?oo6l+Ty2AydoXVJsSIvsJns35rncHfYMZQZE2umyaHVM8c+E6YXvRqkr/OoL?= =?us-ascii?Q?h7NP8MiqNY8WOGyC40Jh7nlyD4YlCIjegH8poxl5UCiQYYoEWXkyoHMrpU63?= =?us-ascii?Q?Vl5bQ2ojn3/7Rhcc/phahYS9je1PXLkvqilAAynYh4bdI3ODs/Vr4HvvbXOn?= =?us-ascii?Q?dFdcmPNju1gfWZPgXE6+w+bic5BirQH4rjRQomh3BRk+doFwEYvzOtBQxpYC?= =?us-ascii?Q?MLuZWPs5drc6R7jppkFI/LolF2lTUkXHxxUF0uebEtoDsZF0mJ+sHqCDJfzp?= =?us-ascii?Q?jCEFBNsJI10vdFkBuk7oeCW3/aovU6s4T3+DXBqH9E5cy6fiXy6n7wOuetXl?= =?us-ascii?Q?NQ5spUleQK6bGaPcGbSuoTjKU0w08+9irz/oN2AVVdnBmbeNpH/6u5mulxxS?= =?us-ascii?Q?EfDLOmbv+xRi1gpqRw4ag7A3bBsvwzN1RjsI5lj8jwilh2vdljX9xsHdH7fV?= =?us-ascii?Q?Su22JeHKIKafmcJuNT6/a8VEo8lYFBiUFgXa1yZmkalLt0XmEpdGzIFfrqyO?= =?us-ascii?Q?1+oJCnsg2MG0ynR3gXxgmASi5X/1hY53es490Z7reodGJIG5X+9vRkq2TPgu?= =?us-ascii?Q?DEC3FGGxGZHp+T3+J+k+Sogb6x5MsRaS38hDXWTAa3+yvKqQO4B1cOnsNZdD?= =?us-ascii?Q?1QZutLrw91Hc0t7vg2rQlDivJwlPAhgetxqpoLXjPKqYJKLUTWlT2cOa/LLv?= =?us-ascii?Q?d9s7xuyholMG++99E7k9DbV318NEy2oZ4zNmCzoSp5pYD4gQAqPzNB5vT1jP?= =?us-ascii?Q?FqlO2jxCkP/4wEYTDVVJhzyk/pMPTRipMrI7AEkTqugFvjrNSaqakHl0ETto?= =?us-ascii?Q?/ZzbUn7qVy0oGkq2lURXyJI/Lw1QG1eFGYtSp/VrQdbj/SgRaY7aufySjjPg?= =?us-ascii?Q?5fQLDF5W19zT32Y5u2BMqeBljP/BCMUvq6j8zlhQ2ogshVe33TRIC7EF/GUx?= =?us-ascii?Q?EdZfcEJacJ/gleFzS5x/L+qRWuHcKofamwmI9djJHr29hCDvyRQFmlW8RZQ/?= =?us-ascii?Q?J2IxgSEvFyACaftA+aTwuRLP+r2FKvxhKizEEwkeb5RSooe27a1ulYYBVUXF?= =?us-ascii?Q?fLmhzPyKdKgak0RBCedYekMXMNUs2VrN6LCpCLz+CW9OSrlfkZbIHZsB34Vk?= =?us-ascii?Q?DfFsKaq2Whm9xnRXqZLRMyvuf3fVAqx/Imxs6zLYrwyqYhe7eausqkjrk401?= =?us-ascii?Q?qJ6ynvNuRUkrBwG8hK89gmfpzSXUq9CKpUWkFvjhKO0ph78Ff5RzvA+Gqtrs?= =?us-ascii?Q?O+FfHsN8BxFpPFMGma+FJg6AggTF2hwSuGZ6fnbvDHu9e6wSm7VcTXHtRl08?= =?us-ascii?Q?eJUEHmhHlmkpDHbYvF9WaFZozBkf7J36iPEHR7ZUTgUdkp6Hj3JbpIqlYuFf?= =?us-ascii?Q?xEaBtsCehAsW+lEWathbiQQlgdwSOV5qhiZbZzcA1VgsPt37aJbrKlzcla47?= =?us-ascii?Q?odYIyeFUkJdy2I?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB149; 5:igK6GeUBO1PO5IdwYlw6Xvx1LtlJ/KNcl81R/geYpvmFbR8wFRcNzHtOWA8BevLkdFnMbahslngS4Ewk0GM7nSw+XyMZTiAB+d7GXdpdoMdi9HbX7Pu6yuYgCYORHvMXrm+9jkUhMuAy+70yFHO8SA==; 24:ciAz7WLCABu2MVyXqeYthqhdXURLFEFSsylNFT+Hy/rAoGmf+kOBYRY+EOcfd62Avh67vIxMBY6zeTkTdIJWTOdTERZbJ171ksS6azQ0RcE= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Jan 2016 03:24:41.0247 (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: BLUPR03MB149 X-Mailman-Approved-At: Fri, 29 Jan 2016 12:14:45 +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, 29 Jan 2016 03:40:37 -0000 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 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, 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 Jan 29 07:36: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 C5A88A71AA8 for ; Fri, 29 Jan 2016 07:36: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 AEC8D1577 for ; Fri, 29 Jan 2016 07:36:05 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id B98442B9BE1; Fri, 29 Jan 2016 08:35:55 +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 01703-09; Fri, 29 Jan 2016 08:35:55 +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 4D7FB2B9BAA; Fri, 29 Jan 2016 08:35:55 +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, 29 Jan 2016 08:35:54 +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, 29 Jan 2016 08:35:54 +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/xyLaKrOi2AAEaGnQAA5R0WAAAFPEIAAHGGIQAB849pAAABp5MAAD39gwAAxCoKAALasVEAAz7Epg Date: Fri, 29 Jan 2016 07:35:54 +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> In-Reply-To: <0f761afc10864ad3aeb89ee7c9b6e8ac@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: Fri, 29 Jan 2016 13:19:03 +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, 29 Jan 2016 07:36:09 -0000 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 Jan 29 08:59:00 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 19216A705FA for ; Fri, 29 Jan 2016 08:59:00 +0000 (UTC) (envelope-from decui@microsoft.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0124.outbound.protection.outlook.com [65.55.169.124]) (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 0D3BE179D for ; Fri, 29 Jan 2016 08:58:58 +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=dlo1nHIZ5wm/SOLo/rTBu8DUAlpDnAbcZGHX+OIN2Gs=; b=EvUELYxUoJfOZvrugtIa1EElaAebGVcN8agU+iz2gkyHf7LFL3TnHH8BTEbciE6BnGT/KdKAbbSAT0+Or3RNDLAc90Pm+BmyUTyjN+e8NXPYMNdbHiBCJxa24cqxmhiSGyToUNsBX7SmmBw/1bgl8dkped+h4I/AXxdDzqHR9wA= Received: from BN3PR0301CA0068.namprd03.prod.outlook.com (10.160.152.164) by BLUPR0301MB2051.namprd03.prod.outlook.com (10.164.22.141) with Microsoft SMTP Server (TLS) id 15.1.390.13; Fri, 29 Jan 2016 08:58:48 +0000 Received: from BN1AFFO11FD048.protection.gbl (2a01:111:f400:7c10::133) by BN3PR0301CA0068.outlook.office365.com (2a01:111:e400:401e::36) with Microsoft SMTP Server (TLS) id 15.1.396.15 via Frontend Transport; Fri, 29 Jan 2016 08:58:48 +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 BN1AFFO11FD048.mail.protection.outlook.com (10.58.53.63) with Microsoft SMTP Server (TLS) id 15.1.355.15 via Frontend Transport; Fri, 29 Jan 2016 08:58:48 +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; Fri, 29 Jan 2016 08:58: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; Fri, 29 Jan 2016 08:58:43 +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/D1A= Date: Fri, 29 Jan 2016 08:58:43 +0000 Message-ID: <4105829efb1e4b3a91bc17f7fbdf8ac8@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> 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.68] X-MS-Office365-Filtering-Correlation-Id: 4e49df7d-d781-4f84-c8f1-08d3288a66d8 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD048; 1:cCZejM4f+JyphMTZOieeBIbJsNa9X1yoUn4CIM1b8WOM1io92HwTKVN2bZPpjkNAApk9pzO/PKyBb2ELf6h0xtDFFsSj0KLm2frgqL/xq2ZXDrj3NNdKBVeGDlwCunFqF52TmswqDZJ29+BYxUVAjISafs/G/GU1zk2c/JcYQb3JaB8vPh03cAGZkJlzxKLg2j6TnEdCjPVyWRR4VgI0qh5YB4IAtIezmMFFYvsrETmiPJvrjYxNuAeFJNr3/fB3sV70ddK1ghSNC0HCkmzhvzr32iXbfNLt34HYoFZL5d+CY2PEWj+SMKCEEVccmvIKqu+Y2VXms/RhMrW3iEa8rg== 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)(13464003)(199003)(5191400?= =?us-ascii?Q?3)(164054003)(189002)(71364002)(3905003)(1220700001)(5129540?= =?us-ascii?Q?02)(1096002)(17760045003)(790700001)(6116002)(15975445007)(1?= =?us-ascii?Q?02836003)(2561002)(106466001)(3470700001)(107886002)(5001960?= =?us-ascii?Q?100002)(2950100001)(84326002)(2900100001)(189998001)(8661200?= =?us-ascii?Q?1)(86362001)(575784001)(260700001)(300700001)(50986999)(9993?= =?us-ascii?Q?6001)(54356999)(76176999)(5001770100001)(93886004)(500360010?= =?us-ascii?Q?0002)(3846002)(586003)(92566002)(86146001)(2421001)(10290500?= =?us-ascii?Q?002)(16796002)(18206015028)(1511001)(87936001)(5008740100001?= =?us-ascii?Q?)(19625215002)(6806005)(10090500001)(5005710100001)(50047301?= =?us-ascii?Q?00002)(108616004)(16236675004)(4001450100002)(19580405001)(1?= =?us-ascii?Q?9580395003)(2906002)(24736003)(66926002)(66066001)(33646002)?= =?us-ascii?Q?(19627595001)(11100500001)(19617315012)(67866002)(1040050000?= =?us-ascii?Q?2)(19300405004)(7099028)(491001)(559001)(579004)(562774006);?= =?us-ascii?Q?DIR:OUT;SFP:1102;SCL:1;SRVR:BLUPR0301MB2051;H:064-smtp-out.m?= =?us-ascii?Q?icrosoft.com;FPR:;SPF:Pass;MLV:sfv;A:1;MX:1;LANG:en;?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB2051; 2:qI3gftU0KKwtY8JBRZmxPaQBIXMv8uxcWUdI1MZM3XpCz7FVeCK+rMU1ZRMU0J6CvAcIqOQY0ldmseza3jWwFcp3SG+9hfLrIwPj44BKmq9BIASfZLRyCYpGabe88m2rVYeLh3Xv4XrQg+iNscIF7gazRF/abMsCowQgjniWl4WbQWU3LFNBvzWiIuIClZxr; 3:arVZk5KAnNgnjFwCY2f5KimLG9pnfjQXhKoDhuplKmi7MSSAO4XB3RAVsWiyBLLjhLJLYjSXCFl/FoWINxUPBjNMAt0EULtJQz4D/AoAq8D3w2zcskvFA9sMvDNKGPnS9oG73XTgB6wGzyFsju2YmeCrv/vfF/t/SCgoyzfI+9ktCqUDB3e13LO1Yefpi5TQEJDe9S4pTLsf4zW0/SjrM8tiPyacpiVIThnAm5lnKOKf6LW6AljOfgvwYCgYB2GzfPv/4cQN49/NwcxsqimYXg==; 25:oGsanglAubpr6oZILJ6gvJgFPmwnR+gf1DHS3apwZ3ALktsh30RcE/k/IUHOf3UFA1Pz84x+Ta/YUQBa/IoQ9t06wVXNcoi7KqOt/QiZr4G4pQmWqm82kf8urZioOeH9aNdo7Jt+Jm1OX5HkpAf2kvrTXptFqi0iPZvZwe8+zvBwM8AjSGNKLuJAipK4/RqE7Uya0aMm2HewQ8vQ/two0esZ9+VHKeVjdW8Qnjb4Z1zHZ73T8kE0+UWXxV4XIGuZBOb+ibo8SAQR/TPXEP8/n77MfewcjQSjvAroTehmi2k= X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501002); SRVR:BLUPR0301MB2051; X-O365EOP-Header: O365_EOP: Allow for Unauthenticated Relay X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB2051; 20:y/QCxiY1A7Fsru80yJgbOnaR2XHBAyFq0jJSVgSQRZ+RFXiLHewxpiqCJJoCqz2aFLJVKkpMj6r9lmPScfX6RCQUSLv5uiz0yvycW+eNItjDAaUnSX3+hkswKWwomW4KBgOfyjPDpK1aCriJP+x+Gp0Rd+LFpghlo4ZH21Eb/g/QMeqUrKetc2oj28KvlUIZQblk2YFBmQukxJ8OwcrU0IA0NES5nTpbqdY8eP2Atl9VUCH9uRvhz/y5NkUG6NebMkX5PhepL7CBQSacnqSYI6lix1dGxMWcWOSt+iUu8M3VBTbEGSIueEzY84blba0UG+52k7x2BwU8TipeSuF65rZugahu/XP25cqbDLfb0fd9MH3ih01Xbfv9O4SOJcwNJ4mOv8rXwisQ7M2B1a/qFKJGNKoCmQ/Z/u2tDeQsSissXnpImMtsE5VFIZce9tJ4ZmGZyMSSMMu0mZ4rq20eBtOeblJFLCEL9L8SfdQ10qAwZysCt/sj8PsSQ3rOhbVoqiLufhucWIUpuYOLBRfUBzC3zTNGYcGh/z2MYa5gYZBP8aum7Bu/pcePJC+k6GrpJIIrpW1m9aHSMp1oIhH26q+AVe9PDX4k4GuFIMzGgOI= 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:BLUPR0301MB2051; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0301MB2051; X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB2051; 4:AXsJWV3Yls8sZpBwRukQUmFbZYwj8lOTBHQ3RtI1P7ye+QaPEQynfJl0DhVHGQb6+7PJ42VcjsZyR+ZZcMbQpn+OTiAvHXGAJS3BCJbossL7WJPinldT0AV9o76TO/WtsK+hJig82AOVUF7Oyd6TC3A53LqIwrDtusWzp1IaFoOC/VJ5+JgdegVO7LDGm2+irPbsEdcM8iS7DYjbbyG/jeB4obvQS7mKP3mQtxCXwfEQA/5e48fVUllxbQD+OcaW0LpqJ1Pw7PWpWfz1e8T+ugKhFBw8mnysIYhBAYa9UoBSdg+2ER9V4oB8t6v9K/w7XdSjVOY8iScd/Gri0u4+7B/zIT01S4ebYx9naH5VaeBUCQRUFN4VmJXZYjp9dzm4Xf2ruekIk0LgS3acoAQ29SfZr3/09oIN3Mm5EwtC/YtjeRylfk20VJWuNUsxz+mSbqviyfpJzVhFqbbiPHKmjR9QE12q1Vvjyl1Q8aqlgwRR56f6zs9UFyjtiNODaSZS06Ky5qvpTRE1QPIYdu5rUg== X-Forefront-PRVS: 083691450C X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR0301MB2051; 23:l9y73OZWPuV6i+ZBgH+vawdLWOHYGT2MGfzFFQZ?= =?us-ascii?Q?k0Abg/Z5PwDs3OCBVlPpvG/T7/ZuYDlCbZIpbjs9/WR1Qk4NaegquLTGN5v6?= =?us-ascii?Q?0BPoR9CQTITtsskNM5wEZyEtFUa9y7z+92f2hSVayP5fT+PeDHUDC+/rR0gy?= =?us-ascii?Q?kqy8AXuYSnqU8gv9EZ3Izo3jhC6fb/IhYDD78MLIvI5TVmi2kIF9IM8bEKH+?= =?us-ascii?Q?LgTu6yUd3wttPLvBwYXCmxXRQDcEVMPtDtG2G2VkQ100Vk322bZNJuvJykpK?= =?us-ascii?Q?HnL+13vq9eYdMoQXdIz4kIvg9fXsZogOQolTU5ZDnTqQZa18njh98SunXqAA?= =?us-ascii?Q?CXcnCT1Be9h2pZ/Yn32VOARK7wOCCo/XNg85kLZGeg7zoZi+r+YViczmI+Fz?= =?us-ascii?Q?XWo4GEZ/JZbP92K1+sXsBKgH1wuSuHIZlw1jyT+jDQ5OQvJSJE+HfXw8XXgZ?= =?us-ascii?Q?vevDjmA7HOHzbOHBcy7kv4pkXxn2Y1Djti7Cs7LsNkebdE3YIJXpJ/wSejTX?= =?us-ascii?Q?OhagdBhoAKSr3tt1+sqCvIf7DsQidWYWCEh7t5bccY8cZb5icq44cnKqatyM?= =?us-ascii?Q?lu+ESf8xOoSt1i7Ds52830HJkVhWmGPxBYDyyZEX24xAq8WMe2l54OMZYBvh?= =?us-ascii?Q?F92418uJB02wcj4OenjH+T/yz/3w3CtNWjDD5b2+x/XOMmYsAttMDrYL1h+b?= =?us-ascii?Q?Jl6taYF5U9JEnka8ScuAmxR+Cp2tGewSbuqbMJ7c5MgOWdXLx+ciWX+yT53y?= =?us-ascii?Q?c0Ui5BWwsnlTC03IiaNOmWop6AQ5XChslAOE9bmBlvgvWAEQ67i1yXDZMNBJ?= =?us-ascii?Q?85YCLJmhjh1zQKDGOEa3EfAsU9CYYqaXBVuid+I+WH+SFZYwf1Bsm+IHmPw0?= =?us-ascii?Q?KNUh6CcNrjCfjvvZs6dJSBWuKa5aZRXzDqV/3LEZHJlncQ1cdFDqPQzeeh8k?= =?us-ascii?Q?wlydLcefq8koGGKe+Uk75uCsbXDeFn4aijPhiRea+XnEtdSqdmmFYJjW3icE?= =?us-ascii?Q?pO6yh72tGONEadmzCKQg5vE2Q7tlHxa++7YlqcmzydjtlCxJjf+9ZuD7NjBn?= =?us-ascii?Q?1Bi487d0whPxu55YymhRsGuIEfIsyXOD0Cxmp8mA8q4yekrWEH+rpBMe8gMf?= =?us-ascii?Q?iUxxEfhjEesK/k08+t0laIoDzh2to2p9Jj5jb9vTheHCSQRAD+Dr2GTPcDb6?= =?us-ascii?Q?BMiofeWcn/Pgs96DpI0o/7QJbrhfC7bWnlq5t9a87JtCzgufYnTe5hQFjuBf?= =?us-ascii?Q?xxZ31JMIcwVAex84OmKJuLisqK+dNt3J0hTmFB6wGo3R8Lom1pyUgpuGgiPN?= =?us-ascii?Q?y0oyqAFteoqSL1Xv6OVz3CnNhfEfnnEjRgk2EEoTLWgahiWbPSXxKVo8il2S?= =?us-ascii?Q?ORgZ6sqGMGySSzfYnFkxxzkzw865b22wrmBdUQ/mXPaqzyu0gdUwCutWAWWk?= =?us-ascii?Q?RUdqt8UkqVWpgzPh9DBchrOl6kZfu+XVE+odapfHBGJFCz51tANL94mUZ5Q1?= =?us-ascii?Q?Fs0+htD3oN+ZLzIW9Qt+CQTAdFsz4Shg0ib5bHSPpMv/vNIe3LtXb7njRU0z?= =?us-ascii?Q?wBcyJS6DWKDSYsAQTlyiE2/CNt6zEncozR7Z0+nWvYbcx70DfpK03mb4pEq1?= =?us-ascii?Q?6jciWk5U/wGc8Nb+qHGdICnUcxlKLILSCrRgF66X7rZ38WPILaSXJuho+ScZ?= =?us-ascii?Q?N1Xe7ZBdF2JdSenmm3rTY/6M06hquubwtqrbzGQKZLIxX2BHYDvuquDq3/CA?= =?us-ascii?Q?lJo3WxvHbu26SlaaeqpcRotqOMbHZl3b1GnN2LOB6jf0OpQQn6FNFLZ/m4+H?= =?us-ascii?Q?MwEu64bBrOWxfS/xje5zT8PV4+dc5jFgXPQppXFtf5/7rjFmgEzbUvcesjMs?= =?us-ascii?Q?Wu5SRYj81a02alUrY6DVc+vp5mJCsXWnNJjPfc8ZZjcPZQ+9JOybUQEeEdKP?= =?us-ascii?Q?elrxQqcCCVSnUJ5pXdtdk?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR0301MB2051; 5:9lmAj/1x4MubGYO+Dhz5//w8DZxlLa1Fb9kR4SCcn5y1CgEJO/DcQX90GKdI4/pN165j7ac5+tGOwx07uaQkvy4nrqIgEyGaCeJvbuksn8n8cwT18/ZpSR0+yj8EKMSiO++WSWzL0w3QwUXlzmqfBw==; 24:xGL4zhTbIacxE1cLFTlM2gkojC40rcWQZ96xtCe5B1DjtEP4E25jDQpez8KVOSRiY57KV+MrAQfLM5nQCCJbB+Ks3D5yXGr0oceALgku7wM= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Jan 2016 08:58:48.1241 (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: BLUPR0301MB2051 X-Mailman-Approved-At: Fri, 29 Jan 2016 13:19:19 +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, 29 Jan 2016 08:59:00 -0000 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 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, 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 Jan 29 17:37: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 1D3DFA7252E for ; Fri, 29 Jan 2016 17:37:10 +0000 (UTC) (envelope-from clint@clintarmstrong.net) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (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 E70A010DE for ; Fri, 29 Jan 2016 17:37:09 +0000 (UTC) (envelope-from clint@clintarmstrong.net) Received: by mail-ig0-x22c.google.com with SMTP id t15so41769094igr.0 for ; Fri, 29 Jan 2016 09:37:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clintarmstrong.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=LCMfX0CcO7sgs5Tz6O5Hu3BbAi5QI5j/xyqEsLnLCws=; b=IvQMPdRAVmeT7LuIKLEg2SDVM98WC+XOkuMysKnkAyvJqfbhudiXEUJcCxaiGu/ICZ C1qNBV6q1PN92ylukeQ3FtW1UAhad7J5QDun8UqshJXFFjJhpgClpE7X7r1cQacBI7ZH PlWAhQ2WWQniYpxswFMA5ywzn2vvbiMTEltQ8= 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:cc:content-type; bh=LCMfX0CcO7sgs5Tz6O5Hu3BbAi5QI5j/xyqEsLnLCws=; b=N4YCm3J/Jmg5iQReMwAMa285k6EwYFpo0MREe/id56wWb0/EpQUQF5WWOTp3bHJXmt MyHwOMyZgfBjmTXKNj9VYbVFY2tOPyGyKUcwdz2Ue2rzXWS0d7R7f7xkhwy4yGpA+gpX HjMNmI0/xFJhsyH4udHbmJrKs+qQHBZIrWv1E2ICR1DQGQeogj9asgg2mKZUPenq/aao kk17BZ5FlXMxzP9YVZYfTwlHQVpO5B4WAdLhji+SoOIAjOLqyGhj8IVlk0XZmnGssk6h wG6mwZQZB292o2cwWfR92YC03EQLKZfcklEGk4AXWDyWagWBTyHRPGj6CIQ1dXspH7wJ E6iQ== X-Gm-Message-State: AG10YOSvic/d+fm801WlKw0AwbbDTrxMZcGuYT72Vfq4eaty77xwP369wWWejUAqYpg+jQMblsxjYvbJYQ7t2w== X-Received: by 10.50.122.38 with SMTP id lp6mr11012864igb.12.1454089029020; Fri, 29 Jan 2016 09:37:09 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Clint Armstrong Date: Fri, 29 Jan 2016 17:36:59 +0000 Message-ID: Subject: Re: ATTN Docker, Jetpack users (was: Re: Docker on FreeBSD) To: Sergey Zakharchenko , Matthew Veety , Ryan Holt Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 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, 29 Jan 2016 17:37:10 -0000 I had to give up on Docker on FreeBSD because the latest versions of docker are now very dependent on netlink APIs for networking. The new network driver API for docker may allow creating a network driver for FreeBSD that would bypass that, but I haven't had a chance to look into it yet. I think good docker support is going to be dependent on newer Linux kernel emulation in FreeBSD if porters don't want to make a full time job of implementing workarounds with every docker update. On Fri, Jan 29, 2016 at 6:48 AM Sergey Zakharchenko < doublef.mobile@gmail.com> wrote: > Hi Matthew, > > What needs to be done with docker to get it running better on FreeBSD? Is > > there any place with a list of bugs or a todo list? I would be > interested in > > getting it working better. > > It's more like a list of things which work, many things that don't, > and a sea of things which 'sorta' work. Mainly because of this one > entry in > https://github.com/kvasdopil/docker/blob/freebsd-compat/FREEBSD-PORTING.md > : > > >>> volumes - not working > > It's a small benign-looking entry. Not in bold, not highlighted, > hidden deeply from those unaware. > > Image building doesn't *really* work because of that, because the > resolver configuration and hosts file are, like, 'single-file mounts'. > So when you do a pkg install in the image-building container, you get > no address record. Jumping through some hoops, including > custom-generated Dockerfiles (what a crappy file format BTW), can > still get things done. You're left with jumping more hoops with adding > the volumes when you instantiate and start a container. > > Problems indicated by kvasdopil: Docker is too much of a moving target > and his patches no longer apply to the latest, they change everything > all the time (e.g. network config revamping, etc.). That is a valid > concern. > > Should I contribute to the whole thing? Too few people seem to care. > > My questions are: Is anyone here interested in a patch which improves > container-building performance (I'm patching Docker but a similar > approach should benefit Jetpack)? Now, is anyone interested and > *competent enough* in fixing the volume problem? > > Oh, and there's the whole port forwarding thing... > > >>> port forward - ok > > OK would be native support of a FreeBSD firewall, e.g. PF. Please > don't tell me you like the userland proxy. That's partial support, and > the container access logs become useless... > > P.S. Ryan wrote: > > I've since moved to Gentoo, ZFS for Linux, and Docker. Works really well. > > That's exactly the attitude the current state of things provoke. Not > blaming you in any way. Docker in general sounds like 'run it anywhere > and pray it's the latest 64-bit Ubuntu' :) > > Best regards, > > -- > DoubleF > _______________________________________________ > 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 Sat Jan 30 00:04: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 5DD9BA71B86 for ; Sat, 30 Jan 2016 00:04:46 +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 21F9C1ABB for ; Sat, 30 Jan 2016 00:04:45 +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 8549A20B4B67 for ; Sat, 30 Jan 2016 10:04:37 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 7E714280A3C for ; Sat, 30 Jan 2016 10:04: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 Vbeg13Axj2oj for ; Sat, 30 Jan 2016 10:04:37 +1000 (AEST) Received: from Peters-MacBook-Pro.local (c-50-184-135-69.hsd1.ca.comcast.net [50.184.135.69]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id AE686280903; Sat, 30 Jan 2016 10:04:34 +1000 (AEST) Subject: Re: VirtIO Ethernet driver in DragonFlyBSD under FreeBSD bhyve To: Oleg Ginzburg References: <9893747.yFCcEWVR7f@gizmo.my.domain> Cc: freebsd-virtualization@freebsd.org From: Peter Grehan Message-ID: <56ABFE12.4060805@freebsd.org> Date: Fri, 29 Jan 2016 16:04:34 -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: <9893747.yFCcEWVR7f@gizmo.my.domain> 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=ZMguiOAsC5immlfEDy0HCA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=7aQ_Q-yQQ-AA:10 a=jJrOw3FHAAAA:8 a=hpgURV26c7tEzfcD6cEA:9 a=pILNOxqGKmIA:10 a=zGlHrSWtykwA:10 a=-FEs8UIgK8oA:10 a=NWVoK91CQyQA: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: Sat, 30 Jan 2016 00:04:46 -0000 Hi, > I do not know whose it is a problem - DragonFlyBSD vtnet(4) driver or FreeBSD > bhyve(4), so I decided to send on both maillist. > > I've try to boot DragonFlyBSD 4.4 in bhyve. All goes well, however, there is > no network interface. During boot i see: .. > Boot processing : https://youtu.be/iV1eZxEvj0c > > bhyve executed with follow settings: > > /usr/sbin/bhyve -c 1 -m 4294967296 -A -H -P -s 0:0,hostbridge -s 2:0,virtio- > rnd -s 3:0,virtio-net,tap0 ... > > What can be done to correct this error ? Firstly, very happy to see D'Fly booting under bhyve+UEFI/CSM :) I'll do some debug and see if this can be fixed. later, Peter. From owner-freebsd-virtualization@freebsd.org Sat Jan 30 05:40:54 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 70111A73FFF for ; Sat, 30 Jan 2016 05:40:54 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::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 30A3B1FB5 for ; Sat, 30 Jan 2016 05:40:54 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: by mail-ig0-x229.google.com with SMTP id t15so3466890igr.0 for ; Fri, 29 Jan 2016 21:40:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=4MDaChOdWnzc9DGpHtUqewd/PABDh60NR5qUs0gvWvE=; b=bCdxgrpOTkCYfIMLGL2vcFA24W/nEPb/4AjPtIQdKpnbMQ6UXiacGJu9AtlgYS9pBV ppnD92YYy5lBpO1foycVHwb9Amo1PSSYSRhL7S4S7hv2Smco27IWVQ76DUrLwD7TsaWB dB9Xg035zaU0qWFM10CZIh7HtyaC1zSvr7mAtgtGqnyvcHGB/ReyZYjF6izOIBfjriEe LSZzrlRhB3LFrERKfQLyHJCWzviaO20WOFBrkU1tg3oxNEP6PFftS5y0eBdm7V74BsiY JaS+8j7YEu5y6pmnAZS5n2irvgOPc7C/G3jdoOzAHGiTm01o99mz6WfmyxR0LA1Ua2xT Yphg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4MDaChOdWnzc9DGpHtUqewd/PABDh60NR5qUs0gvWvE=; b=HXGUveuJr9uMrOiGGxgVQ83hDP2eC/WkpPc8p6WW2SVHDtzvaFh4ng+3Eof4MDZdWm t9APvvjmgY9Z/Qx84mz7te9lkoBVKZaLkjszVUcX41x8oK5a8E7HkAqSaX0tIulfPvv5 ism7wkEP3peMWA7YRFTxFni/008JgngLUsBDFdNWr0qrfgaX1OAtYFkYB28Ru6iZEPJw DaLuNy+0nxF3fR/pRXG4flrDbWSj9bNKR3xC+smAg7vnDT9QP7867THuaT6UwYZOquN6 bT9SdNbSfE5AcyiPXe1WdmTUgq/R8r5LYlj2fCC34U9xx0XltOHB71kDHeBJSQFSJc0+ 54BA== X-Gm-Message-State: AG10YOSVvE/eW4f8pvWJBbzJEu4AFw9ZxX+8gBW7K5JCPns8YoZp5VnWS/ymvRZzdGyD29MHBlfRHPMJt7cyYw== MIME-Version: 1.0 X-Received: by 10.50.36.35 with SMTP id n3mr852259igj.73.1454132453553; Fri, 29 Jan 2016 21:40:53 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.50.152.69 with HTTP; Fri, 29 Jan 2016 21:40:53 -0800 (PST) In-Reply-To: References: Date: Fri, 29 Jan 2016 21:40:53 -0800 X-Google-Sender-Auth: IQcfXOF3bvQ0kKsgHpl5Gam8QuU Message-ID: Subject: Re: ATTN Docker, Jetpack users (was: Re: Docker on FreeBSD) From: Craig Rodrigues To: Clint Armstrong Cc: Sergey Zakharchenko , Matthew Veety , Ryan Holt , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Sat, 30 Jan 2016 05:40:54 -0000 On Fri, Jan 29, 2016 at 9:36 AM, Clint Armstrong wrote: > I had to give up on Docker on FreeBSD because the latest versions of docker > are now very dependent on netlink APIs for networking. The new network > driver API for docker may allow creating a network driver for FreeBSD that > would bypass that, but I haven't had a chance to look into it yet. > > I think good docker support is going to be dependent on newer Linux kernel > emulation in FreeBSD if porters don't want to make a full time job of > implementing workarounds with every docker update. > > I completely understand that chasing Linux technologies from FreeBSD can be a pain. I hope that when you have time, and maybe when the churn in Docker slows down a bit, you manage to figure out a way to keep Docker on FreeBSD going. FreeBSD has had jails for many years, and bhyve for a few years and these are both very solid and capable technologies. However, they don't have the buzz and integration with third party workflows that Docker has. For example, I've seen how GitLab uses Docker to spawn build nodes, and it works really, really well. It would be a shame to see FreeBSD be left in the dust on this. -- Craig From owner-freebsd-virtualization@freebsd.org Sat Jan 30 19:44: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 F29A5A72B1D for ; Sat, 30 Jan 2016 19:44:46 +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 CF0F680F for ; Sat, 30 Jan 2016 19:44:43 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id 89D392B9BAB; Sat, 30 Jan 2016 20:44:34 +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-01; Sat, 30 Jan 2016 20:44:33 +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 E4DDC2B9BE3; Sat, 30 Jan 2016 20:44:33 +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; Sat, 30 Jan 2016 20:42:11 +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; Sat, 30 Jan 2016 20:42:11 +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/D1AASYVK4A== Date: Sat, 30 Jan 2016 19:42:10 +0000 Message-ID: <0ce04bf413204478b1e7cc71ac28ecac@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> In-Reply-To: <4105829efb1e4b3a91bc17f7fbdf8ac8@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: Sat, 30 Jan 2016 22:16:35 +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: Sat, 30 Jan 2016 19:44:47 -0000 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"