After an upgrade to 25.04 and successful migration of the VM to the new Instance mechanism, the VM is shutting down unexpectedly. It doesn’t seem to be related to lack of system memory. Sometimes it runs for 24h and sometimes after just 2h I suddenly find out it is in the “Stopped” state. I’m running Debian in the VM. I wasn’t able to find any errors that could point me in the right direction.
Can you please suggest a solution or way to debug why the VM is constantly stopping?
In your VM you could try logging with syslog/rsyslog to a log. You should be able to get all the kernel messages dumped to a log. This might be enough to give you clues of how it died/shutdown.
In /etc/rsyslogd.conf
kern.* /var/log/kernel
I’ve looked at the logs that are automatically setup in Debian out of the box according to what you’re suggesting. And there’s nothing suggesting the system shut itself down. The last logs when it was running are from Docker handling some requests.
I had the same issue with both containers and instances on a SATA pool, everything would randomly crash using virtio-scsi but using NVMe on the same pool was stable
By “SATA pool” you mean all of your disks in the pool where virtual disk for the VM is located are connected with SATA cable?
I’m running off of an NVMe connected disks in the pool and using NVMe virtual disk mode. I may try to switch virtio next time it crashes.
Yes SATA connected 7200rpm drives for containers/instances and I use the NVMe pool for apps
Mine are randomly loosing network.