Network Bridge for VM not working after reboot

Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have a CentOS 7 host with a network bridge set up for guest VM's to use. All was well until a recent reboot. After the reboot, the guest VM does not have internet access, nor can it ping other local addresses (and other local machines cannot ping the guest) The host machine has internet access, and I can SSH into it from within the LAN.
I have the following files in /etc/sysconfig/network-scripts on the host system:
ifcfg-br0:
STP=no
TYPE=Bridge
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=br0
UUID=3feaa236-2ea8-4024-9667-d446e952fc44
DEVICE=br0
ONBOOT=yes
IPADDR=192.168.1.130
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
ONBOOT=yes
ifcfg-bridge-slave-enp0s25:
TYPE=Ethernet
NAME=bridge-slave-enp0s25
UUID=b9e60eb8-b9f8-497c-89f6-40d60b4bced8
DEVICE=enp0s25
ONBOOT=yes
BRIDGE=br0
ifcfg-enp0s25:
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s25
UUID=a4799b47-9042-4a95-925c-d1d364fc99de
DEVICE=enp0s25
ONBOOT=yes
IPADDR=192.168.1.131
PREFIX=24
GATEWAY=192.168.1.1
DNS1=8.8.8.8
DNS2=8.8.4.4
IPV6_PRIVACY=no
GUEST SYSTEM'S /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="eth0"
UUID="7c2087a0-7d4b-4e3a-ac71-07b8dcac07ad"
DEVICE="eth0"
ONBOOT="yes"
IPADDR="192.168.1.132"
PREFIX="24"
GATEWAY="192.168.1.1"
DNS1="8.8.8.8"
DNS2="8.8.4.4"
The VM was installed with virt-install using the --network bridge=br0 argument, and it was able to access the web, serve web pages via apache, and it could be pinged my other computer in the LAN.
What can I do next to get this guest VM back on the network through the br0 network bridge?
networking kvm bridge libvirt virsh
add a comment |
I have a CentOS 7 host with a network bridge set up for guest VM's to use. All was well until a recent reboot. After the reboot, the guest VM does not have internet access, nor can it ping other local addresses (and other local machines cannot ping the guest) The host machine has internet access, and I can SSH into it from within the LAN.
I have the following files in /etc/sysconfig/network-scripts on the host system:
ifcfg-br0:
STP=no
TYPE=Bridge
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=br0
UUID=3feaa236-2ea8-4024-9667-d446e952fc44
DEVICE=br0
ONBOOT=yes
IPADDR=192.168.1.130
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
ONBOOT=yes
ifcfg-bridge-slave-enp0s25:
TYPE=Ethernet
NAME=bridge-slave-enp0s25
UUID=b9e60eb8-b9f8-497c-89f6-40d60b4bced8
DEVICE=enp0s25
ONBOOT=yes
BRIDGE=br0
ifcfg-enp0s25:
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s25
UUID=a4799b47-9042-4a95-925c-d1d364fc99de
DEVICE=enp0s25
ONBOOT=yes
IPADDR=192.168.1.131
PREFIX=24
GATEWAY=192.168.1.1
DNS1=8.8.8.8
DNS2=8.8.4.4
IPV6_PRIVACY=no
GUEST SYSTEM'S /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="eth0"
UUID="7c2087a0-7d4b-4e3a-ac71-07b8dcac07ad"
DEVICE="eth0"
ONBOOT="yes"
IPADDR="192.168.1.132"
PREFIX="24"
GATEWAY="192.168.1.1"
DNS1="8.8.8.8"
DNS2="8.8.4.4"
The VM was installed with virt-install using the --network bridge=br0 argument, and it was able to access the web, serve web pages via apache, and it could be pinged my other computer in the LAN.
What can I do next to get this guest VM back on the network through the br0 network bridge?
networking kvm bridge libvirt virsh
@roaima Hey, I had actually deleted that comment and up voted you. It appears that this has actually restored my network access to the VM. I hooked up a monitor and keyboard to that server and rebooted, and everything was perfect. I think that the server itself just appeared to be on (orange power light) but didn't actually reboot. If you'd like to reply with an answer, I'll gladly accept.
– Joshua Schlichting
Mar 10 at 23:52
add a comment |
I have a CentOS 7 host with a network bridge set up for guest VM's to use. All was well until a recent reboot. After the reboot, the guest VM does not have internet access, nor can it ping other local addresses (and other local machines cannot ping the guest) The host machine has internet access, and I can SSH into it from within the LAN.
I have the following files in /etc/sysconfig/network-scripts on the host system:
ifcfg-br0:
STP=no
TYPE=Bridge
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=br0
UUID=3feaa236-2ea8-4024-9667-d446e952fc44
DEVICE=br0
ONBOOT=yes
IPADDR=192.168.1.130
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
ONBOOT=yes
ifcfg-bridge-slave-enp0s25:
TYPE=Ethernet
NAME=bridge-slave-enp0s25
UUID=b9e60eb8-b9f8-497c-89f6-40d60b4bced8
DEVICE=enp0s25
ONBOOT=yes
BRIDGE=br0
ifcfg-enp0s25:
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s25
UUID=a4799b47-9042-4a95-925c-d1d364fc99de
DEVICE=enp0s25
ONBOOT=yes
IPADDR=192.168.1.131
PREFIX=24
GATEWAY=192.168.1.1
DNS1=8.8.8.8
DNS2=8.8.4.4
IPV6_PRIVACY=no
GUEST SYSTEM'S /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="eth0"
UUID="7c2087a0-7d4b-4e3a-ac71-07b8dcac07ad"
DEVICE="eth0"
ONBOOT="yes"
IPADDR="192.168.1.132"
PREFIX="24"
GATEWAY="192.168.1.1"
DNS1="8.8.8.8"
DNS2="8.8.4.4"
The VM was installed with virt-install using the --network bridge=br0 argument, and it was able to access the web, serve web pages via apache, and it could be pinged my other computer in the LAN.
What can I do next to get this guest VM back on the network through the br0 network bridge?
networking kvm bridge libvirt virsh
I have a CentOS 7 host with a network bridge set up for guest VM's to use. All was well until a recent reboot. After the reboot, the guest VM does not have internet access, nor can it ping other local addresses (and other local machines cannot ping the guest) The host machine has internet access, and I can SSH into it from within the LAN.
I have the following files in /etc/sysconfig/network-scripts on the host system:
ifcfg-br0:
STP=no
TYPE=Bridge
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=br0
UUID=3feaa236-2ea8-4024-9667-d446e952fc44
DEVICE=br0
ONBOOT=yes
IPADDR=192.168.1.130
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
ONBOOT=yes
ifcfg-bridge-slave-enp0s25:
TYPE=Ethernet
NAME=bridge-slave-enp0s25
UUID=b9e60eb8-b9f8-497c-89f6-40d60b4bced8
DEVICE=enp0s25
ONBOOT=yes
BRIDGE=br0
ifcfg-enp0s25:
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s25
UUID=a4799b47-9042-4a95-925c-d1d364fc99de
DEVICE=enp0s25
ONBOOT=yes
IPADDR=192.168.1.131
PREFIX=24
GATEWAY=192.168.1.1
DNS1=8.8.8.8
DNS2=8.8.4.4
IPV6_PRIVACY=no
GUEST SYSTEM'S /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="eth0"
UUID="7c2087a0-7d4b-4e3a-ac71-07b8dcac07ad"
DEVICE="eth0"
ONBOOT="yes"
IPADDR="192.168.1.132"
PREFIX="24"
GATEWAY="192.168.1.1"
DNS1="8.8.8.8"
DNS2="8.8.4.4"
The VM was installed with virt-install using the --network bridge=br0 argument, and it was able to access the web, serve web pages via apache, and it could be pinged my other computer in the LAN.
What can I do next to get this guest VM back on the network through the br0 network bridge?
networking kvm bridge libvirt virsh
networking kvm bridge libvirt virsh
asked Mar 10 at 18:43
Joshua SchlichtingJoshua Schlichting
15618
15618
@roaima Hey, I had actually deleted that comment and up voted you. It appears that this has actually restored my network access to the VM. I hooked up a monitor and keyboard to that server and rebooted, and everything was perfect. I think that the server itself just appeared to be on (orange power light) but didn't actually reboot. If you'd like to reply with an answer, I'll gladly accept.
– Joshua Schlichting
Mar 10 at 23:52
add a comment |
@roaima Hey, I had actually deleted that comment and up voted you. It appears that this has actually restored my network access to the VM. I hooked up a monitor and keyboard to that server and rebooted, and everything was perfect. I think that the server itself just appeared to be on (orange power light) but didn't actually reboot. If you'd like to reply with an answer, I'll gladly accept.
– Joshua Schlichting
Mar 10 at 23:52
@roaima Hey, I had actually deleted that comment and up voted you. It appears that this has actually restored my network access to the VM. I hooked up a monitor and keyboard to that server and rebooted, and everything was perfect. I think that the server itself just appeared to be on (orange power light) but didn't actually reboot. If you'd like to reply with an answer, I'll gladly accept.
– Joshua Schlichting
Mar 10 at 23:52
@roaima Hey, I had actually deleted that comment and up voted you. It appears that this has actually restored my network access to the VM. I hooked up a monitor and keyboard to that server and rebooted, and everything was perfect. I think that the server itself just appeared to be on (orange power light) but didn't actually reboot. If you'd like to reply with an answer, I'll gladly accept.
– Joshua Schlichting
Mar 10 at 23:52
add a comment |
1 Answer
1
active
oldest
votes
I don't have CentOS to hand, but I can speak from extensive experience in Debian.
Generally speaking, bridge configurations require that the interface itself (in your case enp0s25) is not configured with an IP address. The physical interface remains unconfigured but UP and RUNNING, and the IP configuration for the host gets applied to logical bridge interface instead.
I'd suggest changing the file ifcfg-enp0s25 to have ONBOOT=no and trying again.
If that doesn't work, delete the ifcfg-enp0s25 file (ie move it some place safe) because you've got the requisite settings in the slave file.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505507%2fnetwork-bridge-for-vm-not-working-after-reboot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't have CentOS to hand, but I can speak from extensive experience in Debian.
Generally speaking, bridge configurations require that the interface itself (in your case enp0s25) is not configured with an IP address. The physical interface remains unconfigured but UP and RUNNING, and the IP configuration for the host gets applied to logical bridge interface instead.
I'd suggest changing the file ifcfg-enp0s25 to have ONBOOT=no and trying again.
If that doesn't work, delete the ifcfg-enp0s25 file (ie move it some place safe) because you've got the requisite settings in the slave file.
add a comment |
I don't have CentOS to hand, but I can speak from extensive experience in Debian.
Generally speaking, bridge configurations require that the interface itself (in your case enp0s25) is not configured with an IP address. The physical interface remains unconfigured but UP and RUNNING, and the IP configuration for the host gets applied to logical bridge interface instead.
I'd suggest changing the file ifcfg-enp0s25 to have ONBOOT=no and trying again.
If that doesn't work, delete the ifcfg-enp0s25 file (ie move it some place safe) because you've got the requisite settings in the slave file.
add a comment |
I don't have CentOS to hand, but I can speak from extensive experience in Debian.
Generally speaking, bridge configurations require that the interface itself (in your case enp0s25) is not configured with an IP address. The physical interface remains unconfigured but UP and RUNNING, and the IP configuration for the host gets applied to logical bridge interface instead.
I'd suggest changing the file ifcfg-enp0s25 to have ONBOOT=no and trying again.
If that doesn't work, delete the ifcfg-enp0s25 file (ie move it some place safe) because you've got the requisite settings in the slave file.
I don't have CentOS to hand, but I can speak from extensive experience in Debian.
Generally speaking, bridge configurations require that the interface itself (in your case enp0s25) is not configured with an IP address. The physical interface remains unconfigured but UP and RUNNING, and the IP configuration for the host gets applied to logical bridge interface instead.
I'd suggest changing the file ifcfg-enp0s25 to have ONBOOT=no and trying again.
If that doesn't work, delete the ifcfg-enp0s25 file (ie move it some place safe) because you've got the requisite settings in the slave file.
answered Mar 11 at 7:31
roaimaroaima
46k758124
46k758124
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505507%2fnetwork-bridge-for-vm-not-working-after-reboot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
@roaima Hey, I had actually deleted that comment and up voted you. It appears that this has actually restored my network access to the VM. I hooked up a monitor and keyboard to that server and rebooted, and everything was perfect. I think that the server itself just appeared to be on (orange power light) but didn't actually reboot. If you'd like to reply with an answer, I'll gladly accept.
– Joshua Schlichting
Mar 10 at 23:52