I had tested against RHEL9 in the past, my notes with x86/KVM are here, see if
it helps:
https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c#file-el9-or-rhel9-acs
Network configuration was the tricky bit for me and I had to use nmcli to
configure that. As I can see your cloudbr0 is 'DOWN', there's something not
properly configured in your setup.
Regards.
________________________________
From: Fariborz Navidan <mdvlinqu...@gmail.com>
Sent: Sunday, July 21, 2024 04:39
To: dev@cloudstack.apache.org <dev@cloudstack.apache.org>
Subject: Management server cannot connect to KVM host on AlmaLinux 9
Hello All,
I have installed a fresh 4.18.2.1 on AlmaLinux 9. Management server and KVM
host is installed on the same node. Adding host was failed during first
time configuration wizard. After that, I ran following commands on the
server as per suggested by one of members in the users mailing list, Wei:
cloudstack-setup-agent
systemctl mask virtqemud.socket virtqemud-ro.socket
virtqemud-admin.socket virtqemud virtnetworkd virtstorage
The host is now automatically added to the management and is showing in UI
but it is in Alert state and management server is unable to connect to it.
Below are errors I have in the agent.log and management-server.log file. I
will highly appreciate if someone can help me put my server to working.
agent.log:
2024-07-20 14:41:55,510 ERROR [kvm.resource.LibvirtConnection]
(Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: invalid
connection pointer in virConnectGetVersion
2024-07-20 14:41:55,459 ERROR [utils.linux.KVMHostInfo]
(Agent-Handler-1:null) (logid:) Unable to retrieve the CPU speed from lscpu.
2024-07-21 00:39:20,270 WARN [cloud.agent.Agent] (Agent-Handler-2:null)
(logid:) Threw away a startup answer because we're reconnecting.
2024-07-21 00:39:20,289 WARN [cloud.agent.Agent] (Agent-Handler-4:null)
(logid:04ac4783) Unable to send response: null
management-server:
2024-07-21 00:38:27,899 WARN [c.c.a.AlertManagerImpl]
(AgentConnectTaskPool-101:ctx-113ad44d) (logid:a2169999) alertType=[7]
dataCenterId=[1] podId=[1] clusterId=[null] message=[Incorrect Network
setup on agent, Reinitialize agent after network names are setup, details :
Can not find network: cloudbr0].
2024-07-21 00:39:21,755 ERROR [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-19:null) (logid:) Failed to send server's
CLOSE message due to socket channel's failure.
I have setup network using nmcli with following commands:
nmcli connection add type vlan con-name vlan427 ifname vlan427 vlan.parent
eth0 vlan.id 427
nmcli con up vlan427
nmcli con add ifname cloudbr0 type bridge con-name cloudbr0 autoconnect yes
nmcli con add type bridge-slave ifname vlan427 master cloudbr0 autoconnect
yes con-name br-vlan427
nmcli connection up cloudbr0
Below is output of "ip a" and "brctl show" commands:
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 3c:7c:3f:bb:16:88 brd ff:ff:ff:ff:ff:ff
altname enp5s0
inet 149.50.116.112/24 brd 149.50.116.255 scope global noprefixroute
eth0
valid_lft forever preferred_lft forever
inet6 2a03:cfc0:8000:2e::9532:7470/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::3e7c:3fff:febb:1688/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
link/ether e6:5e:4e:b9:48:e3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global noprefixroute
cloudbr0
valid_lft forever preferred_lft forever
6: cloud0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN group default qlen 1000
link/ether 4e:63:4a:80:21:74 brd ff:ff:ff:ff:ff:ff
inet 169.254.0.1/16 scope global cloud0
valid_lft forever preferred_lft forever
inet6 fe80::4c63:4aff:fe80:2174/64 scope link
valid_lft forever preferred_lft forever
# brctl show
bridge name bridge id STP enabled interfaces
cloud0 8000.000000000000 no
cloudbr0 8000.000000000000 yes
Any help would be highly appreciated.
Regards.
