On 4/4/23 12:44, Peter Boy wrote:
didn't find anything usefulAm 04.04.2023 um 17:51 schrieb Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx>: Fedora 37 with four qemu/kvm virtual machines. Trying to get internet access from the vm's. Found some advice about using systemd-networkd instead of NetworkManager.Following „some advice“ is usually a good chance for adventure. What was wrong with using Fedora documentation?
Lost internet connection with the host. Restored with NetworkManager. Further research on NetworkManager gets into a tangle with ifcfg scripts and the apparent migration to keyfiles. Totally confused. Can only start the virtual machines if the network device is removed. ---------- VM centos8 failed to start Requested operation is not valid: network 'default' is not active --------- >From cockpit on the web interface tried some of the options with bond looking like a possibility --------- 11:37 AM <info> [1680622647.3084] dhcp6 (bond0): state changed new lease, address=2600:1702:4860:9dd0::34 NetworkManager 11:27 AM <info> [1680622058.5768] manager: (vnet4): new Tun device (/org/freedesktop/NetworkManager/Devices/9) NetworkManager 11:07 AM <info> [1680620850.7934] dhcp6 (bond0): state changed new lease, address=2600:1702:4860:9dd0::34 NetworkManager 11:02 AM <info> [1680620556.1938] manager: (vnet3): new Tun device (/org/freedesktop/NetworkManager/Devices/8) NetworkManager 11:01 AM <info> [1680620475.6234] manager: (vnet2): new Tun device (/org/freedesktop/NetworkManager/Devices/7) NetworkManager 10:40 AM <info> [1680619204.0043] dhcp6 (bond0): state changed new lease, address=2600:1702:4860:9dd0::34 NetworkManager -------- but -------- VM centos8 failed to start Unable to add bridge bond0 port vnet5: Operation not supported ---------- The options seem to be endless with no success. Advice?All these messages are nice, but meaningless for troubleshooting. The first thing is how the host was installed and how the network was configured, as a first start the output of „ip a“. The second one is, how you configured the virtual internet connection of a vm.
The host is a general use server installation with kde desktop added.
First round was from a virt-manager start with add
hardware device->network. First selection "Virtual Network
'default':NAT(Inactive)" with "Hypervisor default" That gave the
message first quoted.
Requested operation is not valid: network 'default' is not active
The bridge setup selection in virt-manager didn't work either.
looked at the networking from cockpit. Got a connection on a vm from cockpit unable to replicate on a second. From the successful connection
from host
----
~]# 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master virbr0 state UP group default qlen 1000
link/ether 18:60:24:b1:dc:82 brd ff:ff:ff:ff:ff:ff
altname enp0s25
6: virbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:28:a4:bf brd ff:ff:ff:ff:ff:ff
20: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether b6:8e:92:80:04:f2 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.155/24 brd 192.168.1.255 scope global dynamic noprefixroute virbr0
valid_lft 45172sec preferred_lft 45172sec
inet6 2600:1702:4860:9dd0::2b/128 scope global dynamic noprefixroute
valid_lft 2904sec preferred_lft 2904sec
inet6 2600:1702:4860:9dd0:f790:2432:acf9:c8e8/64 scope global dynamic noprefixroute
valid_lft 3601sec preferred_lft 3601sec
inet6 fe80::c7d1:6569:1c43:14ff/64 scope link noprefixroute
valid_lft forever preferred_lft forever
25: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:19:3b:a3 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe19:3ba3/64 scope link
valid_lft forever preferred_lft forever
------
>From VM
_____
~]# 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: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:eb:41:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:54:00:19:3b:a3 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.167/24 brd 192.168.1.255 scope global dynamic noprefixroute enp3s0
valid_lft 45641sec preferred_lft 45641sec
inet6 2600:1702:4860:9dd0::3b/128 scope global dynamic noprefixroute
valid_lft 2252sec preferred_lft 2252sec
inet6 2600:1702:4860:9dd0:7067:8cd2:abb9:1fe4/64 scope global dynamic noprefixroute
valid_lft 3144sec preferred_lft 3144sec
inet6 fe80::9f5f:eec7:3bc9:38e5/64 scope link noprefixroute
valid_lft forever preferred_lft forever
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
