- Users - oVirt List Archives

VMware import, username with '.' not accepted
by Martijn Grendelman 24 Oct '16

24 Oct '16

Hi, I'm trying to import a VM from VMware. On the "Import Virtual Machine(s)" screen, my VCenter username is not accepted, because "Name can only contain 'A-Z', 'a-z', '0-9', '_' or '-' characters" and it contains a '.', which should be perfectly fine. Now what? Regards, Martijn.

2 1

Non responsive vms, how to reconnect hosts
by andreas.ewert＠cbc.de 24 Oct '16

24 Oct '16

Hi there, currently our vms are in a non responsive state. Due fibre channel storage problems every machine is tagged by a question mark. Datacenter is in non operational mode. Good news is that the machines are running. I verrified by „virsh list“ on the hypervisors. I know if I reboot the hypervisors then the problem will be solved. But is there any other way to connect the hypervisor hosts to the datacenter? Now storage problems are over and I already tried to restart the vdsm daemon … but no success. Do I really need to reboot the hosts? OS Version of ovirt Hosts: Centos7 DataCenter runs with version 3.5 With best regards Andreas

2 1

Detected conflict in hook delete-POST
by Nathanaël Blanchet 24 Oct '16

24 Oct '16

Hello, What can I do to solve this kind of messages in ovirt 4.0.4? Detected conflict in hook delete-POST-57glusterfind-delete-post.py of Cluster Test. Detected conflict in hook start-POST-31ganesha-start.sh of Cluster Test. -- 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 1

Problem with start VDSMD durring hosted-engine --deploy
by Grzegorz Szypa 24 Oct '16

24 Oct '16

Hi Support, Could you help me with my problem, because when I try to deploy host on fresh Centos 7.1 installation I got an error that vdsmd servies cannot bestarted, and deploy after taht are terminated: [root@vmsrv1 ~]# [root@vmsrv1 ~]# hosted-engine --deploy /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15: DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli import vdsm.vdscli [ INFO ] Stage: Initializing [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and create a VM where you have to install the engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: It has been detected that this program is executed through an SSH connection without using screen. Continuing with the installation may lead to broken installation if the network connection fails. It is highly recommended to abort the installation and run it inside a screen session using command "screen". Do you want to continue anyway? (Yes, No)[No]: Yes [ INFO ] Hardware supports virtualization Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161024074216-iagc54.log Version: otopi-1.5.2 (otopi-1.5.2-1.el7.centos) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup *[ ERROR ] Failed to execute stage 'Environment setup': Failed to start service 'vdsmd'* [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20161024074222.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161024074216-iagc54.log [root@vmsrv1 ~]# Firstly I tried to do it by ovirt portal, but every time failed. so I try to do it by hosted-engine --deploy, and this time I got more information as above. (SELinux is disabled). firewall are disabled. Onlywhat make me confuse are vdsm. So I checkd it and for sure it has been installed (with version vdsm-4.18.13-1.el7.centos.x86_64) [root@vmsrv1 ~]# yum install vdsm Wczytane wtyczki: fastestmirror, versionlock Loading mirror speeds from cached hostfile * base: centos.trisect.eu * epel: epel.mirrors.ovh.net * extras: centos.trisect.eu * ovirt-4.0: ftp.nluug.nl * ovirt-4.0-epel: epel.mirrors.ovh.net * updates: centos.trisect.eu Pakiet vdsm-4.18.13-1.el7.centos.x86_64 jest już zainstalowany w najnowszej wersji Nie ma niczego do zrobienia after that I tried to find it and restart : [root@vmsrv1 ~]# systemctl vdsmd restart Unknown operation 'vdsmd'. So question is if vdsm has been installed, what going on? So: [root@vmsrv1 ~]# systemctl |grep -i vdsm supervdsmd.service loaded active running Auxiliary vdsm service for running helper functions as root vdsm-network.service loaded active exited Virtual Desktop Server Manager network restoration [root@vmsrv1 ~]# As see above there are completly different name convention, and it shuld be like vdsmd.service. What is strange, this exist on host where is Portal, but it is not possible to start it, because of "vdsm-network.service" Question are how to avoid it, because for sure hosted-engine script do not know how to start vdsm Additionaly, I tried to reconfigure vdsm: [root@vmsrv1 ~]# vdsm-tool configure --force /usr/lib/python2.7/site-packages/vdsm/tool/dump_volume_chains.py:28: DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli from vdsm import vdscli Checking configuration status... Current revision of multipath.conf detected, preserving libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts Running configure... Reconfiguration of sebool is done. Reconfiguration of libvirt is done. Done configuring modules to VDSM. [root@vmsrv1 ~]# systemctl start vdsmd A dependency job for vdsmd.service failed. See 'journalctl -xe' for details. [root@vmsrv1 ~]# journalctl -xe -- Subject: Ukończono uruchamianie jednostki libvirtd.service -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka libvirtd.service ukończyła uruchamianie. -- -- Wynik uruchamiania: done. paź 24 07:57:12 vmsrv1.szypa.net systemd[1]: Configuration file /usr/lib/systemd/system/ebtables.service is marked executable. Please remove executable permission bits. Proceeding anyway. paź 24 07:57:12 vmsrv1.szypa.net systemd[1]: Started Auxiliary vdsm service for running helper functions as root. -- Subject: Ukończono uruchamianie jednostki supervdsmd.service -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka supervdsmd.service ukończyła uruchamianie. -- -- Wynik uruchamiania: done. paź 24 07:57:12 vmsrv1.szypa.net systemd[1]: Starting Auxiliary vdsm service for running helper functions as root... -- Subject: Rozpoczęto uruchamianie jednostki supervdsmd.service -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka supervdsmd.service rozpoczęła uruchamianie. paź 24 07:57:54 vmsrv1.szypa.net polkitd[1154]: Registered Authentication Agent for unix-process:14438:14347412 (system bus name :1.4915 [<unknown>], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8) paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Starting Device-Mapper Multipath Device Controller... -- Subject: Rozpoczęto uruchamianie jednostki multipathd.service -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka multipathd.service rozpoczęła uruchamianie. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Starting Virtual Desktop Server Manager network restoration... -- Subject: Rozpoczęto uruchamianie jednostki vdsm-network.service -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka vdsm-network.service rozpoczęła uruchamianie. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: multipathd.service: control process exited, code=exited status=1 paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Failed to start Device-Mapper Multipath Device Controller. -- Subject: Jednostka multipathd.service się nie powiodła -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka multipathd.service się nie powiodła. -- -- Wynik: failed. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Dependency failed for Virtual Desktop Server Manager. -- Subject: Jednostka vdsmd.service się nie powiodła -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka vdsmd.service się nie powiodła. -- -- Wynik: dependency. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Dependency failed for MOM instance configured for VDSM purposes. -- Subject: Jednostka mom-vdsm.service się nie powiodła -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka mom-vdsm.service się nie powiodła. -- -- Wynik: dependency. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Job vdsmd.service/start failed with result 'dependency'. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: Unit multipathd.service entered failed state. paź 24 07:57:54 vmsrv1.szypa.net systemd[1]: multipathd.service failed. paź 24 07:57:54 vmsrv1.szypa.net polkitd[1154]: Unregistered Authentication Agent for unix-process:14438:14347412 (system bus name :1.4915, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pl_PL.UTF-8) (disconnected from bus) paź 24 07:57:54 vmsrv1.szypa.net vdsm-tool[14444]: /usr/lib/python2.7/site-packages/vdsm/tool/dump_volume_chains.py:28: DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli paź 24 07:57:54 vmsrv1.szypa.net vdsm-tool[14444]: from vdsm import vdscli paź 24 07:57:54 vmsrv1.szypa.net vdsm-tool[14454]: /usr/lib/python2.7/site-packages/vdsm/tool/dump_volume_chains.py:28: DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli paź 24 07:57:54 vmsrv1.szypa.net vdsm-tool[14454]: from vdsm import vdscli paź 24 07:57:55 vmsrv1.szypa.net systemd[1]: Started Virtual Desktop Server Manager network restoration. -- Subject: Ukończono uruchamianie jednostki vdsm-network.service -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka vdsm-network.service ukończyła uruchamianie. -- -- Wynik uruchamiania: done. paź 24 07:58:01 vmsrv1.szypa.net systemd[1]: Started Session c2440 of user root. -- Subject: Ukończono uruchamianie jednostki session-c2440.scope -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka session-c2440.scope ukończyła uruchamianie. -- -- Wynik uruchamiania: done. paź 24 07:58:01 vmsrv1.szypa.net systemd[1]: Starting Session c2440 of user root. -- Subject: Rozpoczęto uruchamianie jednostki session-c2440.scope -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Jednostka session-c2440.scope rozpoczęła uruchamianie. paź 24 07:58:01 vmsrv1.szypa.net CROND[14473]: (root) CMD (/usr/local/rtm/bin/rtm 7 > /dev/null 2> /dev/null) lines 4205-4296/4296 (END) -- G.Sz.

2 1

about hosted engine gluster support
by 张余歌 23 Oct '16

23 Oct '16

--_4899065a-17d0-4ba3-a2e1-3dee19639bb2_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 aGV5ICxmcmllbmRzIVJlZmVyIHRvIGh0dHBzOi8vd3d3Lm92aXJ0Lm9yZy9kZXZlbG9wL3JlbGVh c2UtbWFuYWdlbWVudC9mZWF0dXJlcy9lbmdpbmUvc2VsZi1ob3N0ZWQtZW5naW5lLWdsdXN0ZXIt c3VwcG9ydC9pIG1lZXQgc29tZSBwcm9ibGVtOndoZW4gaSBwcm9jZXNzICdob3N0ZWQtZW5naW5l IC0tZGVwbG95J2kgIHNob3cgc3VwcG9ydCBpc2NzaSxuZnMzLG5mczQgLGJ1dCBnbHVzdGVyLg0K aSBzaG91bGQgYmU6UGxlYXNlIHNwZWNpZnkgdGhlIHN0b3JhZ2UgeW91IHdvdWxkIGxpa2UgdG8g dXNlIChnbHVzdGVyZnMsIGlzY3NpLCBuZnMzLCBuZnM0KVtuZnMzXTogZ2x1c3RlcmZzDQppIGZv bGxvd2VkIHRoZSBzdGFnZSBvZiB0aGUgbGluayxidXQgaSBmYWlsZWQgdG8gaG9zdGVkLWVuZ2lu ZSBzdXBwb3J0IGdsdXN0ZXIsbWF5YmUgc29tZXRoaW5nIGVsc2UgaSBzaG91bGQgY29uZmlndXJl P2kgYW0gc28gc28gc28gc28gY29uZnVzZWQhISEhIXdoeSAscGxlYXNlIGhlbHAgbWUhDQp0aGFu a3MuLi4uLg0KbXkgb3ZpcnQgdmVyc2lvbiBpcyAzLjUuNi4NCiAJCSAJICAgCQkgIA== --_4899065a-17d0-4ba3-a2e1-3dee19639bb2_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxzdHlsZT48IS0tDQouaG1tZXNzYWdlIFANCnsNCm1hcmdpbjowcHg7 DQpwYWRkaW5nOjBweA0KfQ0KYm9keS5obW1lc3NhZ2UNCnsNCmZvbnQtc2l6ZTogMTJwdDsNCmZv bnQtZmFtaWx5Os6iyO3RxbraDQp9DQotLT48L3N0eWxlPjwvaGVhZD4NCjxib2R5IGNsYXNzPSdo bW1lc3NhZ2UnPjxkaXYgZGlyPSdsdHInPmhleSAsZnJpZW5kcyE8ZGl2PlJlZmVyIHRvJm5ic3A7 PC9kaXY+PGRpdj48YSBocmVmPSJodHRwczovL3d3dy5vdmlydC5vcmcvZGV2ZWxvcC9yZWxlYXNl LW1hbmFnZW1lbnQvZmVhdHVyZXMvZW5naW5lL3NlbGYtaG9zdGVkLWVuZ2luZS1nbHVzdGVyLXN1 cHBvcnQvIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cub3ZpcnQub3JnL2RldmVsb3AvcmVs ZWFzZS1tYW5hZ2VtZW50L2ZlYXR1cmVzL2VuZ2luZS9zZWxmLWhvc3RlZC1lbmdpbmUtZ2x1c3Rl ci1zdXBwb3J0LzwvYT48L2Rpdj48ZGl2PmkgbWVldCBzb21lIHByb2JsZW06d2hlbiBpIHByb2Nl c3MgJ2hvc3RlZC1lbmdpbmUgLS1kZXBsb3knPC9kaXY+PGRpdj5pICZuYnNwO3Nob3cgc3VwcG9y dCBpc2NzaSxuZnMzLG5mczQgLGJ1dCBnbHVzdGVyLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+ aSBzaG91bGQgYmU6PHNwYW4gc3R5bGU9ImNvbG9yOiBpbmhlcml0OyBmb250LWZhbWlseTogTWVu bG8sIE1vbmFjbywgQ29uc29sYXMsICdDb3VyaWVyIE5ldycsIG1vbm9zcGFjZTsgZm9udC1zaXpl OiAxMnB0OyB3aGl0ZS1zcGFjZTogcHJlLXdyYXA7IGxpbmUtaGVpZ2h0OiAxLjQyODU3OyI+UGxl YXNlJm5ic3A7c3BlY2lmeSZuYnNwO3RoZSZuYnNwO3N0b3JhZ2UmbmJzcDt5b3UmbmJzcDt3b3Vs ZCZuYnNwO2xpa2UmbmJzcDt0byZuYnNwO3VzZSZuYnNwOyhnbHVzdGVyZnMsJm5ic3A7aXNjc2ks Jm5ic3A7bmZzMywmbmJzcDtuZnM0KVtuZnMzXTombmJzcDtnbHVzdGVyZnM8L3NwYW4+PC9kaXY+ PGRpdj48Zm9udCBmYWNlPSJNZW5sbywgTW9uYWNvLCBDb25zb2xhcywgQ291cmllciBOZXcsIG1v bm9zcGFjZSI+PHNwYW4gc3R5bGU9ImxpbmUtaGVpZ2h0OiAyMi44NTcxcHg7IHdoaXRlLXNwYWNl OiBwcmUtd3JhcDsiPjxicj48L3NwYW4+PC9mb250PjwvZGl2PjxkaXY+PGZvbnQgZmFjZT0iTWVu bG8sIE1vbmFjbywgQ29uc29sYXMsIENvdXJpZXIgTmV3LCBtb25vc3BhY2UiPjxzcGFuIHN0eWxl PSJsaW5lLWhlaWdodDogMjIuODU3MXB4OyB3aGl0ZS1zcGFjZTogcHJlLXdyYXA7Ij5pIGZvbGxv d2VkIHRoZSBzdGFnZSBvZiB0aGUgbGluayxidXQgaSBmYWlsZWQgdG8gaG9zdGVkLWVuZ2luZSBz dXBwb3J0IGdsdXN0ZXIsbWF5YmUgc29tZXRoaW5nIGVsc2UgaSBzaG91bGQgY29uZmlndXJlP2kg YW0gc28gc28gc28gc28gY29uZnVzZWQhISEhIXdoeSAscGxlYXNlIGhlbHAgbWUhPC9zcGFuPjwv Zm9udD48L2Rpdj48ZGl2Pjxmb250IGZhY2U9Ik1lbmxvLCBNb25hY28sIENvbnNvbGFzLCBDb3Vy aWVyIE5ldywgbW9ub3NwYWNlIj48c3BhbiBzdHlsZT0ibGluZS1oZWlnaHQ6IDIyLjg1NzFweDsg d2hpdGUtc3BhY2U6IHByZS13cmFwOyI+PGJyPjwvc3Bhbj48L2ZvbnQ+PC9kaXY+PGRpdj48Zm9u dCBmYWNlPSJNZW5sbywgTW9uYWNvLCBDb25zb2xhcywgQ291cmllciBOZXcsIG1vbm9zcGFjZSI+ PHNwYW4gc3R5bGU9ImxpbmUtaGVpZ2h0OiAyMi44NTcxcHg7IHdoaXRlLXNwYWNlOiBwcmUtd3Jh cDsiPnRoYW5rcy4uLi4uPC9zcGFuPjwvZm9udD48L2Rpdj48ZGl2Pjxmb250IGZhY2U9Ik1lbmxv LCBNb25hY28sIENvbnNvbGFzLCBDb3VyaWVyIE5ldywgbW9ub3NwYWNlIj48c3BhbiBzdHlsZT0i bGluZS1oZWlnaHQ6IDIyLjg1NzFweDsgd2hpdGUtc3BhY2U6IHByZS13cmFwOyI+PGJyPjwvc3Bh bj48L2ZvbnQ+PC9kaXY+PGRpdj48Zm9udCBmYWNlPSJNZW5sbywgTW9uYWNvLCBDb25zb2xhcywg Q291cmllciBOZXcsIG1vbm9zcGFjZSI+PHNwYW4gc3R5bGU9ImxpbmUtaGVpZ2h0OiAyMi44NTcx cHg7IHdoaXRlLXNwYWNlOiBwcmUtd3JhcDsiPm15IG92aXJ0IHZlcnNpb24gaXMgMy41LjYuPC9z cGFuPjwvZm9udD48L2Rpdj48ZGl2PjxkaXY+PGJyPjwvZGl2PjwvZGl2PiAJCSAJICAgCQkgIDwv ZGl2PjwvYm9keT4NCjwvaHRtbD4= --_4899065a-17d0-4ba3-a2e1-3dee19639bb2_--

2 1

Ovirt Hypervisor vdsm.Scheduler logs fill partition
by Steve Dainard 23 Oct '16

23 Oct '16

Hello, I had a hypervisor semi-crash this week, 4 of ~10 VM's continued to run, but the others were killed off somehow and all VM's running on this host had '?' status in the ovirt UI. This appears to have been caused by vdsm logs filling up disk space on the logging partition. I've attached the log file vdsm.log.27.xz which shows this error: vdsm.Scheduler::DEBUG::2016-10-11 16:42:09,318::executor::216::Executor::(_discard) Worker discarded: <Worker name=periodic/3017 running <Operation action=<VmDispatcher operation=<class 'virt.periodic.DriveWatermarkMonitor'> at 0x7f8e90021210> at 0x7f8e90021250> discarded at 0x7f8dd123e850> which happens more and more frequently throughout the log. It was a bit difficult to understand what caused the failure, but the logs were getting really large, then being xz'd which compressed 11G+ into a few MB. Once this happened the disk space would be freed, and nagios wouldn't hit the 3rd check to throw a warning, until pretty much right at the crash. I was able to restart vdsmd to resolve the issue, but I still need to know why these logs started to stack up so I can avoid this issue in the future. Hypervisor host info: CentOS 7 # rpm -qa | grep vdsm vdsm-yajsonrpc-4.17.32-1.el7.noarch vdsm-xmlrpc-4.17.32-1.el7.noarch vdsm-infra-4.17.32-1.el7.noarch vdsm-hook-vmfex-dev-4.17.32-1.el7.noarch vdsm-python-4.17.32-1.el7.noarch vdsm-4.17.32-1.el7.noarch vdsm-cli-4.17.32-1.el7.noarch vdsm-jsonrpc-4.17.32-1.el7.noarch Engine host info: CentOS 7 $ rpm -qa | grep ovirt ovirt-engine-lib-3.6.7.5-1.el7.centos.noarch ovirt-iso-uploader-3.6.0-1.el7.centos.noarch ovirt-engine-wildfly-overlay-8.0.5-1.el7.noarch ovirt-engine-webadmin-portal-3.6.7.5-1.el7.centos.noarch ovirt-engine-jboss-as-7.1.1-1.el7.x86_64 ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.7.5-1.el7.centos.noarch ovirt-host-deploy-1.4.1-1.el7.centos.noarch ovirt-engine-vmconsole-proxy-helper-3.6.7.5-1.el7.centos.noarch ovirt-engine-backend-3.6.7.5-1.el7.centos.noarch ovirt-setup-lib-1.0.1-1.el7.centos.noarch ovirt-engine-setup-plugin-websocket-proxy-3.6.7.5-1.el7.centos.noarch ovirt-engine-websocket-proxy-3.6.7.5-1.el7.centos.noarch ovirt-engine-tools-3.6.7.5-1.el7.centos.noarch ovirt-engine-setup-base-3.6.7.5-1.el7.centos.noarch ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch ovirt-vmconsole-1.0.2-1.el7.centos.noarch ovirt-engine-wildfly-8.2.1-1.el7.x86_64 ovirt-engine-tools-backup-3.6.7.5-1.el7.centos.noarch ovirt-engine-userportal-3.6.7.5-1.el7.centos.noarch ovirt-engine-3.6.7.5-1.el7.centos.noarch ovirt-release35-006-1.noarch ovirt-engine-extension-aaa-ldap-1.1.0-0.0.master.20151021074904.git92c5c31.el7.noarch ovirt-release36-3.6.7-1.noarch ovirt-engine-setup-plugin-ovirt-engine-3.6.7.5-1.el7.centos.noarch ovirt-host-deploy-java-1.4.1-1.el7.centos.noarch ovirt-image-uploader-3.6.0-1.el7.centos.noarch ovirt-engine-dbscripts-3.6.7.5-1.el7.centos.noarch ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.0.7-1.el7.noarch ovirt-engine-extensions-api-impl-3.6.7.5-1.el7.centos.noarch ovirt-engine-restapi-3.6.7.5-1.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.6.7.5-1.el7.centos.noarch ovirt-vmconsole-proxy-1.0.2-1.el7.centos.noarch ovirt-engine-cli-3.6.2.0-1.el7.centos.noarch Thanks, Steve

3 3

HTTP Error 405 when trying to use ovirt-vmconsole
by Marcus Sundberg 22 Oct '16

22 Oct '16

Hi, I have enabled ovirt-vmconsole in oVirt 4.0.4, and the ssh server is running, but whenever I try to connect to it I get the following in the log: Oct 21 18:03:13 host ovirt-vmconsole[22076]: 2016-10-21 18:03:13,021 ovirt-vmconsole-list: ERROR main:274 Error: HTTP Error 405: Method Not Allowed Oct 21 18:03:13 host ovirt-vmconsole-proxy-keys[22072]: ERROR Key list execution failed rc=1 Oct 21 18:03:13 host sshd[22069]: error: AuthorizedKeysCommand /usr/libexec/ovirt-vmconsole-proxy-keys returned status 1 and the ssh client authentication naturally fails. Who is responding with 405, and what am I missing for this to work? //Marcus -- --------------------------------------------- Marcus Sundberg <marcus.sundberg(a)aptilo.com> Senior Systems & Software Architect Aptilo Networks AB, http://www.aptilo.com/

1 0

HTTP Error 405 when trying to use ovirt-vmconsole
by Marcus Sundberg 21 Oct '16

21 Oct '16

Hi, I have enabled ovirt-vmconsole in oVirt 4.0.4, and the ssh server is running, but whenever I try to connect to it I get the following in the log: Oct 21 18:03:13 host ovirt-vmconsole[22076]: 2016-10-21 18:03:13,021 ovirt-vmconsole-list: ERROR main:274 Error: HTTP Error 405: Method Not Allowed Oct 21 18:03:13 host ovirt-vmconsole-proxy-keys[22072]: ERROR Key list execution failed rc=1 Oct 21 18:03:13 host sshd[22069]: error: AuthorizedKeysCommand /usr/libexec/ovirt-vmconsole-proxy-keys returned status 1 and the ssh client authentication naturally fails. Who is responding with 405, and what am I missing for this to work? //Marcus -- --------------------------------------------- Marcus Sundberg <marcus.sundberg(a)aptilo.com> Senior Systems & Software Architect Aptilo Networks AB, http://www.aptilo.com/

1 0

oVirt and Ubuntu>=14.04?
by Jon Forrest 21 Oct '16

21 Oct '16

I've done some looking around to find the status of oVirt running on Ubuntu 14.04 and later. I found the announcement of the ovirt-guest-agent for Ubuntu but I see nothing about the oVirt Engine on Ubuntu. Given that KVM works fine on Ubuntu, I'm curious what's preventing all of oVirt from working on Ubuntu. Cordially, Jon Forrest

5 7

Average VM per host
by Nicolas Ecarnot 21 Oct '16

21 Oct '16

Hello, Though I read some surveys about this, I'd rather directly ask the oVirt community this question, and especially to people using it as a production cluster : as an average, how many VM are running on each of your hosts? -- Nicolas ECARNOT

3 3