Change Details

This is the seatbelt mentioned in D20529. Until rXXXXXX, bhyve presented a seg_max to the guest that was too large. This could overflow the virtio queue when the guest used a MAXPHYS of 256 KiB. In order to ensure that our own assertions hold true, limit seg_max according to the virtio queue size.

This is the seatbelt mentioned in D20529. Until r349278, bhyve presented a seg_max to the guest that was too large. Detect this case and clamp it to the virtqueue size. Otherwise, we would fail the "too many segments to enqueue" assertion in virtqueue_enqueue(). I hit this by running a guest with a MAXPHYS of 256 KB.

This is the seatbelt mentioned in D20529. Until rXXXXXX349278, bhyve presented a seg_max to the guest that was too large. TDetect this could overflowase and clamp it to the virtio queue when the guest used a MAXPHYS of 256 KiB.size. Otherwise, we would In order to ensure that our own assertions hold true, limit seg_max according to the virtio queue sizefail the "too many segments to enqueue" assertion in virtqueue_enqueue(). I hit this by running a guest with a MAXPHYS of 256 KB.