Good question... Yes it did :) sorry for the suspense ;) On Tue, 30 Jul 2019 at 14:38, Mike Hammett <[email protected]> wrote:
> Did that fix it? > > > > ----- > Mike Hammett > Intelligent Computing Solutions <http://www.ics-il.com/> > <https://www.facebook.com/ICSIL> > <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> > <https://www.linkedin.com/company/intelligent-computing-solutions> > <https://twitter.com/ICSIL> > Midwest Internet Exchange <http://www.midwest-ix.com/> > <https://www.facebook.com/mdwestix> > <https://www.linkedin.com/company/midwest-internet-exchange> > <https://twitter.com/mdwestix> > The Brothers WISP <http://www.thebrotherswisp.com/> > <https://www.facebook.com/thebrotherswisp> > <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> > ------------------------------ > *From: *"Tom Smyth" <[email protected]> > *To: *"Misc" <[email protected]> > *Sent: *Tuesday, July 30, 2019 8:30:04 AM > *Subject: *PCI-Passthrough XL710 NIC ixl OpenBSD Guest reboot Resets > Hypervisor OS > > Hello all, > > I recently have been playing with PCI Pass through, IO MMU > / SR-IOV with Intel NIC XL710 based 40G nic ixl drivers > with proxmox / kvm and qemu as a hypervisor and OpenBSD > as the guest vms, > > we encountered an issue where if I passed through the > Physical Function (full nic pass through) that when > reboot / halt -p command was entered on the guest the > hypervisor / proxmox would reset and reboot also > > > after diagnosing and trying to pass-through other devices > such as the intel pro 1000 em nics > they did not seem to cause the hypervisor to reboot > when rebooting the openBSD Guest > > I got on to the friendly people at HotLava systems > (my nic vendor) and they suggested the firmware of the > NICs be upgraded, > > I installed the version 7.00 nic firmware (replacing > version 6.01 firmware > > the tool I used to update the firmware on the hypervisor > was > ./nvmupdate64e and comes with the firmware package > from the Intel Download site... > > I hope this helps anyone trying to run openBSD on > a KVM / Qemu based hypervisor like Proxmox > > I couldnt find this issue documented anywhere > so im sending this to the list... > > im sure there is also a security issue where the hypervisor > can be hard reset, by a guest being rebooted ... > but this is a question for the Hypervisor and not OpenBSD > > Hope this helps anyone who has encountered it in the past > and those who may encounter it in the future > > > -- > Kindest regards, > Tom Smyth. > > > -- Kindest regards, Tom Smyth.
