- Users - oVirt List Archives

Network Teamd support
by Carlos C 17 Dec '20

17 Dec '20

Hi folks, Does Ovirt 4.4.4 support or will support Network Teamd? Or only bonding? regards Carlos

3 2

Cannot connect Glusterfs storage to Ovirt
by Ariez Ahito 17 Dec '20

17 Dec '20

HI guys, i have installed ovirt 4.4 hosted engine and a separate glusterfs storage. now during hosted engine deployment when i try do choose STORAGE TYPE: gluster Storage connection: 10.33.50.33/VOL1 Mount Option: when i try to connect this gives me an error: [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Problem while trying to mount target]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Problem while trying to mount target]\". HTTP response code is 400."}

4 6

Move self hosted engine to a different gluster volume
by ralf＠os-s.de 17 Dec '20

17 Dec '20

Hi, I apparently successfully upgraded a hyperconverged self hosted setup from 4.3 to 4.4. During this process the selfhosted engine required a new gluster volume (/engine-new). I used a temporary storage for that. Is it possible to move the SHE back to the original volume (/engine)? What steps would be needed? Could I just do: 1. global maintenance 2. stop engine and SHE guest 3. copy all files from glusterfs /engine-new to /engine 4. use hosted-engine --set-shared-config storage <server1>:/engine hosted-engine --set-shared-config mnt_options backup-volfile-servers=<server2>:<server3> 5. disable maintenance Or are additional steps required? Kind regards, Ralf

1 0

Increase the initial size of LVM snapshots to prevent VM's from freezing
by Gal Villaret 16 Dec '20

16 Dec '20

Hi all, Lately, I have been encountering an issue where VMs freeze during backups. From what I can gather, this happens because some of the VMs sometimes perform large writes during the backup window and the snapshots dose not grow fast enough. I use ISCSI storage with all VM disks preallocated. Is there a configuration value I can change in order to increase the initial size of snapshots and also maybe change the watermark trigger for the expansion of snapshots? Thanks.

2 1

Bad CPU TYPE after Centos 8.3
by Lionel Caignec 15 Dec '20

15 Dec '20

Hi, i've just upgraded one host to latest centos release. And after reboot ovirt said "Host CPU type is not compatible with Cluster Properties." Looking on server i can see cpu is detected as skylake (cat /sys/devices/cpu/caps/pmu_name). My CPU is Intel(R) Xeon(R) Gold 5220R CPU @ 2.20GHz so according to ark cascade lake server. When i installed my new ovirt environment month agos, i configure cluster to be "secure Intel Cascade lake server family" and all sound goods. So anyone can help me? Environment : OS : Centos 8.3 (for manager and host in error) ovirt-engine 4.4.3.12-1.el8 Host with error : vdsm.x86_64 4.40.35.1-1.el8 Working Host : vdsm.x86_64 .40.26.3-1.el8 Maybe someone can help me? I don't know what to do, and does not want to try update another host if it fail... Sorry if i post my message at wrong place. Lionel Caignec.

5 15

How to unlock disk images?
by thomas＠hoberg.net 15 Dec '20

15 Dec '20

On one oVirt 4.3 farm I have three locked images I'd like to clear out. One is an ISO image, that somehow never completed the transfer due to a slow network. It's occupying little space, except in the GUI where it sticks out and irritates. I guess it would just be an update somewhere on the Postgress database to unlock it and have it deletable: But since the schema isn't documented, I'd rather ask here: How to I unlock the image? Two are left-overs from a snapshot that somehow never completed, one for the disk another for the RAM part. I don't know how my colleague managed to get into that state, but impatience/concurrency probably was a factor, a transient failure of a node could have been another. In any case the snapshot operation logically has been going on for weeks without any real activity, survived several restarts (after patches) of all nodes and the ME and shows no sign of disappearing voluntarily. Again, I'd assume that I need to clear out the snapshot job, unlock the images and then delete what's left. Some easy SQL and most likely a management engine restart afterwards... if you knew what you were doing (or there was an option in the GUI). So how do I list/delete snapshot jobs that aren't really running any more? And how do I unlock the images so I can delete them? Thanks for your help!

2 4

illegal disk status
by Daniel Menzel 15 Dec '20

15 Dec '20

Hi, we have a problem with some VMs which cannot be started anymore due to an illegal disk status of a snapshot. What happend (most likely)? we tried to snapshot those vms some days ago but the storage domain didn't have enough free space left. Yesterday we shut those vms down - and from then on they didn't start anymore. What have I tried so far? 1. Via the web interface I tried to remove the snapshot - didn't work. 2. Searched the internet. Found (among other stuff) this: https://bugzilla.redhat.com/show_bug.cgi?id=1649129 3. via /vdsm-tool dump-volume-chains/ I managed to list those 5 snapshots (see below). The output for one machine was: image: 2d707743-4a9e-40bb-b223-83e3be672dfe - 9ae6ea73-94b4-4588-9a6b-ea7a58ef93c9 status: OK, voltype: INTERNAL, format: RAW, legality: LEGAL, type: PREALLOCATED, capacity: 32212254720, truesize: 32212254720 - f7d2c014-e8f5-4413-bfc5-4aa1426cb1e2 status: ILLEGAL, voltype: LEAF, format: COW, legality: ILLEGAL, type: SPARSE, capacity: 32212254720, truesize: 29073408 So my idea was to follow the said bugzilla thread and update the volume - but I didn't manage to find input for the /job_id/ and /generation/. So my question is: Does anyone have an idea on how to (force) remove a given snapshot via vsdm-{tool|client}? Thanks in advance! Daniel -- Daniel Menzel Geschäftsführer Menzel IT GmbH Charlottenburger Str. 33a 13086 Berlin +49 (0) 30 / 5130 444 - 00 daniel.menzel(a)menzel-it.net https://menzel-it.net Geschäftsführer: Daniel Menzel, Josefin Menzel Unternehmenssitz: Berlin Handelsregister: Amtsgericht Charlottenburg Handelsregister-Nummer: HRB 149835 B USt-ID: DE 309 226 751

2 1

Nodes install Python3 every day
by jb 15 Dec '20

15 Dec '20

Hello, I notice a strange thing in the logs. All Nodes (ovirt 4.4.3.12-1.el8) install every days again Python3, after checking for updates. The GUI log shows this entries: 13.12.2020, 11:39 Check for update of host onode1.example.org. Gathering Facts. 13.12.2020, 11:39 Check for update of host onode1.example.org. include_tasks. 13.12.2020, 11:39 Check for update of host onode1.example.org. Detect host operating system. 13.12.2020, 11:39 Check for update of host onode1.example.org. Fetch installed packages. 13.12.2020, 11:39 Check for update of host onode1.example.org. Check if vdsm is preinstalled. 13.12.2020, 11:39 Check for update of host onode1.example.org. Parse operating system release. 13.12.2020, 11:39 Check for update of host onode1.example.org. Detect if host is a prebuilt image. 13.12.2020, 11:39 Check for update of host onode1.example.org. Install Python3 for CentOS/RHEL8 hosts. 13.12.2020, 11:39 Check for update of host onode1.example.org. Set facts. /var/log/ovirt-engine/ansible-runner-service.log shows: 2020-12-13 11:39:20,849 - runner_service.services.playbook - DEBUG - cb_event_handler event_data={'uuid': '7c4b039d-6212-4b52-95fd-40d85036ed98', 'counter': 33, 'stdout': 'ok: [onode1.example.org]', 'start_line': 31, 'end_line': 32, 'runner_ident': '72737578-3d2f-11eb-b955-00163e33f845', 'event': 'runner_on_ok', 'pid': 603696, 'created': '2020-12-13T10:39:20.847869', 'parent_uuid': '00163e33-f845-ee64-acee-000000000013', 'event_data': {'playbook': 'ovirt-host-check-upgrade.yml', 'playbook_uuid': '0eb5c935-9f17-4b07-961e-7e0a866dd5ed', 'play': 'all', 'play_uuid': '00163e33-f845-ee64-acee-000000000008', 'play_pattern': 'all', 'task': 'Install Python3 for CentOS/RHEL8 hosts', 'task_uuid': '00163e33-f845-ee64-acee-000000000013', 'task_action': 'yum', 'task_args': '', 'task_path': '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-facts/tasks/main.yml:20', 'role': 'ovirt-host-deploy-facts', 'host': 'onode1.example.org', 'remote_addr': 'onode1.example.org', 'res': {'msg': 'Nothing to do', 'changed': False, 'results': [], 'rc': 0, 'invocation': {'module_args': {'name': ['python3'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot': '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'lock_timeout': 30, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': False}, 'start': '2020-12-13T10:39:19.872585', 'end': '2020-12-13T10:39:20.847636', 'duration': 0.975051, 'event_loop': None, 'uuid': '7c4b039d-6212-4b52-95fd-40d85036ed98'}} Is this a bug? Best regards Jonathan

3 4

Re: CentOS 8 is dead
by marcel d'heureuse 15 Dec '20

15 Dec '20

So, I think keep the live system on ovirt 4.3 to be sure that's works after 2021? Distribution you have 10 years support? Centos 7 has support up to June 24. Someone starts to evolute Gentoo? marcel Am 8. Dezember 2020 21:15:48 MEZ schrieb "Vinícius Ferrão via Users" <users(a)ovirt.org>: >CentOS Stream is unstable at best. > >I’ve used it recently and it was just a mess. There’s no binary >compatibility with the current point release and there’s no version >pinning. So it will be really difficult to keep track of things. > >I’m really curious how oVirt will handle this. > >From: Wesley Stewart <wstewart3(a)gmail.com> >Sent: Tuesday, December 8, 2020 4:56 PM >To: Strahil Nikolov <hunter86_bg(a)yahoo.com> >Cc: users <users(a)ovirt.org> >Subject: [ovirt-users] Re: CentOS 8 is dead > >This is a little concerning. > >But it seems pretty easy to convert: >https://www.centos.org/centos-stream/ > >However I would be curious to see if someone tests this with having an >active ovirt node! > >On Tue, Dec 8, 2020 at 2:39 PM Strahil Nikolov via Users ><users(a)ovirt.org<mailto:users@ovirt.org>> wrote: >Hello All, > >I'm really worried about the following news: >https://blog.centos.org/2020/12/future-is-centos-stream/ > >Did anyone tried to port oVirt to SLES/openSUSE or any Debian-based >distro ? > >Best Regards, >Strahil Nikolov >_______________________________________________ >Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> >To unsubscribe send an email to >users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> >Privacy Statement: https://www.ovirt.org/privacy-policy.html >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/ >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/HZC4D4OSYL64D… -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

4 4

what's error?
by tommy 15 Dec '20

15 Dec '20

Hi,I installed oVirt on my hosts. But there are many such errors on the console of the host, such as: Why ??? Thanks.

3 2

pgrade 4.3 to 4.4 with migration CentOS7 to CentOS8.3
by Ilya Fedotov 14 Dec '20

14 Dec '20

Good day, Encountered such a problem when migrating to ovirt 4.4 At hosted-engine --deploy --restore-from-file=backup.bck Getting, error below Upgrading engine extension configuration: /etc/ovirt-engine/extensions.d/xx-xxxx.properties", "[ INFO ] Upgrading CA", "[ INFO ] Creating CA: /etc/pki/ovirt-engine/qemu-ca.pem", "[ ERROR ] Failed to execute stage 'Misc configuration': [Errno 17] File exists: '/etc/pki/ovirt-engine/ca.pem' -> '/etc/pki/ovirt-engine/apache-ca.pem'", "[ INFO ] DNF Performing DNF transaction rollback", "[ INFO ] Stage: Clean up", At setting of initial parameters I select "No" parameter in para 'Renew engine CA on restore if needed? Please notice ' 'that if you choose Yes, all hosts will have to be ' 'later manually reinstalled from the engine. ' '(@VALUES@)[@DEFAULT@] Dosnt need to renew the .ca certificate, thats upgrade and dosnt need to re-make connections with nodes! Even with this item, he still tries to create a new certificate. I found a similar question here: https://www.mail-archive.com/users@ovirt.org/msg61114.html Package Data: ovirt-hosted-engine-setup-2.4.8-1.el8.noarch ovirt-hosted-engine-ha-2.4.5-1.el8.noarch ovirt-engine-appliance-4.4-20201110154142.1.el8.x86_64 CentOS Linux release 8.3.2011 4.18.0-240.1.1.el8_3.x86_64 Pls, help programmers..... with br, Ilya Fedotov

2 2

hosted engine wrong bios
by Michael Rohweder 14 Dec '20

14 Dec '20

Hi, i run with ovirt node 4.4.2 in some old mistake. I changed cluster default to uefi weeks ago. now today node must be restarted, and now i cannot work. manager VM try to boot on uefi. and all other vm are down, because i cannot start anny with cli. how can i change (some config, file or something els) that setting in this vm to normal bios? Greetings Michael

1 0

Hosted engine deployment w/ two networks (one migration, one management).
by Gilboa Davara 14 Dec '20

14 Dec '20

Hello all, I'm slowly building a new ovirt over glusterfs cluster with 3 fairly beefy servers. Each of the nodes has the following network configuration: 3x1GbE: ILO, ovirtmgmt and SSH. 4x10GbE: Private and external VM network(s). 2x40GBE: GlusterFS and VM migration. Now, for some odd reasons, I rather keep the two 40GbE networks disconnected from my normal management network. My question is simple: I remember that I can somehow configure ovirt to use two different networks for for management / migration, but as far as I can see, I cannot configure the cluster to use a different network for migration purposes. 1. Am I missing something? 2. Can I somehow configure the hosted engine to have an IP in more than network (management and migration)? 3. More of a gluster question: As the 40GbE NICs and 1GbE NIC sitting on different switches, can I somehow configure gluster to fallback to the 1GbE NIC if the main 40GbE link fails? AFAIR bond doesn't support asymmetrical network device configuration. (And rightly so, in this case). Thanks, Gilboa

2 2

VMs shut down after backup: "moved from 'Up' --> 'Down'" on RHEL host
by Łukasz Kołaciński 14 Dec '20

14 Dec '20

Hello, Thank you for helping with previous issue. Unfortunately we got another. We have RHV manager with several different hosts. After the backup, vm placed on RHEL shuts down. In engine.log I found moment when this happen: "VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'". I attached whole logs to email. It doesn't matter if it's a full or incremental, results are always the same. RHVH hosts works properly. Log fragment: 2020-12-08 10:18:33,845+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-76) [60da31e3-92f6-4555-8c43-2f8afee272e0] Updating image transfer 87bdb42e-e64c-460d-97ac-218e923336a1 (image e57e4af0-5d0b-4f60-9e6c-e217c666e5e6) phase to Finalizing Success 2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Running command: StopVmBackupCommand internal: false. Entities affected : ID: 35183baa-1c70-4016-b7cd-528889876f19 Type: VMAction group BACKUP_DISK with role type ADMIN, ID: e57e4af0-5d0b-4f60-9e6c-e217c666e5e6 Type: DiskAction group BACKUP_DISK with role type ADMIN 2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Stopping VmBackup 'aae03819-cea6-45a1-9ee5-0f831af8464d' 2020-12-08 10:18:33,952+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] START, StopVmBackupVDSCommand(HostName = rhv-2, VmBackupVDSParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', backupId='aae03819-cea6-45a1-9ee5-0f831af8464d'}), log id: 78b2c27a 2020-12-08 10:18:33,958+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] FINISH, StopVmBackupVDSCommand, return: , log id: 78b2c27a 2020-12-08 10:18:33,975+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] EVENT_ID: VM_BACKUP_FINALIZED(10,794), Backup <UNKNOWN> for VM stor2rrd finalized (User: admin@internal-authz). 2020-12-08 10:18:35,221+01 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-73) [] User admin@internal successfully logged out 2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-81) [1b35276c] Running command: TerminateSessionsForTokenCommand internal: true. 2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.SessionDataContainer] (default task-81) [1b35276c] Not removing session '90TxdK0PBueLijy+sCrFoHC/KNUGNzNpZuYMK/yKDAkbAefFr+8wOJsATsDKv18LxpyxCl+eX7hTHNxN23anAw==', session has running commands for user 'admin@internal-authz'. 2020-12-08 10:18:35,447+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19' was reported as Down on VDS 'afad6b8b-78a6-4e9a-a9bd-783ad42a2d47'(rhv-2) 2020-12-08 10:18:35,448+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] START, DestroyVDSCommand(HostName = rhv-2, DestroyVmVDSCommandParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', vmId='35183baa-1c70-4016-b7cd-528889876f19', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 4f473135 2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] FINISH, DestroyVDSCommand, return: , log id: 4f473135 2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down' 2020-12-08 10:18:35,466+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is down with error. Exit message: Lost connection with qemu process. 2020-12-08 10:18:35,484+01 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-34085) [3da40159] Running command: ProcessDownVmCommand internal: true. The environment of faulty host is: OS Version: RHEL - 8.3 - 1.0.el8 OS Description: Red Hat Enterprise Linux 8.3 (Ootpa) Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64 KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69 LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5 VDSM Version: vdsm-4.40.26.3-1.el8ev SPICE Version: 0.14.3 - 3.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: openvswitch-2.11-7.el8ev Nmstate Version: nmstate-0.3.4-13.el8_3 Regards Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.

1 0

install ovirt 4.4.3 hosted-engine ,but it looks suspend.
by tommy 14 Dec '20

14 Dec '20

It looks suspend. 1. On host 2. On VM 3. How to resolve it?

3 3

oVirt and RHEV
by tommy 13 Dec '20

13 Dec '20

1、 If oVirt can be used to manage RHEV ? 2、 What relation between oVirt and RHEV? Thanks!

3 2

OPNsense / FreeBSD 12.1
by Jorge Visentini 12 Dec '20

12 Dec '20

Hi all. I tried to install OPNsense 20.7.6 (FreeBSD 12.1) and it was not possible to detect the NICs. I tried both the virtio driver and the e1000. Virtio does not detect and e1000 crashes at startup. In pure KVM, it works, so I believe there is some incompatibility with oVirt 4.4.4. Any tips? -- Att, Jorge Visentini +55 55 98432-9868

4 7

Recent news & oVirt future
by Charles Kozler 11 Dec '20

11 Dec '20

I guess this is probably a question for all current open source projects that red hat runs but - Does this mean oVirt will effectively become a rolling release type situation as well? How exactly is oVirt going to stay open source and stay in cadence with all the other updates happening around it on packages/etc that it depends on if the streams are rolling release? Do they now need to fork every piece of dependency? What exactly does this mean for oVirt going forward and its overall stability? -- *Notice to Recipient*: https://www.fixflyer.com/disclaimer <https://www.fixflyer.com/disclaimer>

3 6

[CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 11 Dec '20

11 Dec '20

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2021, to be hosted virtually on February 6th 2021. This year will mark FOSDEM’s 21th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 6th & 7th, 2021. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2021 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17>https://penta.fosdem .org/submission/FOSDEM21 [2] iaas-virt-devroom at lists.fosdem.org

1 1

Nodes in CentOS 8.3 and oVirt 4.4.3.12-1.el8 but not able to update cluster version
by Gianluca Cecchi 11 Dec '20

11 Dec '20

Hello, my engine is 4.4.3.12-1.el8 and my 3 oVirt nodes (based on plain CentOS due to megaraid_sas kernel module needed) have been updated, bringing them to CentOS 8.3. But if I try to put cluster into 4.5 I get the error: " Error while executing action: Cannot change Cluster Compatibility Version to higher version when there are active Hosts with lower version. -Please move Host ov300, ov301, ov200 with lower version to maintenance first. " Do I have to wait until final 4.4.4 or what is the problem? Does 4.5 gives anything more apart the second number... (joking..)? On nodes: Software OS Version: RHEL - 8.3 - 1.2011.el8 OS Description: CentOS Linux 8 Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64 KVM Version: 4.2.0 - 34.module_el8.3.0+555+a55c8938 LIBVIRT Version: libvirt-6.0.0-28.module_el8.3.0+555+a55c8938 VDSM Version: vdsm-4.40.35.1-1.el8 SPICE Version: 0.14.3 - 3.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: [N/A] Nmstate Version: nmstate-0.3.6-2.el8 Kernel Features: MDS: (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable), L1TF: (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable), SRBDS: (Not affected), MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: usercopy/swapgs barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: Split huge pages), TSX_ASYNC_ABORT: (Not affected), SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and seccomp) VNC Encryption: Disabled FIPS mode enabled: Disabled Gianluca

4 5

oVirt 4.4: Self-hosted engine deployment fails with backup restore from 4.3 engine
by Oliver Leinfelder 11 Dec '20

11 Dec '20

Hi there, I'm a bit puzzled about an possible upgrade paths from a 4.3 cluster to version 4.4 in a self-hosted engine environment. My idea was: Set up a new host with a clean ovirt node 4.4 installation, then deploy the hosted engine on this with a restored backup from the production cluster and go from there. This however fails with the following error: 2020-05-27 00:17:08,886+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': 'non-zero return code', 'cmd': ['engine-setup', '--accept-defaults', '--config-append=/root/ovirt-engine-answers'], 'stdout': "[ INFO ] Stage: Initializing\n[ INFO ] Stage: Environment setup\n C onfiguration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, /root/ovirt-engine-answers\n Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20200527001657-fyeueu.log\n Version: otop i-1.9.1 (otopi-1.9.1-1.el8)\n[ INFO ] DNF Downloading 1 files, 0.00KB\n[ INFO ] DNF Downloaded CentOS-8 - AppStream\n[ INFO ] DNF Downloading 1 files, 0.00KB\n[ INFO ] DNF Downloaded CentOS-8 - Base\n[ INFO ] DNF Downloading 1 files, 0.00KB\n [...] ... anwsers from backup config follow .... [...] 2020-05-27 00:17:12,396+0200 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 403, in _closeup r = ah.run() File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run raise RuntimeError(_('Failed executing ansible-playbook')) Is this approach (restoring from 4.3) generally supposed to work? If not, what is the appropriate upgrade path? Thank you! Regards Oli

3 7

Deploy hosted engine from backup fails
by JCampos 10 Dec '20

10 Dec '20

Command to execute backup: #engine-backup --mode=backup --file=backup1 --log=backup1.log Command to restore backup: #hosted-engine --deploy --restore-from-file=backup1 Error: 2020-12-09 22:26:25,679+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Available memory ( {'failed': False, 'changed': False, 'ansible_facts': {u'max_mem': u'33211'}}MB ) is less then the minimal requirement (4096MB). Be aware that 512MB is reserved for the host and cannot be allocated to the engine VM."} Ovirt version: 4.3.10.4-1.el7 # cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) Memory available: #free -m total used free shared buff/cache available Mem: 64132 30478 494 145 33158 32961 Swap: 16383 0 16383 Is there a way to ignore this check?

2 2

Another illegal disk snapshot problem!
by Joseph Goldman 10 Dec '20

10 Dec '20

Hi List, oVirt 4.3 I know there have been threads about this before - but I am unable to find the exact scenario I am facing. I have a VM with 3 snapshots - Active, and 2 dated ones (technically created by vProtect) After trying to do a fresh snapshot in the GUI it failed out and marked one of the old snapshot disks as 'illegal' - then the other tried to follow suit. I tried 'unlocking' the entity using the unlock_entity.sh tool but any action reverts them back to illegal. Following previous advice - I can see the VDSM status is all showing LEGAL: image: 23710238-07c2-46f3-96c0-9061fe1c3e0d - *c3dadf14-bb4e-45a7-8bee-b9a01fe29ae1* *status: OK, voltype: INTERNAL, format: RAW, legality: LEGAL, type: SPARSE, capacity: 107374182400, truesize: 18402942976** * - *a6d4533b-b0b0-475d-a436-26ce99a38d94** ** status: OK, voltype: INTERNAL, format: COW, legality: LEGAL, type: SPARSE, capacity: 107374182400, truesize: 21521768448* - 4b6f7ca1-b70d-4893-b473-d8d30138bb6b status: OK, voltype: LEAF, format: COW, legality: LEGAL, type: SPARSE, capacity: 107374182400, truesize: 12617457664 The 2 bold entries are the 'illegal' snapshots. Looking in the DB see's: select image_guid,parentid ,imagestatus ,vm_snapshot_id ,volume_type ,volume_format ,active from images where image_group_id='23710238-07c2-46f3-96c0-9061fe1c3e0d'; image_guid | parentid | imagestatus | vm_snapshot_id | volume_type | volume_format | active --------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+-------- 4b6f7ca1-b70d-4893-b473-d8d30138bb6b | a6d4533b-b0b0-475d-a436-26ce99a38d94 | 1 | d5044ae5-dc48-4700-9e46-d61e676c73fc | 2 | 4 | t c3dadf14-bb4e-45a7-8bee-b9a01fe29ae1 | 00000000-0000-0000-0000-000000000000 | 4 | 57337968-28da-4b03-ac40-134a347d8c11 | 2 | 5 | f a6d4533b-b0b0-475d-a436-26ce99a38d94 | c3dadf14-bb4e-45a7-8bee-b9a01fe29ae1 | 4 | d2d82724-9fe7-452c-a114-f8d70b555520 | 2 | 4 | f So from here previous advice has been to do things such as delete the snapshot/disk etc but thats when they showed as illegal status. I also notice the Active Image is not the same image that has a parentid of all 00000's so im not sure on the process of possibly deleting the other snapshots and disks cleanly and/or safely. Deleting or any tasks in the gui 100% fails and its at a point that if I shut down the (critical) VM it will not come back on because of these status'. On top of this what is a good way to take a clean, manual backup of current in use disk before I start playing with this in case worse comes to worse I have to try build it as a new server (As at this point I can't trust my vProtect backups) Any help appreciated. Thanks, Joe

3 8

Can't import some VMs after storage domain detach and reattach to new datacenter.
by m black 10 Dec '20

10 Dec '20

7 14

ovirt 4.3 - locked image vm - unable to remove a failed deploy of a guest dom
by 3c.monitor＠gruppofilippetti.it 09 Dec '20

09 Dec '20

Hi all. I've deployed a VM from a corrupted template (it's disk is missing, but I've checked it later...). My Software Version is:4.3 Now, I have an unmanaged VM in inventory and unable to remove it too. It's reference is "locked image". I've restarted ovirt-engine many times on self-hosted engine and hosts too, but no benefits. So, what's now? I've also consulted: https://access.redhat.com/solutions/396753 but still no results. No tasks or items results to be "locked"... Any other ideas? Thanks a lot.

3 17