Why resuming the paused VMs are failing with error "argument must be a string or a number" in the vdsm logs

Solution Verified - Updated -


  • After restarting the vdsmd service, the VMs went into paused status.
  • Resuming the paused VMs are failing with below error in the engine logs.
2017-04-24 11:56:27,240 INFO  [org.ovirt.engine.core.vdsbroker.ResumeVDSCommand] (org.ovirt.thread.pool-6-thread-13) [31903304] START, ResumeVDSCommand( ResumeVDSCommandParameters:{runAsync='true', hostId='8459faa5-0810-44e7-af98-6b9a32ac3ae8', vmId='f660174d-422d-4e68-8c56-4b6789ce629d'}), log id: 294c66fa
2017-04-24 11:56:28,245 WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.ResumeBrokerVDSCommand] (org.ovirt.thread.pool-6-thread-13) [31903304] Unexpected return value: StatusForXmlRpc [code=-32603, message=VM u'f660174d-422d-4e68-8c56-4b6789ce629d' was not started yet or was shut down]
  • The VMs are actually running fine and can be accessed using ssh. However it's unmanaged from the RHV-M , since it's paused.


  • Red Hat Virtualization 4.0.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content