GitHub user herrickP added a comment to the discussion: # URGENT HELP NEEDED : Not able to start or create a vm inside any host
Good news, your logs actually point to a pretty specific cause! What's happening InsufficientServerCapacityException while CPU/RAM are free, combined with read-only filesystem inside the VM, points hard at shared primary storage, not compute capacity. Likely chain: your primary storage (probably NFS) disconnected, filled up, or got remounted read-only. That makes the guest filesystem inside the VM go read-only too (why you can SSH in but can't write). And when CloudStack checks host + storage together for deployment planning, if the storage pool is down/disconnected, it throws out every host as invalid, even with free CPU/RAM sitting right there. Quick checks 1) Run mount on each host, confirm NFS primary storage is mounted and not ro. 2) Check the NFS server itself is up and the export isn't full. 3) In CloudStack UI, check Infrastructure > Primary Storage, is it "Down" or in "Maintenance"? 4) Check dmesg for NFS timeout/stale handle errors around when this started. 5) Also worth checking for a storage tag mismatch since you've got mixed Xeon/EPYC hosts. Fix the storage connectivity and the capacity errors usually clear up on their own, no need to touch host capacity settings. We've run into this exact "storage goes read-only and kills capacity checks" scenario a few times managing CloudStack setups at AccuWeb.Cloud, happy to help troubleshoot further if you share mount | grep nfs output! GitHub link: https://github.com/apache/cloudstack/discussions/13596#discussioncomment-17624476 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
