-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to list VMs on the remote KVM host, for import #8704
Comments
Tested the issue and was able to reproduce the issue |
@sureshanaparti @kiranchavala @sureshanaparti
|
@weizhouapache Tried with listen_tcp = 1, but still unable to see list the stopped VMs. with listen_tcp = 0, it's throwing exception and fails with Request Failed (530) error. I think, it's better to show the appropriate message if failed to connect to the remote host's qemu. |
the issue is still present Steps followed
Launch a centos 7 vm and install the following packages
|
@kiranchavala but the vm is not compatible with cloudstack. can you share the vm xml dump ?
|
virsh dumpxml --security-info testkiran dumpxml
|
@kiranchavala |
@kiranchavala |
@sureshanaparti are you going to work on this issue, or should we have @vishesh92 work on this? Thanks. |
@kiranchavala |
Tested with latest 4.19, able to list the VMs (with listen_tcp = 1). Noticed inappropriate error messages when remote host is not reachable, etc - improved messages / logs in this PR #9204. |
Appropriate messages, are addressed in PR #9204. |
fixed in #9204 |
Failed to list the VMs in remote KVM host, for importing them to CloudStack.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
KVM hypervisor / Advanced Zone
OS / ENVIRONMENT
Tried on MS, KVM Hosts on Ubuntu 22.04 & MS / KVM Hosts on Rocky Linux 8
SUMMARY
Failed to list the VMs in remote KVM host, for importing them to CloudStack.
API cmd has the following parameters - zoneid, host, username, password, hypervisor=kvm.
API Response:
Exception in Logs:
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: