From owner-freebsd-virtualization@freebsd.org Tue May 17 15:14: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 9362DB3F01F for ; Tue, 17 May 2016 15:14: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 69C1E651BB for ; Tue, 17 May 2016 15:14:49 +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 u4HFEnQZ052472 for ; Tue, 17 May 2016 15:14:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 209427] if_vtnet(4) is not sending LINK_(UP|DOWN) events Date: Tue, 17 May 2016 15:14:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: novel@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: attachments.isobsolete attachments.created 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.22 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, 17 May 2016 15:14:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209427 Roman Bogorodskiy changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #170183|0 |1 is obsolete| | --- Comment #2 from Roman Bogorodskiy --- Created attachment 170409 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D170409&action= =3Dedit proposed fix, v2 Attaching a new patch that's slightly less dirty than the previous one. Specifically, it does not change vtnet_is_link_up() behavior, but extends vtnet_update_link_status() event triggering. Specifically, if link is here and IFF_DRV_RUNNING is set, but interface was= not active, we mark it active and trigger notification. If there is no link or IFF_DRV_RUNNING, then we consider interface down. Also, add a call to vtnet_update_link_status() on mtu change to trigger eve= nts as well like other if drivers usually do. So, a pair of ifconfig vtnet0 down/up followed by ifconfig vtnet0 mtu 1496 = look like this in devd: !system=3DIFNET subsystem=3Dvtnet0 type=3DLINK_DOWN !system=3DIFNET subsystem=3Dvtnet0 type=3DLINK_UP !system=3DIFNET subsystem=3Dvtnet0 type=3DLINK_DOWN !system=3DIFNET subsystem=3Dvtnet0 type=3DLINK_UP !system=3DIFNET subsystem=3Dvtnet0 type=3DLINK_DOWN !system=3DIFNET subsystem=3Dvtnet0 type=3DLINK_UP I'm yet to figure out how I can test link status change in bhyve so vtnet_is_link_up() returned something other that 1. --=20 You are receiving this mail because: You are the assignee for the bug.=