Hello all,
I have a VM with zfs.rent which has been running pretty well on 14.X-RELEASE for a couple of years. When 15.0-RELEASE was released I upgraded all my FreeBSD machines pretty quickly, including this VM.
Within 24 hours of upgrading this VM had become unresponsive to network traffic and on the console. This happened a couple of times and I rolled back to 14.X-RELEASE as I didn't have time to investigate further.
I upgraded this VM to 15.1-RELEASE on 16th June. In the past week the VM has become unresponsive three times and has required resetting each time.
I monitor uptime of my machines using www/gatus, so can tell within a few minutes of when it becomes unresponsive.
Nothing interesting in /var/log/messages, often there are hours between a message and when the VM becomes unresponsive.
As an aside, as far as I can tell zfs.rent uses QEMU for their virtual machines.
I'm not sure where to look to figure out what the issue might be, and how to solve it. It certainly appears to be specific to 15.0-RELEASE and above.
Any tips or pointers would be greatly appreciated.
Thanks,
Ben
I have a VM with zfs.rent which has been running pretty well on 14.X-RELEASE for a couple of years. When 15.0-RELEASE was released I upgraded all my FreeBSD machines pretty quickly, including this VM.
Within 24 hours of upgrading this VM had become unresponsive to network traffic and on the console. This happened a couple of times and I rolled back to 14.X-RELEASE as I didn't have time to investigate further.
I upgraded this VM to 15.1-RELEASE on 16th June. In the past week the VM has become unresponsive three times and has required resetting each time.
I monitor uptime of my machines using www/gatus, so can tell within a few minutes of when it becomes unresponsive.
Nothing interesting in /var/log/messages, often there are hours between a message and when the VM becomes unresponsive.
As an aside, as far as I can tell zfs.rent uses QEMU for their virtual machines.
I'm not sure where to look to figure out what the issue might be, and how to solve it. It certainly appears to be specific to 15.0-RELEASE and above.
Any tips or pointers would be greatly appreciated.
Thanks,
Ben