GitHub user nickaccuweb added a comment to the discussion: CloudStack KVM + LINSTOR primary storage: VM stuck in Starting although LINSTOR volume is successfully created
@anirudh09041 Thanks for sharing the details. The LINSTOR resource and DRBD device are created, but the ROOT volume is still showing Allocated instead of Ready. This means CloudStack may not have completed the volume preparation. For now, please do not manually promote the DRBD resource to Primary or make any changes to the libvirt storage pool. CloudStack should handle the volume attachment and use the appropriate /dev/drbd/by-res/ path automatically. Please also confirm that the KVM hosts are running CloudStack 4.22.1.0 and that their hostnames match the LINSTOR node names. For one failed VM deployment, please share: 1. Deployment time, timezone, and asynchronous job ID. 2. Relevant entries from management-server.log. 3. Relevant entries from agent.log, including CopyCommand and StartCommand. 4. LINSTOR and libvirt errors from the same time. 5. /var/log/libvirt/qemu/i-2-33-VM.log, if available. 6. Confirm that the /dev/drbd/by-res/ path exists and works correctly. These details will help us identify whether the issue is happening during template preparation, disk access, or VM startup. Regards, Nick R AccuWeb.Cloud GitHub link: https://github.com/apache/cloudstack/discussions/14010#discussioncomment-18500633 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
