haimg
Contributor
Contributor

This is definitely a new one for 6.5... I've seen the issue several times already, unfortunately, and it's not limited exclusively to USB devices. I think the issue happens if the VM config was modified in some way while vCenter was down. It seems that even just starting a VM while vCenter is down could trigger it.

I've managed to recover from the issue in a much more simple way, but my solution is much more limited.

1. Bring the problematic VM down (I knew which one it is because of a specific device mentioned in the log output, but otherwise it could be a problem).

2. Unregister the VM on the host.

3. Bring the vpxd service back up.

4. Unregister the now "orphaned" VM on vCenter.

5. Re-register the VM on the host, and start it again.

This seems like a serious issue with vCenter, and there is no easy or simple way to recover. I'd hate to tinker with vCenter SQL database directly, and my "solution" requires to shut down and unregister the VM, and there is no easy way to know which VM is causing problems...

Reply
0 Kudos