GitHub user akrasnov-drv added a comment to the discussion: CloudStack fails to start more VMs
I cleaned the env, restarted all components, and re-executed tests. After I recently recreated network with own offering that has VR HA and 65K bandwidth limit, and also set VR CPU to 2Ghz, the situation looks better. Now the main problems I see: - part of VMs does not get IP from dnsmasq - numerous STATICNAT.ENABLE errors I tried executing dhclient there, and got no IP either. Expectedly, reboot did not help. But if I execute VM reinstall from UI, it sometimes fixes the issue of missing IP. I'm attaching cloud.log (it's packed as originally it's 180Mb) from VR and also dnsmasq.log I found 59 hosts mentioned in dnsmasq.log at the same time there were more than 150 VMs created, about 80 running and destroyed, and the rest stayed in Starting state (console is not available yet after 3-30 min) [cloud.log.1.gz](https://github.com/user-attachments/files/18442832/cloud.log.1.gz) [cloud.log.gz](https://github.com/user-attachments/files/18442989/cloud.log.gz) [dnsmasq.log](https://github.com/user-attachments/files/18442992/dnsmasq.log) . GitHub link: https://github.com/apache/cloudstack/discussions/10184#discussioncomment-11857231 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
