How to turn off the state of tlbflush for Windows vm
We encounter random Windows BSOD (blue screen of death) issues for vm's in environment running oVirt Engine 4.4.4. Upgrading the environment to 4.4.8 does not fix the issue. There is a suggestion from https://bugzilla.redhat.com/show_bug.cgi?id=1868572 to turn off the state of tlbflush under hyperv section for the Windows vm. Does anyone know how to achieve that? Currently, vm description returned from api call includes the following section that has tlbflush state: <features> <acpi/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <runtime state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <frequencies state='on'/> <reenlightenment state='on'/> <tlbflush state='on'/> </hyperv> </features>
On Sun, Dec 5, 2021 at 12:36 PM Hean-Seng Tan <hean-seng.tan@xilinx.com> wrote:
We encounter random Windows BSOD (blue screen of death) issues for vm's in environment running oVirt Engine 4.4.4. Upgrading the environment to 4.4.8 does not fix the issue. There is a suggestion from https://bugzilla.redhat.com/show_bug.cgi?id=1868572 to turn off the state of tlbflush under hyperv section for the Windows vm. Does anyone know how to achieve that?
Didn't the alternatives that were specified in https://bugzilla.redhat.com/show_bug.cgi?id=1868572#c130 work for you?
Currently, vm description returned from api call includes the following section that has tlbflush state: <features> <acpi/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <runtime state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <frequencies state='on'/> <reenlightenment state='on'/> <tlbflush state='on'/> </hyperv> </features> _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XRHQE3HHSVKHKC...
On Sun, Dec 5, 2021 at 12:36 PM Hean-Seng Tan <hean-seng.tan(a)xilinx.com> wrote:
Didn't the alternatives that were specified in https://bugzilla.redhat.com/show_bug.cgi?id=1868572#c130 work for you?
Thank you for the reply. The suggested alternatives came after I started the thread here. We are testing by changing "Operating System" in virtual machine setting from something like "Windows 2016 x64" to "Other OS". The setting looks unnatural but we hope that BSOD will not occur again.
participants (2)
-
Arik Hadas -
Hean-Seng Tan