Hi,
> VM xxx has been paused due to unknown storage error.
> Migration failed due to a failed validation: [Migrating a VM in paused status
> due to I/O error is not supported.] (VM: xxx, Source: yyy).
Up until recently oVirt 4.5.4 has been running fine on our RHEL 8 hypervisors
with primarily
Hi Jean-Louis,
Sorry for the delay. I was waiting for it to occur again. While waiting for it
to occur again I've updated it to the latest oVirt 4.5.5 snapshot sometime late
last week.
> Do you have discard enabled on the disks?
No. Discard is not enabled. This is a thin provisioned disk,
I recently followed the instructions for enabling VNC encryption for FIPS
enabled hosts [1]. The VNC console seem to be fine on the host where the VM is
initially started (excluding noVNC in the browser). The qemu-kvm arguments are
not maintained properly upon VM migration, declaring
It took me a few days, but I was able to come up with one potential solution.
On each of the hypervisors I modified /usr/libexec/vdsm/vm_libvirt_hook.py
(vdsm) to include the following:
--- before: /usr/libexec/vdsm/vm_libvirt_hook.py.bak
+++ after: /usr/libexec/vdsm/vm_libvirt_hook.py
@@ -5,8
I receive a "Status Code: 500" popup whenever I attempt to create a snapshot
for a Windows VM from the Administration Portal UI. It doesn't matter if the VM
is powered on or off. Nor the OS designation set in the UI (setting Linux or
Other...).
The modal usually states: "Operation Canceled"
Here is how I manually cancel backup operations caught in a finalizing state
from Veeam. I've logged multiple tickets with Veeam about this issue. There is
a forum post [1] about it as well.
1. Obtain a oAuth access token (if keycloak is used).
curl -k -H "Accept: application/json"
Unfortunately my suggestion to use a preallocated disk image was not the
solution. I see a Windows VM has been "paused due to unknown storage error" as
of this morning. Discard is not enabled. Similar message for virsh and messages
in the vdsm/gluster logs.
7 matches
Mail list logo
