This has been working this whole test cycle until today and now I'm stumped that it's not working.
Host = Fedora 22 up to date, x86_64 Guest = managed by virt-manager, also Fedora 22
1. Install Fedora 22 on the host 2. dnf group install virtualization 3. reboot [1] to get the NAT option for the VM 4. Create a VM and use the default network settings which uses NAT
Actual results: - Guest has no Internet access.
- host (192.168.1.128) can't ssh to guest (192.168.122.103) # ssh root@192.168.122.103 ssh: connect to host 192.168.122.103 port 22: No route to host
- Guest can ssh into the host, i.e. # ssh root@192.168.1.128
On the host: [root@f22m]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether c8:2a:14:02:88:99 brd ff:ff:ff:ff:ff:ff 3: wlp3s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e0:f8:47:39:5d:de brd ff:ff:ff:ff:ff:ff inet 192.168.1.128/24 brd 192.168.1.255 scope global dynamic wlp3s0b1 valid_lft 84895sec preferred_lft 84895sec inet6 fe80::e2f8:47ff:fe39:5dde/64 scope link valid_lft forever preferred_lft forever 4: virbr0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 52:54:00:dd:30:37 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 5: virbr0-nic@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:dd:30:37 brd ff:ff:ff:ff:ff:ff 7: vnet0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master virbr0 state UNKNOWN group default qlen 500 link/ether fe:54:00:6d:40:9e brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe6d:409e/64 scope link valid_lft forever preferred_lft forever
On the guest: [root@f22v]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: ens8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6d:40:9e brd ff:ff:ff:ff:ff:ff inet 192.168.122.103/24 brd 192.168.122.255 scope global dynamic ens8 valid_lft 3198sec preferred_lft 3198sec inet6 fe80::5054:ff:fe6d:409e/64 scope link valid_lft forever preferred_lft forever 3: virbr0@NONE: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default link/ether 52:54:00:25:45:a5 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 4: virbr0-nic@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:25:45:a5 brd ff:ff:ff:ff:ff:ff
Previously, Virtual Network Interface Device model was set to virtio and that was working but isn't now, so I flipped it to hypervisor default and when I click apply the setting snaps to rtl8139. But this doesn't change things.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1224398
On Fri, 2015-05-22 at 14:29 -0600, Chris Murphy wrote:
This has been working this whole test cycle until today and now I'm stumped that it's not working.
On the host: [root@f22m]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether c8:2a:14:02:88:99 brd ff:ff:ff:ff:ff:ff 3: wlp3s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e0:f8:47:39:5d:de brd ff:ff:ff:ff:ff:ff inet 192.168.1.128/24 brd 192.168.1.255 scope global dynamic wlp3s0b1 valid_lft 84895sec preferred_lft 84895sec inet6 fe80::e2f8:47ff:fe39:5dde/64 scope link valid_lft forever preferred_lft forever 4: virbr0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 52:54:00:dd:30:37 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 5: virbr0-nic@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:dd:30:37 brd ff:ff:ff:ff:ff:ff 7: vnet0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master virbr0 state UNKNOWN group default qlen 500 link/ether fe:54:00:6d:40:9e brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe6d:409e/64 scope link valid_lft forever preferred_lft forever
On the guest: [root@f22v]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: ens8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6d:40:9e brd ff:ff:ff:ff:ff:ff inet 192.168.122.103/24 brd 192.168.122.255 scope global dynamic ens8 valid_lft 3198sec preferred_lft 3198sec inet6 fe80::5054:ff:fe6d:409e/64 scope link valid_lft forever preferred_lft forever 3: virbr0@NONE: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default link/ether 52:54:00:25:45:a5 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 4: virbr0-nic@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:25:45:a5 brd ff:ff:ff:ff:ff:ff
Late reply, but this looks like a classic case of https://bugzilla.redhat.com/show_bug.cgi?id=1146284 / https://bugzilla.redhat.com/show_bug.cgi?id=1146232 . Taking down virbr0 in the guest should solve it.