From owner-freebsd-bugs@freebsd.org Mon Feb 27 18:31:47 2017 Return-Path: Delivered-To: freebsd-bugs@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 61AD3CF0438 for ; Mon, 27 Feb 2017 18:31: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 515EFD43 for ; Mon, 27 Feb 2017 18:31: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 v1RIVlWO053267 for ; Mon, 27 Feb 2017 18:31:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 217402] Changing LAG settings with iohyve VMs running causes kernel panic Date: Mon, 27 Feb 2017 18:31:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: finlon@gmail.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: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 18:31:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217402 Bug ID: 217402 Summary: Changing LAG settings with iohyve VMs running causes kernel panic Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: finlon@gmail.com Created attachment 180345 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180345&action= =3Dedit info and textdump files Creating/Modifying/Deleting LAG interface while iohyve VM is running causes kernel panic. I've been running two ioyhve VMs for a while, and I just got a new Intel du= al gig port pci express card to set up a LAG. As soon as I created a LAG the system went in to a crash/dump/reboot loop. It appears that if you try to configure or even just create and not use a L= AG interface, and then start a Iohyve VM, the system immediately crashes and reboots. If a LAG is configured, and the Iohyve VM is set to auto boot, the system goes in to a dump/reboot loop. I ended up reinstalling, and loading a backup config. I can either run with= a LAG set up and no iohyve VM's or run iohyve VMs and no LAG. --=20 You are receiving this mail because: You are the assignee for the bug.=