| Summary: | Changing LAG settings with iohyve VMs running causes kernel panic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Scott <finlon> | ||||
| Component: | kern | Assignee: | Bugmeister <bugmeister> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Some People | ||||||
| Priority: | --- | ||||||
| Version: | 11.0-STABLE | ||||||
| Hardware: | amd64 | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
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 ^Triage: close as OBE. I'm sorry that this PR never got looked at, but by now, 11.X is long out of support. |
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.