After Rebooting the Cloudmin Physical Machine, One Particular KVM Guest Needs to have Its Network Bridges Swapped Back and Forth Before It Can Talk on the Secondary Interface

Submitted by dlynes on Mon, 11/28/2016 - 23:37 Pro Licensee

The cloudmin server is running on Debian 7.

KVM is the virtualization platform.

RouterOS (highly customized closed-source Linux distribution for network routing) is the Guest OS

Steps to reproduce the problem:

  • reboot the cloudmin machine
  • when it comes back up, the router OS guest cannot ping anything from eth1
  • expand system configuration->click network interfaces
  • click 'set by virtual system' for eth0
  • change it to br1
  • click save
  • click 'set by virtual system' for eth1
  • change it to br0
  • click save
  • click 'set by virtual system' for eth0
  • change it to br0
  • click save
  • click 'set by virtual system' for eth1
  • change it to br1
  • click save
  • now RouterOS can ping anything from eth1
Status: 
Active

Comments

Submitted by andreychek on Tue, 11/29/2016 - 10:21

Howdy -- sorry to hear you're having problems after rebooting your server!

Just to clarify, is this the only guest on your system?

Or do you have other guests, but the other guests work properly after a reboot?

Submitted by JamieCameron on Tue, 11/29/2016 - 19:12

Can you also post your host system's /etc/network/interfaces file? I'd like to see how these bridges are defined.