Apps DBA Workshop

Oracle Linux Virtualization Manager (OLVM) is a powerful virtualization platform based on oVirt. Ensuring consistent backups of the OLVM environment is critical for disaster recovery and business continuity. The backup process primarily includes the engine database, configuration files, and optionally VM disk images (data domains).  Backup the OLVM Engine Database:  Use the engine-backup utility to back up the manager database and configuration. engine-backup --mode=backup \ --file=/backup/olvm_engine_backup.tar \ --log=/backup/olvm_backup.log \ --scope=all --scope=all ensures both the engine DB and configuration files are included.  Backup should be run on the OLVM manager node. Backup Data Domains (VM disks):  Use storage-level tools or snapshot methods to back up virtual machine disks.  For iSCSI/NFS domains:  Use storage-side snapshots or backup tools like rsync or tar. For GlusterFS:  Use Gluster snapshots or native backup solutions....

 This blogpost will provide details and steps for  automating VLAN-tagged bridge setup on a KVM host using Ansible , and then optionally connect it to OLVM if needed. Use Ansible to: Create a VLAN sub-interface on a physical NIC. Create a Linux bridge attached to that VLAN interface. Ensure the bridge is ready to be used by VMs or OLVM. Prerequisites Ansible installed on a control node. SSH access to the KVM host(s). nmcli or network role availability (for Red Hat-based distros). Ansible Playbook Example Directory Structure: vlan-bridge-setup/ ├── inventory └── vlan_bridge.yml inventory: [kvmhosts] 192.168.125.100 ansible_user=root vlan_bridge.yml: - name: Configure VLAN tagged bridge on KVM host   hosts: kvmhosts   become: yes   tasks:     - name: Create VLAN interface eth0.100       nmcli:         conn_name: vlan100         ifname: eth0         type: vla...

 Oracle KVM Service fails to start with following error: #virsh start db-node1 error: Failed to start domain 'db-node1' error: internal error: QEMU unexpectedly closed the monitor (vm='db-node1'): 2024-04-08Tqemu-kvm: unable to map backing store for guest RAM: Cannot allocate memory   This issue is happening due to the wrong version of the packages:   # rpm -qa | grep qemu qemu-img-8.0.0-16.el9_3.1.x86_64 libvirt-daemon-driver-qemu-9.5.0-7.0.1.el9_3.x86_64 qemu-kvm-tools-8.0.0-16.el9_3.1.x86_64 qemu-pr-helper-8.0.0-16.el9_3.1.x86_64 qemu-kvm-docs-8.0.0-16.el9_3.1.x86_64 ipxe-roms-qemu-20200823-9.git4bd064de.el9_0.noarch qemu-kvm-common-8.0.0-16.el9_3.1.x86_64 qemu-kvm-device-display-virtio-gpu-8.0.0-16.el9_3.1.x86_64 qemu-kvm-ui-opengl-8.0.0-16.el9_3.1.x86_64 qemu-kvm-ui-egl-headless-8.0.0-16.el9_3.1.x86_64 qemu-kvm-device-display-virtio-gpu-pci-8.0.0-16.el9_3.1.x86_64 qemu-kvm-block-blkio-8.0.0-16.el9_3.1.x86_64 qemu-kvm-block-rbd-8.0.0-16.el9_3.1.x86_64 qemu-kvm-devic...

We were trying to install the ovirt engine and Oracle Linux 9 but we were not able to complete the installation successfully.  We should note that Oracle Linux 9 is not currently supported for the installation of KVM hosts and OLVM engine. The latest release of OLVM is OLVM 4.5, and it only supports Oracle Linux 8.8 or later versions.  Conclusion: So we recommend you to use last available version of Oracle Linux 8 for installation of oVirt engine 4.4.10/oVirt engine 4.5 and KVM Host on Server to avoid any issue. thanks for reading. regards, ZAHEER

 This blogpost will guide you to find out the virtual disk path attached to a virtual machine. - Login to the admin console - Navigate to > Storage > Disk - Click on Disk to copy the ID of the disk. - Now Login to the Any KVM host from command line and use below command to know the exact physical location of the virtual disk. This will give you the details of the file location with storage domain. thanks for reading  :) regards, zaheer

 In one of our customer environment we were trying to upload the iso image on KVM storage domain, but when we were trying to upload the image we encountered following error: [root@oraovm REST]# python upload_to_storagedomain.py -l oraovm -u admin@internal -c /etc/pki/ovirt-engine/ca.pem --sdd-name NFS-ISO-DATA -t ISO /home/os_files/SW_DVD9_Win_Server_CORE_2016_64Bit.iso Enter engine Login password:- Creating disk... Traceback (most recent call last): File "upload_to_storagedomain.py", line 179, in main() File "upload_to_storagedomain.py", line 117, in main disk = create_disk() File "upload_to_storagedomain.py", line 101, in create_disk name = arg.sdd_name File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 7074, in add return self._internal_add(disk, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 223, in _internal_add context = self._connection...

 In OLVM Environment while access the guest VM using the console service we have encountered the follow Error: Cause: OLVM certificate is not installed on client machine from where the console is being accessed. Solution: Install the required certificate on the client machine from where the console is being accessed. Thanks for reading :) regards, zaheer