[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries

2020-04-19 Thread Adrian Quintero
Not sure if this is what is needed, as I still cant find the virtual directory .gfid. [root@host1 ~]# getfattr -n glusterfs.gfid.string /mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6 getfattr: Removing leading '/' from absolute path names # file:

[ovirt-users] Re: command line vm start/stop

2020-04-19 Thread Ali Gusainov
According to https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/rest_api_guide/index#services-vm trying to use curl --insecure -v -u admin@internal:password -H Content-type: application/xml -X POST https://FQDN/ovirt-engine/api/vms/VM_NAME/ACTION where ACTION

[ovirt-users] ovirt 4.4 beta4 HCI single host problem unknown CPU feature: tsx-ctrl

2020-04-19 Thread Gianluca Cecchi
Hello, I'm trying what in subject as a nested environment. Physical is oVirt 4.3.9 I configured the VM that has to be the hypervisor with cpu passthrough. The local VM starts ok with these settings: usr/libexec/qemu-kvm -name guest=HostedEngineLocal,debug-threads=on -S -object

[ovirt-users] ovrt node ng 4.4 different fs layout and error if changed

2020-04-19 Thread Gianluca Cecchi
Hello, In CentOS 7 default filesystem in anaconda was xfs, but in ovirt node ng 4.3.9 (based on CentOS 7) the default layout was set to ext4. In CentOS 8 again the default is xfs and I see that ovirt node ng 4.4 beta4 (based on CentOS 8.1) has now xfs for all filesystems, excluded /boot that is

[ovirt-users] Re: disk snapshot in illegal status

2020-04-19 Thread Shani Leviim
The f447cd4f-9ab3-489d-8c2a-b2e69456496f - "Auto-generated" snapshot should be deleted. After that, make sure the 5a58466b-1547-4346-a550-8590880b379e (Active VM) snapshot has an active=true flag. *Regards,* *Shani Leviim* On Thu, Apr 16, 2020 at 9:33 PM David David wrote: > snapshots in

[ovirt-users] Re: VM's in status unknown

2020-04-19 Thread Arik Hadas
I would start by querying the database with: select vm_name, status, run_on_vds from vms where vm_name in ('', ''); Their status should be '7' in that case. The more interesting part though is their 'run_on_vds' field - If it's non-empty and points to the host the VMs ran on, it probably means