ramthota27 opened a new issue, #12592:
URL: https://github.com/apache/cloudstack/issues/12592

   Hello everyone,
   
   I've installed Apache CloudStack 4.20 and added the KVM host. I see two 
system VMs running on the CloudStack UI, but the agent state appears greyed 
out. After following Copilot for troubleshooting, I found that the management 
server isn't able to communicate with the system VMs.
   
   I've set the traffic labels in the physical network as follows:
   
   Management traffic = cloudbr0
   Private network = cloudbr0
   Public/shared network = cloudbr0
   Guest (VM data traffic) = cloudbr1
   
   My KVM host is operational with virt services and has two NICs: ens192 and 
ens224. Both are configured as bridge networks—ens192 is linked to cloudbr0 and 
ens224 to cloudbr1. Both bridges are up, with cloudbr0 assigned IP 
10.80.148.30, while cloudbr1 has no IP. The network YAML file is shown in the 
attached image.
   
   The output of "ip a" on the KVM host is also in the image.
   
   I've noticed an extra NIC named cloud0 keeps getting created automatically, 
even after deleting it (ip link delete cloud0) multiple times. This cloud0 
interface is interfering with my KVM and Apache CloudStack setup. How can I 
permanently remove or stop it from being auto-generated, so the management 
server communicates with cloudbr0 instead?
   
   Since the agent state on the system VMs is disabled/greyed out, the Upload 
ISO option is also disabled in the UI. Any guidance on resolving this issue 
would be appreciated.
   
   Thank you
   With Regards
   Ram 
   
   <img width="870" height="1043" alt="Image" 
src="https://github.com/user-attachments/assets/3deb9c00-77e8-49e0-8487-d67d7204668b";
 />
   <img width="1550" height="848" alt="Image" 
src="https://github.com/user-attachments/assets/2bbd9c4a-1b7a-4135-a05a-12216714b650";
 />


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to