[ovirt-users] In-place upgrade of Windows OS

2023-09-19 Thread Hean-Seng Tan
We are unable to do an in-place upgrade of the Windows OS for a vm from Windows Server 2012r2 to version 2016. Has anyone ever performed successfully an in-place upgrade? Can you please share the steps? ___ Users mailing list -- users@ovirt.org To

[ovirt-users] Re: Uncaught exception on Network Interfaces tab of a newly added host to oVirt 4.5.0

2022-09-30 Thread Hean-Seng Tan
After more retryings, I was able to resolve the issue with the following steps: - restart ovirt-engine and ovirt-engine-dwhd services - delete and re-add the host back to oVirt ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to

[ovirt-users] Re: Editing vm devices

2022-09-27 Thread Hean-Seng Tan
I never needed to this but I could see host devices tab on web console for a vm in oVirt 4.5.0. Clicking on Add Device button will bring up a window to select host and some devices from the host to attach to the vm. Is this what you are looking for? -HS Tan

[ovirt-users] Uncaught exception on Network Interfaces tab of a newly added host to oVirt 4.5.0

2022-09-27 Thread Hean-Seng Tan
I added a few hosts to oVirt that runs engine version 4.5.0.8-1.el8. Most of the hosts work well except that Network Interfaces tab of a host shows the below error on the web browser: Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read properties of

[ovirt-users] Re: How to turn off the state of tlbflush for Windows vm

2021-12-05 Thread Hean-Seng Tan
> On Sun, Dec 5, 2021 at 12:36 PM Hean-Seng Tan 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.

[ovirt-users] How to turn off the state of tlbflush for Windows vm

2021-12-05 Thread Hean-Seng Tan
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