You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I failed to add storage, I clicked on return to fix and then clicked on next again. Add Host reported an error again, stating that it already exists. I think this is a logical bug in the web UI.
this is a known UI bug: #8597
please ignore it for now
Cloudstack agent has been successfully added, but it is always in an initialized state. Because I am testing cloudstack in a virtual machine, which belongs to nested virtualization. Cloudstack was executing LSCPU related instructions and attempted to obtain CPU related information, but failed. Causing the cloudstack agent to remain in the initialization phase forever. Ultimately, the storage function could not be added properly.
Cloudstack agent has been successfully added, but it is always in an initialized state. Because I am testing cloudstack in a virtual machine, which belongs to nested virtualization. Cloudstack was executing LSCPU related instructions and attempted to obtain CPU related information, but failed. Causing the cloudstack agent to remain in the initialization phase forever. Ultimately, the storage function could not be added properly. agent.log
agent.log looks ok, although there are some errors.
is the host Up ? check Infrastructure -> Hosts
No, I don't know where the mistake was, I feel like there's still a long way to go.
The main issue is the lack of some components, but I don't know what they are.
Add primary storage
Add secondary storage
Enable the zone
@0xdddddddd I tried using Debian12 as a KVM host with CloudStack 4.19.0.1. Addhost failed initially, then I installed the cpu-checker. Then executed the cloudstack-setup-agent , and the host is visible in the cloudstack UI now.
@0xdddddddd Yes, it's because the current deb packages are only tested, used and supported for Ubuntu that you're welcome to use to an out-of-box installation experience, support for Debian is largely experimental and it's possible (as you've found out the hard way) Debian needs additional packages and specific configuration.
Most of us may not have any incentive to support Debian (yet), and it's hard to work on all the issues, features and requirements that each and every user wants in our 'free time'. We want to help but as much frustrating it is for you, it's equally or may be more frustrating that we can't help or support you in something that's not supported (yet). As a community-driven opensource project, our community of users help solve such problems with us and we welcome any and all feedback and contributions, and pull requests.
Activity
boring-cyborg commentedon May 3, 2024
Thanks for opening your first issue here! Be sure to follow the issue template!
weizhouapache commentedon May 3, 2024
@0xdddddddd
can you check if file
/dev/kvmexists ?weizhouapache commentedon May 3, 2024
that's strange, the logs show
can you re-add the host ?
weizhouapache commentedon May 3, 2024
this is a known UI bug: #8597
please ignore it for now
weizhouapache commentedon May 3, 2024
agent.log looks ok, although there are some errors.
is the host Up ? check Infrastructure -> Hosts
weizhouapache commentedon May 3, 2024
Add primary storage
Add secondary storage
Enable the zone
rajujith commentedon May 7, 2024
@0xdddddddd I tried using Debian12 as a KVM host with CloudStack 4.19.0.1.
Addhostfailed initially, then I installed thecpu-checker. Then executed thecloudstack-setup-agent, and the host is visible in the cloudstack UI now.yadvr commentedon May 15, 2024
@0xdddddddd Yes, it's because the current deb packages are only tested, used and supported for Ubuntu that you're welcome to use to an out-of-box installation experience, support for Debian is largely experimental and it's possible (as you've found out the hard way) Debian needs additional packages and specific configuration.
Most of us may not have any incentive to support Debian (yet), and it's hard to work on all the issues, features and requirements that each and every user wants in our 'free time'. We want to help but as much frustrating it is for you, it's equally or may be more frustrating that we can't help or support you in something that's not supported (yet). As a community-driven opensource project, our community of users help solve such problems with us and we welcome any and all feedback and contributions, and pull requests.