On a particular Virtualmin/Cloudmin machine (ns83 KVM Host System) which hosts/controls several guest/physical OSs, I was having trouble with a particular guest OS ( git3 ) for quite a while. It has 100 GB virtual HDD, 4 GB RAM, and 2 virtual processors.
It had two real interfaces eth0 and eth1 and had local IPs assigned to them and was working fine. My plan was to delete the second interface and assign a public IP to the first one. But as soon as I deleted eth1, it also deleted eth0 rendering the guest OS unusable. When the instance is down, in the network interfaces, it does not give me a chance to edit eth0 at all. So there is no way to edit this interface.
Even after restarting the guest OS a number times and even restarting the physical machine that hosts this guest, this guest OS is still not starting
The error it gives is this:
started, but a problem was detected : KVM instance was started, but could not be pinged after 60 seconds
But in reality, the KVM instance is not started at all even after repeated attempts!
Re-fetching system status .. .. done. New status is : Down - KVM instance is down
There are other OSs ( guests ns45 and ns47 and physical servers ) controlled by this physical server (Intel Xeon 8 cores, 30 GB RAM, 900 GB HDD), which are doing just fine.
Also tried creating a clone of this guest; but the clone does the same thing as the original OS.