Bug 217402 - Changing LAG settings with iohyve VMs running causes kernel panic
Summary: Changing LAG settings with iohyve VMs running causes kernel panic
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.0-STABLE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-virtualization (Nobody)
Depends on:
Reported: 2017-02-27 18:31 UTC by Scott
Modified: 2017-02-28 20:19 UTC (History)
0 users

See Also:

info and textdump files (68.32 KB, application/x-gzip)
2017-02-27 18:31 UTC, Scott
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott 2017-02-27 18:31:47 UTC
Created attachment 180345 [details]
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 dual 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 LAG 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.
Comment 1 Scott 2017-02-27 18:41:23 UTC
below is my uname -a

FreeBSD nas 11.0-STABLE FreeBSD 11.0-STABLE #0 702b055(stable/11): Fri Feb 24 13:46:08 UTC 2017     root@gauntlet:/freenas-9.10-clean/freenas9/_BE/objs/freenas-9.10-clean/freenas9/_BE/os/sys/FreeNAS.amd64  amd64