hobyte

I have the same problem on openSUSE Tumbleweed . ``` $ sudo -E talosctl cluster create --provisioner=qemu --with-uefi=false validating CIDR and reserving IPs generating PKI and tokens creating state directory...

`sudo --preserve-env=HOME talosctl cluster create --provisioner=qemu` worked for me to keep `$HOME`

I have the same Issue on openSUSE tumblewee. Starting the cluster in Qemu quits with an error message: ``` » sudo -E talosctl cluster create --provisioner=qemu --with-uefi=false validating CIDR and...

> I got one small step ahead. Previously the log of the master node would repeat this forever: > > ``` > [ 72.414966] [talos] failed looking up "pool.ntp.org", ignored...

See the [Development Guide](https://www.talos.dev/v1.1/advanced/developing-talos/#console-logs)

Interesting, how long do you wait for the logs? It might take some time for Talos to start up.

I just discovered the load balancer cannot reach the vms: ``` $ cat clusters/talos-default/lb.log 2022/06/26 00:00:07 healthcheck failed for "10.5.0.2:6443": dial tcp 10.5.0.2:6443: connect: connection refused 2022/06/26 00:00:08 healthcheck failed...

Im just out of Ideas on how to find the problem. I think its the cni, but I see no logs and don't know how to debug it.

Yeah, I tested it on Ubuntu and it works fine. It just bothers me that i cannot get behind the problem. It would be nice to not have to use...

I have one Problem Identified: **Deactivating firewalld** solves the connection problem on my opensuse system. Now on to finding a solution.