Aviv Posted June 11, 2020 Share Posted June 11, 2020 (edited) When im trying to start a vm, i receive this error: " Cannot get interface MTU on 'virbr0': No such device"  It seems my virbr0 interface has gone away? Any tips? 🙂 Thank you!  Edited June 12, 2020 by Aviv Quote Link to comment
Aviv Posted June 11, 2020 Author Share Posted June 11, 2020 (edited) Reboot solved it. Not sure why it happen. any ideas from your experience? Edited June 12, 2020 by Aviv Quote Link to comment
sturmstar Posted August 5, 2020 Share Posted August 5, 2020 Hi - had the same problem.  I did solve it with this command in ssh: Quote virsh net-start default  So - reboot isn't neccessary.   7 7 Quote Link to comment
54tgedrg45 Posted September 8, 2020 Share Posted September 8, 2020 (edited) This happen to me after stopping the array, changing the DNS, and restarting the array. ty sturmstar Edited September 8, 2020 by 54tgedrg45 Quote Link to comment
DesktopMasters Posted December 11, 2020 Share Posted December 11, 2020 On 8/5/2020 at 12:52 AM, sturmstar said: Hi - had the same problem.  I did solve it with this command in ssh:  So - reboot isn't neccessary.   This worked for me also. Thank you. Quote Link to comment
Glassed Silver Posted December 13, 2020 Share Posted December 13, 2020 On 8/5/2020 at 9:52 AM, sturmstar said: Hi - had the same problem. Â I did solve it with this command in ssh: Â So - reboot isn't neccessary. Â Â Thank you so much for this! Really came in handy! Quote Link to comment
Bowling666 Posted January 29, 2021 Share Posted January 29, 2021 Hello i have the same problem with my vms. Sadly a reboot does not fix the problem. Also by running the command "virsh net-start default" came an error.  i hope someone can help me. Thank you! Quote Link to comment
sturmstar Posted January 29, 2021 Share Posted January 29, 2021 From your screenshot I see that you have indeed NO 'br0' network. That's the reason why the VM fails. WHY you don't have no 'br0' is the other question... Â my network looks like this:Â Â Quote Link to comment
Bowling666 Posted January 29, 2021 Share Posted January 29, 2021 I also dont know why "br0" is not there anymore. Hmmm and when i try to add it manually it does not work sadly. Quote Link to comment
sturmstar Posted January 29, 2021 Share Posted January 29, 2021 Look into your network settings - mine looks like this:Â Â Quote Link to comment
Bowling666 Posted January 29, 2021 Share Posted January 29, 2021 My network settings:Â Quote Link to comment
sturmstar Posted January 29, 2021 Share Posted January 29, 2021 (edited) hmm... you could try to disable "bonding" by setting "enable bonding" to "no" - because you only have one bonding-member (eth0) - so there is no benefit in enable bonding?! Â i just saw it - you don't have the "bridging members" - certainly because of enabled "bonding" ... i really would try that! Â ...maybe this makes a difference?! and after that a reboot... Edited January 29, 2021 by sturmstar Quote Link to comment
Bowling666 Posted January 29, 2021 Share Posted January 29, 2021 after my file backup is finished i try it Quote Link to comment
Bowling666 Posted January 29, 2021 Share Posted January 29, 2021 3 hours ago, sturmstar said: hmm... you could try to disable "bonding" by setting "enable bonding" to "no" - because you only have one bonding-member (eth0) - so there is no benefit in enable bonding?! Â i just saw it - you don't have the "bridging members" - certainly because of enabled "bonding" ... i really would try that! Â ...maybe this makes a difference?! and after that a reboot... Thank you very much! The system is running again. 1 Quote Link to comment
nitrossub Posted February 4, 2021 Share Posted February 4, 2021 On 1/29/2021 at 8:29 PM, Bowling666 said: Hello i have the same problem with my vms. Sadly a reboot does not fix the problem. Also by running the command "virsh net-start default" came an error.  i hope someone can help me. Thank you!  go to vm settings and click the refresh button next to the Mac: save then run 2 Quote Link to comment
droobie21 Posted April 23, 2021 Share Posted April 23, 2021 On 2/4/2021 at 4:06 AM, nitrossub said:  go to vm settings and click the refresh button next to the Mac: save then run  Thanks! This did the trick for me. Quote Link to comment
flying_rabbi Posted May 8, 2021 Share Posted May 8, 2021 On 2/4/2021 at 7:06 PM, nitrossub said:  go to vm settings and click the refresh button next to the Mac: save then run On 4/24/2021 at 7:56 AM, droobie21 said:  Thanks! This did the trick for me. +1 - This was my bugbear also Quote Link to comment
Sinister Posted January 1, 2022 Share Posted January 1, 2022 On 8/5/2020 at 3:52 AM, sturmstar said: Hi - had the same problem. Â I did solve it with this command in ssh: Â So - reboot isn't neccessary. Â Â Thank you sir Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.