This binding is only used when creating a `VirtualGuest`, to bind the VirtualGuest parameter to the request body.

The VirtualGuest object, however, has many fields that are not required in the create operation and the binder just extracts the required fields, populates them into a "smaller" object, and then binds it to the request body.

This approach seems a bit confusing, as it might be difficult for users to know which fields of the VirtualGuest object have to be populated in order to create it. Could the api method be refactored to directly receive the `ObjectData` (perhaps renamed to VirtualGuestCreation or similar) instead of the entire VirtualGuest? WDYT?