Re: [ovirt-users] Is windows sso still working on ovirt 4.1 ?

[plysan]

OK, seems the problem is in guest agent:

after login in vm manually, I see the following logs
in C:\Windows\SysWOW64\ovirt-guest-agent.log

//begin log
Dummy-1::INFO::2017-05-07
21:29:55,956::OVirtGuestService::84::root::Starting OVirt Guest Agent
service
Dummy-2::INFO::2017-05-07
21:30:06,545::OVirtAgentLogic::321::root::Received an external command:
api-version...
Dummy-2::INFO::2017-05-07 21:30:06,545::OVirtAgentLogic::117::root::API
Version updated from 0 to 3
Dummy-2::INFO::2017-05-07
21:30:59,503::OVirtAgentLogic::321::root::Received an external command:
lock-screen...
Dummy-2::INFO::2017-05-07
21:31:13,756::OVirtAgentLogic::321::root::Received an external command:
login...
Dummy-2::ERROR::2017-05-07 21:31:14,756::GuestAgentWin32::311::root::Error
writing credentials to pipe [1/3] (error = 2)
Dummy-2::ERROR::2017-05-07 21:31:15,756::GuestAgentWin32::311::root::Error
writing credentials to pipe [2/3] (error = 2)
Dummy-2::ERROR::2017-05-07 21:31:16,755::GuestAgentWin32::311::root::Error
writing credentials to pipe [3/3] (error = 2)
//end log

Digging into agent code to find the answer...



2017-05-07 16:28 GMT+08:00 plysan :

> Hi,
>
> I have recently set up a ovirt 4.1 environment to test vm sso.
>
> spec:
> * host: centos 7.3.1611
> * ovirt-engine: commit af393b7d3a494917dbda33a06813e8e8a8c6698a from
> branch ovirt-engine-4.1 , self compiled.
> * vdsm: vdsm-4.19.10.1-1.el7.centos.x86_64
> * windows 2008 r2 with active directory setup(domain name is "ply.local",
> test user is "ply@ply.local")
> * windows 7 vm with guest tools setup using ovirt-guest-tools-iso-4.
> 1-3.fc24.noarch
>
> I can add AD to ovirt engine successfully using 
> ovirt-engine-extension-aaa-ldap-setup
> tool.[1]
> After adding AD domain to windows7 vm, I can login manually using AD user
> with no problem.
>
> I can see the logs[2] when I login in to userportal with AD user, and
> spice client pop up automatically.
> But the spice client just stops at the windows7 login screen. asking for
> password.
> In the vm, vdagent and vdservice are all running fine. I can provide guest
> agent logs if needed.
>
> So, anyone can point me to the right direction?
>
> cheers
>
>
> [1]: see attachment: ovirt-engine-extension-aaa-ldap-setup-20170507034924-
> w5fwc9.log
> [2]: see attachment: vdsm-log,ovirt-engine-log
>
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM disk update failure

[Kevin Goldblatt]

Hi Stephano,

>From the log I see that the image cannot be found. This would indicate that
you have an issue on your host connected to the storage provider:

OneImageInfoReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=254,
mMessage=Image path does not exist or cannot be accessed/created:
(u'/rhev/data-center/mnt/blockSD/6a386652-629d-4045-835b-
21d2f5c104aa/images/c5fb9190-d059-4d9b-af23-07618ff660ce',)]]

Please provide the following:

1. Provide the exact scenario you performed in the Update of the disk

2. Can you please check to see that the storage domain on which the disk
resides is up and running,

3. If not then check whether the storage on the host is visible through the
host

4. If all the above is working then please submit a bug through bugzilla
and provide the engine, server and vdsm logs.


Regards,


Kevin

On Tue, May 2, 2017 at 11:10 PM, Stefano Bovina  wrote:

> Hi, while trying to update a VM disk, a failure was returned (forcing me
> to add a new disk)
>
> Any advice on how to resolve this error?
>
> Thanks
>
>
> Installation info:
>
> ovirt-release35-006-1.noarch
> libgovirt-0.3.3-1.el7_2.1.x86_64
> vdsm-4.16.30-0.el7.centos.x86_64
> vdsm-xmlrpc-4.16.30-0.el7.centos.noarch
> vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch
> vdsm-jsonrpc-4.16.30-0.el7.centos.noarch
> vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch
> vdsm-python-4.16.30-0.el7.centos.noarch
> vdsm-cli-4.16.30-0.el7.centos.noarch
> qemu-kvm-ev-2.3.0-29.1.el7.x86_64
> qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64
> qemu-kvm-tools-ev-2.3.0-29.1.el7.x86_64
> libvirt-client-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-storage-1.2.17-13.el7_2.3.x86_64
> libvirt-python-1.2.17-2.el7.x86_64
> libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.3.x86_64
> libvirt-lock-sanlock-1.2.17-13.el7_2.3.x86_64
> libvirt-glib-0.1.9-1.el7.x86_64
> libvirt-daemon-driver-network-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-lxc-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-interface-1.2.17-13.el7_2.3.x86_64
> libvirt-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-config-network-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-secret-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-qemu-1.2.17-13.el7_2.3.x86_64
>
>
>  engine.log
>
> 2017-05-02 09:48:26,505 INFO  [org.ovirt.engine.core.bll.UpdateVmDiskCommand]
> (ajp--127.0.0.1-8702-6) [c3d7125] Lock Acquired to object EngineLock
> [exclusiveLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value:
> VM_DISK_BOOT
> key: c5fb9190-d059-4d9b-af23-07618ff660ce value: DISK
> , sharedLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value: VM
> ]
> 2017-05-02 09:48:26,515 INFO  [org.ovirt.engine.core.bll.UpdateVmDiskCommand]
> (ajp--127.0.0.1-8702-6) [c3d7125] Running command: UpdateVmDiskCommand
> internal: false. Entities affected :  ID: c5fb9190-d059-4d9b-af23-07618ff660ce
> Type: DiskAction group EDIT_DISK_PROPERTIES with role type USER
> 2017-05-02 09:48:26,562 INFO  
> [org.ovirt.engine.core.bll.ExtendImageSizeCommand]
> (ajp--127.0.0.1-8702-6) [ae718d8] Running command: ExtendImageSizeCommand
> internal: true. Entities affected :  ID: c5fb9190-d059-4d9b-af23-07618ff660ce
> Type: DiskAction group EDIT_DISK_PROPERTIES with role type USER
> 2017-05-02 09:48:26,565 INFO  [org.ovirt.engine.core.vdsbro
> ker.irsbroker.ExtendImageSizeVDSCommand] (ajp--127.0.0.1-8702-6)
> [ae718d8] START, ExtendImageSizeVDSCommand( storagePoolId =
> 715d1ba2-eabe-48db-9aea-c28c30359808, ignoreFailoverLimit = false), log
> id: 52aac743
> 2017-05-02 09:48:26,604 INFO  [org.ovirt.engine.core.vdsbro
> ker.irsbroker.ExtendImageSizeVDSCommand] (ajp--127.0.0.1-8702-6)
> [ae718d8] FINISH, ExtendImageSizeVDSCommand, log id: 52aac743
> 2017-05-02 09:48:26,650 INFO  
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
> (ajp--127.0.0.1-8702-6) [ae718d8] CommandAsyncTask::Adding
> CommandMultiAsyncTasks object for command cb7958d9-6eae-44a9-891a-7fe088
> a79df8
> 2017-05-02 09:48:26,651 INFO  
> [org.ovirt.engine.core.bll.CommandMultiAsyncTasks]
> (ajp--127.0.0.1-8702-6) [ae718d8] CommandMultiAsyncTasks::AttachTask:
> Attaching task 769a4b18-182b-4048-bb34-a276a55ccbff to command
> cb7958d9-6eae-44a9-891a-7fe088a79df8.
> 2017-05-02 09:48:26,661 INFO  
> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
> (ajp--127.0.0.1-8702-6) [ae718d8] Adding task 
> 769a4b18-182b-4048-bb34-a276a55ccbff
> (Parent Command UpdateVmDisk, Parameters Type org.ovirt.engine.core.common.a
> synctasks.AsyncTaskParameters), polling hasn't started yet..
> 2017-05-02 09:48:26,673 INFO  [org.ovirt.engine.core.dal.db
> broker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-6)
> [ae718d8] Correlation ID: c3d7125, Call Stack: null, Custom Event ID: -1,
> Message: VM sysinfo-73 sysinfo-73_Disk3 disk was updated by admin@internal.
> 

[ovirt-users] Hosted Engine Setup with the gluster bricks on the same disk as the OS

[Mike DePaulo]

Hi. I am trying to follow this guide. Is it possible to use part of my
OS disk /dev/sda for the bricks?
https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and-gluster-storage/

I am using oVirt Node 4.1.1.1. I am aware of the manual partitioning
requirements. I am guessing I have to create an LV for the OS that
does not take up the entire disk during install, manually create a pv
like /dev/sda3 afterwards, and then run Hosted Engine Setup and
specify /sda3 rather than sdb?

Thanks,
-Mike
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Ovirt 4.0] Multiple cluster and multiple storage possible ?

[Fred Rolland]

Hi,

Storage Domains are DC entities and are not related to clusters.
Every hosts in the DC should be able to access the Storage Domain.
Once the SD is first created on one of the hosts, all the other host are
trying to connect also.

Can you mount manually from host2 ?
It maybe a firewall/network issue.

On Wed, May 3, 2017 at 7:09 PM, TranceWorldLogic . <
tranceworldlo...@gmail.com> wrote:

> Hi,
>
> I am trying to setup ovirt as shown below.
>
> DataCenter1 -Cluster1 -host1  NFS1-Data Domain
>   |
>   |-Cluster2 --host2-NFS2-Data Domain
>
>
> As you see in above case I am trying to attach both NFS partition to
> Datacente1 and I got various behaviour:
>
> 1> Once one data domain attached to data center other is failing to
> attached
> (e.g. let say NFS1-Data Domain is attached to DataCenter1 then after that
> NFS2-Data Domain failing to attach DataCenter1)
>
> 2> And sometime both data domain successfully got attached but after that
> host2 is not coming up by saying "host1 cannot access to NFS2-Data Domain
> and hence moving host1 to Non-Operational"
> host1 firewall rules are :
> 
> --
> # iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere state
> RELATED,ESTABLISHED
> ACCEPT icmp --  anywhere anywhere
> ACCEPT all  --  anywhere anywhere
> ACCEPT tcp  --  anywhere anywhere tcp dpt:54321
> ACCEPT tcp  --  anywhere anywhere tcp dpt:54322
> ACCEPT tcp  --  anywhere anywhere tcp
> dpt:sunrpc
> ACCEPT udp  --  anywhere anywhere udp
> dpt:sunrpc
> ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
> ACCEPT udp  --  anywhere anywhere udp dpt:snmp
> ACCEPT tcp  --  anywhere anywhere tcp dpt:websm
> ACCEPT tcp  --  anywhere anywhere tcp dpt:16514
> ACCEPT tcp  --  anywhere anywhere multiport
> dports rockwell-csp2
> ACCEPT tcp  --  anywhere anywhere multiport
> dports rfb:6923
> ACCEPT tcp  --  anywhere anywhere multiport
> dports 49152:49216
> ACCEPT tcp  --  anywhere anywhere tcp
> dpt:sunrpc
> ACCEPT tcp  --  anywhere anywhere tcp dpt:nfs
> ACCEPT udp  --  anywhere anywhere udp dpt:nfs
> ACCEPT udp  --  anywhere anywhere udp
> dpt:sunrpc
> ACCEPT udp  --  anywhere anywhere udp dpt:892
> ACCEPT tcp  --  anywhere anywhere tcp dpt:892
> ACCEPT tcp  --  anywhere anywhere tcp
> dpt:ospf-lite
> REJECT all  --  anywhere anywhere reject-with
> icmp-host-prohibited
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
> REJECT all  --  anywhere anywhere PHYSDEV
> match ! --physdev-is-bridged reject-with icmp-host-prohibited
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
> 
> --
>
> Please help me to understand this issue.
> 1> Do ovirt support multiple-cluster to multiple-storage data domain ?
> 2> Are those firewall rules correct or wrong ?
> 3> Can host1 access storage domain created on another cluster say host2
> m/c ? (NFS technology)
>
>
> Thanks,
> ~Rohit
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM Template Error

[Yaniv Kaul]

On Thu, May 4, 2017 at 4:57 PM, Bryan Sockel  wrote:

> I have been moving around my storage setup, and this storage domain does
> not exist in my environment anymore.  Not sure if this if this VM was
> created on this storage domain and then moved.
>
> I am attempting to create a template on a storage domain that does
> currently exist in my environment.  How would i remove the reference to
> this storage domain so it is not used?
>

You can probably right click on it and select 'destroy'.
Y.


>
>
>
> -Original Message-
> From: Shahar Havivi 
> To: Michal Skrivanek 
> Cc: Bryan Sockel , users 
> Date: Thu, 4 May 2017 08:19:34 +0300
> Subject: Re: [ovirt-users] VM Template Error
>
> According to the log the the storage domain (where the disk is stored is
> not exists)
> StorageDomainDoesNotExist: Storage domain does not exist:
> (u'2de6ad97-1f33-41e5-b021-bacec14ce6e4',)
>
> Does all the storage domain active in your data center?
> Did you move the disk or remove and added a different storage domain?
>
> On Wed, May 3, 2017 at 8:30 PM, Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>>
>>
>>
>> On 3 May 2017, at 16:09, Bryan Sockel  wrote:
>>
>> Hi.  the vm does exist and is bootable.  The vm only has one disk and it
>> is enabled.
>>
>>
>> yes, but the template’s copy of that disk somehow can’t be created.
>> Perhaps share more of the vdsm logs to see why the image copy failed
>>
>> Thanks,
>> michal
>>
>>
>>
>>
>> Thanks
>>
>>
>>
>> -Original Message-
>> From: Shahar Havivi 
>> To: Bryan Sockel 
>> Cc: "users@ovirt.org" 
>> Date: Wed, 3 May 2017 09:05:34 +0300
>> Subject: Re: [ovirt-users] VM Template Error
>>
>> its looks like vdsm complain that the image is not exists.
>> can you run the VM with no errors? (if the VM have more then one disk
>> make sure that its exists and accessible).
>>
>> if all good please attach the full vdsm and engine log.
>>
>>  Shahar.
>>
>> On Tue, May 2, 2017 at 6:29 PM, Bryan Sockel 
>> wrote:
>>>
>>> Hi,
>>>
>>> Having an issue a template from a VM's.
>>>
>>> I am getting the following errors:
>>> engine.log
>>> 2017-05-02 09:40:10,059-05 INFO  [org.ovirt.engine.core.dal.db
>>> broker.auditloghandling.AuditLogDirector] (default task-24) [2ef2fce]
>>> EVENT_ID: USER_ADD_VM_TEMPLATE(48), Correlation ID:
>>> 176fdfa7-0467-48f5-9ecc-901e86768c28, Job ID:
>>> fed9a848-1971-495a-a391-be1fa4a67908, Call Stack: null, Custom Event
>>> ID: -1, Message: Creation of Template test from VM Windows-10-Template was
>>> initiated by admin@internal-authz.
>>>
>>> 2017-05-02 09:48:43,059-05 ERROR [org.ovirt.engine.core.dal.dbb
>>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-20)
>>> [] EVENT_ID: USER_ADD_VM_TEMPLATE_FINISHED_FAILURE(52), Correlation ID:
>>> 176fdfa7-0467-48f5-9ecc-901e86768c28, Job ID:
>>> fed9a848-1971-495a-a391-be1fa4a67908, Call Stack: null, Custom Event
>>> ID: -1, Message: Failed to complete creation of Template test from VM
>>> Windows-10-Template.
>>>
>>> Events Log
>>> ID 10803 - VDSM command DeleteImageGroupVDS failed: Image does not exist
>>> in domain: u'image=6aa525ad-e7f1-432b-959a-2223f7e77083,
>>> domain=e371d380-7194-4950-b901-5f2aed5dfb35'
>>> ID 10802 - VDSM vm-host-colo-2 command HSMGetAllTasksStatusesVDS failed:
>>> low level Image copy failed
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] GET /storagedomains broken ?

[Fred Rolland]

It should work.
Can you share the engine log ?

On Thu, May 4, 2017 at 6:10 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

> I'm playing with the python sdk and getting :
>
> [2017-05-04 17:01:17] 192.168.205.36 "ovirt.XXX" "GET 
> /ovirt-engine/api/storagedomains
> HTTP/1.1" 292250 404 + 188 "-" "PythonSDK/4.1.3"
>
> And in engine.log:
>
> 2017-05-04 17:01:17,727+02 ERROR 
> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource]
> (default task-21) [] Operation Failed: Entity not found: Storage server
> connection: id=6860d96f-557e-4d82-a209-401d72bd6e16
>
> But in the documentation from https://ovirt.prod.exalead.
> com/ovirt-engine/apidoc/#requests, I indeed see:
>
> GET /storagedomains
>
> The ovirt's version I use:
> 
>   oVirt Engine
>   ovirt.org
>   
> 1
> 4.1.1.8-1.el7.centos
> 4
> 1
> 0
>   
> 
>
>
> Is there something obvious I missed ?
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM Template Error

[Shahar Havivi]

Adding Allon,

How did you remove the storage domain while having VMs?

On Thu, May 4, 2017 at 4:57 PM, Bryan Sockel  wrote:

> I have been moving around my storage setup, and this storage domain does
> not exist in my environment anymore.  Not sure if this if this VM was
> created on this storage domain and then moved.
>
> I am attempting to create a template on a storage domain that does
> currently exist in my environment.  How would i remove the reference to
> this storage domain so it is not used?
>
>
>
> -Original Message-
> From: Shahar Havivi 
> To: Michal Skrivanek 
> Cc: Bryan Sockel , users 
> Date: Thu, 4 May 2017 08:19:34 +0300
> Subject: Re: [ovirt-users] VM Template Error
>
> According to the log the the storage domain (where the disk is stored is
> not exists)
> StorageDomainDoesNotExist: Storage domain does not exist:
> (u'2de6ad97-1f33-41e5-b021-bacec14ce6e4',)
>
> Does all the storage domain active in your data center?
> Did you move the disk or remove and added a different storage domain?
>
> On Wed, May 3, 2017 at 8:30 PM, Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>>
>>
>>
>> On 3 May 2017, at 16:09, Bryan Sockel  wrote:
>>
>> Hi.  the vm does exist and is bootable.  The vm only has one disk and it
>> is enabled.
>>
>>
>> yes, but the template’s copy of that disk somehow can’t be created.
>> Perhaps share more of the vdsm logs to see why the image copy failed
>>
>> Thanks,
>> michal
>>
>>
>>
>>
>> Thanks
>>
>>
>>
>> -Original Message-
>> From: Shahar Havivi 
>> To: Bryan Sockel 
>> Cc: "users@ovirt.org" 
>> Date: Wed, 3 May 2017 09:05:34 +0300
>> Subject: Re: [ovirt-users] VM Template Error
>>
>> its looks like vdsm complain that the image is not exists.
>> can you run the VM with no errors? (if the VM have more then one disk
>> make sure that its exists and accessible).
>>
>> if all good please attach the full vdsm and engine log.
>>
>>  Shahar.
>>
>> On Tue, May 2, 2017 at 6:29 PM, Bryan Sockel 
>> wrote:
>>>
>>> Hi,
>>>
>>> Having an issue a template from a VM's.
>>>
>>> I am getting the following errors:
>>> engine.log
>>> 2017-05-02 09:40:10,059-05 INFO  [org.ovirt.engine.core.dal.db
>>> broker.auditloghandling.AuditLogDirector] (default task-24) [2ef2fce]
>>> EVENT_ID: USER_ADD_VM_TEMPLATE(48), Correlation ID:
>>> 176fdfa7-0467-48f5-9ecc-901e86768c28, Job ID:
>>> fed9a848-1971-495a-a391-be1fa4a67908, Call Stack: null, Custom Event
>>> ID: -1, Message: Creation of Template test from VM Windows-10-Template was
>>> initiated by admin@internal-authz.
>>>
>>> 2017-05-02 09:48:43,059-05 ERROR [org.ovirt.engine.core.dal.dbb
>>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-20)
>>> [] EVENT_ID: USER_ADD_VM_TEMPLATE_FINISHED_FAILURE(52), Correlation ID:
>>> 176fdfa7-0467-48f5-9ecc-901e86768c28, Job ID:
>>> fed9a848-1971-495a-a391-be1fa4a67908, Call Stack: null, Custom Event
>>> ID: -1, Message: Failed to complete creation of Template test from VM
>>> Windows-10-Template.
>>>
>>> Events Log
>>> ID 10803 - VDSM command DeleteImageGroupVDS failed: Image does not exist
>>> in domain: u'image=6aa525ad-e7f1-432b-959a-2223f7e77083,
>>> domain=e371d380-7194-4950-b901-5f2aed5dfb35'
>>> ID 10802 - VDSM vm-host-colo-2 command HSMGetAllTasksStatusesVDS failed:
>>> low level Image copy failed
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [oVirt4.1] Does oVirt 4.1 support iSCSI offload?

[Yaniv Kaul]

On Wed, May 3, 2017 at 7:57 PM, wodel youchi  wrote:

> Hi again, and sorry for the delay, I was sick, actually I am still
> sick :-(
>
> Just to have more details, from what I have read about iSCSI offload,
> there are two modes, depending on the hardware you have (the adapter),
> using VMware terminology, no offense :-) , there is :
>
> - Dependent mode : in this mode the adapter still need the software iSCSI
> to use the network configuration of the nic port, so the discovery is done
> on tcp, the rest on offload driver like bnxi2.
>

This one is similar to TCP offload - the iSCSI processing is done on the
HW, the rest is done in software and is supported - it looks like regular
iSCSI to oVirt.

>
> - Independent mode : in this mode the adapter takes all the work by
> itself, the network part, it will have it's own IP address and so on, and
> it does not need anything from the OS or the software iSCSI, the
> configuration is made in the BIOS of the adapter, and the connection is
> made before the OS is up.
>

This one indeed is transparent to the OS, and it looks like FC to oVirt.


>
> Does the configuration on oVirt support the two modes? and is there any
> differences when using them, I mean during the setup.
>

Both are supported. The former looks like regular iSCSI, the latter like FC
to oVirt.
Y.


>
> Regards.
>
>
> 2017-04-30 7:47 GMT+01:00 Yaniv Kaul :
>
>>
>>
>> On Sat, Apr 29, 2017 at 7:27 PM, wodel youchi 
>> wrote:
>>
>>> Hi,
>>>
>>> We have two hypervisors, each one has a 10Gbe nic card with two ports,
>>> the cards support iSCSI offload.
>>>
>>> Does oVirt 4.1 support this?
>>>
>>
>> Yes.
>>
>>
>>> if yes how can someone use it on hosted-engine deployment? the VM engine
>>> will be in the SAN targeted by these cards.
>>>
>>
>> Since iSCSI offloading is configured before the OS even loads, to the OS
>> (and therefore oVirt hypervisors) it seems that the storage is 'just
>> connected' - same as FC for all we care.
>>
>> Y.
>>
>>
>>>
>>> Regards.
>>>
>>>
>>> 
>>>  Virus-free.
>>> www.avast.com
>>> 
>>> <#m_4334077165374483247_m_8732461098692771785_m_4452747818142096065_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Hosted Engine Setup fails

[Yaniv Kaul]

On Thu, May 4, 2017 at 8:45 PM, Manuel Luis Aznar <
manuel.luis.az...@gmail.com> wrote:

> Hello there,
>
> Sorry for the delay to answer the mail, but, I have been busy doing
> things...
>
> The permission on /dev/random are the following:
>
> [root@host1 manuel]# ls -la /dev/random
> crw-rw-rw-. 1 root root 1, 8 may  4 18:06 /dev/random
>
> Suppose that these permission should look something like:
>
> [root@host1 manuel]# ls -la /dev/random
> crw-rw-rw-. 1 vdsm kvm 1, 8 may  4 18:06 /dev/random
>
> Finally I do not know what you meant with permission on SELinux audit
> logs?¿? Sorry for my lack of understanding, so, please let me know much
> more precisely and I will look for it
>

You can get the selinux settings of a file with ls -Z . For example:
[ykaul@ykaul ovirt-system-tests]$ ls -Z /dev/kvm
system_u:object_r:kvm_device_t:s0 /dev/kv

Also, you can search for selinux issues either in /var/log/audit or using
ausearch. For example:
sudo ausearch -m AVC -i

Y.

>
>
> Thanks for all in advance
> I will be waiting for you
> Manuel Luis Aznar
>
> 2017-05-03 15:09 GMT+01:00 Simone Tiraboschi :
>
>>
>>
>> On Wed, May 3, 2017 at 11:30 AM, Manuel Luis Aznar <
>> manuel.luis.az...@gmail.com> wrote:
>>
>>> Hello Simone and all others,
>>>
>>> I have attached to the mail the requested files. If you have any other
>>> inquiry just say it, The failed installation drive would be keep safe until
>>> solving this problem.
>>>
>>> Thanks for all in advance
>>> Manuel
>>>
>>
>> The issue is here:
>> May  1 11:47:45 host1 journal: libvirt version: 2.0.0, package:
>> 10.el7_3.5 (CentOS BuildSystem ,
>> 2017-03-03-02:09:45, c1bm.rdu2.centos.org)
>> May  1 11:47:45 host1 journal: hostname: host1.bajada.es
>> May  1 11:47:45 host1 journal: Falló al conectar con el socket de
>> monitor: No existe el proceso
>> May  1 11:47:45 host1 journal: internal error: process exited while
>> connecting to monitor: /dev/random -device 
>> virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x7
>> -msg timestamp=on#012Could not access KVM kernel module: Permission
>> denied#012failed to initialize KVM: Permission denied
>> May  1 11:47:45 host1 journal: libvirt version: 2.0.0, package:
>> 10.el7_3.5 (CentOS BuildSystem ,
>> 2017-03-03-02:09:45, c1bm.rdu2.centos.org)
>> May  1 11:47:45 host1 journal: hostname: host1.bajada.es
>> May  1 11:47:45 host1 journal: Fin de archivo al leer datos: Error de
>> entrada/salida
>> May  1 11:47:45 host1 journal: Fin de archivo al leer datos: Error de
>> entrada/salida
>>
>> could you please also check the permission on /dev/random and SELinux
>> audit logs?
>>
>>
>>
>>>
>>> 2017-05-02 10:55 GMT+01:00 Simone Tiraboschi :
>>>
 Sure, but first we need to understand what it's happening: in our CI
 process everything is fine so I think it's something specific to your env.
 Could you please share your:
 /var/log/libvirt/qemu/HostedEngine.log
 /var/log/messages

 thanks,
 Simone


 On Tue, May 2, 2017 at 11:38 AM, Manuel Luis Aznar <
 manuel.luis.az...@gmail.com> wrote:

> Ok thankyou.
>
> Suppose that this problem probably would be solve in a future release.
>
> Thanks,
> Manuel
>
> 2017-05-02 10:35 GMT+01:00 Simone Tiraboschi :
>
>>
>>
>> On Tue, May 2, 2017 at 11:30 AM, Manuel Luis Aznar <
>> manuel.luis.az...@gmail.com> wrote:
>>
>>> Hello there again,
>>>
>>> Yes as I say, I have done several clean installations and the VM
>>> engine sometimes starts without any problem. So Simone any 
>>> recommendation
>>> to make the engine VM starts properly?¿
>>>
>>> While is installing the HA agent and HA broker are down, would I get
>>> good result by starting the services myself?¿
>>>
>>> Any help from Simone or somebody would be appreciated
>>> Thanks for all in advance
>>> Manuel Luis Aznar
>>>
>>
>> I suggest to check libvirt logs.
>>
>>
>>>
>>> 2017-05-02 7:54 GMT+01:00 Simone Tiraboschi :
>>>


 On Mon, May 1, 2017 at 3:14 PM, Manuel Luis Aznar <
 manuel.luis.az...@gmail.com> wrote:

> Hello there,
>
> I have been looking in the internet using google why my
> installation of ovirt-hosted-engine is failing.
>
> I have found this link:
>
>  https://www.mail-archive.com/users@ovirt.org/msg40864.html
> (Hosted engine install failed; vdsm upset about broker)
>
> It seems to be the same error...
>
> So to knarra and Jamie Lawrence my question is:
>
> Did you manage to discover the problem?? In my instalation I
> am using nfs and not gluster...
>
> I have read the error and is the same error
> 

Re: [ovirt-users] New oVirt Node install on oVirt Cluster 4.0.5 - How can I install oVirt Node with same 4.0.5 version ???

[Yaniv Kaul]

On Fri, May 5, 2017 at 9:03 PM, Rogério Ceni Coelho <
rogeriocenicoe...@gmail.com> wrote:

> Hi Yuval,
>
> Yes, it is, but every time I need to install a new oVirt node i will need
> to upgrade ovirt engine at least ?
>

Of course not. You can upgrade the Engine independently from the hosts.


> And i will need to upgrade ovirt nodes that already exist ? I have 20
> ovirt nodes  So, this means a lot of work.
>

No, you can upgrade each host independently.


>
> My enviroment are stable with 4.0.5 and i am happy for now. oVirt is an
> excellent product. Thanks for that.
>
> For example, this morning i try to put an export import storage domain in
> manteinance and an error occur only with my new ovirt node running 4.0.6.1
> and yesterday a lost 2 days debbuging another problem with network start
> with many vlans on 4.0.6.1 ... :-(
>

It'd be great if you can start a different thread about it, or file a bug,
with all the details (VDSM and Engine logs attached).
Y.


>
> StorageDomainDoesNotExist: Storage domain does not exist:
> (u'f9e051a9-6660-4e49-a3f1-354583501610',)
> Thread-12::DEBUG::2017-05-05 10:39:07,473::check::296::
> storage.check::(_start_process) START check 
> '/dev/c58ce4b0-7145-4cd0-900e-eeb99177a7de/metadata'
> cmd=['/usr/bin/taskset', '--cpu-list', '0-31', '/usr/bin/dd',
> 'if=/dev/c58ce4b0-7145-4cd0-900e-eeb99177a7de/metadata', 'of=/dev/null',
> 'bs=4096', 'count=1', 'iflag=direct'] delay=0.00
> Thread-12::DEBUG::2017-05-05 
> 10:39:07,524::asyncevent::564::storage.asyncevent::(reap)
> Process  terminated (count=1)
> Thread-12::DEBUG::2017-05-05 10:39:07,525::check::327::
> storage.check::(_check_completed) FINISH check
> '/dev/c58ce4b0-7145-4cd0-900e-eeb99177a7de/metadata' rc=0
> err=bytearray(b'1+0 records in\n1+0 records out\n4096 bytes (4.1 kB)
> copied, 0.000292117 s, 14.0 MB/s\n') elapsed=0.06
> Thread-12::DEBUG::2017-05-05 10:39:07,886::check::296::
> storage.check::(_start_process) START check u'/rhev/data-center/mnt/corot.
> rbs.com.br:_u00_oVirt_PRD_ISO__DOMAIN/7b8c9293-f103-401a-
> 93ac-550981837224/dom_md/metadata' cmd=['/usr/bin/taskset', '--cpu-list',
> '0-31', '/usr/bin/dd', u'if=/rhev/data-center/mnt/corot.rbs.com.br:
> _u00_oVirt_PRD_ISO__DOMAIN/7b8c9293-f103-401a-93ac-550981837224/dom_md/metadata',
> 'of=/dev/null', 'bs=4096', 'count=1', 'iflag=direct'] delay=0.00
> Thread-12::DEBUG::2017-05-05 10:39:07,898::check::296::
> storage.check::(_start_process) START check u'/rhev/data-center/mnt/
> dd6701.bkp.srvr.rbs.net:_data_col1_ovirt__prd/db89d5df-00ac-
> 4e58-a7e5-e31272f9ea92/dom_md/metadata' cmd=['/usr/bin/taskset',
> '--cpu-list', '0-31', '/usr/bin/dd', u'if=/rhev/data-center/mnt/
> dd6701.bkp.srvr.rbs.net:_data_col1_ovirt__prd/db89d5df-00ac-
> 4e58-a7e5-e31272f9ea92/dom_md/metadata', 'of=/dev/null', 'bs=4096',
> 'count=1', 'iflag=direct'] delay=0.00
> Thread-12::DEBUG::2017-05-05 10:39:07,906::check::327::
> storage.check::(_check_completed) FINISH check
> u'/rhev/data-center/mnt/corot.rbs.com.br:_u00_oVirt_PRD_ISO_
> _DOMAIN/7b8c9293-f103-401a-93ac-550981837224/dom_md/metadata' rc=0
> err=bytearray(b'0+1 records in\n0+1 records out\n386 bytes (386 B) copied,
> 0.00038325 s, 1.0 MB/s\n') elapsed=0.02
> Thread-12::DEBUG::2017-05-05 10:39:07,916::check::296::
> storage.check::(_start_process) START check u'/rhev/data-center/mnt/vnx01.
> srv.srvr.rbs.net:_fs__ovirt_prd__data__domain/fdcf130d-
> 53b8-4978-8f97-82f364639b4a/dom_md/metadata' cmd=['/usr/bin/taskset',
> '--cpu-list', '0-31', '/usr/bin/dd', u'if=/rhev/data-center/mnt/
> vnx01.srv.srvr.rbs.net:_fs__ovirt_prd__data__domain/
> fdcf130d-53b8-4978-8f97-82f364639b4a/dom_md/metadata', 'of=/dev/null',
> 'bs=4096', 'count=1', 'iflag=direct'] delay=0.00
> Thread-12::DEBUG::2017-05-05 10:39:07,930::check::327::
> storage.check::(_check_completed) FINISH check u'/rhev/data-center/mnt/
> dd6701.bkp.srvr.rbs.net:_data_col1_ovirt__prd/db89d5df-00ac-
> 4e58-a7e5-e31272f9ea92/dom_md/metadata' rc=0 err=bytearray(b'0+1 records
> in\n0+1 records out\n360 bytes (360 B) copied, 0.000363751 s, 990 kB/s\n')
> elapsed=0.03
> Thread-12::DEBUG::2017-05-05 
> 10:39:07,964::asyncevent::564::storage.asyncevent::(reap)
> Process  terminated (count=1)
> Thread-12::DEBUG::2017-05-05 10:39:07,964::check::327::
> storage.check::(_check_completed) FINISH check
> u'/rhev/data-center/mnt/vnx01.srv.srvr.rbs.net:_fs__ovirt_
> prd__data__domain/fdcf130d-53b8-4978-8f97-82f364639b4a/dom_md/metadata'
> rc=0 err=bytearray(b'0+1 records in\n0+1 records out\n369 bytes (369 B)
> copied, 0.000319659 s, 1.2 MB/s\n') elapsed=0.05
> Thread-12::DEBUG::2017-05-05 10:39:09,035::check::296::
> storage.check::(_start_process) START check 
> '/dev/1804d02e-7865-4acd-a04f-8200ac2d2b84/metadata'
> cmd=['/usr/bin/taskset', '--cpu-list', '0-31', '/usr/bin/dd',
> 'if=/dev/1804d02e-7865-4acd-a04f-8200ac2d2b84/metadata', 'of=/dev/null',
> 'bs=4096', 'count=1', 'iflag=direct'] delay=0.00
> Thread-12::DEBUG::2017-05-05 
> 

Re: [ovirt-users] High latency on storage domains and sanlock renewal error

[Yaniv Kaul]

On Tue, May 2, 2017 at 11:09 PM, Stefano Bovina  wrote:

> Hi, the engine logs show high latency on storage domains: "Storage domain
>  experienced a high latency of 19.2814 seconds from .. This may
> cause performance and functional issues."
>
> Looking at host logs, I found also these locking errors:
>
> 2017-05-02 20:52:13+0200 33883 [10098]: s1 renewal error -202 delta_length
> 10 last_success 33853
> 2017-05-02 20:52:19+0200 33889 [10098]: 6a386652 aio collect 0
> 0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe9fb000 result 1048576:0 other free
> 2017-05-02 21:08:51+0200 34880 [10098]: 6a386652 aio timeout 0
> 0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe4f2000 ioto 10 to_count 24
> 2017-05-02 21:08:51+0200 34880 [10098]: s1 delta_renew read rv -202 offset
> 0 /dev/6a386652-629d-4045-835b-21d2f5c104aa/ids
> 2017-05-02 21:08:51+0200 34880 [10098]: s1 renewal error -202 delta_length
> 10 last_success 34850
> 2017-05-02 21:08:53+0200 34883 [10098]: 6a386652 aio collect 0
> 0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe4f2000 result 1048576:0 other free
> 2017-05-02 21:30:40+0200 36189 [10098]: 6a386652 aio timeout 0
> 0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe9fb000 ioto 10 to_count 25
> 2017-05-02 21:30:40+0200 36189 [10098]: s1 delta_renew read rv -202 offset
> 0 /dev/6a386652-629d-4045-835b-21d2f5c104aa/ids
> 2017-05-02 21:30:40+0200 36189 [10098]: s1 renewal error -202 delta_length
> 10 last_success 36159
> 2017-05-02 21:30:45+0200 36195 [10098]: 6a386652 aio collect 0
> 0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe9fb000 result 1048576:0 other free
>
> and this vdsm errors too:
>
> Thread-22::ERROR::2017-05-02 21:53:48,147::sdc::137::Storag
> e.StorageDomainCache::(_findDomain) looking for unfetched domain
> f8f21d6c-2425-45c4-aded-4cb9b53ebd96
> Thread-22::ERROR::2017-05-02 21:53:48,148::sdc::154::Storag
> e.StorageDomainCache::(_findUnfetchedDomain) looking for domain
> f8f21d6c-2425-45c4-aded-4cb9b53ebd96
>
> Engine instead is showing this errors:
>
> 2017-05-02 21:40:38,089 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler_Worker-96)
> Command SpmStatusVDSCommand(HostName = , HostId =
> dcc0275a-b011-4e33-bb95-366ffb0697b3, storagePoolId =
> 715d1ba2-eabe-48db-9aea-c28c30359808) execution failed. Exception:
> VDSErrorException: VDSGenericException: VDSErrorException: Failed to
> SpmStatusVDS, error = (-202, 'Sanlock resource read failure', 'Sanlock
> exception'), code = 100
> 2017-05-02 21:41:08,431 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler_Worker-53)
> [6e0d5ebf] Failed in SpmStatusVDS method
> 2017-05-02 21:41:08,443 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler_Worker-53)
> [6e0d5ebf] Command SpmStatusVDSCommand(HostName = ,
> HostId = 7991933e-5f30-48cd-88bf-b0b525613384, storagePoolId =
> 4bd73239-22d0-4c44-ab8c-17adcd580309) execution failed. Exception:
> VDSErrorException: VDSGenericException: VDSErrorException: Failed to
> SpmStatusVDS, error = (-202, 'Sanlock resource read failure', 'Sanlock
> exception'), code = 100
> 2017-05-02 21:41:31,975 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler_Worker-61)
> [2a54a1b2] Failed in SpmStatusVDS method
> 2017-05-02 21:41:31,987 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler_Worker-61)
> [2a54a1b2] Command SpmStatusVDSCommand(HostName = ,
> HostId = dcc0275a-b011-4e33-bb95-366ffb0697b3, storagePoolId =
> 715d1ba2-eabe-48db-9aea-c28c30359808) execution failed. Exception:
> VDSErrorException: VDSGenericException: VDSErrorException: Failed to
> SpmStatusVDS, error = (-202, 'Sanlock resource read failure', 'Sanlock
> exception'), code = 100
>
>
> I'm using Fibre Channel or FCoE connectivity; storage array technical
> support has analyzed it (also switch and OS configurations), but nothing
> has been found.
>

Is this on a specific hosts, or multiple hosts?
Is that FC or FCoE? Anything on the host's /var/log/messages?


>
> Any advice?
>
> Thanks
>
>
> Installation info:
>
> ovirt-release35-006-1.noarch
>

This is a very old release, I suggest, regardless of this issue, to upgrade.
Y.


> libgovirt-0.3.3-1.el7_2.1.x86_64
> vdsm-4.16.30-0.el7.centos.x86_64
> vdsm-xmlrpc-4.16.30-0.el7.centos.noarch
> vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch
> vdsm-jsonrpc-4.16.30-0.el7.centos.noarch
> vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch
> vdsm-python-4.16.30-0.el7.centos.noarch
> vdsm-cli-4.16.30-0.el7.centos.noarch
> qemu-kvm-ev-2.3.0-29.1.el7.x86_64
> qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64
> qemu-kvm-tools-ev-2.3.0-29.1.el7.x86_64
> libvirt-client-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-storage-1.2.17-13.el7_2.3.x86_64
> libvirt-python-1.2.17-2.el7.x86_64
> libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.3.x86_64
> libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.3.x86_64
> 

Re: [ovirt-users] command not found

[Yaniv Kaul]

On Sun, May 7, 2017 at 1:57 AM, Brahim Rifahi 
wrote:

> I am having issues installing oVirt on a CentOS 7 server. After logging in
> as sudo, I run the following series of commands:
>
> # yum -y update
> # yum install http://plain.resources.ovirt.org/pub/yum-repo/ovirt-
> release41.rpm
> 
> # yum -y install ovirt-engine
>
> I then attempted to use the following command and received a “command not
> found” error.
>

Which command exactly failed?
Y.


>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] VM disk update failure

[Stefano Bovina]

Hi, while trying to update a VM disk, a failure was returned (forcing me to
add a new disk)

Any advice on how to resolve this error?

Thanks


Installation info:

ovirt-release35-006-1.noarch
libgovirt-0.3.3-1.el7_2.1.x86_64
vdsm-4.16.30-0.el7.centos.x86_64
vdsm-xmlrpc-4.16.30-0.el7.centos.noarch
vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch
vdsm-jsonrpc-4.16.30-0.el7.centos.noarch
vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch
vdsm-python-4.16.30-0.el7.centos.noarch
vdsm-cli-4.16.30-0.el7.centos.noarch
qemu-kvm-ev-2.3.0-29.1.el7.x86_64
qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64
qemu-kvm-tools-ev-2.3.0-29.1.el7.x86_64
libvirt-client-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-storage-1.2.17-13.el7_2.3.x86_64
libvirt-python-1.2.17-2.el7.x86_64
libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.3.x86_64
libvirt-lock-sanlock-1.2.17-13.el7_2.3.x86_64
libvirt-glib-0.1.9-1.el7.x86_64
libvirt-daemon-driver-network-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-lxc-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-interface-1.2.17-13.el7_2.3.x86_64
libvirt-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-config-network-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-secret-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-qemu-1.2.17-13.el7_2.3.x86_64


 engine.log

2017-05-02 09:48:26,505 INFO  [org.ovirt.engine.core.bll.UpdateVmDiskCommand]
(ajp--127.0.0.1-8702-6) [c3d7125] Lock Acquired to object EngineLock
[exclusiveLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value:
VM_DISK_BOOT
key: c5fb9190-d059-4d9b-af23-07618ff660ce value: DISK
, sharedLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value: VM
]
2017-05-02 09:48:26,515 INFO  [org.ovirt.engine.core.bll.UpdateVmDiskCommand]
(ajp--127.0.0.1-8702-6) [c3d7125] Running command: UpdateVmDiskCommand
internal: false. Entities affected :  ID: c5fb9190-d059-4d9b-af23-07618ff660ce
Type: DiskAction group EDIT_DISK_PROPERTIES with role type USER
2017-05-02 09:48:26,562 INFO
[org.ovirt.engine.core.bll.ExtendImageSizeCommand]
(ajp--127.0.0.1-8702-6) [ae718d8] Running command: ExtendImageSizeCommand
internal: true. Entities affected :  ID: c5fb9190-d059-4d9b-af23-07618ff660ce
Type: DiskAction group EDIT_DISK_PROPERTIES with role type USER
2017-05-02 09:48:26,565 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.ExtendImageSizeVDSCommand]
(ajp--127.0.0.1-8702-6) [ae718d8] START, ExtendImageSizeVDSCommand(
storagePoolId = 715d1ba2-eabe-48db-9aea-c28c30359808, ignoreFailoverLimit =
false), log id: 52aac743
2017-05-02 09:48:26,604 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.ExtendImageSizeVDSCommand]
(ajp--127.0.0.1-8702-6) [ae718d8] FINISH, ExtendImageSizeVDSCommand, log
id: 52aac743
2017-05-02 09:48:26,650 INFO
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
(ajp--127.0.0.1-8702-6) [ae718d8] CommandAsyncTask::Adding
CommandMultiAsyncTasks object for command cb7958d9-6eae-44a9-891a-
7fe088a79df8
2017-05-02 09:48:26,651 INFO
[org.ovirt.engine.core.bll.CommandMultiAsyncTasks]
(ajp--127.0.0.1-8702-6) [ae718d8] CommandMultiAsyncTasks::AttachTask:
Attaching task 769a4b18-182b-4048-bb34-a276a55ccbff to command
cb7958d9-6eae-44a9-891a-7fe088a79df8.
2017-05-02 09:48:26,661 INFO
[org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
(ajp--127.0.0.1-8702-6) [ae718d8] Adding task
769a4b18-182b-4048-bb34-a276a55ccbff
(Parent Command UpdateVmDisk, Parameters Type org.ovirt.engine.core.common.
asynctasks.AsyncTaskParameters), polling hasn't started yet..
2017-05-02 09:48:26,673 INFO  [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-6)
[ae718d8] Correlation ID: c3d7125, Call Stack: null, Custom Event ID: -1,
Message: VM sysinfo-73 sysinfo-73_Disk3 disk was updated by admin@internal.
2017-05-02 09:48:26,674 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
(ajp--127.0.0.1-8702-6) [ae718d8] BaseAsyncTask::startPollingTask: Starting
to poll task 769a4b18-182b-4048-bb34-a276a55ccbff.
2017-05-02 09:48:28,430 INFO
[org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
(DefaultQuartzScheduler_Worker-48) [36cd2f7] Polling and updating Async
Tasks: 1 tasks, 1 tasks to poll now
2017-05-02 09:48:28,435 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.
HSMGetAllTasksStatusesVDSCommand] (DefaultQuartzScheduler_Worker-48)
[36cd2f7] Failed in HSMGetAllTasksStatusesVDS method
2017-05-02 09:48:28,436 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
(DefaultQuartzScheduler_Worker-48) [36cd2f7] SPMAsyncTask::PollTask:
Polling task 769a4b18-182b-4048-bb34-a276a55ccbff (Parent Command
UpdateVmDisk, Parameters Type
org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters)
returned status finished, result 'cleanSuccess'.
2017-05-02 09:48:28,446 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
(DefaultQuartzScheduler_Worker-48) [36cd2f7] 

[ovirt-users] High latency on storage domains and sanlock renewal error

[Stefano Bovina]

Hi, the engine logs show high latency on storage domains: "Storage domain
 experienced a high latency of 19.2814 seconds from .. This may
cause performance and functional issues."

Looking at host logs, I found also these locking errors:

2017-05-02 20:52:13+0200 33883 [10098]: s1 renewal error -202 delta_length
10 last_success 33853
2017-05-02 20:52:19+0200 33889 [10098]: 6a386652 aio collect 0
0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe9fb000 result 1048576:0 other free
2017-05-02 21:08:51+0200 34880 [10098]: 6a386652 aio timeout 0
0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe4f2000 ioto 10 to_count 24
2017-05-02 21:08:51+0200 34880 [10098]: s1 delta_renew read rv -202 offset
0 /dev/6a386652-629d-4045-835b-21d2f5c104aa/ids
2017-05-02 21:08:51+0200 34880 [10098]: s1 renewal error -202 delta_length
10 last_success 34850
2017-05-02 21:08:53+0200 34883 [10098]: 6a386652 aio collect 0
0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe4f2000 result 1048576:0 other free
2017-05-02 21:30:40+0200 36189 [10098]: 6a386652 aio timeout 0
0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe9fb000 ioto 10 to_count 25
2017-05-02 21:30:40+0200 36189 [10098]: s1 delta_renew read rv -202 offset
0 /dev/6a386652-629d-4045-835b-21d2f5c104aa/ids
2017-05-02 21:30:40+0200 36189 [10098]: s1 renewal error -202 delta_length
10 last_success 36159
2017-05-02 21:30:45+0200 36195 [10098]: 6a386652 aio collect 0
0x7f1fb80008c0:0x7f1fb80008d0:0x7f1fbe9fb000 result 1048576:0 other free

and this vdsm errors too:

Thread-22::ERROR::2017-05-02 21:53:48,147::sdc::137::
Storage.StorageDomainCache::(_findDomain) looking for unfetched domain
f8f21d6c-2425-45c4-aded-4cb9b53ebd96
Thread-22::ERROR::2017-05-02 21:53:48,148::sdc::154::
Storage.StorageDomainCache::(_findUnfetchedDomain) looking for domain
f8f21d6c-2425-45c4-aded-4cb9b53ebd96

Engine instead is showing this errors:

2017-05-02 21:40:38,089 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-96) Command SpmStatusVDSCommand(HostName = <
myhost.example.com>, HostId = dcc0275a-b011-4e33-bb95-366ffb0697b3,
storagePoolId = 715d1ba2-eabe-48db-9aea-c28c30359808) execution failed.
Exception: VDSErrorException: VDSGenericException: VDSErrorException:
Failed to SpmStatusVDS, error = (-202, 'Sanlock resource read failure',
'Sanlock exception'), code = 100
2017-05-02 21:41:08,431 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-53) [6e0d5ebf] Failed in SpmStatusVDS method
2017-05-02 21:41:08,443 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-53) [6e0d5ebf] Command
SpmStatusVDSCommand(HostName = , HostId =
7991933e-5f30-48cd-88bf-b0b525613384, storagePoolId =
4bd73239-22d0-4c44-ab8c-17adcd580309) execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
SpmStatusVDS, error = (-202, 'Sanlock resource read failure', 'Sanlock
exception'), code = 100
2017-05-02 21:41:31,975 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-61) [2a54a1b2] Failed in SpmStatusVDS method
2017-05-02 21:41:31,987 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-61) [2a54a1b2] Command
SpmStatusVDSCommand(HostName = , HostId =
dcc0275a-b011-4e33-bb95-366ffb0697b3, storagePoolId =
715d1ba2-eabe-48db-9aea-c28c30359808) execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
SpmStatusVDS, error = (-202, 'Sanlock resource read failure', 'Sanlock
exception'), code = 100


I'm using Fibre Channel or FCoE connectivity; storage array technical
support has analyzed it (also switch and OS configurations), but nothing
has been found.

Any advice?

Thanks


Installation info:

ovirt-release35-006-1.noarch
libgovirt-0.3.3-1.el7_2.1.x86_64
vdsm-4.16.30-0.el7.centos.x86_64
vdsm-xmlrpc-4.16.30-0.el7.centos.noarch
vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch
vdsm-jsonrpc-4.16.30-0.el7.centos.noarch
vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch
vdsm-python-4.16.30-0.el7.centos.noarch
vdsm-cli-4.16.30-0.el7.centos.noarch
qemu-kvm-ev-2.3.0-29.1.el7.x86_64
qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64
qemu-kvm-tools-ev-2.3.0-29.1.el7.x86_64
libvirt-client-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-storage-1.2.17-13.el7_2.3.x86_64
libvirt-python-1.2.17-2.el7.x86_64
libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.3.x86_64
libvirt-lock-sanlock-1.2.17-13.el7_2.3.x86_64
libvirt-glib-0.1.9-1.el7.x86_64
libvirt-daemon-driver-network-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-lxc-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-interface-1.2.17-13.el7_2.3.x86_64
libvirt-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-config-network-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-driver-secret-1.2.17-13.el7_2.3.x86_64
libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.3.x86_64

[ovirt-users] use ovirt sdk with python to query memory/cpu usage on hpyervisors

[Jia Zhang]

Hi all:
This is Kevin Zhang from Beijing. Nice to meet you!
Now I am trying to use python SDK to get a  script to  get the overview of
ovirt engine so we don't have to always log in the web portal .
 I have finished some basic features. but now I stuck on one feature as
subject and I cannot work it out after some trying and googling . So I'd
like to turn some guide from gurus like you.
Issue is:
On a ovirt engine( or RHEV) version 4.0, I would like to use the python SDK
to get a the memory and CPU usage percentage info on each hypervisor, just
like what the webportal showed us as attached. I tried with the options in
api.host.list(), but I don't get the place to query the info.
I am not sure if I am in the wrong direction. Can you kindly shed some
light on it?

Best Regards
Kevin Zhang


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users