SR-IOV support in the ixv driver is currently broken. As a result, FreeBSD 12.0 is unable to access the network on EC2 instances where this hardware is used.
If this is not fixed before the release, we should remove the --sriov flag from src/release/Makefile.ec2 so that the AMIs will be marked as not supporting the ixv hardware (at which point those EC2 instances will provide a Xen virtual network device instead).
Do we have any more details / reproduction recipe? Are the Intel driver folks on it?
Created attachment 195875 [details]
AWS c4.xlarge ixv hang on boot screenshoot
this is how i can reproduce the problem:
1) deploy FreeBSD 11.2-RELEASE AMI (for us-west-2 ami-206a2158)
- choose a non-ixv EC2 instance type. For example: t2.xlarge (4core, 16g, xn NIC)
2) build 12-CURRENT on this system
3) after you have booted into this system and verified it works as expected, stop the instance and change the instance type to one that will expose an ixv NIC for example a c4.xlarge
4) the instance will hang on startup. by viewing the instance screenshot (Actions -> Instance Settings -> Get Instance Screenshot in the AWS web console)
you should see the instance hung.
i've attached a screen shot showing where in boot is has hung to this ticket.
You can stop the instance and revert it back to a t2.xlarge to update things and test again. I am happy to test out any patches or any other things that may help get this resolved. I'm currently using 11.2-REL in my infrastructure but want to make sure 12 works as soon as its ready.
Created attachment 195876 [details]
c4.xlarge verbose boot
this doesn't seem to get to the point of loading the ixv interface, not sure if this is helpful.
I've narrowed this down to between r326378 and r326622, based on launching weekly snapshot AMIs on c4.large EC2 instances.
Fixed by r338593