GitHub user herrickaccuwebhosting added a comment to the discussion: Can't 
start the virtual machine [CloudStack 4.22.1.0 | XCP-NG 8.2.1]

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.
Restart the toolstack. xe-toolstack-restart on the specific host that's 
throwing it, this clears a lot of stale XAPI object cache issues without 
needing a reboot.
Check xensource.log on that host around the same timestamp, XAPI's own log 
usually has more detail on why it rejected that specific UUID than what bubbles 
up to CloudStack's log.
Notice it fails identically across three different hosts (77360, 77359, 77352), 
so this probably isn't a single host issue, it's more likely the VM instance 
record on the CloudStack DB side, or how CloudStack 4.22.1 is calling VM.create 
against XCP-ng 8.2.1 specifically. Worth checking if there's a known 
compatibility issue between that exact CloudStack and XCP-ng version combo on 
GitHub issues, this smells like a version mismatch bug rather than infra.
As a workaround test, try destroying and recreating just that one VM's instance 
record (not the disk) if downtime is acceptable, if a fresh UUID starts clean, 
that confirms it's a stuck/corrupt record rather than a systemic issue.

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.

GitHub link: 
https://github.com/apache/cloudstack/discussions/13717#discussioncomment-17857693

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to