- Users - oVirt List Archives

High latency on storage domains and sanlock renewal error
by Stefano Bovina 13 May '17

13 May '17

Hi, the engine logs show high latency on storage domains: "Storage domain <xxxx> 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 = <myhost.example.com>, 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 = <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 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 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 ------- vdsm.log (high latency) Thread-21::DEBUG::2017-05-02 18:02:23,646::fileSD::261:: Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '0+1 records in\n0+1 records out\n331 bytes (331 B) copied, 0.000285529 s, 1.2 MB/s\n'; <rc> = 0 Thread-18::DEBUG::2017-05-02 18:02:24,335::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) /bin/dd if=/dev/2c501858-bf8d-49a5-a42b-bca341b47827/metadata iflag=direct of=/dev/null bs=4096 count=1 (cwd None) Thread-18::DEBUG::2017-05-02 18:02:24,343::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '1+0 records in\n1+0 records out\n4096 bytes (4.1 kB) copied, 0.000489782 s, 8.4 MB/s\n'; <rc> = 0 Thread-19::DEBUG::2017-05-02 18:02:24,635::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) /bin/dd if=/dev/c5dc09c4-cd79-42d2-a5af-89953076f79e/metadata iflag=direct of=/dev/null bs=4096 count=1 (cwd None) Thread-19::DEBUG::2017-05-02 18:02:24,643::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '1+0 records in\n1+0 records out\n4096 bytes (4.1 kB) copied, 0.000558622 s, 7.3 MB/s\n'; <rc> = 0 Thread-22::DEBUG::2017-05-02 18:02:24,722::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) /bin/dd if=/dev/f8f21d6c-2425-45c4-aded-4cb9b53ebd96/metadata iflag=direct of=/dev/null bs=4096 count=1 (cwd None) Thread-22::DEBUG::2017-05-02 18:02:24,729::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '1+0 records in\n1+0 records out\n4096 bytes (4.1 kB) copied, 0.000632576 s, 6.5 MB/s\n'; <rc> = 0 JsonRpc (StompReactor)::DEBUG::2017-05-02 18:02:25,056::stompReactor:: 98::Broker.StompAdapter::(handle_frame) Handling message <StompFrame command='SEND'> JsonRpcServer::DEBUG::2017-05-02 18:02:25,057::__init__::506:: jsonrpc.JsonRpcServer::(serve_requests) Waiting for request Thread-9372::DEBUG::2017-05-02 18:02:25,060::stompReactor:: 163::yajsonrpc.StompServer::(send) Sending response Thread-20::DEBUG::2017-05-02 18:02:25,895::blockSD::596:: Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '1+0 records in\n1+0 records out\n4096 bytes (4.1 kB) copied, 19.2814 s, 0.2 kB/s\n'; <rc> = 0 JsonRpc (StompReactor)::DEBUG::2017-05-02 18:02:28,075::stompReactor:: 98::Broker.StompAdapter::(handle_frame) Handling message <StompFrame command='SEND'> JsonRpcServer::DEBUG::2017-05-02 18:02:28,076::__init__::506:: jsonrpc.JsonRpcServer::(serve_requests) Waiting for request Thread-9373::DEBUG::2017-05-02 18:02:28,078::stompReactor:: 163::yajsonrpc.StompServer::(send) Sending response JsonRpc (StompReactor)::DEBUG::2017-05-02 18:02:31,094::stompReactor:: 98::Broker.StompAdapter::(handle_frame) Handling message <StompFrame command='SEND'> JsonRpcServer::DEBUG::2017-05-02 18:02:31,095::__init__::506:: jsonrpc.JsonRpcServer::(serve_requests) Waiting for request Thread-9374::DEBUG::2017-05-02 18:02:31,097::stompReactor:: 163::yajsonrpc.StompServer::(send) Sending response Thread-21::DEBUG::2017-05-02 18:02:33,652::fileSD::261:: Storage.Misc.excCmd::(getReadDelay) /bin/dd if=/rhev/data-center/mnt/<myho st.example.com>:_ISO/f105bdc6-efdc-445c-b49e-aa38c91c2569/dom_md/metadata iflag=direct of=/dev/null bs=4096 count=1 (cwd None) Thread-21::DEBUG::2017-05-02 18:02:33,660::fileSD::261:: Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '0+1 records in\n0+1 records out\n331 bytes (331 B) copied, 0.000246594 s, 1.3 MB/s\n'; <rc> = 0 JsonRpc (StompReactor)::DEBUG::2017-05-02 18:02:34,112::stompReactor:: 98::Broker.StompAdapter::(handle_frame) Handling message <StompFrame command='SEND'> JsonRpcServer::DEBUG::2017-05-02 18:02:34,114::__init__::506:: jsonrpc.JsonRpcServer::(serve_requests) Waiting for request Thread-9375::DEBUG::2017-05-02 18:02:34,117::task::595:: Storage.TaskManager.Task::(_updateState) Task=`ea63814e-d25d-4436-8bb5-cfc67af6498d`::moving from state init -> state preparing Thread-9375::INFO::2017-05-02 18:02:34,117::logUtils::44::dispatcher::(wrapper) Run and protect: repoStats(options=None) Thread-9375::INFO::2017-05-02 18:02:34,118::logUtils::47::dispatcher::(wrapper) Run and protect: repoStats, Return response: {'2c501858-bf8d-49a5-a42b-bca341b47827': {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000489782', 'lastCheck': '9.8', 'valid': True}, 'f8f21d6c-2425-45c4-aded-4cb9b53ebd96': {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000632576', 'lastCheck': '9.4', 'valid': True}, '6a386652-629d-4045-835b-21d2f5c104aa': {'code': 0, 'version': 3, 'acquired': True, 'delay': '19.2814', 'lastCheck': '8.2', 'valid': True}, 'f105bdc6-efdc-445c-b49e-aa38c91c2569': {'code': 0, 'version': 0, 'acquired': True, 'delay': '0.000246594', 'lastCheck': '0.5', 'valid': True}, 'c5dc09c4-cd79-42d2-a5af-89953076f79e': {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000558622', 'lastCheck': '9.5', 'valid': True}} Thread-9375::DEBUG::2017-05-02 18:02:34,118::task::1191:: Storage.TaskManager.Task::(prepare) Task=`ea63814e-d25d-4436-8bb5-cfc67af6498d`::finished: {'2c501858-bf8d-49a5-a42b-bca341b47827': {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000489782', 'lastCheck': '9.8', 'valid': True}, 'f8f21d6c-2425-45c4-aded-4cb9b53ebd96': {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000632576', 'lastCheck': '9.4', 'valid': True}, '6a386652-629d-4045-835b-21d2f5c104aa': {'code': 0, 'version': 3, 'acquired': True, 'delay': '19.2814', 'lastCheck': '8.2', 'valid': True}, 'f105bdc6-efdc-445c-b49e-aa38c91c2569': {'code': 0, 'version': 0, 'acquired': True, 'delay': '0.000246594', 'lastCheck': '0.5', 'valid': True}, 'c5dc09c4-cd79-42d2-a5af-89953076f79e': {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000558622', 'lastCheck': '9.5', 'valid': True}} Thread-9375::DEBUG::2017-05-02 18:02:34,119::task::595:: Storage.TaskManager.Task::(_updateState) Task=`ea63814e-d25d-4436-8bb5-cfc67af6498d`::moving from state preparing -> state finished Thread-9375::DEBUG::2017-05-02 18:02:34,119::resourceManager: :940::Storage.ResourceManager.Owner::(releaseAll) Owner.releaseAll requests {} resources {} Thread-9375::DEBUG::2017-05-02 18:02:34,119::resourceManager: :977::Storage.ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {} Thread-9375::DEBUG::2017-05-02 18:02:34,119::task::993:: Storage.TaskManager.Task::(_decref) Task=`ea63814e-d25d-4436-8bb5-cfc67af6498d`::ref 0 aborting False Thread-9375::DEBUG::2017-05-02 18:02:34,122::stompReactor:: 163::yajsonrpc.StompServer::(send) Sending response JsonRpc (StompReactor)::DEBUG::2017-05-02 18:02:34,128::stompReactor:: 98::Broker.StompAdapter::(handle_frame) Handling message <StompFrame command='SEND'> JsonRpcServer::DEBUG::2017-05-02 18:02:34,129::__init__::506:: jsonrpc.JsonRpcServer::(serve_requests) Waiting for request Thread-9376::DEBUG::2017-05-02 18:02:34,132::stompReactor:: 163::yajsonrpc.StompServer::(send) Sending response

3 10

User story
by Johannes Spanier 13 May '17

13 May '17

Hi oVirt community. I did a short series for tweets @jospanier judging my first time user experience with several virtualization platforms and was asked by Sandro Bonazzola to elaborate a bit further than what fits into 140 chars. I had a specific use case: The small-ish learning lab with only 2-3 nodes and it needs to be free. I also wanted live migration to stay flexible with my hosts. I currently use my lab for to run ~10 virtual CSR1000V routers on free ESXi in addition to some real router hardware. I want to expand the lab to be able to explore some other technologies as well like network automation, SDN, infrastructure as code and the likes. The lineup for the PoC was oVirt, ESXi, Openstack and Proxmox VE. I my tweets I was referring to a) the install procedure and b) the operational experience. Here is what I found. These findings are highly subjective and debatable. I am aware of that. Both ESXi and Proxmox VE is trivial to install. You grab the ISO image, use a tool like Rufus to make an bootable USB stick or use iLO virtual CD functionality and off you go. Both installers do not ask many questions and just do their job. After installation ESXi is all ready to run. Just open the WebGui and start deploying your first node. With Proxmox VE you get a TUI wizard guiding you though the last steps. After that the WebGui is ready and you can deploy your first VM immediately. I found oVirt a bit more involved to install. You have to install the Engine on one node and then register the other hosts with it. While that process is easy to handle it is a bit more work. A big thing for me was that at first glance there did no seem to be a "single node" install. My fist impression was that I needed a minimum of two servers. Of course later I learned about the Hosted Engine and the All-In-One install. Do not get me wrong. First time oVirt installation is still easy to handle on a quiet afternoon. Openstack installation compared to that is a PITA nightmare. I tried both RDO (TripleO) and Fuel for setup but gave up after two days for both, confused about what I actually need to do for a start. Got some nodes running with Fuel but was not satisfied. I then followed the Openstack manual Install Guide. I have a day job, so it took me about 5 days to get through the whole procedure, but a least I understood what was going on and what I needed to do. So that was my "first day" experience with those. Now for the "second day" i.e. operation. ESXi and Proxmox VE are both very simple to understand. You usually do not need a manual to find you way around. Deploying a VM is a breeze. oVirt is pretty simple to understand too. But you have to wrap your head around the Data Center principle underpinning everything. Its just a bit more complicated. On one or two occasions while playing around it was unclear at first why my datacenter was offline and I had to consult the manual for that. One can immediately feel that multi-tenancy is a big benefit of oVirt that is not so obvious in ESXi and Proxmox. But it comes with the price of added complexity. The new WebGui in the ESXi 6.5 I used is sloooow but some functions are not available with the vSphere Client Tool any more. Proxmox and oVirt WebGui are very responsive and "feel" way better. The Openstack WebGui is also quite nice. If you want to build a private multi-teneant scale-out cloud OpenStack is probably your best horse in the stable. But for my purpose it was just overkill. The process of deploying a simple VM was the most work from all four tools. Wrap-up For the specific use-case (see above) Proxmox VE was the best fit for me, closely followed by oVirt due to the more involved installation. ESXi comes in lagging in third place as it does not offer live migration in the free version and due to the poor WebGui experience I got. Also you have to pay big bucks to get the same functionality as in the other three. Openstack is placed at a distant fourth place for this use case. Hope that was interesting. Do reach out to me on twitter if you have any further questions or suggestions. Regards Johannes

2 1

can i Extend volume from replica 2 to replica 3 with arbiter
by Khalid Jamal 13 May '17

13 May '17

1 0

ansible and list of vms
by Nathanaël Blanchet 12 May '17

12 May '17

Hello, I didn't find anyway to easy list all my vms thanks to the ansible modules... I tried the ovirt4.py script which is able to list the whole facts, so vms list, when the number of them is small in a test datacenter, but in a production datacenter, I get an issue: File "./ovirt4.py", line 262, in <module> main() File "./ovirt4.py", line 254, in main vm_name=args.host, File "./ovirt4.py", line 213, in get_data vms[name] = get_dict_of_struct(connection, vm) File "./ovirt4.py", line 185, in get_dict_of_struct (device.name, [ip.address for ip in device.ips]) for device in devices File "./ovirt4.py", line 185, in <genexpr> (device.name, [ip.address for ip in device.ips]) for device in devices TypeError: 'NoneType' object is not iterable What is the simpliest way to get this basic information with sdk4??? (with sdk3 : ovirt-shell -E "list vms") -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 9

Re: [ovirt-users] Ovirt + Citrix Xenserver support?
by Peter Wood 12 May '17

12 May '17

Thank you for replying. I must've hit Reply instead of Reply All. I copied the ML to this email. Your answer may be helpful to other people too. Thanks, -- Peter On Thu, May 11, 2017 at 10:37 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > On Thu, May 11, 2017 at 11:33 PM, Peter Wood <peterwood.sd(a)gmail.com> > wrote: > >> I believe the question was about Citrix Xen. The URL that was pointed out >> talks about Xen on RHEL. >> >> Are you saying that Citrix Xen VMs conversion to oVirt is also supported? >> > > I would suggest to keep users(a)ovirt.org in CC next time :-) > I'm not sure about direct conversion from Citrix Xen, according to > http://libguestfs.org/virt-v2v.1.html it has not been recently tested but > it's supposed to work. > In the past there were issues but according to https://access.redhat.com/ > solutions/54076 a workaround is to use p2v instead of v2v. > > > > >> >> On Thu, May 11, 2017 at 8:14 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> >>> >>> On Tue, May 9, 2017 at 12:29 PM, santosh bhabal <sdbhabal(a)gmail.com> >>> wrote: >>> >>>> Hello Experts, >>>> >>>> I am new to Ovirt community. >>>> >>> >>> Hi, welcome to the oVirt community! >>> >>> >>> >>>> Apology if this question has asked earlier. >>>> I just wanted to know that does Ovirt support Citrix Xenserver or not? >>>> >>> >>> Sadly oVirt doesn't support Xen. There was an attempt in the past to >>> support it, see http://www.ovirt.org/documentation/how-to/xen/ but it >>> has been abanoned. >>> >>> However, we support conversion of VMs from Xen to oVirt (see >>> http://www.ovirt.org/develop/release-management/features/vir >>> t/virt-v2v-integration/ ) so you can setup an oVirt datacenter next to >>> the Xen one and move VMs to oVirt / KVM. >>> >>> >>> >>>> >>>> Reagrds >>>> Santosh. >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>>> >>> >>> >>> -- >>> >>> SANDRO BONAZZOLA >>> >>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> <https://red.ht/sig> >>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> > > > -- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >

1 0

Re: [ovirt-users] oVirt Hosted Engine Setup fails
by Manuel Luis Aznar 12 May '17

12 May '17

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 2017-05-02 10:55 GMT+01:00 Simone Tiraboschi <stirabos(a)redhat.com>: > 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.aznar(a)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 <stirabos(a)redhat.com>: >> >>> >>> >>> On Tue, May 2, 2017 at 11:30 AM, Manuel Luis Aznar < >>> manuel.luis.aznar(a)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 <stirabos(a)redhat.com>: >>>> >>>>> >>>>> >>>>> On Mon, May 1, 2017 at 3:14 PM, Manuel Luis Aznar < >>>>> manuel.luis.aznar(a)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 "BrokerConnectionError: >>>>>> ...". The ovirt-ha-agent and ovirt-ha-broker did not start when the >>>>>> installation is creating the engine VM... >>>>>> >>>>> >>>>> This is just a false positive: the HA agent and the HA broker are >>>>> still down so vdsm is complaining but at that point it's absolutely fine by >>>>> itself since the engine VM still doesn't exists. >>>>> We already have an open bug to reduce the impact of that message. >>>>> >>>>> The real issue is that for some reason the engine VM could not start >>>>> on your system. >>>>> >>>>> >>>>>> >>>>>> As I have said before any help would be very appreciated...no matter >>>>>> whom will give it >>>>>> Thanks for all in advance >>>>>> Manuel Luis Aznar >>>>>> >>>>>> >>>>>> >>>>>> 2017-05-01 12:21 GMT+01:00 Manuel Luis Aznar < >>>>>> manuel.luis.aznar(a)gmail.com>: >>>>>> >>>>>>> Hello Simone and all the comunity, >>>>>>> >>>>>>> I have been doing the instalation of ovirt hosted engine again and >>>>>>> it fails, libvirtd and vdsmd services are failing. They are failing with >>>>>>> the following errors: >>>>>>> >>>>>>> >>>>>>> libvirt daemon >>>>>>> >>>>>>> libvirtd.service - Virtualization daemon >>>>>>> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; >>>>>>> enabled; vendor preset: enabled) >>>>>>> Drop-In: /etc/systemd/system/libvirtd.service.d >>>>>>> ââunlimited-core.conf >>>>>>> Active: active (running) since lun 2017-05-01 11:43:49 WEST; >>>>>>> 14min ago >>>>>>> Docs: man:libvirtd(8) >>>>>>> http://libvirt.org >>>>>>> Main PID: 21993 (libvirtd) >>>>>>> CGroup: /system.slice/libvirtd.service >>>>>>> ââ21993 /usr/sbin/libvirtd --listen >>>>>>> >>>>>>> may 01 11:43:49 host1.bajada.es systemd[1]: Starting Virtualization >>>>>>> daemon... >>>>>>> may 01 11:43:49 host1.bajada.es systemd[1]: Started Virtualization >>>>>>> daemon. >>>>>>> may 01 11:47:45 host1.bajada.es libvirtd[21993]: libvirt version: >>>>>>> 2.0.0, package: 10.el7_3.5 (CentOS BuildSystem < >>>>>>> http://bugs.centos.org>, 2017-03-03-02:09:45, c1bm.rdu2.centos.org) >>>>>>> may 01 11:47:45 host1.bajada.es libvirtd[21993]: hostname: >>>>>>> host1.bajada.es >>>>>>> may 01 11:47:45 host1.bajada.es libvirtd[21993]: FallÃ³ al conectar >>>>>>> con el socket de monitor: No existe el proceso >>>>>>> may 01 11:47:45 host1.bajada.es libvirtd[21993]: 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 >>>>>>> Could not access >>>>>>> KVM kernel module: Permission denied >>>>>>> failed to >>>>>>> initialize KVM: Permission denied >>>>>>> >>>>>>> vdsm daemon >>>>>>> >>>>>>> vdsmd.service - Virtual Desktop Server Manager >>>>>>> Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; >>>>>>> vendor preset: enabled) >>>>>>> Active: active (running) since lun 2017-05-01 11:43:51 WEST; >>>>>>> 15min ago >>>>>>> Main PID: 22119 (vdsm) >>>>>>> CGroup: /system.slice/vdsmd.service >>>>>>> ââ22119 /usr/bin/python2 /usr/share/vdsm/vdsm >>>>>>> ââ22612 /usr/libexec/ioprocess --read-pipe-fd 68 >>>>>>> --write-pipe-fd 67 --max-threads 10 --max-queued-requests 10 >>>>>>> ââ22630 /usr/libexec/ioprocess --read-pipe-fd 76 >>>>>>> --write-pipe-fd 75 --max-threads 10 --max-queued-requests 10 >>>>>>> ââ22887 /usr/libexec/ioprocess --read-pipe-fd 44 >>>>>>> --write-pipe-fd 43 --max-threads 10 --max-queued-requests 10 >>>>>>> ââ22893 /usr/libexec/ioprocess --read-pipe-fd 52 >>>>>>> --write-pipe-fd 50 --max-threads 10 --max-queued-requests 10 >>>>>>> >>>>>>> may 01 11:58:37 host1.bajada.es vdsm[22119]: vdsm >>>>>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to >>>>>>> connect to broker, the number of errors has exceeded the limit (1) >>>>>>> may 01 11:58:37 host1.bajada.es vdsm[22119]: vdsm root ERROR failed >>>>>>> to retrieve Hosted Engine HA info >>>>>>> Traceback (most recent >>>>>>> call last): >>>>>>> File >>>>>>> "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 231, in >>>>>>> _getHaInfo >>>>>>> stats = >>>>>>> instance.get_all_stats() >>>>>>> File >>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", >>>>>>> line 102, in get_all_stats >>>>>>> with >>>>>>> broker.connection(self._retries, self._wait): >>>>>>> File >>>>>>> "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ >>>>>>> return >>>>>>> self.gen.next() >>>>>>> File >>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", >>>>>>> line 99, in connection >>>>>>> >>>>>>> self.connect(retries, wait) >>>>>>> File >>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", >>>>>>> line 78, in connect >>>>>>> raise >>>>>>> BrokerConnectionError(error_msg) >>>>>>> BrokerConnectionError: >>>>>>> Failed to connect to broker, the number of errors has exceeded the limit (1) >>>>>>> may 01 11:58:52 host1.bajada.es vdsm[22119]: vdsm >>>>>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to >>>>>>> connect to broker, the number of errors has exceeded the limit (1) >>>>>>> >>>>>>> I have been looking to the ovirt mailing list (and also internet >>>>>>> looking up in google) but I dont get what is the problem. >>>>>>> >>>>>>> I have attached to the mail the vdsm, ovirt-hosted-engine-setup and >>>>>>> the answer of the installation. In the vdsm.log I got the following error: >>>>>>> >>>>>>> libvirtError: 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 >>>>>>> Could not access KVM kernel module: Permission denied >>>>>>> failed to initialize KVM: Permission denied >>>>>>> >>>>>>> I have been looking for that error but I dont get anything clear, so >>>>>>> I will greatly appreciate the help of somebody... >>>>>>> >>>>>>> The KVM modules are loaded because if I fired up this "lsmod | grep >>>>>>> kvm" I get the following: >>>>>>> >>>>>>> kvm_intel 170181 0 >>>>>>> kvm 554609 1 kvm_intel >>>>>>> irqbypass 13503 1 kvm >>>>>>> >>>>>>> Also the group owner of /dev/kvm is: >>>>>>> >>>>>>> crw-rw-rw-+ 1 root kvm 10, 232 may 1 01:26 /dev/kvm >>>>>>> >>>>>>> Hope somebody could help >>>>>>> Thanks for all in advance >>>>>>> Manuel Luis Aznar >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2017-03-15 11:58 GMT+00:00 Manuel Luis Aznar < >>>>>>> manuel.luis.aznar(a)gmail.com>: >>>>>>> >>>>>>>> Hello there again, >>>>>>>> >>>>>>>> Yes that is correct. I interrupted the setup with Ctrl+C. That was >>>>>>>> because while I was answering, at the same time, I was looking at this >>>>>>>> file, and I saw this: >>>>>>>> >>>>>>>> FAILED: conflicting vdsm and libvirt-qemu tls configuration. >>>>>>>> vdsm.conf with ssl=True requires the following changes: >>>>>>>> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1 >>>>>>>> qemu.conf: spice_tls=1. >>>>>>>> >>>>>>>> So I decided to interrupt the installation, because of the error, >>>>>>>> edit the files (vdsm.conf and qemu.conf) and then I executed the >>>>>>>> installation again and it was successful. It seams that the change of the >>>>>>>> values in that files, in my case, produced a successful instalation. >>>>>>>> >>>>>>>> Sorry if my english is hard to understand, now you understand what >>>>>>>> I did. >>>>>>>> >>>>>>>> Any question, remark just go ahead >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Manuel >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 2017-03-15 11:22 GMT+00:00 Simone Tiraboschi <stirabos(a)redhat.com>: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Mar 15, 2017 at 12:17 PM, Manuel Luis Aznar < >>>>>>>>> manuel.luis.aznar(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hello Simone, >>>>>>>>>> >>>>>>>>>> The quoted lines on your last message are on lines 1238-1245 on >>>>>>>>>> the attached log ovirt-hosted-engine-setup file. >>>>>>>>>> >>>>>>>>>> That file is the first hosted-engine setup. But this log file is >>>>>>>>>> not the result of a host-engine-setup file. I start with the installation >>>>>>>>>> and while I was answering the question I was looking to this log file for >>>>>>>>>> errors and when I found this errors I stopped and done this: >>>>>>>>>> >>>>>>>>>> FAILED: conflicting vdsm and libvirt-qemu tls configuration. >>>>>>>>>> vdsm.conf with ssl=True requires the following changes: >>>>>>>>>> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1 >>>>>>>>>> qemu.conf: spice_tls=1. >>>>>>>>>> >>>>>>>>>> Previously to this installation I have done several installations >>>>>>>>>> without revising this log file and always getting failed installations. >>>>>>>>>> >>>>>>>>>> Please its important to note that: >>>>>>>>>> >>>>>>>>>> The currently setup which we are talking about was using >>>>>>>>>> repo "ovirt-release41-pre.rpm". After correcting that two files >>>>>>>>>> I do the installation and in the end it was completed successfully. >>>>>>>>>> >>>>>>>>>> When I have some time I will try to install again using the >>>>>>>>>> realease repo "ovirt-release41.rpm" >>>>>>>>>> >>>>>>>>>> If you have any explanation, question or remark, please go >>>>>>>>>> ahead... >>>>>>>>>> >>>>>>>>> >>>>>>>>> From the attached logs it seams that you voluntary interrupted the >>>>>>>>> setup from keyboard here: >>>>>>>>> 2017-03-07 11:23:17 DEBUG otopi.plugins.otopi.dialog.human >>>>>>>>> dialog.__logString:204 DIALOG:SEND iptables was detected on >>>>>>>>> your computer, do you wish setup to configure it? (Yes, No)[Yes]: >>>>>>>>> 2017-03-07 12:06:15 DEBUG otopi.context context._executeMethod:142 >>>>>>>>> method exception >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File "/usr/lib/python2.7/site-packages/otopi/context.py", line >>>>>>>>> 132, in _executeMethod >>>>>>>>> method['method']() >>>>>>>>> File "/usr/share/ovirt-hosted-engin >>>>>>>>> e-setup/scripts/../plugins/gr-he-setup/network/firewall_manager.py", >>>>>>>>> line 157, in _customization >>>>>>>>> default=_('Yes'), >>>>>>>>> File "/usr/share/otopi/plugins/otopi/dialog/human.py", line >>>>>>>>> 177, in queryString >>>>>>>>> value = self._readline(hidden=hidden) >>>>>>>>> File "/usr/lib/python2.7/site-packages/otopi/dialog.py", line >>>>>>>>> 246, in _readline >>>>>>>>> value = self.__input.readline() >>>>>>>>> File "/usr/lib/python2.7/site-packages/otopi/main.py", line 53, >>>>>>>>> in _signal >>>>>>>>> raise RuntimeError("SIG%s" % signum) >>>>>>>>> RuntimeError: SIG2 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I will report back. >>>>>>>>>> Thanks for all in advance >>>>>>>>>> Manuel >>>>>>>>>> >>>>>>>>>> 2017-03-13 17:29 GMT+00:00 Simone Tiraboschi <stirabos(a)redhat.com >>>>>>>>>> >: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Mar 13, 2017 at 4:08 PM, Manuel Luis Aznar < >>>>>>>>>>> manuel.luis.aznar(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hello to all there again, >>>>>>>>>>>> >>>>>>>>>>>> I was having some troubles while installing ovirt Hosted >>>>>>>>>>>> Engine, I took some look at the hosted engine setup logs while I was >>>>>>>>>>>> running the hosted-engine --deploy and I found the following in the ovirt >>>>>>>>>>>> hosted engine setup logs: >>>>>>>>>>>> >>>>>>>>>>>> lvm requires configuration >>>>>>>>>>>> libvirt is not configured for vdsm yet >>>>>>>>>>>> FAILED: conflicting vdsm and libvirt-qemu tls configuration. >>>>>>>>>>>> vdsm.conf with ssl=True requires the following changes: >>>>>>>>>>>> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1 >>>>>>>>>>>> qemu.conf: spice_tls=1. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> hosted-engine setup is already running vdsm-tool configure >>>>>>>>>>> --force so it should configure libvirt and qemu for you, not sure why it >>>>>>>>>>> failed. >>>>>>>>>>> Could you please attach the logs from the failed >>>>>>>>>>> hosted-engine-setup run? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> When I saw this I stopped the setup and edited this two files >>>>>>>>>>>> (vdsm.conf and qemu.conf) set the stated configurations and run the deploy >>>>>>>>>>>> again. All was fine and I dont have any trouble the installation finished >>>>>>>>>>>> successfully. This was using ovirt-release41-pre.rpm repo. >>>>>>>>>>>> >>>>>>>>>>>> I will be trying the same installation with ovirt-release41.rpm >>>>>>>>>>>> (when I have time) and I will report what happened. >>>>>>>>>>>> >>>>>>>>>>>> Thanks for all >>>>>>>>>>>> Manuel Luis Aznar >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 2017-03-06 1:31 GMT+00:00 Manuel Luis Aznar < >>>>>>>>>>>> manuel.luis.aznar(a)gmail.com>: >>>>>>>>>>>> >>>>>>>>>>>>> Hey there, >>>>>>>>>>>>> >>>>>>>>>>>>> I have been loking around, of course as of now the following I >>>>>>>>>>>>> am going to say I suppose is not anything new to you: >>>>>>>>>>>>> >>>>>>>>>>>>> This is the status of libvirtd: >>>>>>>>>>>>> >>>>>>>>>>>>> â libvirtd.service - Virtualization daemon >>>>>>>>>>>>> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; >>>>>>>>>>>>> enabled; vendor preset: enabled) >>>>>>>>>>>>> Drop-In: /etc/systemd/system/libvirtd.service.d >>>>>>>>>>>>> ââunlimited-core.conf >>>>>>>>>>>>> Active: active (running) since lun 2017-03-06 01:25:05 WET; >>>>>>>>>>>>> 1min 37s ago >>>>>>>>>>>>> Docs: man:libvirtd(8) >>>>>>>>>>>>> http://libvirt.org >>>>>>>>>>>>> Main PID: 24350 (libvirtd) >>>>>>>>>>>>> CGroup: /system.slice/libvirtd.service >>>>>>>>>>>>> ââ24350 /usr/sbin/libvirtd --listen >>>>>>>>>>>>> >>>>>>>>>>>>> mar 06 01:25:05 host1.bajada.es systemd[1]: Starting >>>>>>>>>>>>> Virtualization daemon... >>>>>>>>>>>>> mar 06 01:25:05 host1.bajada.es systemd[1]: Started >>>>>>>>>>>>> Virtualization daemon. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> After looking at the state I fire up the VM engine with the >>>>>>>>>>>>> command "hosted-engine --vm-start" and I got the following: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> VM exists and is down, destroying it >>>>>>>>>>>>> Machine destroyed >>>>>>>>>>>>> >>>>>>>>>>>>> ed786811-0321-431e-be4b-2d03764c1b02 >>>>>>>>>>>>> Status = WaitForLaunch >>>>>>>>>>>>> nicModel = rtl8139,pv >>>>>>>>>>>>> statusTime = 4374100040 <(437)%20410-0040> >>>>>>>>>>>>> emulatedMachine = pc >>>>>>>>>>>>> pid = 0 >>>>>>>>>>>>> vmName = HostedEngine >>>>>>>>>>>>> devices = [{'index': '2', 'iface': 'ide', >>>>>>>>>>>>> 'specParams': {}, 'readonly': 'true', 'deviceId': >>>>>>>>>>>>> '506df4eb-e783-4451-a8a6-993fa4dbb381', 'address': {'bus': >>>>>>>>>>>>> '1', 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '0'}, >>>>>>>>>>>>> 'device': 'cdrom', 'shared': 'false', 'path': '', 'type': 'disk'}, >>>>>>>>>>>>> {'index': '0', 'iface': 'virtio', 'format': 'raw', 'bootOrder': '1', >>>>>>>>>>>>> 'poolID': '00000000-0000-0000-0000-000000000000', 'volumeID': >>>>>>>>>>>>> '2bc39472-1a4b-4c7d-8ef9-1212182ad802', 'imageID': >>>>>>>>>>>>> '08288fcf-6b12-4bd1-84d3-259992e7aa6d', 'specParams': {}, >>>>>>>>>>>>> 'readonly': 'false', 'domainID': 'f44afe8d-56f9-4e1e-beee-4daa548dbad8', >>>>>>>>>>>>> 'optional': 'false', 'deviceId': '08288fcf-6b12-4bd1-84d3-259992e7aa6d', >>>>>>>>>>>>> 'address': {'slot': '0x06', 'bus': '0x00', 'domain': '0x0000', 'type': >>>>>>>>>>>>> 'pci', 'function': '0x0'}, 'device': 'disk', 'shared': 'exclusive', >>>>>>>>>>>>> 'propagateErrors': 'off', 'type': 'disk'}, {'device': 'scsi', 'model': >>>>>>>>>>>>> 'virtio-scsi', 'type': 'controller'}, {'nicModel': 'pv', 'macAddr': >>>>>>>>>>>>> '00:16:3e:65:a6:4e', 'linkActive': 'true', 'network': 'ovirtmgmt', >>>>>>>>>>>>> 'specParams': {}, 'deviceId': '84b82c6c-bcca-4983-82d5-8d1e3ab3811a', >>>>>>>>>>>>> 'address': {'slot': '0x03', 'bus': '0x00', 'domain': '0x0000', 'type': >>>>>>>>>>>>> 'pci', 'function': '0x0'}, 'device': 'bridge', 'type': 'interface'}, >>>>>>>>>>>>> {'device': 'console', 'specParams': {}, 'type': 'console', 'deviceId': >>>>>>>>>>>>> '6236af73-8dab-4d14-b950-fb4ad01d4420', 'alias': 'console0'}, >>>>>>>>>>>>> {'device': 'vga', 'alias': 'video0', 'type': 'video'}, {'device': 'virtio', >>>>>>>>>>>>> 'specParams': {'source': 'random'}, 'model': 'virtio', 'type': 'rng'}] >>>>>>>>>>>>> guestDiskMapping = {} >>>>>>>>>>>>> vmType = kvm >>>>>>>>>>>>> clientIp = >>>>>>>>>>>>> displaySecurePort = -1 >>>>>>>>>>>>> memSize = 4096 >>>>>>>>>>>>> displayPort = -1 >>>>>>>>>>>>> cpuType = Broadwell >>>>>>>>>>>>> spiceSecureChannels = smain,sdisplay,sinputs,scursor >>>>>>>>>>>>> ,splayback,srecord,ssmartcard,susbredir >>>>>>>>>>>>> smp = 2 >>>>>>>>>>>>> displayIp = 0 >>>>>>>>>>>>> display = vnc >>>>>>>>>>>>> maxVCpus = 6 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> After that if I look again at the status of libvirtd I obtain: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> â libvirtd.service - Virtualization daemon >>>>>>>>>>>>> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; >>>>>>>>>>>>> enabled; vendor preset: enabled) >>>>>>>>>>>>> Drop-In: /etc/systemd/system/libvirtd.service.d >>>>>>>>>>>>> ââunlimited-core.conf >>>>>>>>>>>>> Active: active (running) since lun 2017-03-06 01:25:05 WET; >>>>>>>>>>>>> 5min ago >>>>>>>>>>>>> Docs: man:libvirtd(8) >>>>>>>>>>>>> http://libvirt.org >>>>>>>>>>>>> Main PID: 24350 (libvirtd) >>>>>>>>>>>>> CGroup: /system.slice/libvirtd.service >>>>>>>>>>>>> ââ24350 /usr/sbin/libvirtd --listen >>>>>>>>>>>>> >>>>>>>>>>>>> mar 06 01:25:05 host1.bajada.es systemd[1]: Starting >>>>>>>>>>>>> Virtualization daemon... >>>>>>>>>>>>> mar 06 01:25:05 host1.bajada.es systemd[1]: Started >>>>>>>>>>>>> Virtualization daemon. >>>>>>>>>>>>> mar 06 01:29:39 host1.bajada.es libvirtd[24350]: libvirt >>>>>>>>>>>>> version: 2.0.0, package: 10.el7_3.5 (CentOS BuildSystem < >>>>>>>>>>>>> http://bugs.centos.org>, 2017-03-03-02:09:45, >>>>>>>>>>>>> c1bm.rdu2.centos.org) >>>>>>>>>>>>> mar 06 01:29:39 host1.bajada.es libvirtd[24350]: hostname: >>>>>>>>>>>>> host1.bajada.es >>>>>>>>>>>>> mar 06 01:29:39 host1.bajada.es libvirtd[24350]: FallÃ³ al >>>>>>>>>>>>> conectar con el socket de monitor: No existe el proceso >>>>>>>>>>>>> mar 06 01:29:39 host1.bajada.es libvirtd[24350]: internal >>>>>>>>>>>>> error: process exited while connecting to monitor: Could not access KVM >>>>>>>>>>>>> kernel module: Permission denied >>>>>>>>>>>>> failed to >>>>>>>>>>>>> initialize KVM: Permission denied >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> So the libvirtd is the problem, as i said this is nothing new >>>>>>>>>>>>> to you of course... >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks again for any help >>>>>>>>>>>>> Manuel >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 2017-03-05 18:51 GMT+00:00 Manuel Luis Aznar < >>>>>>>>>>>>> manuel.luis.aznar(a)gmail.com>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hey there again, >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Can you check if you have KVM modules loaded? >>>>>>>>>>>>>> >>>>>>>>>>>>>> In order to check that I fire up the following command: >>>>>>>>>>>>>> "lsmod | grep kvm" >>>>>>>>>>>>>> >>>>>>>>>>>>>> Result was: >>>>>>>>>>>>>> >>>>>>>>>>>>>> kvm_intel 170181 0 >>>>>>>>>>>>>> kvm 554609 1 kvm_intel >>>>>>>>>>>>>> irqbypass 13503 1 kvm >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Also check group owner for "/dev/kvm". I fire this: "ls -la >>>>>>>>>>>>>> /dev/kvm". The result was: >>>>>>>>>>>>>> >>>>>>>>>>>>>> crw-rw-rw-+ 1 root kvm 10, 232 mar 5 03:35 /dev/kvm >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Also I check if there were some remain packages pending to >>>>>>>>>>>>>> install for kvm and qemu and I got: >>>>>>>>>>>>>> >>>>>>>>>>>>>> yum install \*kvm\* >>>>>>>>>>>>>> >>>>>>>>>>>>>> The result is, that the system need to install the following: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Instalando: >>>>>>>>>>>>>> centos-release-qemu-ev noarch >>>>>>>>>>>>>> 1.0-1.el7 extras >>>>>>>>>>>>>> 11 k >>>>>>>>>>>>>> qemu-guest-agent x86_64 >>>>>>>>>>>>>> 10:2.5.0-3.el7 base >>>>>>>>>>>>>> 133 k >>>>>>>>>>>>>> qemu-kvm-ev-debuginfo x86_64 >>>>>>>>>>>>>> 10:2.6.0-28.el7_3.3.1 ovirt-4.0 12 M >>>>>>>>>>>>>> vdsm-hook-faqemu noarch >>>>>>>>>>>>>> 4.18.21-1.el7.centos ovirt-4.0 >>>>>>>>>>>>>> 15 k >>>>>>>>>>>>>> vdsm-hook-qemucmdline noarch >>>>>>>>>>>>>> 4.18.21-1.el7.centos ovirt-4.0 >>>>>>>>>>>>>> 11 k >>>>>>>>>>>>>> Instalando para las dependencias: >>>>>>>>>>>>>> centos-release-virt-common noarch >>>>>>>>>>>>>> 1-1.el7.centos extras >>>>>>>>>>>>>> 4.5 k >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Checking libvirtd service status I got: >>>>>>>>>>>>>> >>>>>>>>>>>>>> libvirtd.service - Virtualization daemon >>>>>>>>>>>>>> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; >>>>>>>>>>>>>> enabled; vendor preset: enabled) >>>>>>>>>>>>>> Drop-In: /etc/systemd/system/libvirtd.service.d >>>>>>>>>>>>>> ââunlimited-core.conf >>>>>>>>>>>>>> Active: active (running) since dom 2017-03-05 15:56:11 >>>>>>>>>>>>>> WET; 2h 51min ago >>>>>>>>>>>>>> Docs: man:libvirtd(8) >>>>>>>>>>>>>> http://libvirt.org >>>>>>>>>>>>>> Main PID: 19415 (libvirtd) >>>>>>>>>>>>>> CGroup: /system.slice/libvirtd.service >>>>>>>>>>>>>> 19415 /usr/sbin/libvirtd --listen >>>>>>>>>>>>>> >>>>>>>>>>>>>> mar 05 15:56:10 host1.bajada.es systemd[1]: Starting >>>>>>>>>>>>>> Virtualization daemon... >>>>>>>>>>>>>> mar 05 15:56:11 host1.bajada.es systemd[1]: Started >>>>>>>>>>>>>> Virtualization daemon. >>>>>>>>>>>>>> mar 05 16:00:04 host1.bajada.es libvirtd[19415]: libvirt >>>>>>>>>>>>>> version: 2.0.0, package: 10.el7_3.5 (CentOS BuildSystem < >>>>>>>>>>>>>> http://bugs.centos.org>, 2017-03-03-02:09:45, >>>>>>>>>>>>>> c1bm.rdu2.centos.org) >>>>>>>>>>>>>> mar 05 16:00:04 host1.bajada.es libvirtd[19415]: hostname: >>>>>>>>>>>>>> host1.bajada.es >>>>>>>>>>>>>> mar 05 16:00:04 host1.bajada.es libvirtd[19415]: Failed to >>>>>>>>>>>>>> connect to the socket monitor: process does not exits >>>>>>>>>>>>>> >>>>>>>>>>>>>> (Fallo al conectar con el socket de monitor: No existe el proceso) >>>>>>>>>>>>>> mar 05 16:00:04 host1.bajada.es libvirtd[19415]: internal >>>>>>>>>>>>>> error: process exited while connecting to monitor: Could not access KVM >>>>>>>>>>>>>> kernel module: Permission denied >>>>>>>>>>>>>> failed to >>>>>>>>>>>>>> initialize KVM: Permission denied >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks for all in advance >>>>>>>>>>>>>> I will be waiting for you. Any help appreciated >>>>>>>>>>>>>> Manuel >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2017-03-05 17:33 GMT+00:00 Artyom Lukianov < >>>>>>>>>>>>>> alukiano(a)redhat.com>: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I found this one under the vdsm log: >>>>>>>>>>>>>>> libvirtError: internal error: process exited while >>>>>>>>>>>>>>> connecting to monitor: Could not access KVM kernel module: Permission denied >>>>>>>>>>>>>>> failed to initialize KVM: Permission denied >>>>>>>>>>>>>>> Thread-70::INFO::2017-03-05 16:00:04,325::vm::1330::virt.vm::(setDownStatus) >>>>>>>>>>>>>>> vmId=`ed786811-0321-431e-be4b-2d03764c1b02`::Changed state >>>>>>>>>>>>>>> to Down: internal error: process exited while connecting to monitor: Could >>>>>>>>>>>>>>> not access KVM kernel module: Permission denied >>>>>>>>>>>>>>> failed to initialize KVM: Permission denied (code=1) >>>>>>>>>>>>>>> Thread-70::INFO::2017-03-05 16:00:04,325::guestagent::430::virt.vm::(stop) >>>>>>>>>>>>>>> vmId=`ed786811-0321-431e-be4b-2d03764c1b02`::Stopping >>>>>>>>>>>>>>> connection >>>>>>>>>>>>>>> Thread-70::DEBUG::2017-03-05 16:00:04,325::vmchannels::238::vds::(unregister) >>>>>>>>>>>>>>> Delete fileno 52 from listener. >>>>>>>>>>>>>>> Thread-70::DEBUG::2017-03-05 16:00:04,325::vmchannels::66::vds::(_unregister_fd) >>>>>>>>>>>>>>> Failed to unregister FD from epoll (ENOENT): 52 >>>>>>>>>>>>>>> Thread-70::DEBUG::2017-03-05 16:00:04,326::__init__::209::jsonrpc.Notification::(emit) >>>>>>>>>>>>>>> Sending event {"params": {"ed786811-0321-431e-be4b-2d03764c1b02": >>>>>>>>>>>>>>> {"status": "Down", "exitReason": 1, "exitMessage": "internal error: process >>>>>>>>>>>>>>> exited while connecting to monitor: Could not access KVM kernel module: >>>>>>>>>>>>>>> Permission denied\nfailed to initialize KVM: Permission denied", >>>>>>>>>>>>>>> "exitCode": 1}, "notify_time": 4339924730}, "jsonrpc": "2.0", "method": >>>>>>>>>>>>>>> "|virt|VM_status|ed786811-0321-431e-be4b-2d03764c1b02"} >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Can you check if you have KVM modules loaded? Also, check >>>>>>>>>>>>>>> group owner for "/dev/kvm". >>>>>>>>>>>>>>> Best Regards >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sat, Mar 4, 2017 at 4:24 PM, Manuel Luis Aznar < >>>>>>>>>>>>>>> manuel.luis.aznar(a)gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello there again, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The error on the first email was using the repo >>>>>>>>>>>>>>>> ovirt-release41.rpm (http://resources.ovirt.org/pu >>>>>>>>>>>>>>>> b/yum-repo/ovirt-release41.rpm), so as I were getting the >>>>>>>>>>>>>>>> same error again and again I am currently trying with >>>>>>>>>>>>>>>> ovirt-release41-snapshot.rpm (http://resources.ovirt.org/pu >>>>>>>>>>>>>>>> b/yum-repo/ovirt-release41-snapshot.rpm) and the result is >>>>>>>>>>>>>>>> nearly the same. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> After creating the VM on the installation I got the same >>>>>>>>>>>>>>>> error with the command "systemctl status vdsmd": >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> mar 04 14:10:19 host1.bajada.es vdsm[20443]: vdsm root >>>>>>>>>>>>>>>> ERROR failed to retrieve Hosted Engine HA info >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", >>>>>>>>>>>>>>>> line 231, in _getHaInfo >>>>>>>>>>>>>>>> stats = instance.get_all_stats() >>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packa >>>>>>>>>>>>>>>> ges/ovirt_hosted_engine_ha/client/client.py", line 102, in >>>>>>>>>>>>>>>> get_all_stats >>>>>>>>>>>>>>>> with broker.connection(self._retries, >>>>>>>>>>>>>>>> self._wait): >>>>>>>>>>>>>>>> File "/usr/lib64/python2.7/contextlib.py", line >>>>>>>>>>>>>>>> 17, in __enter__ >>>>>>>>>>>>>>>> return self.gen.next() >>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packa >>>>>>>>>>>>>>>> ges/ovirt_hosted_engine_ha/lib/brokerlink.py", line 99, in >>>>>>>>>>>>>>>> connection >>>>>>>>>>>>>>>> self.connect(retries, wait) >>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packa >>>>>>>>>>>>>>>> ges/ovirt_hosted_engine_ha/lib/brokerlink.py", line 78, in >>>>>>>>>>>>>>>> connect >>>>>>>>>>>>>>>> raise BrokerConnectionError(error_msg) >>>>>>>>>>>>>>>> BrokerConnectionError: Failed to connect to >>>>>>>>>>>>>>>> broker, the number of errors has exceeded the limit (1) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> mar 04 14:10:34 host1.bajada.es vdsm[20443]: vdsm >>>>>>>>>>>>>>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR >>>>>>>>>>>>>>>> Failed to connect to broker, the number of errors has exceeded the limit (1) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have noticed that the ovirt-ha-agent and ovirt-ha-broker >>>>>>>>>>>>>>>> services was not running. I guess if this have something to do with the >>>>>>>>>>>>>>>> error in vsmd service log. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> But in this case the ovirt-hosted-engine-installation >>>>>>>>>>>>>>>> prints the vnc connection and I can connect to the engine VM. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks for all in advance >>>>>>>>>>>>>>>> Any help would be appreciated >>>>>>>>>>>>>>>> Manuel Luis Aznar >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2017-03-03 21:48 GMT+00:00 Manuel Luis Aznar < >>>>>>>>>>>>>>>> manuel.luis.aznar(a)gmail.com>: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hello there, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I am having some trouble when deploying an oVirt 4.1 >>>>>>>>>>>>>>>>> hosted engine installation. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> When I m just to end the installation and the hosted >>>>>>>>>>>>>>>>> engine setup script is about to start the Vm engine (appliance) it fails >>>>>>>>>>>>>>>>> saying "The VM is not powring up". >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> If I double check the service vdsmd i get this error all >>>>>>>>>>>>>>>>> the time: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> vdsm root ERROR failed to retrieve Hosted Engine HA info >>>>>>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", >>>>>>>>>>>>>>>>> line 231, in _getHaInfo >>>>>>>>>>>>>>>>> stats = instance.get_all_stats() >>>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packa >>>>>>>>>>>>>>>>> ges/ovirt_hosted_engine_ha/client/client.py", line 102, >>>>>>>>>>>>>>>>> in get_all_stats >>>>>>>>>>>>>>>>> with broker.connection(self._retries, >>>>>>>>>>>>>>>>> self._wait): >>>>>>>>>>>>>>>>> File "/usr/lib64/python2.7/contextlib.py", line 17, >>>>>>>>>>>>>>>>> in __enter__ >>>>>>>>>>>>>>>>> return self.gen.next() >>>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packa >>>>>>>>>>>>>>>>> ges/ovirt_hosted_engine_ha/lib/brokerlink.py", line 99, >>>>>>>>>>>>>>>>> in connection >>>>>>>>>>>>>>>>> self.connect(retries, wait) >>>>>>>>>>>>>>>>> File "/usr/lib/python2.7/site-packa >>>>>>>>>>>>>>>>> ges/ovirt_hosted_engine_ha/lib/brokerlink.py", line 78, >>>>>>>>>>>>>>>>> in connect >>>>>>>>>>>>>>>>> raise BrokerConnectionError(error_msg) >>>>>>>>>>>>>>>>> BrokerConnectionError: Failed to connect to broker, the >>>>>>>>>>>>>>>>> number of errors has exceeded the limit (1) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Did anyone have experimented the same problem?¿? Any hint >>>>>>>>>>>>>>>>> on How to solved it?¿? I have tried several times with clean installations >>>>>>>>>>>>>>>>> and always getting the same... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The host where I am trying to do the installation have >>>>>>>>>>>>>>>>> CentOS 7... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks for all in advance >>>>>>>>>>>>>>>>> Will be waiting for any hint to see what I am doing >>>>>>>>>>>>>>>>> wrong... >>>>>>>>>>>>>>>>> Manuel Luis Aznar >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Users mailing list >>>>>>>>>>>>>>>> Users(a)ovirt.org >>>>>>>>>>>>>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Users mailing list >>>>>>>>>>>> Users(a)ovirt.org >>>>>>>>>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

3 5

searching users and field mapping
by Fabrice Bacchella 12 May '17

12 May '17

When I export a user I find values like: <department></department> <domain_entry_id>39323336363566612D373333622D346532612D396530632D316630396536643634636432</domain_entry_id> <email></email> <last_name></last_name> <name>admin</name> <namespace>*</namespace> <principal>admin</principal> <user_name>admin@internal-authz</user_name> <domain href="/ovirt-engine/api/domains/696E7465726E616C2D617574687A" id="696E7465726E616C2D617574687A"> <name>internal-authz</name> </domain> <permissions href="/ovirt-engine/api/users/0000001a-001a-001a-001a-0000000003b4/permissions"/> <roles href="/ovirt-engine/api/users/0000001a-001a-001a-001a-0000000003b4/roles"/> <ssh_public_keys href="/ovirt-engine/api/users/0000001a-001a-001a-001a-0000000003b4/sshpublickeys"/> <tags href="/ovirt-engine/api/users/0000001a-001a-001a-001a-0000000003b4/tags"/> They are the same that one defined from the type in sdk (http://ovirt.github.io/ovirt-engine-sdk/master/types.m.html#ovirtsdk4.types…) If I look in http://www.ovirt.org/documentation/admin-guide/appe-Using_Search_Bookmarks_…, I see fields like pool, group that I don't map to fields in the type. In the search bar in the UI, I also see fields like login, directory or type. The mapping is less obvious, even if I can guess that login maps to principal. But I wonder why such name discrepancy exists and if they are documented somewhere.

1 0

slow kerberos authentication
by Fabrice Bacchella 12 May '17

12 May '17

I'm using kerberos authentication in ovirt for the URL /sso/oauth/token-http-auth, but kerberos is done in Apache using auth_gssapi_module and it's quite slow, about 6s for a request. I'm trying to understand if it's apache or ovirt-engine that are slow. Is there a way to get response time metered for http requests inside ovirt instead of seen from apache ?

4 11

ovs-vswitchd high cpu usage
by Arnaud Lauriou 12 May '17

12 May '17

Hi, Just updated last week ovirt hosts from 4.0.6 to 4.1.1 and I noticed ovs-vswitchd high cpu usage, around 100%. My cluster switch type is in legacy mode, so I decided to stop ovs-vswitchd process on each ovirt host. This morning, when trying to run a new VM and I've got the following error message : Exit message: (21, 'Executing commands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)') Even if the cluster is in legacy mode, it seems that ovs-vswitchd needs to be up and running for vdsm. So, how can reduce the cpu usage of ovs-vswitchd process ? Regards, Arnaud

1 2

[ANN] oVirt 4.1.2 Second Release Candidate is now available
by Sandro Bonazzola 12 May '17

12 May '17

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 4.1.2 for testing, as of May 12th, 2017 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the second release candidate of the second in a series of stabilization updates to the 4.1 series. 4.1.2 brings more than 25 enhancements and more than 220 bugfixes, including more than 90 high or urgent severity fixes, on top of oVirt 4.1 series This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * oVirt Node 4.1 * Fedora 24 (tech preview) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live has been already built [4] - oVirt Node has been already built [4] Additional Resources: * Read more about the oVirt 4.1.2 release highlights: http://www.ovirt.org/release/4.1.2/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.2/ [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0