Hi Simone,
sadly it seems that starting the engine from an alternative config is not working.
Virsh reports that the VM is defined , but shut down and the dumpxml doesn't show any disks - maybe this is normal for oVirt (I have never checked a running VM).
No, it's not:
devices={index:0,iface:virtio,format:raw,poolID:00000000-0000-0000-0000-000000000000,volumeID:a9ab832f-c4f2-4b9b-9d99-6393fd995979,imageID:8ec7a465-151e-4ac3-92a7-965ecf854501,specParams:{},readonly:false,domainID:808423f9-8a5c-40cd-bc9f-2568c85b8c74,optional:false,deviceId:a9ab832f-c4f2-4b9b-9d99-6393fd995979,address:{bus:0x00, slot:0x06,
the disk was definitively there in vm.conf but then the VM ignores it.
I'd suggest to double check vdsm.log for errors or something like that.
Strangely , both OVF have been wiped out at almost the same time.
I'm attaching some console output and gluster logs. In the gluster stuff I can see:
glusterd.log
The message "E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler" repeated 47 times between [2019-03-04 05:
17:15.810686] and [2019-03-04 05:19:08.576724]
[2019-03-04 05:19:16.147795] I [MSGID: 106488] [glusterd-handler.c:1558:__glusterd_handle_cli_get_volume] 0-management: Received get vol req
[2019-03-04 05:19:16.149524] E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler
[2019-03-04 05:19:42.728693] E [MSGID: 106419] [glusterd-utils.c:6943:glusterd_add_inode_size_to_dict] 0-management: could not find (null) to getinode size f
or systemd-1 (autofs): (null) package missing?
[2019-03-04 05:20:54.236659] I [MSGID: 106499] [glusterd-handler.c:4389:__glusterd_handle_status_volume] 0-management: Received status volume req for volume
data
[2019-03-04 05:20:54.245844] I [MSGID: 106499] [glusterd-handler.c:4389:__glusterd_handle_status_volume] 0-management: Received status volume req for volume
engine
and the log of the mountpoint:
[2019-03-04 05:19:35.381378] E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler
[2019-03-04 05:19:37.294931] I [MSGID: 108031] [afr-common.c:2543:afr_local_discovery_cbk] 0-engine-replicate-0: selecting local read_child engine-client-0
The message "I [MSGID: 108031] [afr-common.c:2543:afr_local_discovery_cbk] 0-engine-replicate-0: selecting local read_child engine-client-0" repeated 7 times
between [2019-03-04 05:19:37.294931] and [2019-03-04 05:21:26.171701]
The message "E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler" repeated 865 times between [2019-03-04 05
:19:35.381378] and [2019-03-04 05:21:26.233004]
[2019-03-04 05:21:35.699082] E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler
[2019-03-04 05:21:38.671811] I [MSGID: 108031] [afr-common.c:2543:afr_local_discovery_cbk] 0-engine-replicate-0: selecting local read_child engine-client-0
The message "I [MSGID: 108031] [afr-common.c:2543:afr_local_discovery_cbk] 0-engine-replicate-0: selecting local read_child engine-client-0" repeated 7 times
between [2019-03-04 05:21:38.671811] and [2019-03-04 05:23:31.654205]
The message "E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler" repeated 889 times between [2019-03-04 05
:21:35.699082] and [2019-03-04 05:23:32.613797]
Adding also Sahina here.
Best Regards,
Strahil Nikolov