Limit the size of a virtuqueue to its maximum possible about firecracker HOT 1 CLOSED

The lack of accessor methods is one thing we'll probably want to alleviate going forward, but at the same time, their usage is more of a best effort approach, since even fields which are not public can still be liberally accessed from the module their parent struct is defined in, and from any other children of that module.

While it's true that an incorrectly set size will generate warnings, this will only happen in response to certain guest actions, which can already trigger other similar messages by providing invalid input in quite a number of contexts :-s I think we should try to fix all these similar issues by changing the way we respond to the erroneous conditions within Firecracker, and I'll create an issue regarding this. Closing this one, because I think it's not something that should be considered in isolation.

from firecracker.