I have tried that. I don’t have the options listed showing in the document for
the VM edit dialog. I am assuming this is because the hosts do not have the TPM
module enabled in BIOS? I don’t know if that’s the case or not. Would the TPM
setting need to be enabled in hardware on the hosts
Sorry here, after some further investigation, this is not using a Gluster
share. These particular VMs were set up using an NFS share on a NAS device we
have. I don’t know why this was used for these particular devices. Maybe it was
a temporary thing and the idea was to move these into the
Incidentally, I also did find this in the OVIRT logs:
MainProcess|jsonrpc/7::DEBUG::2021-09-09
15:36:32,791::commands::219::root::(execCmd) FAILED: = 'mount.nfs: No
route to host\n'; = 32
MainProcess|jsonrpc/7::DEBUG::2021-09-09
15:36:32,792::logutils::319::root::(_report_stats)
Thanks for the reply.
I ended up moving the disk for another VM that was also paused and using the
same NFS share for storage. I moved the disk to a different share, and then
moved it back. Then to my surprise, the VM would start up. I then tried to
start the VM this thread opened on and it
eating ISO Storage Domain after
Manager Rebuild
On Sat, Aug 15, 2020 at 9:24 AM Alex K wrote:
>
>
>
> On Fri, Aug 14, 2020, 16:50 Bob Franzke via Users wrote:
>>
>> OK thanks for the reply. As you can perhaps tell I am a complete noob with
>> Ovirt. The fact its
OK thanks for the reply. As you can perhaps tell I am a complete noob with
Ovirt. The fact its working now at all is a complete miracle.
>>> I see 2 approaches on fixing the broken storage domain:
>>> - log to engine, switch to postgresql and start searching in the DB for the
>>> uuid.
I am
6 matches
Mail list logo
