GitHub user nickaccuweb added a comment to the discussion: CloudStack-KVM integration for Veeam B&R
@yadvr Thanks for testing this again with CloudStack 4.23 GA and sharing the details. Based on your latest test, this does not appear to be related to HA. The worker executes shutdown -h now, but CloudStack is not changing the instance state from Running to Stopped, so Veeam cannot continue until the instance is manually stopped. Could you please check the following immediately after the worker shuts down? - Run virsh domstate <worker-vm-name> on the KVM host. - Check management-server.log for the worker VM, especially entries related to VirtualMachinePowerStateSyncImpl or PowerReportMissing. - Confirm whether CloudStack still shows the instance as Running while virsh shows it as shut off. If possible, please share these log entries. This will help confirm whether the issue is with the VM shutdown itself or CloudStack synchronizing the VM state. Regarding the IP address, I agree that the same static IP should also be correctly assigned/reserved for the worker in CloudStack, since Veeam is using the IP reported by CloudStack. Regards, AccuWeb.Cloud Team GitHub link: https://github.com/apache/cloudstack/discussions/12869#discussioncomment-18781567 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
