[ovirt-users] Live ("any") disk migration between storages KILLS a virtual machine with Windows (UEFI) !!!

[Patrick Lomakin]

The weekend went horribly. I created a second storage domain in order to move all the virtual machines to a higher performance RAID array (From RAID6 to RAID10). My mistake was trying to move two Windows domain controllers from one storage domain to another. The problem is that when I "live" moved the virtual machine disk between storage domains, my Windows Server 2019 virtual machines worked fine until the next reboot. After a reboot, the machine just won't start and throws an error - Status: 0xc0000428 - The digital signature for this file couldn't be verified. Moving back to the "old" domain doesn't help.
None of the procedures with VMs worked (Re-create boot area, turn on kernel flag - bcdedit.exe /set nointegritychecks on). I am ready to help and interested in developing Ovirt. I can also provide more information to developers if needed.
_______________________________________________
Users mailing list -- ***@ovirt.org
To unsubscribe send an email to users-***@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/user

[Patrick Lomakin]

What type of storage (and brand) are you using for the storage ?
Best Regards,Strahil Nikolov
The weekend went horribly. I created a second storage domain in order to move all the
virtual machines to a higher performance RAID array (From RAID6 to RAID10). My mistake was
trying to move two Windows domain controllers from one storage domain to another. The
problem is that when I "live" moved the virtual machine disk between storage
domains, my Windows Server 2019 virtual machines worked fine until the next reboot. After
a reboot, the machine just won't start and throws an error - Status: 0xc0000428 - The
digital signature for this file couldn't be verified. Moving back to the
"old" domain doesn't help.
None of the procedures with VMs worked (Re-create boot area, turn on kernel flag -
bcdedit.exe /set nointegritychecks on). I am ready to help and interested in developing
Ovirt. I can also provide more information to developers if needed.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/

I use Lenovo DS4200 SAN with iSCSI
_______________________________________________
Users mailing list -- ***@ovirt.org
To unsubscribe send an email to users-***@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/***@ovirt.or

[Eyal Shenitzky]

Can you share the engine and VDSM logs?

Post by Patrick Lomakin
The weekend went horribly. I created a second storage domain in order to
move all the virtual machines to a higher performance RAID array (From
RAID6 to RAID10). My mistake was trying to move two Windows domain
controllers from one storage domain to another. The problem is that when I
"live" moved the virtual machine disk between storage domains, my Windows
Server 2019 virtual machines worked fine until the next reboot. After a
0xc0000428 - The digital signature for this file couldn't be verified.
Moving back to the "old" domain doesn't help.
None of the procedures with VMs worked (Re-create boot area, turn on
kernel flag - bcdedit.exe /set nointegritychecks on). I am ready to help
and interested in developing Ovirt. I can also provide more information to
developers if needed.
_______________________________________________
Privacy Statement: https://www.ovirt.org/privacy-policy.html
https://www.ovirt.org/community/about/community-guidelines/

[Patrick Lomakin]

Post by Eyal Shenitzky
Can you share the engine and VDSM logs?

As I continued, I learned that a colleague had encountered this problem at Proxmox. In this case, migrating the disk to the original storage helped start the VM. In oVirt, this did not happen. And yes - this problem only affects Windows with UEFI (in my particular case). I assume it is related to KVM-based systems, and yet it is a very serious problem. In oVirt, as it is, it's not very convenient to back up VMs and it's just unacceptable to destroy virtual machines at the same time. I have attached the logs of the engine - https://wdfiles.ru/73360d and VDSM - https://wdfiles.ru/3f4f1e
_______________________________________________
Users mailing list -- ***@ovirt.org
To unsubscribe send an email to users-***@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/***@ovirt.or

[Eyal Shenitzky]

I can't download the logs from that source.

Please file a bug and attach the logs there with all the needed info -
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

Post by Patrick Lomakin

Post by Eyal Shenitzky
Can you share the engine and VDSM logs?
On Wed, 12 May 2021 at 21:01, Patrick Lomakin <patrick.lomakin(a)

As I continued, I learned that a colleague had encountered this problem at
Proxmox. In this case, migrating the disk to the original storage helped
start the VM. In oVirt, this did not happen. And yes - this problem only
affects Windows with UEFI (in my particular case). I assume it is related
to KVM-based systems, and yet it is a very serious problem. In oVirt, as
it is, it's not very convenient to back up VMs and it's just unacceptable
to destroy virtual machines at the same time. I have attached the logs of
the engine - https://wdfiles.ru/73360d and VDSM -
https://wdfiles.ru/3f4f1e
_______________________________________________
Privacy Statement: https://www.ovirt.org/privacy-policy.html
https://www.ovirt.org/community/about/community-guidelines/