- Users - oVirt List Archives

oVirt 3.6.1 ISO storage domain with all-in-one local disk install not working as expected
by Matthew Bohnsack 30 Dec '15

30 Dec '15

Hello, I installed an all-in-one oVirt 3.6.1 system on CentOS 7.2 with local disk configured for images and ISOs. However, the engine web GUI doesn't mention the ISO_DOMAIN, and I can't seem to select an uploaded ISO and attach it to a VM. Any idea what I'm doing wrong here? Thanks, -Matthew Additional detail... I did engine setup with this where all paths are on local disk: OVESETUP_CONFIG/isoDomainName=str:ISO_DOMAIN OVESETUP_CONFIG/isoDomainACL=str:*(rw) OVESETUP_CONFIG/isoDomainMountPoint=str:/home/ovirt-localdisk/iso OVESETUP_AIO/storageDomainDir=str:/home/ovirt-localdisk/images/ With this, I was able to upload an image like so: [root@host ~]# engine-iso-uploader upload -i ISO_DOMAIN ./CentOS-7-x86_64-Minimal-1511.iso Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): Uploading, please wait... INFO: Start uploading ./CentOS-7-x86_64-Minimal-1511.iso Uploading: [########################################] 100% INFO: ./CentOS-7-x86_64-Minimal-1511.iso uploaded successfully After this, the local filesystem had my image: [root@host ~]# find /home/ovirt-localdisk/iso/ -iname \*.iso /home/ovirt-localdisk/iso/d33449b5-f660-4e90-abd4-5d55f9c27b85/images/11111111-1111-1111-1111-111111111111/CentOS-7-x86_64-Minimal-1511.iso But this seems to say something's wrong: [root@host ~]# engine-iso-uploader list Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: There are no ISO storage domains. Further, the engine web gui has no mention of the ISO storage domain nor does CentOS-7-x86_64-Minimal-1511.iso show up as an option to attach as a CDROM to guests.

2 3

Re: [ovirt-users] Self-hosted engine: Host cannot activate - network issues
by Yedidyah Bar David 30 Dec '15

30 Dec '15

On Tue, Dec 29, 2015 at 4:15 AM, Alan Murrell <lists(a)murrell.ca> wrote: > I am attempting to install oVirt 3.6 on a CentOS7 host. it is a single > server, so I am trying to install a self-hosted engine. I am able to > install oVirt 3.5 self-hosted engine, but am having some problems doing it > with 3.6. > > Everything appears to go fine; the engine-setup completes successfully. On > the host, I pressed"1" to indicate engine-setup was complete, and it can > connect to the webadmin but the host never becomes operational. > > I am able to log in to the webadmin, and indeed the host is in a > non-operational state. When I click on the host then click on the "Virtual > networks" tab, all my interfaces are showing a red arrow. > > When I click on "Setup Host Networks", my "ovirtmgmt" network is unassigned. > Believing this to be why my host is not operational (since it is under > "Required"), I assigned it to my management interface, but the interfaces > still remain red. In addition, the "ovirtmgmt" network does have a green > arrow, but also the icon indicating "Out of sync". If I click on "Sync All > Networks", I get the following error: > > "Error while executing action SyncAllHostNetworks: Network is currently > being used" > > which makes sense, since "ovirtmgmt" is assigned/in use. I am unable to > unassign ovirtmgmt. > > Current status is this: > > - All network interfaces are showing the red "down" arrow > - "ovirtmgmt" is assigned to my management NIC, but indicating that it is > out of sync > - I am unable to unassign the "ovirtmgmt" network (or at least, if I do, > the "OK" button is greyed out) > > I could destroy the engine VM and go through the setup again, with the idea > of once it is installed and waiting for the host to become operational, I > could do a "Sync All Networks" and see if the networks turn green and go > from there. > > I wanted to see what sort of insight I could get from here first. I am not > sure what logs would be useful to you, so let me know what you want to see > and I and make them available (I will likely zip them up and post a link) from host: /var/log/ovirt-hosted-engine-*/* (-setup and -ha) /var/log/vdsm/* from engine: /var/log/ovirt-engine/* /var/log/ovirt-engine/host-deploy/* If last one is empty, it means the engine did not manage to get host-deploy logs. Please check and try to copy what you find from /tmp of the host while waiting for host-deploy ("Waiting for the host to become operational"). > > Something else I could try if this becomes a "puzzler" is to do a 3.5.x > self-hosted engine then perform an in-place upgrade to 3.6 and see if that > works? I would rather try to help make a direct 3.6 install work, though... Did you principally do exactly the same thing in 3.5 and 3.6? In both cases just had a simple network interface (no vlan/bonding/whatever) and input it when asked? What exact versions (OS and ovirt)? I also changed the subject. Best, -- Didi

2 5

ovirt 3.6 centos7.2 all-in-one install: The VDSM host was found in a failed state.
by Matthew Bohnsack 29 Dec '15

29 Dec '15

Hello, I am attempting to build a fairly basic proof of concept ovirt 3.6 machine with the engine, host and guests all on a single physical CentOS 7.2 box with local storage (to start), but am running into issues where engine-install produces the following error: [ ERROR ] The VDSM host was found in a failed state. Please check engine and bootstrap installation logs. The engine webconsole seems to be working fine after this - I can login and click around - but there's no host CPU/storage resources available, as expected. From the logs shown below, there seems to be an issue with the vdsm installation process being unable to contact the engine host during installation. Any ideas what's going wrong and/or what I can do to debug things further so I can move beyond this issue? Thanks, -Matthew Steps I took to install and diagnose the problem: 1. Installed system with our configuration management system. 2. Deleted users using UID=36 (needed by vdsm user) and UID=108 (needed by ovirt user). 3. Ensured that /etc/sudoers contained the line "#includedir /etc/sudoers.d" so that /etc/sudoers.d/50_vdsm will take effect. 4. Made directories for isos and images: # mkdir /state/partition1/images/; chmod 777 /state/partition1/images/ # mkdir /state/partition1/iso/; chmod 777 /state/partition1/iso/ 5. Ensured selinux was disabled and no firewall rules were installed. 6. Installed RPMs: # yum -y install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm # yum -y install ovirt-engine ovirt-engine-setup-plugin-allinone # rpm -qa | grep ovirt-release36 ovirt-release36-002-2.noarch 7. Installed engine with an all-in-one configuration (Configure VDSM on this host? Yes): # cat /root/ovirt-engine.ans # action=setup [environment:default] OVESETUP_DIALOG/confirmSettings=bool:True OVESETUP_CONFIG/applicationMode=str:virt OVESETUP_CONFIG/remoteEngineSetupStyle=none:None OVESETUP_CONFIG/sanWipeAfterDelete=bool:False OVESETUP_CONFIG/storageIsLocal=bool:False OVESETUP_CONFIG/firewallManager=none:None OVESETUP_CONFIG/remoteEngineHostRootPassword=none:None OVESETUP_CONFIG/firewallChangesReview=none:None OVESETUP_CONFIG/updateFirewall=bool:False OVESETUP_CONFIG/remoteEngineHostSshPort=none:None OVESETUP_CONFIG/fqdn=<...host.fqdn...> OVESETUP_CONFIG/storageType=none:None OSETUP_RPMDISTRO/requireRollback=none:None OSETUP_RPMDISTRO/enableUpgrade=none:None OVESETUP_DB/secured=bool:False OVESETUP_DB/host=str:localhost OVESETUP_DB/user=str:engine OVESETUP_DB/dumper=str:pg_custom OVESETUP_DB/database=str:engine OVESETUP_DB/fixDbViolations=none:None OVESETUP_DB/port=int:5432 OVESETUP_DB/filter=none:None OVESETUP_DB/restoreJobs=int:2 OVESETUP_DB/securedHostValidation=bool:False OVESETUP_ENGINE_CORE/enable=bool:True OVESETUP_CORE/engineStop=none:None OVESETUP_SYSTEM/memCheckEnabled=bool:True OVESETUP_SYSTEM/nfsConfigEnabled=bool:True OVESETUP_PKI/organization=str:<...dn...> OVESETUP_PKI/renew=none:None OVESETUP_CONFIG/isoDomainName=str:ISO_DOMAIN OVESETUP_CONFIG/engineHeapMax=str:7975M OVESETUP_CONFIG/adminPassword=str:<...password...> OVESETUP_CONFIG/isoDomainACL=str:*(rw) OVESETUP_CONFIG/isoDomainMountPoint=str:/state/partition1/iso OVESETUP_CONFIG/engineDbBackupDir=str:/var/lib/ovirt-engine/backups OVESETUP_CONFIG/engineHeapMin=str:7975M OVESETUP_AIO/configure=bool:True OVESETUP_AIO/storageDomainName=str:local_storage OVESETUP_AIO/storageDomainDir=str:/state/partition1/images/ OVESETUP_PROVISIONING/postgresProvisioningEnabled=bool:True OVESETUP_APACHE/configureRootRedirection=bool:True OVESETUP_APACHE/configureSsl=bool:True OVESETUP_VMCONSOLE_PROXY_CONFIG/vmconsoleProxyConfig=bool:True OVESETUP_ENGINE_CONFIG/fqdn=str:<...fqdn...> OVESETUP_CONFIG/websocketProxyConfig=bool:True # engine-setup --config-append=/root/ovirt-engine.ans ... [ INFO ] Starting engine service [ INFO ] Restarting httpd [ INFO ] Waiting for VDSM host to become operational. This may take several minutes... [ ERROR ] The VDSM host was found in a failed state. Please check engine and bootstrap installation logs. [WARNING] Local storage domain not added because the VDSM host was not up. Please add it manually. [ INFO ] Restarting ovirt-vmconsole proxy service [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20151228112813-iksxhe.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20151228113003-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of setup completed successfully 8. Examined /var/log/ovirt-engine/setup/ovirt-engine-setup-20151228112813-iksxhe.log and found this error message which seems to indicate that the vdsm installation process was unable to contact the engine: 2015-12-28 11:29:29 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:941 execute-output: ('/bin/systemctl', 'start', 'httpd.service') stderr: 2015-12-28 11:29:29 DEBUG otopi.context context._executeMethod:142 Stage closeup METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi.Plugin._closeup 2015-12-28 11:29:29 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:211 Connecting to the Engine 2015-12-28 11:29:29 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitEngineUp:103 Waiting Engine API response 2015-12-28 11:29:29 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitEngineUp:133 Cannot connect to engine Traceback (most recent call last): File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/all-in-one/vdsmi.py", line 127, in _waitEngineUp insecure=True, File "/usr/lib/python2.7/site-packages/ovirtsdk/api.py", line 191, in __init__ url='' File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 115, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 155, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: ^M status: 503^M reason: Service Unavailable^M detail: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. </body></html> 2015-12-28 11:29:36 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitEngineUp:133 Cannot connect to engine Traceback (most recent call last): File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/all-in-one/vdsmi.py", line 127, in _waitEngineUp insecure=True, File "/usr/lib/python2.7/site-packages/ovirtsdk/api.py", line 191, in __init__ url='' File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 115, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 155, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: ^M status: 404^M reason: Not Found^M detail: ... <!DOCTYPE html> <html> <head> <meta http-equiv="Content-type" content="text/html; charset=utf-8" /> <link id="id-link-favicon" rel="shortcut icon" href="/ovirt-engine/theme-resource/favicon" type="image/x-icon" /> <title>404 - Page not found</title> ... </html> 2015-12-28 11:29:50 DEBUG otopi.ovirt_engine_setup.engine_common.database database.execute:171 Database: 'None', Statement: ' select version, option_value from vdc_options where option_name = %(name)s ', args: {'name': 'SupportedClusterLevels'} 2015-12-28 11:29:50 DEBUG otopi.ovirt_engine_setup.engine_common.database database.execute:221 Result: [{'version': 'general', 'option_value': '3.0,3.1,3.2,3.3,3.4,3.5,3.6'}] 2015-12-28 11:29:50 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:225 engine SupportedClusterLevels [3.0,3.1,3.2,3.3,3.4,3.5,3.6], PACKAGE_VERSION [3.6.1.3], 2015-12-28 11:29:50 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._getSupportedClusterLevels:181 Attempting to load the dsaversion vdsm module 2015-12-28 11:29:50 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:236 VDSM SupportedClusterLevels [['3.4', '3.5', '3.6']], VDSM VERSION [4.17.13-0.el7.centos], 2015-12-28 11:29:50 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:259 Creating the local data center 2015-12-28 11:29:50 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:269 Creating the local cluster into the local data center 2015-12-28 11:29:52 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:284 Adding the local host to the local cluster 2015-12-28 11:29:55 INFO otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:58 Waiting for VDSM host to become operational. This may take several minutes... 2015-12-28 11:29:55 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:87 VDSM host in installing state 2015-12-28 11:29:56 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:87 VDSM host in installing state 2015-12-28 11:29:58 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:87 VDSM host in installing state 2015-12-28 11:29:59 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:87 VDSM host in installing state 2015-12-28 11:30:00 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:87 VDSM host in installing state 2015-12-28 11:30:01 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:87 VDSM host in installing state 2015-12-28 11:30:02 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._waitVDSMHostUp:77 The VDSM host was found in a failed state. Please check engine and bootstrap installation logs. 2015-12-28 11:30:02 WARNING otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi vdsmi._closeup:306 Local storage domain not added because the VDSM host was not up. Please add it manually. 2015-12-28 11:30:02 DEBUG otopi.context context._executeMethod:142 Stage closeup METHOD otopi.plugins.ovirt_engine_setup.vmconsole_proxy_helper.system.Plugin._closeup 9. Looked at the vdsm logs and examined service status: # ls -l /var/log/vdsm/ total 8 drwxr-xr-x 2 vdsm kvm 6 Dec 9 03:24 backup -rw-r--r-- 1 vdsm kvm 0 Dec 28 11:13 connectivity.log -rw-r--r-- 1 vdsm kvm 0 Dec 28 11:13 mom.log -rw-r--r-- 1 root root 2958 Dec 28 11:30 supervdsm.log -rw-r--r-- 1 root root 1811 Dec 28 11:30 upgrade.log -rw-r--r-- 1 vdsm kvm 0 Dec 28 11:13 vdsm.log # cat /var/log/vdsm/upgrade.log MainThread::DEBUG::2015-12-28 11:30:02,803::upgrade::90::upgrade::(apply_upgrade) Running upgrade upgrade-unified-persistence MainThread::DEBUG::2015-12-28 11:30:02,806::libvirtconnection::160::root::(get) trying to connect libvirt MainThread::DEBUG::2015-12-28 11:30:02,813::utils::669::root::(execCmd) /sbin/ip route show to 0.0.0.0/0 table main (cwd None) MainThread::DEBUG::2015-12-28 11:30:02,826::utils::687::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0 MainThread::DEBUG::2015-12-28 11:30:02,826::unified_persistence::46::root::(run) upgrade-unified-persistence upgrade persisting networks {} and bondings {} MainThread::INFO::2015-12-28 11:30:02,827::netconfpersistence::179::root::(_clearDisk) Clearing /var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/ MainThread::DEBUG::2015-12-28 11:30:02,827::netconfpersistence::187::root::(_clearDisk) No existent config to clear. MainThread::INFO::2015-12-28 11:30:02,827::netconfpersistence::179::root::(_clearDisk) Clearing /var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/ MainThread::DEBUG::2015-12-28 11:30:02,827::netconfpersistence::187::root::(_clearDisk) No existent config to clear. MainThread::INFO::2015-12-28 11:30:02,827::netconfpersistence::129::root::(save) Saved new config RunningConfig({}, {}) to /var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/ MainThread::DEBUG::2015-12-28 11:30:02,827::utils::669::root::(execCmd) /usr/share/vdsm/vdsm-store-net-config unified (cwd None) MainThread::DEBUG::2015-12-28 11:30:02,836::utils::687::root::(execCmd) SUCCESS: <err> = 'cp: cannot stat \xe2\x80\x98/var/run/vdsm/netconf\xe2\x80\x99: No such file or directory\n'; <rc> = 0 MainThread::DEBUG::2015-12-28 11:30:02,837::upgrade::51::upgrade::(_upgrade_seal) Upgrade upgrade-unified-persistence successfully performed # cat /var/log/vdsm/supervdsm.log MainThread::DEBUG::2015-12-28 11:30:02,415::supervdsmServer::539::SuperVdsm.Server::(main) Making sure I'm root - SuperVdsm MainThread::DEBUG::2015-12-28 11:30:02,415::supervdsmServer::548::SuperVdsm.Server::(main) Parsing cmd args MainThread::DEBUG::2015-12-28 11:30:02,415::supervdsmServer::551::SuperVdsm.Server::(main) Cleaning old socket /var/run/vdsm/svdsm.sock MainThread::DEBUG::2015-12-28 11:30:02,415::supervdsmServer::555::SuperVdsm.Server::(main) Setting up keep alive thread MainThread::DEBUG::2015-12-28 11:30:02,415::supervdsmServer::561::SuperVdsm.Server::(main) Creating remote object manager MainThread::DEBUG::2015-12-28 11:30:02,416::fileUtils::192::Storage.fileUtils::(chown) Changing owner for /var/run/vdsm/svdsm.sock, to (36:36) MainThread::DEBUG::2015-12-28 11:30:02,416::supervdsmServer::572::SuperVdsm.Server::(main) Started serving super vdsm object sourceRoute::DEBUG::2015-12-28 11:30:02,416::sourceroutethread::79::root::(_subscribeToInotifyLoop) sourceRouteThread.subscribeToInotifyLoop started restore-net::DEBUG::2015-12-28 11:30:03,080::libvirtconnection::160::root::(get) trying to connect libvirt restore-net::INFO::2015-12-28 11:30:03,188::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV network device which is not persisted found at: 0000:01:00.1. restore-net::INFO::2015-12-28 11:30:03,189::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV network device which is not persisted found at: 0000:01:00.0. restore-net::INFO::2015-12-28 11:30:03,189::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV network device which is not persisted found at: 0000:01:00.3. restore-net::INFO::2015-12-28 11:30:03,189::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV network device which is not persisted found at: 0000:01:00.2. restore-net::INFO::2015-12-28 11:30:03,189::vdsm-restore-net-config::385::root::(restore) starting network restoration. restore-net::DEBUG::2015-12-28 11:30:03,189::vdsm-restore-net-config::183::root::(_remove_networks_in_running_config) Not cleaning running configuration since it is empty. restore-net::INFO::2015-12-28 11:30:03,205::netconfpersistence::179::root::(_clearDisk) Clearing /var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/ restore-net::DEBUG::2015-12-28 11:30:03,206::netconfpersistence::187::root::(_clearDisk) No existent config to clear. restore-net::INFO::2015-12-28 11:30:03,206::netconfpersistence::129::root::(save) Saved new config RunningConfig({}, {}) to /var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/ restore-net::DEBUG::2015-12-28 11:30:03,207::vdsm-restore-net-config::329::root::(_wait_for_for_all_devices_up) All devices are up. restore-net::INFO::2015-12-28 11:30:03,214::netconfpersistence::71::root::(setBonding) Adding bond0({'nics': [], 'options': ''}) restore-net::INFO::2015-12-28 11:30:03,214::vdsm-restore-net-config::396::root::(restore) restoration completed successfully. # systemctl status supervdsmd ● supervdsmd.service - Auxiliary vdsm service for running helper functions as root Loaded: loaded (/usr/lib/systemd/system/supervdsmd.service; static; vendor preset: enabled) Active: active (running) since Mon 2015-12-28 11:30:02 EST; 1h 8min ago Main PID: 81535 (supervdsmServer) CGroup: /system.slice/supervdsmd.service └─81535 /usr/bin/python /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock Dec 28 11:30:02 hostname systemd[1]: Started Auxiliary vdsm service for running helper functions as root. Dec 28 11:30:02 hostname systemd[1]: Starting Auxiliary vdsm service for running helper functions as root.

1 2

Network instability after upgrade 3.6.0 -> 3.6.1
by Stefano Danzi 29 Dec '15

29 Dec '15

Hello, I have one testing host (only one host) with self hosted engine and 2 VM (one linux and one windows). After upgrade ovirt from 3.6.0 to 3.6.1 the network connection works discontinuously. Every 10 minutes HA agent restart hosted engine VM because result down. But the machine is UP, only the network stop to work for some minutes. I activate global maintenace mode to prevent engine reboot. If I ssh to the hosted engine sometimes the connection work and sometimes no. Using VNC connection to engine I see that sometime VM reach external network and sometimes no. If I do a tcpdump on phisical ethernet interface I don't see any packet when network on vm don't work. Same thing happens fo others two VM. Before the upgrade I never had network problems.

3 4

virt-viewer error
by 靳占冰 29 Dec '15

29 Dec '15

virt-viewer-x64-3.0.msi version can not connect a virtual machine. Error: Can not find the specified file

2 1

Hosted engine vs. hypervisor hosts naming on hyperconverged setup
by Will Dennis 29 Dec '15

29 Dec '15

Hi all, I have a hyperconverged setup where I have a hosted engine that runs on one of three hosts, which are named “ovirt-node-[01,02,03]” — [root@ovirt-node-01 ~]# hosted-engine --vm-status | grep -e "Hostname" -e "Engine" Hostname : ovirt-node-01 Engine status : {"health": "good", "vm": "up", "detail": "up"} Hostname : ovirt-node-02 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Hostname : ovirt-node-03 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown”} When I deployed the hosted engine, I gave it a separate hostname/IP, as I expected it would need it (hostname = “ovirt-engine-01”) However, when I look at the hosts in the oVirt web admin screen, I see that the first host has the name “ovirt-engine-01” whereas it has the hostname of “ovirt-node-01” I also notice that even though the 1st host is showing the number of VM’s running as “1”, when I click on the “VMs” node, there are no VMs showing. Not sure of what “should be”, but, would expect that the first host would have a name equal to its DNS hostname (like the other two do), and that in VMs I would see the engine VM. But is that not how a hosted engine setup works? And if not, if the engine VM migrates over to another host, will that host gain the name "“ovirt-engine-01”? I ask this now because I want to set up a storage domain on these hosts using GlusterFS, and I have to select a host to base the connection on. In the “Use Host” dropbox, I currently see the values: ovirt-node-03 ovirt-node-02 ovirt-engine-01 I would expect that the last entry would be for “ovirt-host-01”, not “ovirt-engine-01”… I don’t want to set up the storage domain until I figure this out, so as to prevent potential breakage... Thanks, Will

3 10

Hosted engine support
by Budur Nagaraju 29 Dec '15

29 Dec '15

HI Installed KVM in the host in which VT is enabled . installed one vm centos6.7 64 bit in the KVM server and tried to configure Hosted engine ,getting the below error , *"Failed to execute stage ‘Environment Customization’: Hardware virtualization support is not available :please check BIOS settings and turn on NX support if available"* Even though VT is enabled facing the issue any setting needs to be done in the vm ? Thanks, Nagaraju

2 1

Change "ovirt-engine" virtual directory
by Hamid Mazrae Mollaie 29 Dec '15

29 Dec '15

hi all i want to change "ovirt-engine" in url's web admin portal for branding. how can i do? tanx

2 3

oVirt 3.6.1 USB Host Device passthrough
by ovirt＠timmi.org 29 Dec '15

29 Dec '15

This is a multi-part message in MIME format. --------------070308000109060601050508 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi list, I'm currently trying to get USB devices into a VM. My host is running a oVirt 3.6.1. I'm trying to use the GUI feature to add the device into the VM and I'm facing two issues: 1. I receive the following message while starting the VM: Error while executing action: <VM_Name>: * Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: * The host <host_name> did not satisfy internal filter HostDevice because it does not support host device passthrough.. 2. The USB device list never get refreshed while removing or inserting different devices. Does anyone knows what I'm doing wrong or what I need to check? I found for example the following description for oVirt 3.5. http://wiki.rosalab.com/en/index.php/Blog:ROSA_Planet/How_to_use_USB_device… But this is not helping me as I will have multiple USB devices with the same ID in the host. Best regards and Merry Christmas Christoph --------------070308000109060601050508 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi list, I'm currently trying to get USB devices into a VM. My host is running a oVirt 3.6.1. I'm trying to use the GUI feature to add the device into the VM and I'm facing two issues: 1. I receive the following message while starting the VM: <tt>Error while executing action: </tt><tt> </tt><tt> </tt><tt><VM_Name>:</tt> <ul style="margin-top:0"> <li><tt>Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:</tt></li> <li><tt>The host <host_name> did not satisfy internal filter HostDevice because it does not support host device passthrough..</tt></li> </ul> 2. The USB device list never get refreshed while removing or inserting different devices. Does anyone knows what I'm doing wrong or what I need to check? I found for example the following description for oVirt 3.5. <a class="moz-txt-link-freetext" href="http://wiki.rosalab.com/en/index.php/Blog:ROSA_Planet/How_to_use_USB_device…">http://wiki.rosalab.com/en/index.php/Blog:ROSA_Planet/How_to_use_USB_device…</a> But this is not helping me as I will have multiple USB devices with the same ID in the host. Best regards and Merry Christmas Christoph </body> </html> --------------070308000109060601050508--

4 5

oVirt 3.6: Dummy interfaces
by Alan Murrell 29 Dec '15

29 Dec '15

Hello, I just upgraded my oVirt 3.5.1 install to 3.6. I have a self-hosted engine setup all on a single server. I make use of dummy interfaces for internal networks for my various labs/testing setups. Normally I edit the following file: /usr/lib/python2.7/site-packages/vdsm/config.py I then go to the variable 'fake_nics' and add 'dummy*", so it looks like this: ('fake_nics', 'dummy_*,veth_*,dummy*', ), After I added my entry, I even restarted the whole server (which restarts the VDSM on the host as well as the engine VM), but when I go into the "Network Interfaces" on the host the dummy interfaces are not showingup. Are dummy interfaces still supported in 3.6? I see a feature called "Isolated Networks" in 3.6; is this essentially a replacement? The Features page is a bit confusing to me on how to create an isolated network? Thanks! Regards, Alan

4 4