On Tuesday, April 27, 2021 10:08:55 PM CEST Kevin Fenzi wrote: > On Tue, Apr 27, 2021 at 08:01:18AM +0200, Pavel Raiskup wrote: > > > > Meh, sorry for complications, I'll try to be much more careful next time. > > > > Perhaps you don't have to hurry up for the fix since we have the rest of > > the stack (3 more boxes) that we still have to setup via ansible.. So > > there's a chance that we'll break something else :-(. > > > > I mean, because ipv4 addresses (32+ for each hypervisor) aren't available > > I'm trying other things. Qemu port-forwarding to libvirt guests didn't > > work for me (but I'll try better), ipv6 guest access did not work either > > (I'll retry as well), so perhaps we'll have to try iptables hacks or > > setup VPN(s) eventually. I'm afraid all those configuration tasks aren't > > really that trivial to be 100% sure that no mistake happens :-(. > > I would think a bridge would work fine and just assign the guests ipv6 > addresses? But I agree it will take some testing/tweaking. ;( Indeed, I was able to configure one VM like that now - so I obviously did something wrong before (I tested F33, now with F34, but I doubt this makes any difference). So ... I think I shouldn't break the hypervisors anymore :-). Pavel _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
