- Users - oVirt List Archives

Re: Hyper-V to KVM | v2v
by Strahil 07 Dec '19

07 Dec '19

Have you tried to power up and fully shutdown the VM ? Best Regards, Strahil NikolovOn Dec 6, 2019 15:52, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: > > Hello, > > > > I am trying to convert a Hyper-V guest VM to run on KVM using virt-v2v utility. > > > > Getting below error: > > > > > > Any suggestions how to solve this. > > > > Thanks > > > > Vijay Sachdeva > >

2 2

ovirt-ha-agent not running
by Stefan Wolf 07 Dec '19

07 Dec '19

hello, since some days ovirt-ha-agent is not running anymore i ve 4 ovirt hosts and only on one host the agent is running. maybe it was from an update, because i lost one agent after an other. i ve done a complete fresh install for the host with the latest ovirt node. I ve got on tree hosts this error [root@kvm380 ~]# systemctl status ovirt-ha-agent ● ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring Agent Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Sa 2019-12-07 14:56:21 UTC; 5s ago Process: 28002 ExecStart=/usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent (code=exited, status=157) Main PID: 28002 (code=exited, status=157) Tasks: 0 CGroup: /system.slice/ovirt-ha-agent.service Dez 07 14:56:21 kvm380.durchhalten.intern systemd[1]: ovirt-ha-agent.service: main process exited, code=exited, status=157/n/a Dez 07 14:56:21 kvm380.durchhalten.intern systemd[1]: Unit ovirt-ha-agent.service entered failed state. Dez 07 14:56:21 kvm380.durchhalten.intern systemd[1]: ovirt-ha-agent.service failed. and this is in /var/log/ovirt-hosted-engine-ha/agent.log MainThread::INFO::2019-12-07 15:01:51,048::agent::67::ovirt_hosted_engine_ha.agent.agent.Agent::(run) ovirt-hosted-engine-ha agent 2.3.6 started MainThread::INFO::2019-12-07 15:01:51,161::hosted_engine::234::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname) Found certificate common name: kvm380.durchhalten.intern MainThread::INFO::2019-12-07 15:01:51,374::hosted_engine::543::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Initializing ha-broker connection MainThread::INFO::2019-12-07 15:01:51,378::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor network, options {'tcp_t_address': None, 'network_test': None, 'tcp_t_port': None, 'addr': '192.168.200.1'} MainThread::ERROR::2019-12-07 15:01:51,379::hosted_engine::559::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Failed to start necessary monitors MainThread::ERROR::2019-12-07 15:01:51,381::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent return action(he) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper return he.start_monitoring() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 432, in start_monitoring self._initialize_broker() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 556, in _initialize_broker m.get('options', {})) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 89, in start_monitor ).format(t=type, o=options, e=e) RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'tcp_t_address': None, 'network_test': None, 'tcp_t_port': None, 'addr': '192.168.200.1'}] MainThread::ERROR::2019-12-07 15:01:51,381::agent::145::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Trying to restart agent MainThread::INFO::2019-12-07 15:01:51,382::agent::89::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down maybe someone can give me an advice thx shb

1 1

VLANs with one NIC in ovirt
by siovelrm＠gmail.com 06 Dec '19

06 Dec '19

Hi, is it possible to use different VLANs with one NIC in ovirt? Regards

4 4

Hyper-V to KVM | v2v
by Vijay Sachdeva 06 Dec '19

06 Dec '19

Hello, I am trying to convert a Hyper-V guest VM to run on KVM using virt-v2v utility. Getting below error: Any suggestions how to solve this. Thanks Vijay Sachdeva

3 2

Issue deploying self hosted engine on new install
by Robert Webb 06 Dec '19

06 Dec '19

Hi all, I am trying to deploy the self hosted engine via cockpit and it is failing at the very end of deployment when it is checking the VM Health. I have done multiple clean installs and run this and it fails every time. I have also tried from the cli via ssh with the same outcome. After the failure, if I look at the oVirt Machines section of the node, the VM is there but will not start. Anyone else having this issue?

1 0

[ANN] oVirt 4.3.8 First Release Candidate is now available for testing
by Sandro Bonazzola 06 Dec '19

06 Dec '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.8 First Release Candidate for testing, as of December 6th, 2019. This update is a release candidate of the eighth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.8 release highlights: http://www.ovirt.org/release/4.3.8/ * 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] http://www.ovirt.org/release/4.3.8/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Gluster FS & hosted engine fails to set up
by rob.downer＠orbitalsystems.co.uk 05 Dec '19

05 Dec '19

I have set up 3 new servers and as you can see Gluster is working well, however the hosted engine deployment fails can anyone suggest a reason ? I have wiped and set up all three servers again and set up Gluster first. This is the gluster congig I have used for the setup. Please review the configuration. Once you click the 'Finish Deployment' button, the management VM will be transferred to the configured storage and the configuration of your hosted engine cluster will be finalized. You will be able to use your hosted engine once this step finishes. * StorageStorage Type:glusterfs Storage Domain Connection:gfs3.gluster.private:/engine Mount Options:backup-volfile-servers=gfs2.gluster.private:gfs1.gluster.private Disk Size (GiB):58 [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Unexpected exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Unexpected exception]\". HTTP response code is 400."} root@ovirt3 ~]# gluster volume status Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gfs3.gluster.private:/gluster_bricks/ data/data 49152 0 Y 3756 Brick gfs2.gluster.private:/gluster_bricks/ data/data 49153 0 Y 3181 Brick gfs1.gluster.private:/gluster_bricks/ data/data 49152 0 Y 15548 Self-heal Daemon on localhost N/A N/A Y 17602 Self-heal Daemon on gfs1.gluster.private N/A N/A Y 15706 Self-heal Daemon on gfs2.gluster.private N/A N/A Y 3348 Task Status of Volume data ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gfs3.gluster.private:/gluster_bricks/ engine/engine 49153 0 Y 3769 Brick gfs2.gluster.private:/gluster_bricks/ engine/engine 49154 0 Y 3194 Brick gfs1.gluster.private:/gluster_bricks/ engine/engine 49153 0 Y 15559 Self-heal Daemon on localhost N/A N/A Y 17602 Self-heal Daemon on gfs1.gluster.private N/A N/A Y 15706 Self-heal Daemon on gfs2.gluster.private N/A N/A Y 3348 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gfs3.gluster.private:/gluster_bricks/ vmstore/vmstore 49154 0 Y 3786 Brick gfs2.gluster.private:/gluster_bricks/ vmstore/vmstore 49152 0 Y 2901 Brick gfs1.gluster.private:/gluster_bricks/ vmstore/vmstore 49154 0 Y 15568 Self-heal Daemon on localhost N/A N/A Y 17602 Self-heal Daemon on gfs1.gluster.private N/A N/A Y 15706 Self-heal Daemon on gfs2.gluster.private N/A N/A Y 3348 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks

1 0

Re: Importing a Virtual Machine from a KVM Host
by Dirk Streubel 05 Dec '19

05 Dec '19

Hello Paul, thanks a lot for your answer. If i have any other questions during the import maybe i can asked again? And i let you know the result :) Regards Dirk Am 05.12.19 um 13:22 schrieb Staniforth, Paul: > Hello Dirk, > The link you are using is old developer docs, try the following. > https://www.ovirt.org/documentation/admin-guide/chap-External_Providers.html > > You need to setup an external provider and use a proxy host in the datacentre (not the engine host) you want to import into, this needs to be on the same network as your KVM host and have the virt-v2v package installed. > > Regards, > Paul S. > > -----Original Message----- > From: Dirk Streubel <dirk.streubel(a)posteo.de> > Sent: 05 December 2019 11:10 > To: users <users(a)ovirt.org> > Subject: [ovirt-users] Importing a Virtual Machine from a KVM Host > > Hello everbody, > > i am just a little bit confused about importing Qemu Images from my KVM Host. > > At home, and at work i am using a ovirt engine in a VM. The Version is 4.3.7 and on bare metal my host. > > Everything works fine but i have the same problem at home and on work. I want to import my qcow2 Images from a KVM Host but i > > will not work. > > The command virsh -r -c 'qemu+tcp://root@host1.example.org/system' list --all shows me akk my VMs. > > But when i want to load the images in the GUI, nothing happens. I follow this instruction: > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > After that, i take a look on the official 4.3 Rhev Documentation from Red Hat. There stand this: > > Log in to the proxy host and generate SSH keys for the vdsm user. > > sudo -u vdsm ssh-keygen > > So, i have no proxy host. So i want to do this on my ovirt-engine. Is this right? > > Next thing: the user vdsm is locked on the ovirt-engine machine and the host. > > So, do i have to unlocked the account of the user vdsm or what is the best way. > > My Problem is i found nothing that would help me to solve this problem. > > Maybe somebody here do me a favour and help me to solve this "challenge" > > Regards > > Dirk > > > > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/

1 0

Possible sources of cpu steal and countermeasures
by klaasdemter＠gmail.com 05 Dec '19

05 Dec '19

Hi, I'm having performance issues with a ovirt installation. It is showing high steal (5-10%) for a cpu intensive VM. The hypervisor however has more than 65% of his resources idle while the steal is seen inside of the VM. Even when placing only a single VM on a hypervisor it still receives steal (0-2%), even though the hypervisor is not overcommited. Hypervisor: 2 Socket system in total 2*28(56HT) cores VM: 30vCPUs (ovirt seems to think its a good idea to make that 15 sockets * 2 cores) My questions are: a) Could it be that the hypervisor is trying to schedule all 30 cores on a single numa node, ie using the HT cores instead of "real" ones and this shows up as steal? b) Do I need to make VMs this big numa-aware and spread the vm over both numa nodes? c) Would using the High Performance VM type help in this kind of situation? d) General advise: how do I reduce steal in an environment where the hypervisor has idle resources Any advise would be appreciated. Greetings Klaas

3 2

Re: Unable to attach ISO domain to Datacenter
by Strahil 05 Dec '19

05 Dec '19

Hi Ivan, Which file is this ? Contact me in private and I will send you my copy for comparison. Best Regards, Strahil NikolovOn Dec 4, 2019 18:55, Ivan Apolonio <ivan(a)apolonio.com.br> wrote: > > I've tried to commenting out this line on /etc/pam.d/password-auth: > > auth requisite pam_succeed_if.so uid >= 1000 quiet_success > > However, although it has stopped complaining about "requirement uid >= 1000 not met by user vdsm" on /var/log/secure , the error trying to attach ISO Domain to Datacenter still persists, showing the same error message, so it looks that this was not the cause of the problem :-( > > Going back to stage zero. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TTD4PH2FIUK23…

1 0

Ovirt-OSN integration
by siovelrm＠gmail.com 04 Dec '19

04 Dec '19

Hi, I want to use External Logical Networks Openstack Neutron. For this it is necessary to have all Openstack installed or is it possible to have only Neutron and used as a service? Sorry if the question is very obvious but I am starting now with this topic.

2 2

Re: 3node HCI fails when HostedEngineLocal is trying to add additional Gluster members
by Strahil 04 Dec '19

04 Dec '19

If you manage to get your VM on the gluster - you are almost done. I had similar situation and using virsh/hosted-engine , I have managed to reach the GUI. From there we can have a Clue what is going on. Usually there is a dependency: - Master storage domain should be UP -This allows the DC to become UP -Then a host in the cluster can become SPM (control storage) -And only then you can start your other gluster volumes. So I can only recommend you to try to reach GUI and check the situation. Then it will be moderately easy to bring everything up. Best Regards, Strahil NikolovOn Dec 4, 2019 17:06, thomas(a)hoberg.net wrote: > > Thanks Strahil, for your suggestions. > > Actually, I was far beyond the pick-up point you describe, as the Gluster had all been prepared and was operable, even the local VM was already running and accessible via the GUI. > > But I picked up your hint to try to continue with the scripted variant, and found that it allowed me much better insight into what was going on. > > I am a little worried, though, that it actually works a little differently from the GUI-wizard variant, in any case the failures don't seem identical. > That would have implications in terms of test-automation, which I'd rather not have to worry about. > > In a separate test for the same operation on a separate set of hardware the installation got significantly further, up to the point where the local VM had actually been moved onto the Gluster storage and into the Cluster, but then failed a validation step at the very end (while the VM is actually up and running, albeit only withe primary host and that listed as "Unresponsive" while it's hosting the VM....) > > I have opened a separate tickt for that... > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FTCFIP7Q5KWXT…

1 0

Cannot activate/deactivate storage domain
by Albl, Oliver 04 Dec '19

04 Dec '19

Hi all, I run an oVirt 4.3.6.7-1.el7 installation (50+ hosts, 40+ FC storage domains on two all-flash arrays) and experienced a problem accessing single storage domains. As a result, hosts were taken "not operational" because they could not see all storage domains, SPM started to move around the hosts. oVirt messages start with: 2019-11-04 15:10:22.739+01 | VDSM HOST082 command SpmStatusVDS failed: (-202, 'Sanlock resource read failure', 'IO timeout') 2019-11-04 15:10:22.781+01 | Invalid status on Data Center <name>. Setting Data Center status to Non Responsive (On host HOST82, Error: General Exception). ... 2019-11-04 15:13:58.836+01 | Host HOST017 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.85+01 | Host HOST005 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.85+01 | Host HOST012 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.851+01 | Host HOST002 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.851+01 | Host HOST010 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.851+01 | Host HOST011 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.852+01 | Host HOST004 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.011+01 | Host HOST017 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.238+01 | Host HOST004 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.249+01 | Host HOST005 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.255+01 | Host HOST012 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.273+01 | Host HOST002 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.279+01 | Host HOST010 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.386+01 | Host HOST011 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:15:14.145+01 | Storage domain HOST_LUN_221 experienced a high latency of 9.60953 seconds from host HOST038. This may cause performance and functional issues. Please consult your Storage Administrator. The problem mainly affected two storage domains (on the same array) but I also saw single messages for other storage domains (one the other array as well). Storage domains stayed available to the hosts, all VMs continued to run. When constantly reading from the storage domains (/bin/dd iflag=direct if=<metadata> bs=4096 count=1 of=/dev/null) we got expected 20+ MBytes/s on all but some storage domains. One of them showed "transfer rates" around 200 Bytes/s, but went up to normal performance from time to time. Transfer rate to this domain was different between the hosts. /var/log/messages contain qla2xxx abort messages on almost all hosts. There are no errors on SAN switches or storage array (but vendor is still investigating). I did not see high load on the storage array. The system seemed to stabilize when I stopped all VMs on the affected storage domain and this storage domain became "inactive". Currently, this storage domain still is inactive and we cannot place it in maintenance mode ("Failed to deactivate Storage Domain") nor activate it. OVF Metadata seems to be corrupt as well (failed to update OVF disks <id>, OVF data isn't updated on those OVF stores). The first six 512 byte blocks of /dev/<id>/metadata seem to contain only zeros. Any advice on how to proceed here? Is there a way to recover this storage domain? All the best, Oliver

4 13

3node HCI fails when HostedEngineLocal is trying to add additional Gluster members
by thomas＠hoberg.net 04 Dec '19

04 Dec '19

Three Gen8 HP360 recalled from retirement with single 1TB TLC SATA SSD for boot and oVirt /engine and 7x4TB HDD RAID6 for /vmstore and /data, 10Gbit NICs and network. All CentOS 7.7 updated daily. These machines may not be used exclusively for oVirt so I don't want to re-install the OS, when an oVirt setup fails: Instead I try my best to clean up the nodes when doing another oVirt installation run. They ran oVirt for a week or two using a completely distinct set of storage, so they are fundamentally sound, but we wanted higher storage capacity so I swapped everything and re-installed CentOS very much the same way as before. The first oVirt setup went smoothly but the cluster crumbled without much usage. I won't go into details here, because I didn't want to investigate for now, instead I focussed on redoing the installation and cleaning up the old setup. I know the docs actually recommend starting with wiped hardware, but operationally that would be a show-stopper for the intended use case. So I cleaned up the best I can (ovirt-hosted-engine-cleanup with and without redoing the whole Gluster storage setup, where apart from SSD caching not working, I don't have issues). Undoing the network changes in such a way that the oVirt HCI wizard ceases complaining is a bit more involved. I typically run: - vdsm-tool ovn-unconfigure - vdsm-tool clear-nets (now need to switch to the console) - vdsm-tool remove-config and then I still need to edit /etc/sysconfig/network-scripts/ifcfg-<ethernet-device> to bring the physical adapter back to life. Sometimes I still need to remove the ovirtmgmnt bridge manually etc. Whether I remove and redo the Gluster as a bit of an effect in re-installation, but it doesn't make a difference in what follows. So here is where I am currently getting stuck consistently: The wizard is gone through preparing the Gluster storage (which is completely functional at that point), has created the local VM on the installation node, installed the Postgres database, filled it etc. basically has oVirt up and running with the primary Gluster node and now would like to add the second and third nodes. At that point I get "Connection lost" in the Web-Wizard, evidently as a consequence of Ansible fiddling around heavily to set up the local bridge for the VM. I remember that for the scripted variant of the setup it is recommended to run the script behind 'screen' or 'tmux' in order to ensure its execution isn't interrupted by that. But for the GUI variant, evidently there *should* be some other type of potection, perhaps via the re-connecting nature of HTTP... Pushing the "Reconnect" button on the GUI at that point doesn't return you to the point of the setup, but only offers to redeploy, while the HostedEngineLocal is still there and running. I ssh'd into the machine and started looking for errors and warning and saw that the installation had gone rather far without incidence. OTOPI had completely finished the WildFly server is up and running the Postgres database fully installed and running smoothly, the only thing I can find is that it's trying to add the additional gluster nodes, but complains that these nodes (quotes gluster-UUIDs) are not part of the "cluster". An investigation into the Postgres database shows, that the 'gluster_server' table indeed only has the primary node in it. I don't know what part of the process should have added the other two nodes, but there seems to be no *remaining* connectivity issue with the Gluster members. I installed gscli and connected to all three nodes and volumes without issue. I am guessing at this point, that the complex rewiring of the software defined network is causing a temporary issue and a race condition that I don't know how to recover from. Since the oVirt management GUI is actually fully operational and can be reached from the primary node via the temporary bridge, I went into the GUI and even managed to add the additional two nodes without any problems. Their installation went through without any issues, they showed up in the gluster_servers table on Postgress and basically the installation could have proceeded from that point, except... that I don't know how to restart the process from that point: It still has to 'beam' the local VM into the Gluster storage and restart it there. I have gone through the process three times now, with absolutely identical results. I could use some help how to recover from that situation, which looks like a race condition, nothing a re-installation of everything would really resolve. In the mean-time, I'll try the scripted variant on 'screen' to see if that fares better.

2 3

Re: Certificate of host is invalid
by Strahil 04 Dec '19

04 Dec '19

Hi , You can try with: 1. Set the host in maintenance 2. From Install dropdown , select 'reinstall' and then configure the necessary info + whether you would like to use the host as Host for the HostedEngine VM. Once the reinstall (of Ovirt software) is OK, the node will be activated automatically. Best Regards, Strahil NikolovOn Nov 27, 2019 18:01, Jon bae <jonbae77(a)gmail.com> wrote: > > Hello everybody, > since last update to 4.3.7 I get this error message: > > Certificate of host host.name is invalid. The certificate doesn't contain valid subject alternative name, please enroll new certificate for the host. > > Have you an idea of how I can fix that? > > Regards > Jonathan

3 3

Re: Scenario: Ovirt-engine on hardware and recovery
by Yedidyah Bar David 04 Dec '19

04 Dec '19

On Tue, Dec 3, 2019 at 3:44 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Didi, > > Thanks for the reply. > > Yes, backups are done, I am just thinking in the case of Murphy's Law where nothing works and the engine is gone. I am also new to oVirt and am always loking for the "proper" backup method as you have laready mentioned using engine-backup. > > Storage is NFS backed and backups are done in case of storage server failure. OK. I suggest, then, that you methodically plan, document and test your environment on various different failure modes. Since you are new to oVirt, it's obvious you still do not have the full mental image of all the components, their behaviour, etc., and even more so how they might react, or be handled, in emergency situations. In particular, spend some time learning about the SPM, master storage domain, HA VMs and how they might be affected by/affecting restore flows, etc. Good luck! > > What is the preferred VM backup method so both disk and VM config is captured? Would rather not have to put agents on all the VM for OS level backups and then have to manually recreate all of the machines. Do all the VM configs get stored on the shared storage just like one of the other virtualization vendors? oVirt does not supply, nor endorse, a specific "preferred method" for this. Rather, it exposes an API, and provides a simple example script: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/vm_backu… There are several backup products/projects, both large and small, both open and closed source, that use this API and can be used. I personally never used any, so can't recommend anything. If you search a bit the list archives you'll find at least some of them. Best regards, > > Appreciate the time from folks on the list who respond. > ________________________________ > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: Tuesday, December 3, 2019 3:29 AM > To: Robert Webb <rwebb(a)ropeguru.com> > Cc: users <users(a)ovirt.org> > Subject: Re: [ovirt-users] Scenario: Ovirt-engine on hardware and recovery > > On Tue, Dec 3, 2019 at 4:38 AM <rwebb(a)ropeguru.com> wrote: > > > > So thinking about my setup, I am thinking through different failure scenarios. > > > > So lets say I have a small physical server with 8 cores and 16GB RAM and I install Centos 7 and ovirt-engine on bare metal. This would also be the same scenario is the engine were on a VM. > > > > I run into a major hardware issue and completely lose the engine. > > You do take backups, right? :-) > > For the engine itself, you can use engine-backup. > > > > > How does one recover the cluster setup and not have to start from scratch by having to rebuild all the nodes? Can the engine just be rebuilt and the ovirt nodes be imported? > > You didn't mention your plans re storage. > > If you put your VMs on well-handled storage, and lose everything but > the storage, you can install a new engine, new nodes, and then import > the VMs from the existing storage. You will still miss some > configuration etc., but should mostly be ok. > > If you plan to use gluster storage using the same nodes, aka HCI, the > same applies, obviously, only that the nodes are your storage, and not > an external system. You still have to make sure you handle them > properly - backup, DR, etc., depending on your needs and budget. > > If you do have engine-backup backups, but lost all your storage, > engine-backup will not help you. > > > > > > This scenario is based on the nodes being built from the ovirt node iso. > > That's ok, but is not relevant. Main question is the storage. Can be > external or local/gluster with either ovirt-node or EL. > > Good luck, > > -- > Didi > -- Didi

1 0

Re: Failed export to OVA
by Strahil 04 Dec '19

04 Dec '19

Have you checked /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20191203112412-kvmclst1a.home.whootis.com-67d3d8f2.log ? Best Regards, Strahil NikolovOn Dec 3, 2019 21:36, Geoff Sweet <geoffrsweet+ovirtusers(a)gmail.com> wrote: > > I'm currently running a stand alone server on 4.2.0.2-1.el7.centos. I know this is an older version and I am trying to do some exports for migrations off of it. The Export to OVA seems simple enough but it fails consistently and I really can't figure out why. The logfiles don't provide a lot of information that speaks to me. I double checked the known bug (of older versions) to make sure there is a description set for the disks associated with the VM. I also tried to look in the Ansible logs referenced below but no such log exists. I've also tried multiple different paths for the output. All with the same failure. Below you can see I am attempting to export to /tmp/. Here is the output of the engine logs: > > ###### engine.log ###### > > 2019-12-03 11:15:43,320-08 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3785977) [d25a398d-f650-4911-ae2a-2ca2b54e8396] EVENT_ID: IMPORTEXPORT_STARTING_EXPORT_VM_TO_OVA(1,223), Starting to export Vm GRAYLOG as a Virtual Appliance > 2019-12-03 11:15:43,916-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:15:43,923-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'default' is using 0 threads out of 1 and 5 tasks are waiting in the queue. > 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engine' is using 0 threads out of 500, 9 threads waiting for tasks and 0 tasks in queue. > 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engineScheduled' is using 0 threads out of 100 and 100 tasks are waiting in the queue. > 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engineThreadMonitoring' is using 1 threads out of 1 and 0 tasks are waiting in the queue. > 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'hostUpdatesChecker' is using 0 threads out of 5 and 5 tasks are waiting in the queue. > 2019-12-03 11:15:45,979-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:15:45,988-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:15:46,882-08 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now > 2019-12-03 11:15:46,893-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] SPMAsyncTask::PollTask: Polling task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'running'. > 2019-12-03 11:15:46,893-08 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Finished polling Tasks, will poll again in 10 seconds. > 2019-12-03 11:15:50,059-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:15:50,064-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:15:58,074-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:15:58,080-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:16:08,138-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:16:08,144-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:16:18,219-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:16:18,227-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:16:28,297-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:16:28,304-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:16:38,371-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:16:38,377-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:16:48,389-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:16:48,394-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:16:58,406-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:16:58,412-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:17:08,423-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:17:08,429-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:17:18,442-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:17:18,449-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:17:28,461-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:17:28,466-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:17:38,476-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:17:38,481-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:17:48,492-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-69) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:17:48,499-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-69) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:17:58,509-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:17:58,515-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:18:08,577-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-68) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:18:08,582-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-68) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:18:18,651-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:18:18,657-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:18:28,723-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:18:28,728-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:18:38,739-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:18:38,744-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:18:48,754-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:18:48,759-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:18:58,821-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-51) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:18:58,826-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-51) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:19:08,889-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-79) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:19:08,894-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-79) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:19:18,906-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:19:18,911-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:19:28,925-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:19:28,932-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:19:38,945-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:19:38,952-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:19:48,962-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:19:48,967-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:19:58,978-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-52) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:19:58,983-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-52) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:20:09,063-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-8) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:20:09,068-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-8) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:20:19,154-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-32) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:20:19,159-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-32) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:20:29,169-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-9) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:20:29,174-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-9) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:20:39,184-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:20:39,189-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:20:49,199-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:20:49,205-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:20:59,217-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:20:59,222-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:21:09,233-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:21:09,239-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:21:19,254-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:21:19,260-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:21:29,324-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:21:29,332-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:21:39,341-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:21:39,347-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:21:49,413-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:21:49,418-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:21:59,429-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:21:59,434-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:22:09,497-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-17) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:22:09,502-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-17) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:22:19,568-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:22:19,573-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:22:29,583-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:22:29,589-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:22:39,600-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:22:39,606-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:22:49,616-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:22:49,621-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:22:59,632-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-53) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:22:59,638-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-53) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:23:09,648-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:23:09,653-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:23:19,663-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:23:19,669-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:23:29,679-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:23:29,684-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:23:39,694-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:23:39,699-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:23:49,712-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:23:49,719-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:23:59,781-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-4) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:23:59,786-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-4) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete > 2019-12-03 11:24:07,476-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] SPMAsyncTask::PollTask: Polling task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'success'. > 2019-12-03 11:24:07,479-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] BaseAsyncTask::onTaskEndSuccess: Task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. > 2019-12-03 11:24:07,479-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] CommandAsyncTask::endActionIfNecessary: All tasks of command '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' has ended -> executing 'endAction' > 2019-12-03 11:24:07,479-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247'): calling endAction '. > 2019-12-03 11:24:07,480-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'CopyImageGroup', > 2019-12-03 11:24:07,492-08 INFO [org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command [id=0e3e3df9-73f5-4ca2-b592-0b9ce7371247]: Updating status to 'SUCCEEDED', The command end method logic will be executed by one of its parent commands. > 2019-12-03 11:24:07,492-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CopyImageGroup' completed, handling the result. > 2019-12-03 11:24:07,493-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CopyImageGroup' succeeded, clearing tasks. > 2019-12-03 11:24:07,493-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fe1a173f-869c-4522-9984-9c57bace7c87' > 2019-12-03 11:24:07,496-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', ignoreFailoverLimit='false', taskId='fe1a173f-869c-4522-9984-9c57bace7c87'}), log id: 693daae4 > 2019-12-03 11:24:07,498-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, HSMClearTaskVDSCommand(HostName = KVMCLST1A, HSMTaskGuidBaseVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', taskId='fe1a173f-869c-4522-9984-9c57bace7c87'}), log id: 3d8ab113 > 2019-12-03 11:24:07,514-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, HSMClearTaskVDSCommand, log id: 3d8ab113 > 2019-12-03 11:24:07,514-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, SPMClearTaskVDSCommand, log id: 693daae4 > 2019-12-03 11:24:07,517-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] BaseAsyncTask::removeTaskFromDB: Removed task 'fe1a173f-869c-4522-9984-9c57bace7c87' from DataBase > 2019-12-03 11:24:07,517-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' > 2019-12-03 11:24:09,852-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete > 2019-12-03 11:24:09,858-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' child commands '[0e3e3df9-73f5-4ca2-b592-0b9ce7371247]' executions were completed, status 'SUCCEEDED' > 2019-12-03 11:24:10,867-08 INFO [org.ovirt.engine.core.bll.storage.disk.CreateAllOvaDisksCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Ending command 'org.ovirt.engine.core.bll.storage.disk.CreateAllOvaDisksCommand' successfully. > 2019-12-03 11:24:10,877-08 INFO [org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand' successfully. > 2019-12-03 11:24:10,887-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, GetImageInfoVDSCommand( GetImageInfoVDSCommandParameters:{storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', ignoreFailoverLimit='false', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 4ba602b2 > 2019-12-03 11:24:10,890-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, GetVolumeInfoVDSCommand(HostName = KVMCLST1A, GetVolumeInfoVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 2524e570 > 2019-12-03 11:24:10,914-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@4c8c88fe, log id: 2524e570 > 2019-12-03 11:24:10,914-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, GetImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@4c8c88fe, log id: 4ba602b2 > 2019-12-03 11:24:10,988-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, PrepareImageVDSCommand(HostName = KVMCLST1A, PrepareImageVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b'}), log id: 11dbdafe > 2019-12-03 11:24:11,010-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, PrepareImageVDSCommand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 11dbdafe > 2019-12-03 11:24:11,014-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetQemuImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, GetQemuImageInfoVDSCommand(HostName = KVMCLST1A, GetVolumeInfoVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 79697ffd > 2019-12-03 11:24:11,221-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetQemuImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, GetQemuImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.QemuImageInfo@5f543b3b, log id: 79697ffd > 2019-12-03 11:24:11,226-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, TeardownImageVDSCommand(HostName = KVMCLST1A, ImageActionsVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b'}), log id: 1f4cb783 > 2019-12-03 11:24:11,230-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, TeardownImageVDSCommand, return: StatusReturn:{status='Status [code=0, message=Done]'}, log id: 1f4cb783 > 2019-12-03 11:24:12,266-08 INFO [org.ovirt.engine.core.bll.CreateOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Running command: CreateOvaCommand internal: true. > 2019-12-03 11:24:12,271-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] START, PrepareImageVDSCommand(HostName = KVMCLST1A, PrepareImageVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b'}), log id: 6e612ef8 > 2019-12-03 11:24:12,294-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] FINISH, PrepareImageVDSCommand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 6e612ef8 > 2019-12-03 11:24:12,301-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] START, GetVolumeInfoVDSCommand(HostName = KVMCLST1A, GetVolumeInfoVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 648e4c38 > 2019-12-03 11:24:12,321-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@4c8c88fe, log id: 648e4c38 > 2019-12-03 11:24:12,332-08 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Executing Ansible command: [/usr/bin/ansible-playbook, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory830646465207814253, --extra-vars=target_directory=/tmp, --extra-vars=ova_name=GRAYLOG.ova, --extra-vars=ovirt_ova_pack_ovf='<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?><ovf:Envelope xmlns:ovf=\\\"http://schemas.dmtf.org/ovf/envelope/1\\\" xmlns:rasd=\\\"http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSet…" xmlns:vssd=\\\"http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingD…" xmlns:xsi=\\\"http://www.w3.org/2001/XMLSchema-instance\\\" xmlns=\\\"http://schemas.dmtf.org/ovf/envelope/1\\\" xmlns:ovirt=\\\"http://www.ovirt.org/ovf\\\"><References><File ovf:href=\\\"2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9\\\" ovf:id=\\\"2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9\\\" ovf:size=\\\"3448045568\\\"></File></References><NetworkSection><Info>List of networks</Info><Network ovf:name=\\\"net_HOME\\\"></Network></NetworkSection><DiskSection><Info>List of Virtual Disks</Info><Disk ovf:diskId=\\\"a1b75b90-04c8-4f8d-899e-7d0354e36b09\\\" ovf:capacity=\\\"100\\\" ovf:capacityAllocationUnits=\\\"byte * 2^30\\\" ovf:populatedSize=\\\"3448045568\\\" ovf:parentRef=\\\"\\\" ovf:fileRef=\\\"2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9\\\" ovf:format=\\\"http://www.gnome.org/~markmc/qcow-image-format.html\\\" ovf:volume-format=\\\"COW\\\" ovf:volume-type=\\\"Sparse\\\" ovf:disk-interface=\\\"VirtIO_SCSI\\\" ovf:boot=\\\"true\\\" ovf:pass-discard=\\\"false\\\" ovf:disk-alias=\\\"GRAYLOG_Disk1\\\" ovf:disk-description=\\\"GRAYLOG_Disk1\\\" ovf:wipe-after-delete=\\\"false\\\" ovf:description=\\\"Active VM\\\" ovf:disk_storage_type=\\\"IMAGE\\\" ovf:cinder_volume_type=\\\"\\\"></Disk></DiskSection><VirtualSystem ovf:id=\\\"aecb985a-450a-43f1-957a-09776aa48899\\\"><Name>GRAYLOG</Name><Description>GrayLog looging system</Description><CreationDate>2018/01/27 23:20:25</CreationDate><ExportDate>2019/12/03 19:24:12</ExportDate><DeleteProtected>false</DeleteProtected><SsoMethod>guest_agent</SsoMethod><IsSmartcardEnabled>false</IsSmartcardEnabled><TimeZone>Etc/GMT</TimeZone><default_boot_sequence>9</default_boot_sequence><Generation>66</Generation><ClusterCompatibilityVersion>4.2</ClusterCompatibilityVersion><VmType>1</VmType><ResumeBehavior>AUTO_RESUME</ResumeBehavior><MinAllocatedMem>4096</MinAllocatedMem><IsStateless>false</IsStateless><IsRunAndPause>false</IsRunAndPause><AutoStartup>true</AutoStartup><Priority>1</Priority><CreatedByUserId>5a655cbf-012a-0161-03dc-000000000307</CreatedByUserId><VmInit ovf:regenerateKeys=\\\"false\\\" ovf:networks=\\\"[ ]\\\"></VmInit><MigrationSupport>0</MigrationSupport><IsBootMenuEnabled>true</IsBootMenuEnabled><IsSpiceFileTransferEnabled>true</IsSpiceFileTransferEnabled><IsSpiceCopyPasteEnabled>true</IsSpiceCopyPasteEnabled><AllowConsoleReconnect>true</AllowConsoleReconnect><ConsoleDisconnectAction>LOCK_SCREEN</ConsoleDisconnectAction><CustomEmulatedMachine></CustomEmulatedMachine><CustomCpuName></CustomCpuName><PredefinedProperties></PredefinedProperties><UserDefinedProperties></UserDefinedProperties><MaxMemorySizeMb>16384</MaxMemorySizeMb><TemplateId>00000000-0000-0000-0000-000000000000</TemplateId><TemplateName>Blank</TemplateName><IsInitilized>true</IsInitilized><Origin>3</Origin><app_list>kernel-3.10.0-693.17.1.el7,ovirt-guest-agent-common-1.0.13-2.el7,kernel-3.10.0-693.el7</app_list><quota_id>5b0590e8-9611-4240-abdc-07cd4bbaed1f</quota_id><DefaultDisplayType>1</DefaultDisplayType><TrustedService>false</TrustedService><OriginalTemplateId>00000000-0000-0000-0000-000000000000</OriginalTemplateId><OriginalTemplateName>Blank</OriginalTemplateName><UseHostCpu>false</UseHostCpu><UseLatestVersion>false</UseLatestVersion><StopTime>2019/12/03 18:44:44</StopTime><OperatingSystemSection ovf:id=\\\"80\\\" ovirt:id=\\\"24\\\" ovf:required=\\\"false\\\"><Info>Guest Operating System</Info><Description>Red Hat Enterprise Linux 7.x x64</Description></OperatingSystemSection><VirtualHardwareSection><Info>2 CPU, 4096 Memory</Info><System><vssd:VirtualSystemType>ENGINE 4.1.0.0</vssd:VirtualSystemType></System><Item><rasd:Caption>2 virtual cpu</rasd:Caption><rasd:Description>Number of virtual CPU</rasd:Description><rasd:InstanceId>1</rasd:InstanceId><rasd:ResourceType>3</rasd:ResourceType><rasd:num_of_sockets>2</rasd:num_of_sockets><rasd:cpu_per_socket>1</rasd:cpu_per_socket><rasd:threads_per_cpu>1</rasd:threads_per_cpu><rasd:max_num_of_vcpus>16</rasd:max_num_of_vcpus><rasd:VirtualQuantity>2</rasd:VirtualQuantity></Item><Item><rasd:Caption>4096 MB of memory</rasd:Caption><rasd:Description>Memory Size</rasd:Description><rasd:InstanceId>2</rasd:InstanceId><rasd:ResourceType>4</rasd:ResourceType><rasd:AllocationUnits>MegaBytes</rasd:AllocationUnits><rasd:VirtualQuantity>4096</rasd:VirtualQuantity></Item><Item><rasd:Caption>GRAYLOG_Disk1</rasd:Caption><rasd:InstanceId>2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9</rasd:InstanceId><rasd:ResourceType>17</rasd:ResourceType><rasd:HostResource>ovf:disk/a1b75b90-04c8-4f8d-899e-7d0354e36b09</rasd:HostResource><rasd:Parent>00000000-0000-0000-0000-000000000000</rasd:Parent><rasd:Template>00000000-0000-0000-0000-000000000000</rasd:Template><rasd:ApplicationList></rasd:ApplicationList><rasd:StorageId>c79208ed-8753-4ded-a137-8f08dfff5a40</rasd:StorageId><rasd:StoragePoolId>7bb7ac30-0406-4fbf-802f-57b1a575383f</rasd:StoragePoolId><rasd:CreationDate>2019/12/03 19:15:38</rasd:CreationDate><rasd:LastModified>2019/12/03 19:15:38</rasd:LastModified><rasd:last_modified_date>2019/12/03 19:15:38</rasd:last_modified_date><Type>disk</Type><Device>disk</Device><rasd:Address>{type=drive, bus=0, controller=0, target=0, unit=0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>scsi0-0-0-0</Alias></Item><Item><rasd:Caption>Ethernet adapter on net_HOME</rasd:Caption><rasd:InstanceId>4adaa616-f98b-4e1f-b60f-14156665e344</rasd:InstanceId><rasd:ResourceType>10</rasd:ResourceType><rasd:OtherResourceType>net_HOME</rasd:OtherResourceType><rasd:ResourceSubType>3</rasd:ResourceSubType><rasd:Connection>net_HOME</rasd:Connection><rasd:Linked>true</rasd:Linked><rasd:Name>nic1</rasd:Name><rasd:ElementName>nic1</rasd:ElementName><rasd:MACAddress>00:1a:4a:16:01:04</rasd:MACAddress><rasd:speed>1000</rasd:speed><Type>interface</Type><Device>bridge</Device><rasd:Address>{type=pci, slot=0x03, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>net0</Alias></Item><Item><rasd:Caption>USB Controller</rasd:Caption><rasd:InstanceId>3</rasd:InstanceId><rasd:ResourceType>23</rasd:ResourceType><rasd:UsbPolicy>DISABLED</rasd:UsbPolicy></Item><Item><rasd:Caption>Graphical Controller</rasd:Caption><rasd:InstanceId>585fc912-16d6-421d-acda-eeaa17b955c1</rasd:InstanceId><rasd:ResourceType>20</rasd:ResourceType><rasd:VirtualQuantity>1</rasd:VirtualQuantity><rasd:SinglePciQxl>false</rasd:SinglePciQxl><Type>video</Type><Device>qxl</Device><rasd:Address>{type=pci, slot=0x02, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>video0</Alias><SpecParams><vgamem>16384</vgamem><heads>1</heads><vram>32768</vram><ram>65536</ram></SpecParams></Item><Item><rasd:Caption>Graphical Framebuffer</rasd:Caption><rasd:InstanceId>8c56ce64-dc7b-4a05-995a-eba2f31997fe</rasd:InstanceId><rasd:ResourceType>26</rasd:ResourceType><Type>graphics</Type><Device>spice</Device><rasd:Address></rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias></Alias></Item><Item><rasd:Caption>Graphical Framebuffer</rasd:Caption><rasd:InstanceId>ecfe54b9-26f1-4f44-9745-50cc45c9d50e</rasd:InstanceId><rasd:ResourceType>26</rasd:ResourceType><Type>graphics</Type><Device>vnc</Device><rasd:Address></rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias></Alias></Item><Item><rasd:Caption>CDROM</rasd:Caption><rasd:InstanceId>922be48e-a7ef-4490-8a46-df6d09d30aab</rasd:InstanceId><rasd:ResourceType>15</rasd:ResourceType><Type>disk</Type><Device>cdrom</Device><rasd:Address>{type=drive, bus=1, controller=0, target=0, unit=0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>true</IsReadOnly><Alias>ide0-1-0</Alias><SpecParams><path>CentOS-7-x86_64-NetInstall-1708.iso</path></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>e4f99c78-0a99-4b36-a3da-34e9267c9d59</rasd:InstanceId><Type>channel</Type><Device>spicevmc</Device><rasd:Address>{type=virtio-serial, bus=0, controller=0, port=3}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>channel2</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>0307995b-613a-4819-b667-4c077880eca9</rasd:InstanceId><Type>controller</Type><Device>ide</Device><rasd:Address>{type=pci, slot=0x01, bus=0x00, domain=0x0000, function=0x1}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>ide</Alias><SpecParams><index>0</index></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>0cc781c0-18c8-4096-8ab5-062eb51b1ef9</rasd:InstanceId><Type>channel</Type><Device>unix</Device><rasd:Address>{type=virtio-serial, bus=0, controller=0, port=1}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>channel0</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>55a35000-8756-45e5-89e6-32c914b1ef75</rasd:InstanceId><Type>channel</Type><Device>unix</Device><rasd:Address>{type=virtio-serial, bus=0, controller=0, port=2}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>channel1</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>c4cc5f36-26c3-4f1e-9a40-7cb1a4c28025</rasd:InstanceId><Type>controller</Type><Device>virtio-serial</Device><rasd:Address>{type=pci, slot=0x05, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>virtio-serial0</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>d64ea1bd-cf70-4786-9bfd-80121e30cbdf</rasd:InstanceId><Type>controller</Type><Device>usb</Device><rasd:Address>{type=pci, slot=0x01, bus=0x00, domain=0x0000, function=0x2}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>usb</Alias><SpecParams><index>0</index><model>piix3-uhci</model></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>2b5977d2-133d-4180-98b8-e96ab5401a0f</rasd:InstanceId><Type>rng</Type><Device>virtio</Device><rasd:Address>{type=pci, slot=0x06, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>rng0</Alias><SpecParams><source>urandom</source></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>f0c7a69b-6cd6-4428-84bf-5e862cb20202</rasd:InstanceId><Type>controller</Type><Device>virtio-scsi</Device><rasd:Address>{type=pci, slot=0x04, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>scsi0</Alias></Item></VirtualHardwareSection></VirtualSystem></ovf:Envelope>', --extra-vars=ovirt_ova_pack_disks=/rhev/data-center/mnt/10.25.0.11:_mnt_vol01_kvmclst1_vmstore/c79208ed-8753-4ded-a137-8f08dfff5a40/images/a1b75b90-04c8-4f8d-899e-7d0354e36b09/2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9::3448045568, /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml] [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20191203112412-kvmclst1a.home.whootis.com-67d3d8f2.log] > 2019-12-03 11:24:22,637-08 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Ansible playbook command has exited with value: 2 > 2019-12-03 11:24:22,638-08 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Failed to create OVA. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20191203112412-kvmclst1a.home.whootis.com-67d3d8f2.log > 2019-12-03 11:24:22,640-08 ERROR [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Failed to create OVA file > 2019-12-03 11:24:22,640-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Command 'ExportOva' id: 'd684210f-56b3-41ba-a699-e93341afdba2' failed when attempting to perform the next operation, marking as FAILED '[ef1b7dde-5908-4f1f-9d0a-228bf234d9fa]' > 2019-12-03 11:24:22,640-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Command 'ExportOva' id: 'd684210f-56b3-41ba-a699-e93341afdba2' child commands '[ef1b7dde-5908-4f1f-9d0a-228bf234d9fa]' executions were completed, status 'FAILED' > 2019-12-03 11:24:23,655-08 ERROR [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Ending command 'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure. > 2019-12-03 11:24:23,657-08 INFO [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Lock freed to object 'EngineLock:{exclusiveLocks='[aecb985a-450a-43f1-957a-09776aa48899=VM]', sharedLocks=''}' > 2019-12-03 11:24:23,667-08 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [d25a398d-f650-4911-ae2a-2ca2b54e8396] EVENT_ID: IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm GRAYLOG as a Virtual Appliance to path /tmp/GRAYLOG.ova on Host KVMCLST1A > > > Thanks for any help you can be! > -Geoff > >

1 0

Windows Sluggish Performance
by Vijay Sachdeva 03 Dec '19

03 Dec '19

Hello Everyone, I managed to install Windows Server 2016 server on Ovirt node using ovirt engine.All virtio-Win drivers also installed, but the performance of Windows using console is very sluggish and mouse pointer is not at all responsive. Can anyone let me know, what could be the reason. Not able to to even add IP to VM as mouse doesn’t work at all. Thanks

3 3

Re: Scenario: Ovirt-engine on hardware and recovery
by Jayme 03 Dec '19

03 Dec '19

Take a look at vProtect for backups. Works really well for our environment, and supports incremental backups as well which is very handy. It's free for up to 10 VMs to try. On Tue, Dec 3, 2019 at 4:20 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > Didi, > > Thanks for the reply. > > Yes, backups are done, I am just thinking in the case of Murphy's Law > where nothing works and the engine is gone. I am also new to oVirt and am > always loking for the "proper" backup method as you have laready mentioned > using engine-backup. > > Storage is NFS backed and backups are done in case of storage server > failure. > > What is the preferred VM backup method so both disk and VM config is > captured? Would rather not have to put agents on all the VM for OS level > backups and then have to manually recreate all of the machines. Do all the > VM configs get stored on the shared storage just like one of the other > virtualization vendors? > > Appreciate the time from folks on the list who respond. > ------------------------------ > *From:* Yedidyah Bar David <didi(a)redhat.com> > *Sent:* Tuesday, December 3, 2019 3:29 AM > *To:* Robert Webb <rwebb(a)ropeguru.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Scenario: Ovirt-engine on hardware and > recovery > > On Tue, Dec 3, 2019 at 4:38 AM <rwebb(a)ropeguru.com> wrote: > > > > So thinking about my setup, I am thinking through different failure > scenarios. > > > > So lets say I have a small physical server with 8 cores and 16GB RAM and > I install Centos 7 and ovirt-engine on bare metal. This would also be the > same scenario is the engine were on a VM. > > > > I run into a major hardware issue and completely lose the engine. > > You do take backups, right? :-) > > For the engine itself, you can use engine-backup. > > > > > How does one recover the cluster setup and not have to start from > scratch by having to rebuild all the nodes? Can the engine just be rebuilt > and the ovirt nodes be imported? > > You didn't mention your plans re storage. > > If you put your VMs on well-handled storage, and lose everything but > the storage, you can install a new engine, new nodes, and then import > the VMs from the existing storage. You will still miss some > configuration etc., but should mostly be ok. > > If you plan to use gluster storage using the same nodes, aka HCI, the > same applies, obviously, only that the nodes are your storage, and not > an external system. You still have to make sure you handle them > properly - backup, DR, etc., depending on your needs and budget. > > If you do have engine-backup backups, but lost all your storage, > engine-backup will not help you. > > > > > > This scenario is based on the nodes being built from the ovirt node iso. > > That's ok, but is not relevant. Main question is the storage. Can be > external or local/gluster with either ovirt-node or EL. > > Good luck, > > -- > Didi > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/M2URCFAZJQYCE… >

1 0

Re: Windows VirtIO drivers
by Vijay Sachdeva 03 Dec '19

03 Dec '19

Anyone, please let me know. Really stuck at this point. I am using Ovirt Manager 4.3 and while installing Windows VMs If I used disk type as IDE, I can see the disks to install the OS but if I use virtIO-scsi for disks the disk is not seen. So I attached floppy disk to VM, but it says no drivers detected. Can anyone let me know the best way to install Windows 2016? Thanks Vijay Sachdeva From: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> Date: Tuesday, 3 December 2019 at 6:56 PM To: Gal Zaidman <gzaidman(a)redhat.com>, <users(a)ovirt.org> Subject: Re: [ovirt-users] Windows VirtIO drivers Hi Gal, I have downloaded the virtio-win_x86.vfd and uploaded to ISO domain. Used Run Once and attached the floppy drive, while looking for drivers in A drive it gives below error: I followed all the steps as per the guidelines shared in the document. Don’t know what I am missing. Thanks Vijay Sachdeva From: Gal Zaidman <gzaidman(a)redhat.com> Date: Tuesday, 3 December 2019 at 6:44 PM To: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com>, <users(a)ovirt.org> Subject: Re: [ovirt-users] Windows VirtIO drivers Going back to the user list, just in case it will be relevant to others On Tue, Dec 3, 2019 at 3:02 PM Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: Hi Gal, Thank you so much for replying, can you please a steps to do that. Right now what I am doing is: Installed Windows 2016 using IDE interface, but performance is very bad and it’ really hard to install any further .exe into it. I never used the IDE interface so I can't say from personal experience, but I don't think that should be the behavior, please open a bug on that so that we can examin. Other option I see attaching the floppy drive when we use “Run Once”, but problem is when pointing to floppy drive while loading drivers. It says no drivers detected. Using Run Once is the preferred option, see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… Make sure that you attach the latest virtio-win vdf (the link I sent earlier should be ok) and select the relevant drivers, if there is a problem then please open a bug on virtio-win project and send me the url so I will track it, thanks. Please share let me know the best way to perform this action as need to deliver the Ovirt infra to one of my customer and really stuck on this driver installation. Appreciate your quick response.!! Vijay Sachdeva From: Gal Zaidman <gzaidman(a)redhat.com> Date: Tuesday, 3 December 2019 at 6:22 PM To: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> Subject: Re: [ovirt-users] Windows VirtIO drivers HI Vijay, There a package on fedora: virtio-win-0.1.173-2 which contains an MSI installer for the drivers and the ovirt agent (which is disabled on a normal installation, so please enable it when you install). This installer should replace the ovirt-wgt that we have currently on the next versions, and it is new, so please give us feedback once you used it. P.S the installer installs the drivers normally so if the regular drivers from virtio-win fail to install, then using the installer will not change much probably, and it means that you have a deeper problem. In case the installation fails then please generate logs but running the installer through cmd.exe "msiexec /i {installer} /l*v {path to log}" (https://www.advancedinstaller.com/user-guide/qa-log.html) and open a bug/reply here and I will try and help Thanks On Tue, Dec 3, 2019 at 2:11 PM Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: Dear Team, How can we install virtIO windows drivers to Windows 2016. As of now I tried to attach floppy drive with virtio-win.vfd image but while installing drivers didn’t get loaded. Please guide or let me know the proper way to install drivers. Vijay Sachdeva _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XBYY54K62BYJ…

2 2

Zabbix monitoring within the node
by Vinícius Ferrão 03 Dec '19

03 Dec '19

Hello, There are some documentation on the web about using Zabbix with oVirt to monitor the hypervisor itself like here: https://github.com/hudecof/libzbxovirt and here: https://github.com/jensdepuydt/zabbix-ovirt But what are you ppl doing about this issue? Any recommendations on Zabbix monitoring with oVirt Node? Should I use the Zabbix Agent as a package or use SNMP instead? Thanks,

1 0

Re: Windows VirtIO drivers
by Vijay Sachdeva 03 Dec '19

03 Dec '19

Hi Gal, I have downloaded the virtio-win_x86.vfd and uploaded to ISO domain. Used Run Once and attached the floppy drive, while looking for drivers in A drive it gives below error: I followed all the steps as per the guidelines shared in the document. Don’t know what I am missing. Thanks Vijay Sachdeva From: Gal Zaidman <gzaidman(a)redhat.com> Date: Tuesday, 3 December 2019 at 6:44 PM To: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com>, <users(a)ovirt.org> Subject: Re: [ovirt-users] Windows VirtIO drivers Going back to the user list, just in case it will be relevant to others On Tue, Dec 3, 2019 at 3:02 PM Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: Hi Gal, Thank you so much for replying, can you please a steps to do that. Right now what I am doing is: Installed Windows 2016 using IDE interface, but performance is very bad and it’ really hard to install any further .exe into it. I never used the IDE interface so I can't say from personal experience, but I don't think that should be the behavior, please open a bug on that so that we can examin. Other option I see attaching the floppy drive when we use “Run Once”, but problem is when pointing to floppy drive while loading drivers. It says no drivers detected. Using Run Once is the preferred option, see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… Make sure that you attach the latest virtio-win vdf (the link I sent earlier should be ok) and select the relevant drivers, if there is a problem then please open a bug on virtio-win project and send me the url so I will track it, thanks. Please share let me know the best way to perform this action as need to deliver the Ovirt infra to one of my customer and really stuck on this driver installation. Appreciate your quick response.!! Vijay Sachdeva From: Gal Zaidman <gzaidman(a)redhat.com> Date: Tuesday, 3 December 2019 at 6:22 PM To: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> Subject: Re: [ovirt-users] Windows VirtIO drivers HI Vijay, There a package on fedora: virtio-win-0.1.173-2 which contains an MSI installer for the drivers and the ovirt agent (which is disabled on a normal installation, so please enable it when you install). This installer should replace the ovirt-wgt that we have currently on the next versions, and it is new, so please give us feedback once you used it. P.S the installer installs the drivers normally so if the regular drivers from virtio-win fail to install, then using the installer will not change much probably, and it means that you have a deeper problem. In case the installation fails then please generate logs but running the installer through cmd.exe "msiexec /i {installer} /l*v {path to log}" (https://www.advancedinstaller.com/user-guide/qa-log.html) and open a bug/reply here and I will try and help Thanks On Tue, Dec 3, 2019 at 2:11 PM Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: Dear Team, How can we install virtIO windows drivers to Windows 2016. As of now I tried to attach floppy drive with virtio-win.vfd image but while installing drivers didn’t get loaded. Please guide or let me know the proper way to install drivers. Vijay Sachdeva _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XBYY54K62BYJ…

2 1

Sigh... still vdsmd memory leak
by Chris Adams 03 Dec '19

03 Dec '19

I've seen vdsmd leak memory (RSS increasing) for a while, and never gotten anywhere with diagnosing it. I upgraded a small setup (2 hosts with hosted engine and iSCSI SAN) last week to 4.3.7 plus latest CentOS 7.7 updates, and I am still seeing this. Currently, there are only 3 active VMs, plus the engine, all running on one of the two node (which is also the SPM), and vdsmd on that node is up to 450M RSS (6 days after upgrading), which is up almost 100M in the last 24 hours. On the other node, vdsmd RSS has not changed in the last 24 hours (83M). I have a script watching the RSS on the growing node, and it's a pretty steady increase: 07:59:59.735 452080 +28 08:00:03.361 452104 +24 08:00:04.852 452112 +8 08:00:21.088 452116 +4 08:00:25.456 452120 +4 08:00:25.753 452124 +4 08:00:34.219 452132 +8 08:00:35.866 452136 +4 08:00:44.360 452140 +4 08:00:51.213 452144 +4 08:00:57.046 452152 +8 08:00:59.855 452160 +8 08:01:01.461 452164 +4 08:01:04.615 452168 +4 08:01:10.544 452172 +4 08:01:11.003 452180 +8 08:01:13.826 452184 +4 08:01:14.737 452188 +4 08:01:15.002 452192 +4 08:01:21.350 452196 +4 08:01:29.870 452200 +4 08:01:34.995 452208 +8 This is a problem I have in multiple oVirt setups - don't know if it is just something about how I installed or what, but I'd really like to work on getting this figured out and fixed. -- Chris Adams <cma(a)cmadams.net>

1 0

Scenario: Ovirt-engine on hardware and recovery
by rwebb＠ropeguru.com 03 Dec '19

03 Dec '19

So thinking about my setup, I am thinking through different failure scenarios. So lets say I have a small physical server with 8 cores and 16GB RAM and I install Centos 7 and ovirt-engine on bare metal. This would also be the same scenario is the engine were on a VM. I run into a major hardware issue and completely lose the engine. How does one recover the cluster setup and not have to start from scratch by having to rebuild all the nodes? Can the engine just be rebuilt and the ovirt nodes be imported? This scenario is based on the nodes being built from the ovirt node iso.

3 2

Re: Windows VirtIO drivers
by Gal Zaidman 03 Dec '19

03 Dec '19

Going back to the user list, just in case it will be relevant to others On Tue, Dec 3, 2019 at 3:02 PM Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: > Hi Gal, > > > > Thank you so much for replying, can you please a steps to do that. Right > now what I am doing is: > > > > 1. Installed Windows 2016 using IDE interface, but performance is very > bad and it’ really hard to install any further .exe into it. > > I never used the IDE interface so I can't say from personal experience, but I don't think that should be the behavior, please open a bug on that so that we can examin. > > 1. > 2. Other option I see attaching the floppy drive when we use “Run > Once”, but problem is when pointing to floppy drive while loading drivers. > It says no drivers detected. > > Using Run Once is the preferred option, see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… Make sure that you attach the latest virtio-win vdf (the link I sent earlier should be ok) and select the relevant drivers, if there is a problem then please open a bug on virtio-win project and send me the url so I will track it, thanks. > > > Please share let me know the best way to perform this action as need to > deliver the Ovirt infra to one of my customer and really stuck on this > driver installation. > > > > Appreciate your quick response.!! > > > > Vijay Sachdeva > > > > > > *From: *Gal Zaidman <gzaidman(a)redhat.com> > *Date: *Tuesday, 3 December 2019 at 6:22 PM > *To: *Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> > *Subject: *Re: [ovirt-users] Windows VirtIO drivers > > > > HI Vijay, > > > > There a package on fedora: > > virtio-win-0.1.173-2 > > which contains an MSI installer for the drivers and the ovirt agent (which > is disabled on a normal installation, so please enable it when you install). > > > > This installer should replace the ovirt-wgt that we have currently on the > next versions, > > and it is new, so please give us feedback once you used it. > > > > P.S > > the installer installs the drivers normally so if the regular drivers from > virtio-win fail to install, then using the installer will not change much > probably, and it means that you have a deeper problem. > > In case the installation fails then please generate logs but running the > installer through cmd.exe "msiexec /i {installer} /l*v {path to log}" ( > https://www.advancedinstaller.com/user-guide/qa-log.html) > > and open a bug/reply here and I will try and help > > > > Thanks > > > > On Tue, Dec 3, 2019 at 2:11 PM Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> > wrote: > > Dear Team, > > > > How can we install virtIO windows drivers to Windows 2016. As of now I > tried to attach floppy drive with virtio-win.vfd image but while installing > drivers didn’t get loaded. > > > > Please guide or let me know the proper way to install drivers. > > > > > > Vijay Sachdeva > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XBYY54K62BYJ… > >

1 0