This is not the correct way to negotiate virtio features and causes this
panic when running on a machine with a virtio-serial device, such as
the default non-CI machine:
"ASSERTION FAILED: m_did_accept_features.was_set()"
Additionally, I don't think this is the correct way to fix this, as QEMU
never seems to have advertised VIRTIO_F_IN_ORDER.
A correct fix would be to handle descriptors being processed out of
order correctly.
This reverts commit 0d9a095f5a.
Sönke Holz
31872aee3f