Hey Nux, thanks a bunch! You totally saved the day. Perhaps it would be beneficial to include these points in the documentation.
Jon On Mon, Sep 2, 2024 at 3:10 AM Nux <n...@li.nux.ro> wrote: > Add the following to /etc/libvirt/libvirt.conf : > remote_mode="legacy" > > Then restart services. > > On 2024-09-01 16:40, Joan g wrote: > > Hi > > > > Yes done but masking them did not help. Still connection refused for > > sudo/root > > > > Jon > > > > On Sun, Sep 1, 2024 at 8:39 PM Fariborz Navidan <mdvlinqu...@gmail.com> > > wrote: > > > >> Hi. > >> > >> > >> Run the following command to mask the necessary services and let me > >> know > >> the outcome. > >> > >> > >> systemctl mask virtqemud.socket virtqemud-ro.socket > >> > > virtqemud-admin.socket virtqemud virtnetworkd virtstoraged > >> > >> Regards. > >> > >> On Sun, 1 Sept 2024, 16:42 Joan g, <joang...@gmail.com> wrote: > >> > >> > Hi Fariborz, > >> > > >> > Thank you, I was able to manage bridge configurations. > >> > > >> > Now I am not able to add the host to pool. Agent logs print below: > >> > > >> > 2024-09-01 14:03:17,273 ERROR [cloud.agent.AgentShell] (main:null) > >> (logid:) > >> > Unable to start agent: > >> > com.cloud.utils.exception.CloudRuntimeException: Failed to connect > socket > >> > to '/var/run/libvirt/virtqemud-sock': Connection refused > >> > at > >> > > >> > > >> > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:1153) > >> > at com.cloud.agent.Agent.<init>(Agent.java:193) > >> > at > com.cloud.agent.AgentShell.launchNewAgent(AgentShell.java:452) > >> > at > >> > > com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:431) > >> > at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:415) > >> > at com.cloud.agent.AgentShell.start(AgentShell.java:511) > >> > at com.cloud.agent.AgentShell.main(AgentShell.java:541) > >> > > >> > Did I miss some configs? > >> > > >> > I noticed that I can't run `virsh` as the root user or with `sudo`: > >> > > >> > # virsh list --all > >> > error: failed to connect to the hypervisor > >> > error: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': > >> > Connection refused > >> > > >> > But as a user in wheel group its successful > >> > $ virsh list --all > >> > Id Name State > >> > -------------------- > >> > > >> > > >> > *Jon* > >> > > >> > > >> > On Tue, Aug 27, 2024 at 11:16 PM Fariborz Navidan < > mdvlinqu...@gmail.com > >> > > >> > wrote: > >> > > >> > > Hello, > >> > > > >> > > I was able to configure Cloudstack 4.18 on AlmaLinux 9 last month.I > >> used > >> > > the following nmcli commands to create the bridge: > >> > > > >> > > nmcli con add ifname cloudbr0 type bridge con-name cloudbr0 > autoconnect > >> > yes > >> > > nmcli con add type bridge-slave ifname eth0 master cloudbr0 > >> > > nmcli con up cloudbr0 > >> > > > >> > > After creating the bridge, remove any assigned IP from the slave > >> > interface > >> > > (e.g eth0) and assign it to the bridge. > >> > > > >> > > Regards. > >> > > > >> > > On Tue, Aug 27, 2024 at 3:59 PM Joan g <joang...@gmail.com> wrote: > >> > > > >> > > > Hello Community, > >> > > > > >> > > > Could someone provide guidance on setting up a bridge for the > latest > >> > > > AlmaLinux 9.4? When I use `nmcli` to create a bridge, the ethernet > >> > > > interfaces keep going down, and I'm unable to bring them online. > Any > >> > > > suggestions on working `nmcli` commands would be greatly > appreciated > >> > and > >> > > > helpful. > >> > > > > >> > > > Regards, > >> > > > Jon > >> > > > > >> > > > >> > > >> >
