Quantcast
Channel: Ubuntu Forums - Virtualisation
Viewing all articles
Browse latest Browse all 4211

[SOLVED] failed to bring up enp0s8 connection in vm machine

$
0
0
I got an error saying this, not entirely sure where to look for exactly
Code:

root@pc1:/home/owl# /etc/init.d/networking restart
[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
 failed!

when I looked at "journalctl -xe" I saw

Code:

-- Unit networking.service has finished shutting down.
Jun 11 01:35:07 pc1 systemd[1]: Starting Raise network interfaces...
-- Subject: Unit networking.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit networking.service has begun starting up.
Jun 11 01:35:07 pc1 ifup[1750]: RTNETLINK answers: File exists
Jun 11 01:35:07 pc1 ifup[1750]: Failed to bring up enp0s8.
Jun 11 01:35:07 pc1 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 11 01:35:07 pc1 systemd[1]: Failed to start Raise network interfaces.
-- Subject: Unit networking.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit networking.service has failed.
--
-- The result is failed.
Jun 11 01:35:07 pc1 systemd[1]: networking.service: Unit entered failed state.
Jun 11 01:35:07 pc1 systemd[1]: networking.service: Failed with result 'exit-code'.

Any ideas?

This is on VM machine, issuing commands through open ssh from host terminal

On VM Ubuntu 16.04 server is installed and host is Ubuntu 16.04 based eOs

Viewing all articles
Browse latest Browse all 4211

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>