Replies: 1 comment
|
That Types$UuidInvalid right after "Created Instance ... for i-354-8711-VM" is the interesting part, XAPI is rejecting the VM object CloudStack just created, not failing on capacity or networking (those all succeeded). A few things worth checking: XAPI database desync on that host. This error often shows up when the XenServer/XCP-ng host's XAPI toolstack has a stale or orphaned VM object with the same UUID sitting in its local DB, sometimes left behind from a previous failed start/migrate. Try xe vm-list params=uuid,name-label on the affected hosts (77360, 77359, 77352 in your logs) and check if d81f6675-9f75-4b28-bf89-bbee9c4c4432 already exists there in a weird state. We run XCP-ng backed CloudStack too at AccuWeb.Cloud and this specific UUID rejection has usually traced back to toolstack cache weirdness in our experience, so the toolstack restart is worth trying first since it's low risk. |
Uh oh!
There was an error while loading. Please reload this page.
Hello, everyone.
I can't start the VM. Please help me figure out the reason.
I'm getting the following errors in the CloudStack log files:
All reactions