| Summary: | Accidently reboot VMs after OS Upgrade 12.2 to 13.0 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Arkadiy Yaruta <yaruta.arkadiy> | ||||||||||
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||||||||
| Status: | Closed Not A Bug | ||||||||||||
| Severity: | Affects Only Me | CC: | grahamperrin, shuriku, yaruta.arkadiy | ||||||||||
| Priority: | --- | ||||||||||||
| Version: | 13.0-STABLE | ||||||||||||
| Hardware: | amd64 | ||||||||||||
| OS: | Any | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Arkadiy Yaruta
2022-01-10 11:15:28 UTC
Update: I figure out that happens on clustered VMs (Microsoft Fileover cluster 2012R2 and 2019). Should I install addition components on FreeBSD VMs for supporting clustering or something else? Created attachment 230870 [details]
pciconf -lv
pciconf -lv
Please attach full /var/log/messages as well. Does reboots occurs on vm migrations or not? What do you see in hyper-v console or logs related to your vm while rebooting? Created attachment 230878 [details]
var-log-messages
Created attachment 230879 [details]
Clusters errors
Reboot occurred without VM migration. I took all servers out of clusters. Clusters errors and reboots stopped. I added 1 VM (SRV5) to the 2012R2 cluster again and reboot it (dmesg is attached). Live migration works fine. I'll watch the server for a few days. Created attachment 230881 [details]
dmesg
Nothing unusual in dmesg. IMO it is related to Failover Cluster Service and not to FreeBSD guest. We have some 12.3-13.0 VMs running in Hyper-V cluster and no special settings were made for them, but we prefer to run Gen2 VMs. We have found some network issues in our Windows cluster. As a result, the cluster was unstable, and the virtual machines rebooted periodically. Based on this, I'm pretty sure that the problem is not related to the version of the FreeBSD OS. Thanks for your help and answers! |