July 2019 - Users - oVirt List Archives

Re: VM Migrations Failing
by Strahil 11 Jul '19

11 Jul '19

Power down the VM and reduce the memory a little bit but keep the maximum memory value the same or larger. Then power it up and extend the ram to the same value the VM had. It's a wild guess... So don't expect miracles. Best Regards, Strahil NikolovOn Jul 10, 2019 18:21, Michael Watters <wattersm(a)watters.ws> wrote: > > I need to migrate running VMs from one host in our cluster to another > however the task keeps failing any time I start a migration. The engine > logs show a few different errors as follows. > > 2019-07-10 09:53:19,440-04 ERROR > [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] > (ForkJoinPool-1-worker-2) [] Migration of VM 'vm1' to host > 'ovirt-node-production3' failed: VM destroyed during the startup. > > 2019-07-10 09:53:06,542-04 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-51) [c1daf639-ff39-4397-b1bf-09426cacf72d] EVENT_ID: > VM_MIGRATION_FAILED(65), Migration failed due to a failed validation: > [Cannot migrate VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host ovirt-node-production3 did > not satisfy internal filter Memory.] (VM: vm2, Source: > ovirt-node-production2). > > I also checked the vdsm.log on the destination host which is showing an > error like this. > > ERROR (jsonrpc/2) [virt.vm] > (vmId='f5bb25a8-3176-40b6-b21b-f07ed1089b27') Alias not found for device > type balloon during migration at destination host (vm:5562) > > Does anybody know how to resolve this? The destination host is able to > run VMs and I've been able to move a few VMs by shutting down and doing > a restart however I'd like to do a live migration if possible. > > > > > > _______________________________________________ > 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/AWOTK2Q7OJGJX…

2 1

Manual Migration not working and Dashboard broken after 4.3.4 update
by Neil 11 Jul '19

11 Jul '19

Hi guys. I have two problems since upgrading from 4.2.x to 4.3.4 First issue is I can no longer manually migrate VM's between hosts, I get an error in the ovirt GUI that says "Could not fetch data needed for VM migrate operation" and nothing gets logged either in my engine.log or my vdsm.log Then the other issue is my Dashboard says the following "Error! Could not fetch dashboard data. Please ensure that data warehouse is properly installed and configured." If I look at my ovirt-engine-dwhd.log I see the following if I try restart the dwh service... 2019-07-09 11:48:04|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** 2019-07-09 11:48:10|ETL Service Stopped 2019-07-09 11:49:59|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** 2019-07-09 11:52:56|ETL Service Stopped 2019-07-09 11:52:57|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** 2019-07-09 12:16:01|ETL Service Stopped 2019-07-09 12:16:45|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** I have a hosted engine, and I have two hosts and my storage is FC based. The hosts are still running on 4.2 because I'm unable to migrate VM's off. I have plenty resources available in terms of CPU and Memory on the destination host, and my Cluster version is set to 4.2 because my hosts are still on 4.2 I have recently upgraded from 4.1 to 4.2 and then I upgraded my hosts to 4.2 as well, but I can't get my hosts to 4.3 because of the above migration issue. Below my ovirt packages installed... ovirt-ansible-cluster-upgrade-1.1.13-1.el7.noarch ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.20-1.el7.noarch ovirt-ansible-image-template-1.1.11-1.el7.noarch ovirt-ansible-infra-1.1.12-1.el7.noarch ovirt-ansible-manageiq-1.1.14-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-ansible-roles-1.1.6-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-ansible-vm-infra-1.1.18-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-4.3.4.3-1.el7.noarch ovirt-engine-api-explorer-0.0.5-1.el7.noarch ovirt-engine-backend-4.3.4.3-1.el7.noarch ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch ovirt-engine-dbscripts-4.3.4.3-1.el7.noarch ovirt-engine-dwh-4.3.0-1.el7.noarch ovirt-engine-dwh-setup-4.3.0-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.4.3-1.el7.noarch ovirt-engine-metrics-1.3.3.1-1.el7.noarch ovirt-engine-restapi-4.3.4.3-1.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-engine-setup-4.3.4.3-1.el7.noarch ovirt-engine-setup-base-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-cinderlib-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.3.4.3-1.el7.noarch ovirt-engine-tools-4.3.4.3-1.el7.noarch ovirt-engine-tools-backup-4.3.4.3-1.el7.noarch ovirt-engine-ui-extensions-1.0.5-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.4.3-1.el7.noarch ovirt-engine-webadmin-portal-4.3.4.3-1.el7.noarch ovirt-engine-websocket-proxy-4.3.4.3-1.el7.noarch ovirt-engine-wildfly-15.0.1-1.el7.x86_64 ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch ovirt-guest-agent-common-1.0.16-1.el7.noarch ovirt-guest-tools-iso-4.3-3.el7.noarch ovirt-host-deploy-common-1.8.0-1.el7.noarch ovirt-host-deploy-java-1.8.0-1.el7.noarch ovirt-imageio-common-1.5.1-0.el7.x86_64 ovirt-imageio-proxy-1.5.1-0.el7.noarch ovirt-imageio-proxy-setup-1.5.1-0.el7.noarch ovirt-iso-uploader-4.3.1-1.el7.noarch ovirt-js-dependencies-1.2.0-3.1.el7.centos.noarch ovirt-provider-ovn-1.2.22-1.el7.noarch ovirt-release41-4.1.9-1.el7.centos.noarch ovirt-release42-4.2.8-1.el7.noarch ovirt-release43-4.3.4-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-vmconsole-proxy-1.0.7-2.el7.noarch ovirt-web-ui-1.5.2-1.el7.noarch python2-ovirt-engine-lib-4.3.4.3-1.el7.noarch python2-ovirt-host-deploy-1.8.0-1.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch python-ovirt-engine-sdk4-4.3.1-2.el7.x86_64 [root@dell-ovirt ~]# rpm -qa | grep postgre rh-postgresql10-postgresql-contrib-10.6-1.el7.x86_64 rh-postgresql10-postgresql-10.6-1.el7.x86_64 postgresql-libs-9.2.24-1.el7_5.x86_64 collectd-postgresql-5.8.1-4.el7.x86_64 postgresql-server-9.2.24-1.el7_5.x86_64 rh-postgresql10-postgresql-server-10.6-1.el7.x86_64 rh-postgresql95-postgresql-9.5.14-1.el7.x86_64 rh-postgresql95-postgresql-contrib-9.5.14-1.el7.x86_64 postgresql-jdbc-9.2.1002-6.el7_5.noarch rh-postgresql10-runtime-3.1-1.el7.x86_64 rh-postgresql95-postgresql-libs-9.5.14-1.el7.x86_64 rh-postgresql10-postgresql-libs-10.6-1.el7.x86_64 postgresql-9.2.24-1.el7_5.x86_64 rh-postgresql95-runtime-2.2-2.el7.x86_64 rh-postgresql95-postgresql-server-9.5.14-1.el7.x86_64 I'm also seeing a strange error on my hosts when I log in showing... node status: DEGRADED Please check the status manually using `nodectl check` [root@host-a ~]# nodectl check Status: FAILED Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... FAILED - It looks like the LVM layout is not correct. The reason could be an incorrect installation. Checking available space in thinpool ... OK Checking thinpool auto-extend ... FAILED - In order to enable thinpool auto-extend,activation/thin_pool_autoextend_threshold needs to be set below 100 in lvm.conf vdsmd ... OK I'm running CentOS Linux release 7.6.1810 (Core) These are my package versions on my hosts... [root@host-a ~]# rpm -qa | grep -i ovirt ovirt-release41-4.1.9-1.el7.centos.noarch ovirt-hosted-engine-ha-2.2.19-1.el7.noarch ovirt-host-deploy-1.7.4-1.el7.noarch ovirt-node-ng-nodectl-4.2.0-0.20190121.0.el7.noarch ovirt-vmconsole-host-1.0.6-2.el7.noarch ovirt-provider-ovn-driver-1.2.18-1.el7.noarch ovirt-engine-appliance-4.2-20190121.1.el7.noarch ovirt-release42-4.2.8-1.el7.noarch ovirt-release43-4.3.4-1.el7.noarch python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64 cockpit-ovirt-dashboard-0.11.38-1.el7.noarch ovirt-imageio-daemon-1.4.6-1.el7.noarch ovirt-host-4.2.3-1.el7.x86_64 ovirt-setup-lib-1.1.5-1.el7.noarch ovirt-node-ng-image-update-4.2.8-1.el7.noarch ovirt-imageio-common-1.4.6-1.el7.x86_64 ovirt-vmconsole-1.0.6-2.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-host-dependencies-4.2.3-1.el7.x86_64 ovirt-release-host-node-4.2.8-1.el7.noarch cockpit-machines-ovirt-193-2.el7.noarch ovirt-hosted-engine-setup-2.2.33-1.el7.noarch [root@host-a ~]# rpm -qa | grep -i vdsm vdsm-http-4.20.46-1.el7.noarch vdsm-common-4.20.46-1.el7.noarch vdsm-network-4.20.46-1.el7.x86_64 vdsm-jsonrpc-4.20.46-1.el7.noarch vdsm-4.20.46-1.el7.x86_64 vdsm-hook-ethtool-options-4.20.46-1.el7.noarch vdsm-hook-vhostmd-4.20.46-1.el7.noarch vdsm-python-4.20.46-1.el7.noarch vdsm-api-4.20.46-1.el7.noarch vdsm-yajsonrpc-4.20.46-1.el7.noarch vdsm-hook-fcoe-4.20.46-1.el7.noarch vdsm-hook-openstacknet-4.20.46-1.el7.noarch vdsm-client-4.20.46-1.el7.noarch vdsm-gluster-4.20.46-1.el7.x86_64 vdsm-hook-vmfex-dev-4.20.46-1.el7.noarch I am seeing the following error every minute or so in my vdsm.log as follows.... 2019-07-09 12:50:31,543+0200 WARN (qgapoller/2) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7f52b01b85f0> on ['9a6561b8-5702-43dc-9e92-1dc5dfed4eef'] (periodic:323) Then also under /var/log/messages.. Jul 9 12:57:48 host-a ovs-vsctl: ovs|00001|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) I'm not using ovn so I'm guessing this can be ignored. If I search for ERROR or WARN in my logs nothing relevant is logged Any suggestions on what to start looking for please? Please let me know if you need further info. Thank you. Regards. Neil Wilson

4 9

Re: Impossible to install VM Machine
by Juan Pablo Lorier 10 Jul '19

10 Jul '19

Hi Abdoul, what I don't get right is what is your setup. Ovirt can have data domains that is where you put the vm disks. That domains can be NFS share, gluster bricks, iscsi san or direct disk. When you say files sharing folders, I can't think of a data domain attached there unless it's a NFS local share. Maybe I'm missing something, but I can see that working. Do you have a data domain in storage? I tend to think you have because otherway you can't create the disks for the vms (which you add when you create the vm) Please, replay to the list too so others can see the thread. Regards On 10/7/19 16:51, Abdoul-Rahamane Issoufou Oumarou wrote: > Thank you Juan Pablo, > > Yes indeed I installed everything on one machine. Before I used > ovirt-node and ovirt but it always gave me the same problem. > > I'm going to try again and I'll make you a catch of the mistakes I get. > > Otherwise for storage, I created FILES sharing folders on the ovirt > machine it's them that I use. > > Thank you very much > > Le mer. 10 juil. 2019 à 20:24, Juan Pablo Lorier <jplorier(a)gmail.com > <mailto:jplorier@gmail.com>> a écrit : > > Hi, > > We need more information to try and find the problem. Did you look at > the logs in ovirt-engine? I assume by your description that you ran an > all in one install. What storage are you using? > > Regards >

2 1

Impossible to install VM Machine
by Juan Pablo Lorier 10 Jul '19

10 Jul '19

Hi, We need more information to try and find the problem. Did you look at the logs in ovirt-engine? I assume by your description that you ran an all in one install. What storage are you using? Regards

1 0

Re: iptables with 4.3+?
by Strahil 10 Jul '19

10 Jul '19

Firewalld was deployed in EL7 , because they got plans of getting rid of iptables. With EL8 , we got only emulation of iptables for backward compatibility. Also the integration between NetworkManager.service and firewalld is quite good - which is another reason behind that. Last but not least, in the enterprise almost all systems are with firewalld down and behind hardware-based appliances and keeping the complex filtering away of the systems. Thus firewalld is nice for simple tasks, while complex tasks require nftables ... It makes sense and we have to deal with the changes or get extended support for as long as possible :) Best Regards, Strahil NikolovOn Jul 10, 2019 18:13, Michael Watters <wattersm(a)watters.ws> wrote: > > Same here. Our engine is configured to use iptables and works fine. I > really wish RedHat would stop trying to force firewalld on everything. > It isn't needed and causes issues with environments using the > puppetlabs-firewall module. > > On 7/4/19 3:17 PM, Darrell Budic wrote: > > I’m in the same boat, puppet managing iptables rules, and was able to continue forcing it on my 4.3.x ovirt systems. Engine-setup complains all the time, but so far it hasn’t broken anything. > > > > -Darrell > > > > > >> On Jul 4, 2019, at 9:38 AM, Jordan Conway <jconway(a)linuxfoundation.org> wrote: > >> > >> Hello, > >> I'm working on migrating an existing ovirt setup to a new hosted-engine setup and I've been seeing messages about iptables support being deprecated and slated to be removed. > >> Can I continue using iptables to manage the firewalls on my ovirt hosts if I don't care about allowing ovirt to configure the firewalls? > >> We manage all of our machines with puppet and iptables is deeply integrated into this. It would be non-trivial to migrate to firewalld support. > >> As it stands I already manage the firewall rules for our ovirt hosts with puppet and iptables and have always ignored the "Automatically Configure Firewall" option when adding new hosts. Will this continue to work? > >> > >> Also with hosted engine, I had to cowboy enable firewalld to get the engine installed, but now that I've got a cluster up and running with hosted engine enabled on several hosts, can I just switch back from firewalld to iptables assuming I've got all the correct ports open? > >> > >> Thank you, > >> Jordan Conway > >> _______________________________________________ > >> 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/CFKUWD44EKAOG… > > _______________________________________________ > > 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/7HKXXY6KFVICS… > _______________________________________________ > 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/QBDHDHEC7FNQE…

1 0

VM Migrations Failing
by Michael Watters 10 Jul '19

10 Jul '19

I need to migrate running VMs from one host in our cluster to another however the task keeps failing any time I start a migration. The engine logs show a few different errors as follows. 2019-07-10 09:53:19,440-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-2) [] Migration of VM 'vm1' to host 'ovirt-node-production3' failed: VM destroyed during the startup. 2019-07-10 09:53:06,542-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-51) [c1daf639-ff39-4397-b1bf-09426cacf72d] EVENT_ID: VM_MIGRATION_FAILED(65), Migration failed due to a failed validation: [Cannot migrate VM. There is no host that satisfies current scheduling constraints. See below for details:, The host ovirt-node-production3 did not satisfy internal filter Memory.] (VM: vm2, Source: ovirt-node-production2). I also checked the vdsm.log on the destination host which is showing an error like this. ERROR (jsonrpc/2) [virt.vm] (vmId='f5bb25a8-3176-40b6-b21b-f07ed1089b27') Alias not found for device type balloon during migration at destination host (vm:5562) Does anybody know how to resolve this? The destination host is able to run VMs and I've been able to move a few VMs by shutting down and doing a restart however I'd like to do a live migration if possible.

1 0

ovirt_disk and ubuntu issues
by Vrgotic, Marko 10 Jul '19

10 Jul '19

Dear oVirt, I am downloading the ubuntu cloud image 16.04 and or 18.04: - name: "Download base cloud image from server" get_url: url: "{{ image_url }}" checksum: "sha256:{{ image_checksum }}" validate_certs: yes dest: "/tmp/{{ inventory_hostname_short }}.qcow2" delegate_to: localhost creating a 40GB HDD and attaching image to it: - name: "Create oVirt disk with base image (with 40Gb allocated)" ovirt_disk: name: "{{ inventory_hostname_short }}" interface: virtio size: 40GiB format: cow upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2" storage_domain: ovirt_production wait: true delegate_to: localhost creating VM afterwards: - name: "Create new Ubuntu VMs from cloud image" delegate_to: localhost ovirt_vm: auth: "{{ ovirt_auth }}" name: "{{ inventory_hostname_short }}" disks: - name: "{{ inventory_hostname_short }}" graphical_console: protocol: vnc serial_console: true usb_support: true soundcard_enabled: false operating_system: "{{ operating_system_type }}" type: server nics: - name: nic1 profile_name: tenant1 interface: virtio nic_on_boot: true cloud_init: host_name: "{{ inventory_hostname }}" user_name: ubuntu authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}" state: "running" cluster: "{{ ovirt_cluster }}" when: inventory_hostname in groups['ubuntu-baker'] When VM gets created, I can see in oVIrt VM details disk created is 40GB. Executing df -h, gives me following: root@av3-ubuntu-18-base:/home/ubuntu# df -h Filesystem Size Used Avail Use% Mounted on udev 447M 0 447M 0% /dev tmpfs 92M 696K 92M 1% /run /dev/vda1 2.0G 1.3G 706M 65% / tmpfs 460M 0 460M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 460M 0 460M 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi tmpfs 92M 0 92M 0% /run/user/1000 Initially I thought growpart or resize2fs is not triggered, but then running dmesg or fdisk /dev/vda, told me that physical disk size is still only size of the downloaded ubuntu cloud image. Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do not have this behavior with CentOS 7 images? Can you advise how to proceed, in case I am missing some configuration parameter or command to be run? The following Ubuntu images are used: ubuntu-16: image_url=https://cloud-images.ubuntu.com/xenial/current/xenial-server-clou… image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae ubuntu-18: image_url=https://cloud-images.ubuntu.com/bionic/current/bionic-server-clou… image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663 Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic Sr. System Engineer @ System Administration m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> tel. +31 (0)35 677 4131

1 0

Re: Help!
by Strahil 10 Jul '19

10 Jul '19

Edit the VM and go to 'system' tab (on the left). If you don't see it -click on 'show advanced options'. There select Harddisk as 1st device and DVD as second. Also mark the tick for the disk and from the dropdown choose your install disk. Then poweroff and then poweron. Best Regards, Strahil NikolovOn Jul 10, 2019 15:27, Abdoul-Rahamane Issoufou Oumarou <ioabdoulrahamaneapp.site(a)gmail.com> wrote: > > Good evening > > Today it's been almost a week since my efforts are in vain in the face of this problem that pushes me to write to you again. > > I installed ovirt 4.3 on a minimal centos installation. > Then I confided ovirt as well as the iso and data domains. > > Now the problem, I try to create a VM by setting up the entries and attaching a CD from the iso data center. > > As soon as I run the machine by opening the console, the VM blocks on the boot and the installation does not start. I'll give you two previews for my config and the problem in question. > > Thank you in advance to all those who would like to help me solve this problem.

1 0

Impossible to install VM Machine
by ioabdoulrahamaneapp.site＠gmail.com 10 Jul '19

10 Jul '19

Good evening Today it's been almost a week since my efforts are in vain in the face of this problem that pushes me to write to you again. I installed ovirt 4.3 on a minimal centos installation. Then I confided ovirt as well as the iso and data domains. Now the problem, I try to create a VM by setting up the entries and attaching a CD from the iso data center. As soon as I run the machine by opening the console, the VM blocks on the boot and the installation does not start. I'll give you two previews for my config and the problem in question. Thank you in advance to all those who would like to help me solve this problem. http://prntscr.com/od3ywo http://prntscr.com/od43v6

1 0

Help!
by Abdoul-Rahamane Issoufou Oumarou 10 Jul '19

10 Jul '19

Good evening Today it's been almost a week since my efforts are in vain in the face of this problem that pushes me to write to you again. I installed ovirt 4.3 on a minimal centos installation. Then I confided ovirt as well as the iso and data domains. Now the problem, I try to create a VM by setting up the entries and attaching a CD from the iso data center. As soon as I run the machine by opening the console, the VM blocks on the boot and the installation does not start. I'll give you two previews for my config and the problem in question. Thank you in advance to all those who would like to help me solve this problem.

1 0