Networking stops randomly running Ubuntu Hirsute on Virtualbox
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Networking stops randomly running Ubuntu Hirsute on Virtualbox
I recently installed a VDI of Ubuntu 21.04 Hirsute that I downloaded from OSBoxes.org. I have run a large number of VM's in Virtualbox and have not experienced this problem before. Essentially what will happen is the network interface will stop responding and using systemctl status enp0s3 will report that the device is loaded and inactive(dead).
A ping test will show the following:
Code:
$>ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time-0.022 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time-0.031 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time-0.029 ms
^C
--- 127.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2036ms
rtt min/avg/max/mdev = 0.022/0.027/0.031/0.003 ms
$>ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1005 ms
Restarting the network service will restore connectivity immediately and will result in successful pings outbound:
So far the specs look fine. The server is under 0 load when this happens it is just running in a VM on my laptop. i5 processor with 8 GB memory, windows 10 VM. Load: 0% and the network interface goes down. It may be related to leaving the VM process and moving to another one. As long as I keep interacting things seem to keep working.
When I'm in Virtualbox, each machine shows 3 little dots and lines to the right. Expanding for: details, screenshots and logs... something may show up in those log tabs?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.