LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Virtualization and Cloud (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/)
-   -   network statement in kickstart file only works with 192.168.122.0/24 default KVM network? (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/network-statement-in-kickstart-file-only-works-with-192-168-122-0-24-default-kvm-network-4175635158/)

KarolDworak 07-28-2018 08:33 PM
network statement in kickstart file only works with 192.168.122.0/24 default KVM network?
 
Trying to do an automated install using Kickstart file. But I want to use a different virt bride/switch/network than the default one created at 192.168.122.0/24. I have not been able to get that to happen and I need some help. When I use a Kickstart file with network info of 192.168.122.0/24 network the auto install finishes fine. If I use a kickstart file with network statement of 192.168.100.0/24 it does not work. When I create two VMs using the 192.168.122.0/24 kickstart file I end up with two VMs on that network. Next I edit the ifcfg-eth0 file of one of the VMs and reboot. But I cant even ping my own gateway 192.168.100.1 Host unreachable.

I can successfully ping 192.168.100.1 from host and the VM on the default KVM network. the VM on the default KVM network can ping the internet as well.

So my question is, What do I have to do to get that Virbr1 or virbr6 to say UP instead of DOWN like virbr0 does in the ip addr command. Thats the only difference I see in the output info.

Also, what are those vnet interfaces that spawn off of virbr0?

below is the Host info

ip addr
Code:
2: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether f4:06:69:59:d2:fb brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.11/24 brd 192.168.0.255 scope global noprefixroute dynamic wlp7s0
      valid_lft 74306sec preferred_lft 74306sec
    inet6 fe80::e98a:bdeb:2e38:e758/64 scope link noprefixroute
      valid_lft forever preferred_lft forever
3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:a3:b0:23 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: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:a3:b0:23 brd ff:ff:ff:ff:ff:ff
7: virbr6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:3f:2a:fe brd ff:ff:ff:ff:ff:ff
    inet 192.168.106.1/24 brd 192.168.106.255 scope global virbr6
      valid_lft forever preferred_lft forever
8: virbr6-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr6 state DOWN group default qlen 1000
    link/ether 52:54:00:3f:2a:fe brd ff:ff:ff:ff:ff:ff
9: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:e9:ee:13 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fee9:ee13/64 scope link
      valid_lft forever preferred_lft forever
16: virbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:a3:b0:23 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global virbr1
      valid_lft forever preferred_lft forever
17: virbr1-nic: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master virbr1 state DOWN group default qlen 1000
    link/ether 52:54:00:a3:b0:23 brd ff:ff:ff:ff:ff:ff
24: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:6c:ea:87 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe6c:ea87/64 scope link
      valid_lft forever preferred_lft forever
ip route
Code:
default via 192.168.0.1 dev wlp7s0 proto dhcp metric 600
192.168.0.0/24 dev wlp7s0 proto kernel scope link src 192.168.0.11 metric 600
192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1
192.168.106.0/24 dev virbr6 proto kernel scope link src 192.168.106.1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
brctl show
Code:
bridge name        bridge id                STP enabled        interfaces
virbr0                8000.525400a3b023        yes                virbr0-nic
                                                        vnet0
                                                        vnet1
virbr1                8000.525400a3b023        yes                virbr1-nic
virbr6                8000.5254003f2afe        yes                virbr6-nic
virsh net-list -all
Code:
Name                State      Autostart    Persistent
----------------------------------------------------------
 default              active    yes          yes
 outsider            active    yes          yes
 testernet            active    yes          yes
Thank you for your time.

KarolDworak 08-02-2018 08:16 AM
bump

KarolDworak 08-02-2018 08:33 AM
I tried doing a virt-install with a kickstart file set to 192.168.100.1/24 network directive and I used the 192.168.100.0/24 network in my virt-install command for my http path... I noticed a new tap interface showed up but its master is virbr0 ... I would need that to be virbr1 and Id be good to go?

Code:
9: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:e9:ee:13 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fee9:ee13/64 scope link
      valid_lft forever preferred_lft forever
11: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:47:be:45 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe47:be45/64 scope link
      valid_lft forever preferred_lft forever
Anyone know how to plug into the right virbr?


All times are GMT -5. The time now is 02:23 AM.