Re: [ovirt-users] oVirt API (4.0 and 4.1) not reporting vms running on a given storage domain

2018-03-02 Thread Luca 'remix_tj' Lorenzetto
Got it. I'm changing my code accordingly. Many thanks Luca Il 2 mar 2018 5:59 PM, "Ondra Machacek" ha scritto: > On 03/02/2018 05:24 PM, Luca 'remix_tj' Lorenzetto wrote: > >> On Fri, Mar 2, 2018 at 3:21 PM, Ondra Machacek >> wrote: >> >>> Hi, >>>

Re: [ovirt-users] oVirt API (4.0 and 4.1) not reporting vms running on a given storage domain

2018-03-02 Thread Ondra Machacek
On 03/02/2018 05:24 PM, Luca 'remix_tj' Lorenzetto wrote: On Fri, Mar 2, 2018 at 3:21 PM, Ondra Machacek wrote: Hi, As per documentation: http://ovirt.github.io/ovirt-engine-api-model/4.1/#services/storage_domain_vms That resource is used to list VMs on export storage

Re: [ovirt-users] oVirt API (4.0 and 4.1) not reporting vms running on a given storage domain

2018-03-02 Thread Luca 'remix_tj' Lorenzetto
On Fri, Mar 2, 2018 at 3:21 PM, Ondra Machacek wrote: > Hi, > > As per documentation: > > http://ovirt.github.io/ovirt-engine-api-model/4.1/#services/storage_domain_vms > > That resource is used to list VMs on export storage domain, not on data > domain. > > If you want to

Re: [ovirt-users] Issue with deploy HE on another host 4.1

2018-03-02 Thread Simone Tiraboschi
Thanks Artem, all right. Krzysztof, can you please attach or send me your host-deploy logs for this additional host from your engine VM to let me try understanding how it got a wrong ID? On Fri, Mar 2, 2018 at 3:52 PM, Artem Tambovskiy wrote: > Hello Krzysztof, > >

Re: [ovirt-users] Cannot activate storage domain

2018-03-02 Thread Bruckner, Simone
Hi all, I managed to get the inactive storage domain to maintenance by stopping all running VMs that were using it, but I am still not able to activate it. Trying to activate results in the following events: For each host: VDSM command GetVGInfoVDS failed: Volume Group does not exist:

Re: [ovirt-users] VMs stuck in migrating state

2018-03-02 Thread Milan Zamazal
nico...@devels.es writes: > El 2018-03-02 14:10, Milan Zamazal escribió: >> nico...@devels.es writes: >> >>> We're running 4.1.9 and during the weekend we had a storage issue that >>> seemed >>> to leave some hosts in an strange state. One of the hosts has almost all VMs >>> migrating (although

Re: [ovirt-users] Issue with deploy HE on another host 4.1

2018-03-02 Thread Artem Tambovskiy
Hello Krzysztof, As I can see both hosts have the same host_id=1, which causing conflict. You need this this manually on the newly deployed host and restart ovirt-ha-agent. You may run following command on engine VM in order to find correct host_id values for your hosts. sudo -u postgres psql

Re: [ovirt-users] oVirt API (4.0 and 4.1) not reporting vms running on a given storage domain

2018-03-02 Thread Ondra Machacek
Hi, As per documentation: http://ovirt.github.io/ovirt-engine-api-model/4.1/#services/storage_domain_vms That resource is used to list VMs on export storage domain, not on data domain. If you want to find VMs using specific storage you may use following query:

Re: [ovirt-users] VMs stuck in migrating state

2018-03-02 Thread Milan Zamazal
nico...@devels.es writes: > We're running 4.1.9 and during the weekend we had a storage issue that seemed > to leave some hosts in an strange state. One of the hosts has almost all VMs > migrating (although it seems to not actually being migrating them) and the > migration state cannot be

[ovirt-users] Issue with deploy HE on another host 4.1

2018-03-02 Thread Krzysztof Wajda
Hi, I have an issue with Hosted Engine when I try to deploy via gui on another host. There is no errors after deploy but in GUI I see only "Not active" status HE, and hosted-engine --status shows only 1 node (on both nodes same output). In hosted-engine.conf I see that host_id is the same as it

[ovirt-users] [ANN] oVirt 4.2.2 Third Release Candidate is now available

2018-03-02 Thread Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt 4.2.2 Third Release Candidate, as of March 2nd, 2018 This update is a release candidate of the second in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used

Re: [ovirt-users] hosted-engine --deploy : Failed executing ansible-playbook

2018-03-02 Thread Simone Tiraboschi
On Fri, Mar 2, 2018 at 11:25 AM, wrote: > Hello, > > > > I am on CENTOS 7.4.1708 > > > > I follow the documentation: > > [root@srvvm42 ~]# yum install ovirt-hosted-engine-setup > > [root@srvvm42 ~]# yum info ovirt-hosted-engine-setup > Loaded plugins: fastestmirror,

[ovirt-users] hosted-engine --deploy : Failed executing ansible-playbook

2018-03-02 Thread geomeid
Hello, I am on CENTOS 7.4.1708 I follow the documentation: [root@srvvm42 ~]# yum install ovirt-hosted-engine-setup [root@srvvm42 ~]# yum info ovirt-hosted-engine-setup Loaded plugins: fastestmirror, package_upload, product-id, search-disabled-repos, subscription-manager This system is

[ovirt-users] upgrade domain V3.6 to V4.2 with disks and snapshots failed on NFS, Export, QCOW V2/V3 renaming probl.

2018-03-02 Thread Oliver Riesener
Hi, after upgrading cluster compatibility from V3.6 to V4.2, i found all V3.6 disks with *snapshots* QCOW V2 are not working on NFS and Export Domains. Non UI command solves this problem, all stuck, they worsen disk state to "Illegal" and produces "Async Tasks" these newer ends. It seems

Re: [ovirt-users] VM Migrations

2018-03-02 Thread Milan Zamazal
"Bryan Sockel" writes: > Thanks for the info, I will be sure to update to 4.2.2 when it is ready. > With out the ability to migrate vm's based on this image it makes it less > convenient to patch my servers on a more consistent basis.I was also > experiencing this

[ovirt-users] upgrading disks with snapshots from V3.6 domain failed on NFS and Export domain V4, QCOW V2 to V3 renaming

2018-03-02 Thread Oliver Riesener
Hi, after upgrading cluster compatibility from V3.6 to V4.2, i found all V3.6 disks with *snapshots* QCOW V2 are not working on NFS and Export Domains. Non UI command solves this problem, all stuck, they worsen disk state to "Illegal" and produces "Async Tasks" these newer ends. It seems

Re: [ovirt-users] windows vm

2018-03-02 Thread suporte
I change the cpu type and windows vm is running. Thanks. De: "Vincent Royer" Para: supo...@logicworks.pt Cc: "ovirt users" Enviadas: Quinta-feira, 1 De Março de 2018 18:04:49 Assunto: Re: [ovirt-users] windows vm Broadwell Vincent Royer