@audian no problem at all! I'm enjoying the TNSR experience and look forward to seeing the fixes and improvements you all are working on.

Nothing like that available yet and I'm not seeing anything in open feature requests either. If you are already in contact with someone from Sales/CSE, make sure they know it's a feature you'd like to see.

I will certainly give it a read and a watch and look for reasons to learn and practice. Really appreciate your insight and perspective. I'm sure we'll interact again soon assuming you're ok with questions/complaints/feature requests. I'm trying to be diligent about researching before asking for help but, as you have witnessed personally, I've hit a wall a few times now.

Not at the moment, it's all in an internal bug tracker. Every once in a while we revisit making that public but so far it's mostly private with internal chatter. If anything changes there, it will be in the release notes and related posts around a new release.

Thanks! I wasn't aware that I could do that without assigning an IP address etc to that interface.

@jimp has the same question, thank you for the answer :))

@leoan we tried that at one point and it loaded successfully, but as shown in my screenshot only the virtual NIC would load properly.

I initially named this thread wrong, not realizing the NIC naming convention came from the driver. Our VMX3 virtual side loaded just fine, it was the PCIpassthrough of a BCM driver that is not currently implemented or supported in TNSR.

Thanks for your help.

So, I did a package update and after reboot, it immediately Kernel panics. Since this is isn't in production, I just did a fresh install from the latest version ISO. Now all the interfaces populate as expected.

Changing the OS Guest version to CentOS 7 64bit made the Virtual Adapter visible, but as you can see here, the PCI passthrough is not taking...
Screenshot from 2019-12-09 13-48-05.png