Now that potentially buggy versions of Xen are automatically detected
(see r302635), there is no need to force msix interrupt migration off via loader.conf. Reverts: r302184 MFC after: 3 days
This commit is contained in:
parent
56d2f7d8e5
commit
d53ee33e1c
@ -72,12 +72,6 @@ vm_extra_pre_umount() {
|
|||||||
# nodes, but apply the workaround just in case.
|
# nodes, but apply the workaround just in case.
|
||||||
echo 'hw.broken_txfifo="1"' >> ${DESTDIR}/boot/loader.conf
|
echo 'hw.broken_txfifo="1"' >> ${DESTDIR}/boot/loader.conf
|
||||||
|
|
||||||
# Some EC2 instances run on a version of Xen which has a bug relating
|
|
||||||
# to the migration of MSI-X interrupts; this is visible as SR-IOV
|
|
||||||
# networking (aka. "EC2 Enhanced Networking") not being able to pass
|
|
||||||
# packets. Disable MSI-X interrupt migration to work around this bug.
|
|
||||||
echo 'machdep.disable_msix_migration="1"' >> ${DESTDIR}/boot/loader.conf
|
|
||||||
|
|
||||||
# The first time the AMI boots, the installed "first boot" scripts
|
# The first time the AMI boots, the installed "first boot" scripts
|
||||||
# should be allowed to run:
|
# should be allowed to run:
|
||||||
# * ec2_configinit (download and process EC2 user-data)
|
# * ec2_configinit (download and process EC2 user-data)
|
||||||
|
Loading…
Reference in New Issue
Block a user