Description of problem:
Using the current VDSM <-> rhev-agent protocol, VDSM can't recover from a malformed message, and the channel between the VDSM to the rhev-agent becomes useless.
This protocol's origin is in the old hypercall device (not upstream) on rhel 5.X.
On RHEL 6 we moved to vioserial device.
On one of the vioserial discussions, it was brought up that the vioserial does not guarantee that the message will reach it's destiny intact (this was especially emphasized in the last round of discussions regarding s3/s4 support).
In order to be able to recover the protocol must be altered to identify the malformed message and drop it.
Since the VDSM <-> rhev-agent API is stateless dropping a single (malformed) message does not break anything.
*** Bug 738355 has been marked as a duplicate of this bug. ***
Verified between agent rhev-agent-2.3.14-1.el6 and vdsm-4.9-104.el6.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.