- Users - oVirt List Archives

Intel Xeon Platinum 8276M vs oVirt 4.4.10.2-1
by Jorge Visentini 24 Jun '23

24 Jun '23

Hi all! Does anyone use or used Intel Xeon Platinum 8276M with oVirt 4.4.10? *I have the following situation:* I have these 2 sockets on a host, and on bash (lscpu) I identify the 2 sockets, however the oVirt interface only identifies 1 socket: *lscpu:* [root@ovirt03 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 112 On-line CPU(s) list: 0-111 Thread(s) per core: 2 Core(s) per socket: 28 *Socket(s): 2* NUMA node(s): 2 Vendor ID: GenuineIntel BIOS Vendor ID: Intel(R) Corporation CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz BIOS Model name: Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz Stepping: 7 CPU MHz: 2990.453 CPU max MHz: 4000.0000 CPU min MHz: 1000.0000 BogoMIPS: 4400.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 39424K NUMA node0 CPU(s): 0-27,56-83 NUMA node1 CPU(s): 28-55,84-111 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke avx512_vnni md_clear flush_l1d arch_capabilities [root@ovirt03 ~]# *oVirt Host Interface:* CPU Model Name: Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz CPU Type: Secure Intel Cascadelake Server Family *CPU Sockets: 1* CPU Cores per Socket: 56 CPU Threads per Core: 2 (SMT Enabled) TSC Frequency: 2199999000 (scaling enabled) I need it to show the 2 sockets because I need to configure the NUMA. If anyone has any tips or fixes, I'd appreciate it. -- Att, Jorge Visentini +55 55 98432-9868

1 0

Ovirt 4.5 different VNC Server
by R A 23 Jun '23

23 Jun '23

Hello, is it possible to use a custom vnc server like tigervnc on the hosts and forward the display then to the vms ?? Is there any guide for this? BR R A

1 0

Ovirt 4.5 any alternatives to Remote Viewer
by R A 23 Jun '23

23 Jun '23

Hello, are there any alternatives to Remote Viewer which can open the console.vv provided by ovirt engine? BR R A

1 0

ovirt 4.5 VNC Failed to complete handshake Error in the pull function on Windows
by R A 23 Jun '23

23 Jun '23

Hello, i am using ovirt 4.5.4-1.el9 standalone on Rocky Linux and have some struggle with vnc connection. I ve engine.mydomain.de which contains the ovirt-engine. I installed third party certificate successfully. So when i call engine.mydomain.de/ovirt-engine or node1.mydomain.de:9090 the browser tell me that connection is secured. My first host is node1.mydomain.de, which has currently one VM up. On Linux Client (Rocky Linux 9.2) 1. When i run "remote-viewer --debug /home/user1/Downloads/console.vv --gtk-vnc-debug" everything works fine. RemoteViewer opens and i can see the console of my vm 2. When i try to open the console.vv directly via remoteViewer from enngine-portal i get feedback from remoteViewer: "The certificate is not trusted" 3. When i try to open via novnc a new tab opens and i get "Something went wrong, connection is closed" On Windows 11 1. When i generate the console.vv and copy the password and hostadress + port to TigerVNC client everything work fine. TigerVNC tells me that connection is secured 2. When opening console.vv directly via RemoteViewer i get "Filed to complete handshake Error in the pull function 3. When i try to open via novnc a new tab opens and i get "Something went wrong, connection is closed" 4. When i run "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\VirtViewer\Remote viewer.lnk" --debug C:\Users\rezaa\Downloads\console.vv --gtk-vnc-debug I get : C:\Users\rezaa>"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\VirtViewer\Remote viewer.lnk" --debug C:\Users\rezaa\Downloads\console.vv --gtk-vnc-debug C:\Users\rezaa>(remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.218: keymap string is empty - nothing to do (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.264: Opening display to C:\Users\rezaa\Downloads\console.vv (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.265: Guest (NULL) has a vnc display (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.271: ../src/vncconnection.c Init VncConnection=00000000070f1c90 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.271: ../src/vncdisplaykeymap.c Using Win32 virtual keycode mapping (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.272: ../src/vncdisplay.c Grab sequence is now Control_L+Alt_L (remote-viewer.exe:9460): libsoup-WARNING **: 19:16:33.277: Could not set SSL credentials from '/etc/pki/tls/certs/ca-bundle.crt': Vertrauenswürdigkeitsliste konnte nicht aus /etc/pki/tls/certs/ca-bundle.crt befüllt werden: Error while reading file. (remote-viewer.exe:9460): libsoup-WARNING **: 19:16:33.277: Could not set SSL credentials from '/etc/pki/tls/certs/ca-bundle.crt': Vertrauenswürdigkeitsliste konnte nicht aus /etc/pki/tls/certs/ca-bundle.crt befüllt werden: Error while reading file. (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.278: Spice foreign menu updated (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.278: After open connection callback fd=-1 (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.279: Opening connection to display at C:\Users\rezaa\Downloads\console.vv (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.289: fullscreen display 0: 0 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.289: ../src/vncconnection.c Open host=node1.mydomain.de port=5900 (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.289: notebook show status 0000000004408580 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.875: ../src/vncconnection.c Open coroutine starting (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.876: ../src/vncconnection.c Started background coroutine (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.877: ../src/vncconnection.c Resolving host node1.mydomain.de 5900 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.880: ../src/vncconnection.c Trying one socket (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.881: ../src/vncconnection.c Schedule socket timeout 00000000070f0a40 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.882: ../src/vncconnection.c Socket pending (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.914: ../src/vncconnection.c Finally connected (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.915: ../src/vncconnection.c Remove timeout 00000000070f0a40 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.916: ../src/vncconnection.c Emit main context 13 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.917: ../src/vncdisplay.c Grab sequence is now (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.917: notebook show status 0000000004408580 (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.919: Insert display 0 0000000007572f80 (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.919: notebook show status 0000000004408580 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.920: ../src/vncdisplay.c Connected to VNC server (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.920: ../src/vncconnection.c Protocol initialization (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.920: ../src/vncconnection.c Schedule greeting timeout 00000000070f0a40 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.921: ../src/vncconnection.c Read error Ein nicht blockierender Socketvorgang konnte nicht sofort ausgeführt werden. (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.922: Allocated 1024x768 (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.922: Child allocate 1024x640 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.946: ../src/vncconnection.c Remove timeout 00000000070f0a40 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.947: ../src/vncconnection.c Server version: 3.8 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.950: ../src/vncconnection.c Sending full greeting (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.951: ../src/vncconnection.c Using version: 3.8 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.964: ../src/vncconnection.c Read error Ein nicht blockierender Socketvorgang konnte nicht sofort ausgeführt werden. (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.983: ../src/vncconnection.c Possible auth 19 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.984: ../src/vncconnection.c Emit main context 11 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.984: ../src/vncconnection.c Thinking about auth type 19 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.985: ../src/vncconnection.c Decided on auth type 19 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.985: ../src/vncconnection.c Waiting for auth type (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.986: ../src/vncconnection.c Choose auth 19 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.986: ../src/vncconnection.c Checking if credentials are needed (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.987: ../src/vncconnection.c No credentials required (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.987: ../src/vncconnection.c Read error Ein nicht blockierender Socketvorgang konnte nicht sofort ausgeführt werden. (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.019: ../src/vncconnection.c Read error Ein nicht blockierender Socketvorgang konnte nicht sofort ausgeführt werden. (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.050: ../src/vncconnection.c Possible VeNCrypt sub-auth 261 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.051: ../src/vncconnection.c Emit main context 12 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.052: ../src/vncconnection.c Requested auth subtype 261 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.053: ../src/vncconnection.c Waiting for VeNCrypt auth subtype (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.054: ../src/vncconnection.c Choose auth 261 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.055: ../src/vncconnection.c Checking if credentials are needed (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.056: ../src/vncconnection.c No credentials required (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.056: ../src/vncconnection.c Read error Ein nicht blockierender Socketvorgang konnte nicht sofort ausgeführt werden. (remote-viewer.exe:9460): GLib-GIO-WARNING **: 19:16:34.073: Unexpectedly, UWP app `Microsoft.ScreenSketch_11.2303.17.0_x64__8wekyb3d8bbwe' (AUMId `Microsoft.ScreenSketch_8wekyb3d8bbwe!App') supports 29 extensions but has no verbs (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.088: ../src/vncconnection.c Do TLS handshake (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.089: ../src/vncconnection.c Checking if credentials are needed (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.092: ../src/vncconnection.c Want a TLS clientname (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.094: ../src/vncconnection.c Requesting missing credentials (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.102: ../src/vncconnection.c Emit main context 10 (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:34.105: Got VNC credential request for 1 credential(s) (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.105: ../src/vncconnection.c Set credential 2 libvirt (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.106: ../src/vncconnection.c Searching for certs in /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.108: ../src/vncconnection.c Failed to find certificate CA/cacert.pem (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.109: ../src/vncconnection.c No CA certificate provided, using GNUTLS global trust (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.111: ../src/vncconnection.c Failed to find certificate CA/cacrl.pem (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.113: ../src/vncconnection.c Failed to find certificate libvirt/private/clientkey.pem (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.113: ../src/vncconnection.c Failed to find certificate libvirt/clientcert.pem (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.114: ../src/vncconnection.c Waiting for missing credentials (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.117: ../src/vncconnection.c Got all credentials ( remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.120: ../src/vncconnection.c No CA certificate provided; trying the system trust store instead (remote-viewer.exe:9460): GLib-GIO-WARNING **: 19:16:34.120: Unexpectedly, UWP app `Clipchamp.Clipchamp_2.6.2.0_neutral__yxz26nhyzhsrt' (AUMId `Clipchamp.Clipchamp_yxz26nhyzhsrt!App') supports 41 extensions but has no verbs (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.132: ../src/vncconnection.c Using the system trust store and CRL (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.132: ../src/vncconnection.c No client cert or key provided (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.133: ../src/vncconnection.c No CA revocation list provided (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.133: ../src/vncconnection.c Error: Failed to complete handshake Error in the pull function. (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.134: ../src/vncconnection.c Emit main context 16 (remote-viewer.exe:9460): virt-viewer-WARNING **: 19:16:34.134: vnc-session: got vnc error Failed to complete handshake Error in the pull function. (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.135: ../src/vncdisplay.c VNC server error (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.135: ../src/vncconnection.c Auth failed (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.135: ../src/vncconnection.c Doing final VNC cleanup (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.136: ../src/vncconnection.c Close VncConnection=00000000070f1c90 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.136: ../src/vncconnection.c Emit main context 15 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.137: ../src/vncdisplay.c Disconnected from VNC server (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:34.137: Not removing main window 0 00000000044694d0 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.138: ../src/vncdisplay.c Grab sequence is now (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:34.138: Disconnected (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:47.126: close vnc=00000000070ec090 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.127: ../src/vncconnection.c Init VncConnection=00000000053f6af0 (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.127: ../src/vncdisplaykeymap.c Using Win32 virtual keycode mapping (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.128: ../src/vncdisplay.c Grab sequence is now Control_L+Alt_L (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.129: ../src/vncdisplay.c Display destroy, requesting that VNC connection close (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.129: ../src/vncdisplay.c Releasing VNC widget (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.129: ../src/vncconnection.c Finalize VncConnection=00000000053f6af0 The solutions provided here was not successfull https://access.redhat.com/solutions/6217601 BR R A

1 0

Constant vdsmd ssl handshake errros on all node (system seems to be ok) - can you help track down error / cinfirm i can ignore ?
by morgan cox 23 Jun '23

23 Jun '23

Hi. I have a (mostly) working Ovirt setup - i.e everything is working as far as I can tell. I have a 'standalone Manager with local databases' setup and several nodes. On all nodes I see this error constantly produced ----- Jun 23 15:50:26 ovirt-node2 vdsm[10344]: ERROR ssl handshake: socket error, address: ::ffff:127.0.0.1 Jun 23 15:50:26 ovirt-node2 vdsm[10344]: WARN unhandled write event ----- As mentioned everything seems to be working, all nodes are up, I can update them , etc. Is the error perhaps related to no ipv6 access and I can safely ignore ? I have an installed cert (not self signed) which i have added to the web ui - could this be connected ? If so can someone confirm which certs and ca should be the same/match (engine and nodes)? One issue I am having is that live migration seems to randomly fail (i.e message is migration was cancelled) could see anything obvious looking at the logs

1 0

Customizing ovirt vm / user web portal
by R A 23 Jun '23

23 Jun '23

Hello, i want to customize the interface and some functions in the ovirt user portal. For example adding some Buttons with functionality or doing some style changes. Is this possible? Is there any guide how to do that? BR Peter

1 0

Ovirt and packer integration
by cello86＠gmail.com 22 Jun '23

22 Jun '23

Hi All, we're checking some integration with packer and ovirt to automatically generate templates for the golden image used by terraform. We found this outdated repo https://github.com/ganto/packer-builder-ovirt. Could you help us to verify the possibility to integrate Ovirt 4 with Hashicorp Packer? Thanks, Marcello

3 4

ovirt and terraform disk size issue on template creation
by cello86＠gmail.com 22 Jun '23

22 Jun '23

Hi, I tried to create a VM from an OVF template imported on ovirt 4 but the VM has a disk size of 2 GBs and if I tried to attach a different disk this operation gone in timeout. I understand that you have to create the vm and assign disk and nic after the creation but I do not fully understand the templates attachments override option. Can you help me to understand the correct procedure to set the correct space on the new vm? Thanks, Marcello

1 0

PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
by grig.4n＠gmail.com 20 Jun '23

20 Jun '23

Hello. web access on ovirt-engine is not working. find information about certificate renewal: hosted-engine --set-maintenance --mode=global !! Cluster is in GLOBAL MAINTENANCE mode !! run engine-setup --offline Renew certificates? (Yes, No) [No]: yes but got an error [ ERROR ] It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode. In that case you should put the system into the "Global Maintenance" mode before running engine-setup, or the hosted-engine HA agent might kill the machine, which might corrupt your data. [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup detected, but Global Maintenance is not set.

2 4

VM migration failed after upgrade to 4.4
by joris dedieu 20 Jun '23

20 Jun '23

Hi list, I'm troubleshooting an issue with live migration on an upgrade context. I have a 4.3 cluster that I try to upgrade in 4.4. The engine is OK in 4.4 and I already have upgraded a single host which had kindly reintegrated the cluster. The host is OK. I can start vms on it and migrate vms from it to other hosts. But, if I try to migrate a vm from a 4.3 host to the 4.4 host, it failed with : * on the host : qemu-kvm: terminating on signal 15 from pid XXXX (<unknown process>) * on the engine : VM 'VM_UUID' was unexpectedly detected as 'Down' on VDS 'HOST_UUID' Does anyone here can help me to find what's goning on ? I will be greate regards Joris

3 2

Cannot start VM with vGPU (NVIDIA)
by pawel.osadtschy01＠dhl.com 20 Jun '23

20 Jun '23

Hi, need a help! may be the problem is very simple, but I've not found solution: -oVirt 4.5.4 on RHEL 8.7 -amd_iommu is on on the Host with Nvidia Card A40 I can see my cards in vGPU Settings for Windows VMs (Windows 10 Pro). Without activation of the vGPU device VM started normally. With one active vGPU card VM cannot start. Error message on the Host: Jun 07 13:39:51 depotlsa8ovh1 kernel: [nvidia-vgpu-vfio] e80ae200-4cea-4213-9e78-ebf0b86a756a: start failed. status: 0x0 Timeout Occured Jun 07 13:39:51 depotlsa8ovh1 libvirtd[3278]: Kann nicht vom Monitor lesen: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt Jun 07 13:39:51 depotlsa8ovh1 libvirtd[3278]: Interner Fehler: qemu unexpectedly closed the monitor: 2023-06-07T11:39:51.494056Z qemu-kvm: -device vfio-pci-nohotplug,id=hostdev0,sysfsdev=/sys/bus/mdev/devices/e80ae200-4cea-4213-9e78-ebf0b86a756a,display=on,ramfb=on,bus=pci.7,addr=0x0: vfio e80ae200-4cea-4213-9e78-ebf0b86a756a: error getting device from group 156: Connection timed out. Verify all devices in group 156 are bound to vfio-<bus> or pci-stub and not already in use. Looks like libvirtd cannot get any device. Is it problem of Nvidia settings on the host or Problem of VM settings? Thank you Paolo

3 3

Re: Resending with Log: Hosted Engine Deploy Fails at "Waiting for Host to be up"
by Gilboa Davara 16 Jun '23

16 Jun '23

Hello, I'm seeing the same when trying to install nightly on high-end server (Either direct over NFS or gluster cluster). Seems that oVirt deployment fails to change the HE IP address after deployment. I'm thinking about trying other options, such as switching to Oracle (Ugh!) / oVirt 4.4 which seems to be stable and has long term support. - Gilboa On Sun, Jun 11, 2023 at 4:30 PM Angel, Christopher < christopher.angel(a)usask.ca> wrote: > I’ve installed 3 Ovirt Nodes and am trying to set up the hosted engine. > Every time I run it however, it fails at the ‘Waiting for host to be up’ > stage. I’ve attached the relevant log. > > > > -- > > Christopher Angel, B.Eng, B.Sc > > Laboratory Systems Analyst, Computer Science Department > > University of Saskatchewan > > Christopher.angel(a)usask.ca > > 3069661434 > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/VN7NXEPRDA7O2… >

1 0

Unable to find a match: cockpit-ovirt-dashboard
by R A 15 Jun '23

15 Jun '23

Hello, maybe someone can help me. I am using ovirt 4.5 standalone engine with local database on Rocky Linux 9 on Server A. On Server B, C and D i ve installed ovirt Node 4.5 and now i want to user Gluster Hyperconverged via cockpit with 4 Server (one for standalone engine) Ovirt 4.5 Standalone Engine is already running on Server A. My Problem is i cant download cockpit-ovirt-dashboard [root@pluto volrath]# yum install cockpit-ovirt-dashboard Last metadata expiration check: 1:41:33 ago on Thu Jun 15 19:36:53 2023. No match for argument: cockpit-ovirt-dashboard Error: Unable to find a match: cockpit-ovirt-dashboard The instructions in Section "Installing on RHEL 9.0 or derivates" from here https://www.ovirt.org/download/install_on_rhel.html are done. But i am still not able to finde the cockpit-plugin. Ansible-Runner ist installed too. What i am missing? Or does Rocky Linux do not support the Cockpit-Plugin? BR Peter

1 0

Re: Resending with Log: Hosted Engine Deploy Fails at "Waiting for Host to be up"
by Thomas Hoberg 15 Jun '23

15 Jun '23

I have seen this type of behavior when building a HCI cluster on Atoms. The problem is that at this poing the machine that is generated for the management engine has a machine type that is above what is actually supported in hardware. Since it's not the first VM that is run during the setup process, it's not really intuitive but the libvirt configuration for that prototypical management engine is created by code that assumes to modern a default (I never found the source, but since all development has ceased it won't matter any more). While modern Atoms are actually more like Core CPUs in terms of the instruction set they support, my Goldmont Plus/Gemini Lake Atoms were regarded by KVM as next to a Nehalem CPU and the VM would refuse to start. It's very hard to find in the logs, because it is actually a KVM issue (created by the oVirt ME creation mechanism, of couse). I got out of that fix using removable storage: I had the setup run on an i7-7700k (was a bit faster, too) and then changed the machine type of the management engine (and lowest common denominator for the cluster) to Nehalem before transplanting the SSD back into the Atom. I've gone through that excercise with ovirt 4.3 and again with Oracle's 4.4 variant, which is by far the most stable oVirt/RHEV available right now.

1 0

Windows VMs pause ofte when disk images are located on CephFS storage
by change_jeeringly679＠dralias.com 15 Jun '23

15 Jun '23

Hey guys, I have tried to write on the IRC channel, regarding this issue, but I'm no sure if I'm not doing it right or maybe there are not many people watching the #ovirt channel. We have deployed a 6 node oVirt cluster, and have moved roughly 100 VMs on them. We started the cluster with NFS storage, which we were building and testing with our Ceph cluster. The Ceph has been ready for a few months now, and we have tested running oVirt VMs on it using RBD, CephFS and by using the NFS Ganesha server which can be enabled on Ceph. Initially I tested with RBD using the cinderlib functionality in oVirt. This appears to be working fine, and I can live with the fact tha live storage migrations from posix storage are not possible. The biggest hurdle vi encountered are, that the backup APIs in oVirt cannot be used to create a backup and download the backups. This breaks our RHV Veeam backup solution, which we have grown quite fond of. But even my homegrown backup solutions from earlier don't work either, as they use the APIs. For this reason we have now changed to CephFS. It has a different set of problems, as we can only supply 1 monitor when mounting the CephFS storage, making i less robust as it should be. It is also making metadata storage dependent on the MDS. As far as I understand, is data access still connecting to the OSDs where it resides directly. I have multiple MDS containers on the Ceph cluster for loadbalancing and redundancy, but it still feels less tidy than RBD with native Ceph support. The good thing is, that as CephFS is a POSIX filesystem, the backup APIs work and so does Veeam backup. The biggest problems I am struggling with, is the unexplained pausing of exclusively VMs running the Windows Operating system. This is why I didn't notice issues initially, as I have been testing the storage with Linux VMs. The machines pause at a random moment in time with a "Storage Error". I cannot resume the machine, not even using virsh on the host it is running on. The only thing I can do is power it off, and reboot. And in many cases, it then pauses during the boot process. I have been watching the VDSM logs, and couldn't work out why this happens. When I move the disk to plain NFS storage (not on Ceph), this never happens. The result is that most Windows based VMs have not been moved yet to CephFS. I have 0 occurrences of this happening with Linux VMs, of which I have many (I think we have 80 linux VMs vs 20 Windows VMs). The Ceph cluster does not show and problems before, during or after this happening. Is there anyone with experience wih oVirt and Ceph, that can share experiences or help me find the root cause of this problem? I have a couple of things I can progress wih: 1. Move a couple of Windows VMs to RBD, and install a Veeam agent on the servers instead. This is just opening a new can of worms, as it requires some work on the servers each time I add a new server and I also need to make network openings from the server to the backup repos. It is just a little less neat than the RHV Veeam backup solution using the hypervisor. 2. Move a couple of Windows VMs to the NFS Ganesha implementation. This means ALL traffic is going through the NFS containers created on the Ceph cluster, and I loose the distributed nature of the oVirt hosts talking direcly to the OSDs on the Ceph cluster. If I was to go this way, I should probably create some NFS Ganesha servers that connect to Ceph natively on the one end and provide NFS services to oVirt. Both tests would still test Ceph, but using an alternative method to CephFS. My preferred solution really is 1., was it not for the backup APIs being rendered useless. Is work still being carried out on development in these areas, or has oVirt/Ceph development ceased? Thoughts and comments are welcome. Looking forward to sparring with someone that has experience with this :-) With kind regards Jelle

1 0

RHEL 9 (rocky/centos/..) guest console problem
by marek 15 Jun '23

15 Jun '23

hi, i know spice/QXL is deprecated so, i have guest VM with console config VGA/VNC (tried Bochs/VNC too) virt-viewer from windows cannot connect to console ("console" button in ovirt admin) if i use VNC params from "console.vv" i can connect to it with tigerVNC client (tightVNC does not work) any ideas what can be wrong? btw is there option to prolong password in console.vv? there is note in the file "# Password is valid for 120 seconds." Marek

3 3

Trying to recover local domain from failed host
by Tim Tuck 15 Jun '23

15 Jun '23

Hi all, I had a catastrophic failure of a host with but the disk with the domain on it is fine. I've put the disk in a new machine, mounted it on /backups and I can see this structure ... [root@max backups]# ls -laR * 2f2da2d7-596f-4a53-8a1b-a301f84b3b74: total 20 drwxr-xr-x. 5 vdsm kvm 4096 Sep 15 2020 . drwxr-xr-x. 4 vdsm kvm 4096 Jun 10 11:53 .. drwxr-xr-x. 2 vdsm kvm 4096 Sep 15 2020 dom_md drwxr-xr-x. 23 vdsm kvm 4096 May 20 11:35 images drwxr-xr-x. 4 vdsm kvm 4096 Sep 15 2020 master 2f2da2d7-596f-4a53-8a1b-a301f84b3b74/dom_md: total 32780 drwxr-xr-x. 2 vdsm kvm 4096 Sep 15 2020 . drwxr-xr-x. 5 vdsm kvm 4096 Sep 15 2020 .. -rwxr-xr-x. 1 vdsm kvm 0 Sep 15 2020 ids -rwxr-xr-x. 1 vdsm kvm 16777216 Sep 15 2020 inbox -rwxr-xr-x. 1 vdsm kvm 0 Sep 15 2020 leases -rwxr-xr-x. 1 vdsm kvm 486 Sep 15 2020 metadata -rwxr-xr-x. 1 vdsm kvm 16777216 Sep 15 2020 outbox 2f2da2d7-596f-4a53-8a1b-a301f84b3b74/images: total 92 drwxr-xr-x. 23 vdsm kvm 4096 May 20 11:35 . drwxr-xr-x. 5 vdsm kvm 4096 Sep 15 2020 .. drwxr-xr-x. 2 vdsm kvm 4096 Feb 3 2021 1eb2b682-ef45-409d-9341-abcf61418619 drwxr-xr-x. 2 vdsm kvm 4096 Aug 11 2022 283838fd-43b5-42b9-a332-a7b980613188 drwxr-xr-x. 2 vdsm kvm 4096 Oct 4 2020 36237183-54a2-4232-b0b3-6d1a9457c23a drwxr-xr-x. 2 vdsm kvm 4096 Jan 5 2022 366e7b29-2123-45c0-9190-dafead431651 drwxr-xr-x. 2 vdsm kvm 4096 May 20 09:29 3ea98df5-3ee8-4d21-8607-94284e7fff37 drwxr-xr-x. 2 vdsm kvm 4096 May 20 09:29 44c3611b-1205-48ca-9a84-007eaae03cbb drwxr-xr-x. 2 vdsm kvm 4096 May 18 23:49 674b364c-b74a-4fff-a38b-ca1089103241 drwxr-xr-x. 2 vdsm kvm 4096 Oct 15 2021 6949a9e0-4cc0-4eee-be99-e88795cd6447 drwxr-xr-x. 2 vdsm kvm 4096 Jan 5 2022 8b618bad-6dfb-48de-90ad-f325bf50cd45 drwxr-xr-x. 2 vdsm kvm 4096 Feb 6 2021 91f1f606-0f26-4ef0-a2fe-cccde6c78e89 drwxr-xr-x. 2 vdsm kvm 4096 May 20 11:35 94f4bf41-2b2f-42bc-ae21-0e80205ba19a drwxr-xr-x. 2 vdsm kvm 4096 May 20 11:35 a18f0c48-b3ac-4b89-9e52-fddaddbc8f4a drwxr-xr-x. 2 vdsm kvm 4096 May 26 15:51 ac4a428d-961e-46ae-a279-f282fd9ecf94 drwxr-xr-x. 2 vdsm kvm 4096 May 26 15:51 ba1a624c-6995-4109-b770-7bbd1efc340e drwxr-xr-x. 2 vdsm kvm 4096 Sep 15 2020 dec14b5b-69fe-4c51-abb4-d8296c547a0b drwxr-xr-x. 2 vdsm kvm 4096 Sep 15 2020 e7a17f3b-7567-4c90-b58e-18f34d4686c0 drwxr-xr-x. 2 vdsm kvm 4096 May 20 09:29 ea786bee-b98e-44c0-a44a-a63af63b8c51 drwxr-xr-x. 2 vdsm kvm 4096 Apr 21 2021 ec37f395-3b4b-41df-8f5b-8a22b7e1273b drwxr-xr-x. 2 vdsm kvm 4096 Feb 25 2022 f3e641c7-a2cc-42af-bcd1-b5ecdf437e03 drwxr-xr-x. 2 vdsm kvm 4096 May 18 23:55 f4c221a6-6ce4-44cc-8d32-d673e40aa915 drwxr-xr-x. 2 vdsm kvm 4096 May 20 11:35 f539c098-3f16-410f-938f-3de6ef37b017 2f2da2d7-596f-4a53-8a1b-a301f84b3b74/images/1eb2b682-ef45-409d-9341-abcf61418619: total 104857624 drwxr-xr-x. 2 vdsm kvm 4096 Feb 3 2021 . drwxr-xr-x. 23 vdsm kvm 4096 May 20 11:35 .. -rwxr-xr-x. 1 vdsm kvm 107374182400 Feb 3 2021 e29b005f-d272-49f8-a162-41f908ca67a4 -rwxr-xr-x. 1 vdsm kvm 300 Feb 3 2021 e29b005f-d272-49f8-a162-41f908ca67a4.meta 2f2da2d7-596f-4a53-8a1b-a301f84b3b74/images/283838fd-43b5-42b9-a332-a7b980613188: total 23223760 drwxr-xr-x. 2 vdsm kvm 4096 Aug 11 2022 . drwxr-xr-x. 23 vdsm kvm 4096 May 20 11:35 .. -rwxr-xr-x. 1 vdsm kvm 23781113856 Aug 11 2022 3273221e-1649-4e4a-816c-2ffec18e51c7 -rwxr-xr-x. 1 vdsm kvm 251 Aug 11 2022 3273221e-1649-4e4a-816c-2ffec18e51c7.meta . . etc So... is there a way to get this back ? I tried "Import Domain" both with the disk manually mounted and unmounted, both failed and I get errors in the vdsm.log like this... 2023-06-15 15:57:55,166+1000 INFO (jsonrpc/0) [storage.StorageServer.MountConnection] Creating directory '/rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74' (storageServer:167) 2023-06-15 15:57:55,166+1000 INFO (jsonrpc/0) [storage.fileUtils] Creating directory: /rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74 mode: None (fileUtils:201) 2023-06-15 15:57:55,166+1000 INFO (jsonrpc/0) [storage.Mount] mounting /backups/2f2da2d7-596f-4a53-8a1b-a301f84b3b74 at /rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74 (mount:207) 2023-06-15 15:57:55,176+1000 ERROR (jsonrpc/0) [storage.HSM] Could not connect to storageServer (hsm:2374) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2371, in connectStorageServer conObj.connect() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 180, in connect six.reraise(t, v, tb) File "/usr/lib/python3.6/site-packages/six.py", line 693, in reraise raise value File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 171, in connect self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP) File "/usr/lib/python3.6/site-packages/vdsm/storage/mount.py", line 210, in mount cgroup=cgroup) File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in mount File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod raise convert_to_error(kind, result) vdsm.storage.mount.MountError: Command ['/usr/bin/mount', '-t', 'posix', '/backups/2f2da2d7-596f-4a53-8a1b-a301f84b3b74', '/rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74'] failed with rc=32 out=b'' err=b"mount: /rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74: unknown filesystem type 'posix'.\n" 2023-06-15 15:57:55,176+1000 INFO (jsonrpc/0) [storage.StorageDomainCache] Invalidating storage domain cache (sdc:74) 2023-06-15 15:57:55,176+1000 INFO (jsonrpc/0) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'id': '00000000-0000-0000-0000-000000000000', 'status': 477}]} from=::ffff:172.20.1.160,47702, flow_id=6693c76d-b62b-4e62-9b70-c87f2a199705, task_id=682abcff-3040-46d7-aaa1-f2445f0a6698 (api:54) 2023-06-15 15:57:55,283+1000 INFO (jsonrpc/2) [vdsm.api] START disconnectStorageServer(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'vfs_type': 'posix', 'port': '', 'iqn': '', 'connection': '/backups/2f2da2d7-596f-4a53-8a1b-a301f84b3b74', 'ipv6_enabled': 'false', 'id': '00000000-0000-0000-0000-000000000000', 'user': '', 'tpgt': '1'}]) from=::ffff:172.20.1.160,47702, flow_id=0d3d4a3e-3523-4436-93b3-e22bff47f082, task_id=11870123-365d-4b40-b481-be5d44098fc2 (api:48) 2023-06-15 15:57:55,284+1000 INFO (jsonrpc/2) [storage.Mount] unmounting /rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74 (mount:215) 2023-06-15 15:57:55,290+1000 ERROR (jsonrpc/2) [storage.HSM] Could not disconnect from storageServer (hsm:2480) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2476, in disconnectStorageServer conObj.disconnect() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 202, in disconnect self._mount.umount(True, True) File "/usr/lib/python3.6/site-packages/vdsm/storage/mount.py", line 217, in umount umount(self.fs_file, force=force, lazy=lazy, freeloop=freeloop) File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in umount File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod raise convert_to_error(kind, result) vdsm.storage.mount.MountError: Command ['/usr/bin/umount', '-f', '-l', '/rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74'] failed with rc=32 out=b'' err=b'umount: /rhev/data-center/mnt/_backups_2f2da2d7-596f-4a53-8a1b-a301f84b3b74: no mount point specified.\n' 2023-06-15 15:57:55,290+1000 INFO (jsonrpc/2) [storage.StorageDomainCache] Refreshing storage domain cache (resize=False) (sdc:80) 2023-06-15 15:57:55,290+1000 INFO (jsonrpc/2) [storage.ISCSI] Scanning iSCSI devices (iscsi:442) 2023-06-15 15:57:55,328+1000 INFO (jsonrpc/2) [storage.ISCSI] Scanning iSCSI devices: 0.04 seconds (utils:390) 2023-06-15 15:57:55,328+1000 INFO (jsonrpc/2) [storage.HBA] Scanning FC devices (hba:60) 2023-06-15 15:57:55,416+1000 INFO (jsonrpc/2) [storage.HBA] Scanning FC devices: 0.09 seconds (utils:390) 2023-06-15 15:57:55,416+1000 INFO (jsonrpc/2) [storage.Multipath] Waiting until multipathd is ready (multipath:112) 2023-06-15 15:57:57,458+1000 INFO (jsonrpc/2) [storage.Multipath] Waited 2.04 seconds for multipathd (tries=2, ready=2) (multipath:139) 2023-06-15 15:57:57,458+1000 INFO (jsonrpc/2) [storage.StorageDomainCache] Refreshing storage domain cache: 2.17 seconds (utils:390) 2023-06-15 15:57:57,458+1000 INFO (jsonrpc/2) [vdsm.api] FINISH disconnectStorageServer return={'statuslist': [{'id': '00000000-0000-0000-0000-000000000000', 'status': 477}]} from=::ffff:172.20.1.160,47702, flow_id=0d3d4a3e-3523-4436-93b3-e22bff47f082, task_id=11870123-365d-4b40-b481-be5d44098fc2 (api:54) 2023-06-15 15:57:57,458+1000 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call StoragePool.disconnectStorageServer took more than 1.00 seconds to succeed: 2.18 (__init__:316) any help appreciated thanks Tim

1 0

self-hosted engine with Local Storage
by Jorge Visentini 14 Jun '23

14 Jun '23

Hello. I know that there is no logic, that there is no HA, redundancy and all that... but is there any possibility that I can deploy the oVirt self-hosted engine using an array of local disks on the host? *In my scenario I don't need to have HA.* *What I need:* 1 host with a self-hosted mechanism on a local domain store, that's all. On this host I will locally run some old VMs. Isolated VMs. -- Att, Jorge Visentini +55 55 98432-9868

2 7

oVirt 4.4 - High Performance VMs with Direct LUN attached disks pause when an upstream SAN path failed
by angus＠ajct.uk 14 Jun '23

14 Jun '23

Hello Our SAN engineer performed some maintenance during which time the KVM host lost 2 of the 4 paths to storage. My High Performance VMs with Direct LUN disks with SCSI-Pass-Through enabled paused and had to be rebooted resolve. Other VMs (not High Performance, no Direct LUN disks) on the same host were unaffected. What do you think? Thanks Angus

1 0

Cinder and Managed Block Storage
by Jorge Visentini 12 Jun '23

12 Jun '23

Is it still possible to configure cinder to use Managed Block Storage? If yes, is there a particular setting or can I just stick to Cinder's default setting? Thanks all. -- Att, Jorge Visentini +55 55 98432-9868

2 1

Had issue with storage and now storage domain won't mount VMs are in unknown status
by jsmith1299＠live.com 12 Jun '23

12 Jun '23

Hi All, We have an odd setup in out environment but each storage data center has one host and one storage domain. We had an issue with the storage domain attached to a host. After the reboot I am seeing in the vdsm logs over and over again vmrecovery 2023-06-09 21:01:30,419+0000 INFO (periodic/2) [vdsm.api] START repoStats(domains=()) from=internal, task_id=40f5b198-cb82-4ba2-8c20-b8cee34a7f47 (api:48) 2023-06-09 21:01:30,420+0000 INFO (periodic/2) [vdsm.api] FINISH repoStats return={} from=internal, task_id=40f5b198-cb82-4ba2-8c20-b8cee34a7f47 (api:54) 2023-06-09 21:01:30,810+0000 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=74b1a1cf-fab1-4918-b0da-b3fd152d9d1a (api:48) 2023-06-09 21:01:30,811+0000 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=74b1a1cf-fab1-4918-b0da-b3fd152d9d1a (api:54) 2023-06-09 21:01:30,811+0000 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) I've also checked the firewall and it is still disabled. systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─unlimited-core.conf Active: active (running) since Fri 2023-06-09 20:51:11 UTC; 16min ago Docs: man:libvirtd(8) https://libvirt.org Main PID: 4984 (libvirtd) Tasks: 17 (limit: 32768) Memory: 39.7M CGroup: /system.slice/libvirtd.service └─4984 /usr/sbin/libvirtd --listen Jun 09 20:51:11 hlkvm01 systemd[1]: Starting Virtualization daemon... Jun 09 20:51:11 hlkvm01 systemd[1]: Started Virtualization daemon. ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-06-09 20:53:11 UTC; 14min ago Process: 10496 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 10587 (vdsmd) Tasks: 39 Memory: 79.5M CGroup: /system.slice/vdsmd.service └─10587 /usr/bin/python2 /usr/share/vdsm/vdsmd Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|596001c3-33e7-44a4-bdf9-0b53ab1dd810' args={'596001c3-33e7-44a4-bdf9-0b53ab1dd810': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-2283890943663580625', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '596001c3-33e7-44a4-bdf9-0b53ab1dd810', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893978', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|87155499-1e10-4228-aa69-7c487007746e' args={'87155499-1e10-4228-aa69-7c487007746e': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-5453960159391982695', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '87155499-1e10-4228-aa69-7c487007746e', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893973', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|0ec7a66d-fac2-4a4a-a939-e05fc7b097b7' args={'0ec7a66d-fac2-4a4a-a939-e05fc7b097b7': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-1793949836195780752', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '0ec7a66d-fac2-4a4a-a939-e05fc7b097b7', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893976', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|9c8802c3-c7c9-473c-bbfb-abb0bd0f8fdb' args={'9c8802c3-c7c9-473c-bbfb-abb0bd0f8fdb': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-1144924804541449415', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '9c8802c3-c7c9-473c-bbfb-abb0bd0f8fdb', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893971', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|f799c326-9969-4892-8d67-3b1229baf0ef' args={'f799c326-9969-4892-8d67-3b1229baf0ef': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '5564598485369155833', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': 'f799c326-9969-4892-8d67-3b1229baf0ef', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893980', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|e9311d9f-d770-458b-b5ad-cdc2eb35f1bd' args={'e9311d9f-d770-458b-b5ad-cdc2eb35f1bd': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-5622951617346770490', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': 'e9311d9f-d770-458b-b5ad-cdc2eb35f1bd', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893972', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|1fc4ddad-203f-4cdf-9cb3-c3d66fb97c87' args={'1fc4ddad-203f-4cdf-9cb3-c3d66fb97c87': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-1397731328049024241', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '1fc4ddad-203f-4cdf-9cb3-c3d66fb97c87', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893981', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|321183ed-b0a6-42c7-bbee-2ad46a5f37ae' args={'321183ed-b0a6-42c7-bbee-2ad46a5f37ae': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '4398712824561987912', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '321183ed-b0a6-42c7-bbee-2ad46a5f37ae', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893970', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|731a11e8-62ba-4639-bdee-8c44b5790d82' args={'731a11e8-62ba-4639-bdee-8c44b5790d82': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-1278467655696539707', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '731a11e8-62ba-4639-bdee-8c44b5790d82', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893977', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} Jun 09 20:53:14 hlkvm01 vdsm[10587]: WARN Not ready yet, ignoring event '|virt|VM_status|411a97e6-41c7-473e-819b-04aa10bc2bf0' args={'411a97e6-41c7-473e-819b-04aa10bc2bf0': {'status': 'Down', 'displayInfo': [{'tlsPort': '-1', 'ipAddress': '0', 'type': 'vnc', 'port': '-1'}], 'hash': '-11964682092647781', 'exitMessage': 'VM terminated with error', 'cpuUser': '0.00', 'monitorResponse': '0', 'vmId': '411a97e6-41c7-473e-819b-04aa10bc2bf0', 'exitReason': 1, 'cpuUsage': '0.00', 'elapsedTime': '893975', 'cpuSys': '0.00', 'timeOffset': '0', 'clientIp': '', 'exitCode': 1}} This has been going on for hours. On the management VM I am seeing the following over and over again 2023-06-09 13:59:25,129-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM hlkvm01 command Get Host Capabilities failed: Message timeout which can be caused by communication issues 2023-06-09 13:59:25,129-07 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Unable to RefreshCapabilities: VDSNetworkE xception: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues I am able to restart the Host from the management VM (Web Console). When I try to put the host in maintenance mode I get "Error while executing action. Cannot switch Host to Maintenance mode. Hose still has running VMs on it and is in Non Responsive state" If I try to set the "Confirm host has been rebooted" I get an error saying that another power management action is already in progress. Can someone please help me out here? Is there a way to set the manage for all of the VMs to down? Anything I can do to get the storage domain back up? Thanks

1 1

Tutorial: How to Fix Struck Zombie VM Problem
by Andrei Verovski 12 Jun '23

12 Jun '23

Hi, I made short video tutorial on Youtube - how to fix struck zombie VM problem. https://www.youtube.com/watch?v=vm55caHxRj8 with best regards Andrei

1 0

how to expand a arbitrated-distributed-replicated volume
by Hans Kuhl 11 Jun '23

11 Jun '23

Hello all, how can I expand a arbitrated-distributed-replicated volume without adding additional arbiter bricks? my current gluster config is: Volume Name: data Type: Distributed-Replicate Volume ID: dcf75cf7-1937-4ce9-a7d0-46a56a3be4b4 Status: Started Snapshot Count: 0 Number of Bricks: 3 x (2 + 1) = 9 Transport-type: tcp Bricks: Brick1: gl1.lan:/gluster_bricks/sdc/sdc Brick2: gl2.lan:/gluster_bricks/sdc/sdc Brick3: gl3.lan:/gluster_bricks/sdx/sdx (arbiter) Brick4: gl2.lan:/gluster_bricks/sdd/sdd Brick5: gl3.lan:/gluster_bricks/sdc/sdc Brick6: gl1.lan:/gluster_bricks/sdx/sdx (arbiter) Brick7: gl3.lan:/gluster_bricks/sdd/sdd Brick8: gl1.lan:/gluster_bricks/sdd/sdd Brick9: gl2.lan:/gluster_bricks/sdx/sdx (arbiter)

2 1

Non responsive host (4.3.10)
by Maria Souvalioti 08 Jun '23

08 Jun '23

Hello everyone! Due to a recent major power outage in my area I now have an unresponsive self hosted host in an environment of 3 self hosted hosts. There's one vm stuck on there as well as some metadata I guess from when hosted engine was running there (before the power went down). I'm running 4.3.10 ovirt node with 3 nodes and GlusterFS, no arbiter, and I'm using it to provide services to our clients i.e. DNS, web sites, wikis, ticketing etc. and I cannot shut them down. The ovirt engine is up and running and I can manage all the other VMs that run on the other hosts through the web gui. The unresponsive host replies only to ICMP requests; in every other sense it's dead, no ssh, no gluster bricks, no console, nothing. I tried to place the faulty host in maintenance, using the option to stop glusterd, but wasn't able to as the engine won't let the host go into maintenance mode because it thinks the host has running VMs on it. The host won't go into maintenance even if I chose the "Ignore gluster quorum and self-heal validations" option. I spent last week creating a backup environment were I copied the VMs, to have somewhere to run them in case something goes terribly wrong with the systems or the gluster in the production system. I'm thinking of using the global maintenance mode and then shutting down the engine itself with *hosted-engine --vm-shutdown* and rebooting the affected host. Should I remove the host from the cluster and then re-add it or should I do something else? Thanks for any of your help!

3 4

Renew the engine certificate - egine-setup
by Fabrice Soler 08 Jun '23

08 Jun '23

Hello, We have an standalone engine version 4.3.6 and we try to renew the engine certificate. We have followed the official documentation but the engine-setup never ask us the question "Renew certificate ?" Do you have an idea ? Sincerely, -- Carte de visite DSI-DIT *Fabrice SOLER* Responsable du Département des Infrastructures Techniques (DIT) /Rectorat de la Guadeloupe - BP 480/ 97183 Les Abymes cedex *Téléphone : *0590 47 8321 +590 690 335 564 *Courriel*: www.ac-guadeloupe.fr

1 0

Rename Virtual Machine
by lavi.buchnik＠exlibrisgroup.com 08 Jun '23

08 Jun '23

Hi, We have this scenario: - VM running Centos-7 - VM running Oracle-8 Then, we shutdown and delete Centos-7 VM (verified by API and UI) Then, we rename Oracle-8 VM (via API) to have the name of the old Centos-7 VM and then stop/start Oracle-8 VM. Rename is working and VM is coming up (status is "up" from API and also in the UI). The problem is that Oracle-8 VM is not really up. it is hanging. not replying to PING nor to SSH. Seems like the root cause is this: - Oracle-8 VM name is indeed Centos-7 VM. but its FQDN (seen in UI) is still its Original name. - So when getting both Centos-7 VM name and Oracle-8 VM name status, I get an answer (via API) about both of them: Both reply with "up" I'm using a simple API to rename the VM as followed (vm_name is Oracle-8 VM name, and new_name is Centos-7 VM name): vm_id_obj = self.get_vm_id(vm_name) updated_vm = vm_id_obj.update( vm=types.Vm( name=new_name ) ) Thanks, Lavi

1 0

VM disks Block device
by hemak88＠gmail.com 08 Jun '23

08 Jun '23

LVM is used underneath the storage domain for disk management in kvm cluster on ovirt. VG which is the storage domain is visbile and active in all hosts in the same datacenter on ovirt. But, LV under this vg (that is the virtual disks of vms) is not active and the corresponding block devices of these LVs is not available on all hosts in cluster. I find only the running VMs LVs are active on the corresponding host. Is this a feature? Is it possible to get a corresponding block device and LV on all hosts in cluster?

3 2

Resending with Log: Hosted Engine Deploy Fails at "Waiting for Host to be up"
by Angel, Christopher 07 Jun '23

07 Jun '23

I've installed 3 Ovirt Nodes and am trying to set up the hosted engine. Every time I run it however, it fails at the 'Waiting for host to be up' stage. I've attached the relevant log. -- Christopher Angel, B.Eng, B.Sc Laboratory Systems Analyst, Computer Science Department University of Saskatchewan Christopher.angel(a)usask.ca<mailto:Christopher.angel@usask.ca> 3069661434

1 0

Ovirt Error after creating a VM image
by lavi.buchnik＠exlibrisgroup.com 07 Jun '23

07 Jun '23

Hi, I wrote an automation that provisioning a VM using ovirtsdk4 (we are using Ovirt 4.3). In the last week, we notice that sometimes the VM provisioning is failing with this error: "The response content type 'text/html; charset=iso-8859-1' isn't the expected XML" This error is happening when the automation is creating the VM image and waiting for its status to get change from "image-locked", this to be able to set affinity on it and later to start the new VM. So the error is happening while the image is in "image-locked" state. Can you please let me know why it is happening (note that it is occurring like 1 out of 4 attempts) and how can it get fixed? Thanks, Lavi

1 0

Unable to add more than 16 vCPUs to running VM
by David White 06 Jun '23

06 Jun '23

I have a fully patched / up-to-date engine: Software Version:4.5.4-1.el8 And a fully patched, up-to-date host. [root@cha3-storage dwhite]# yum info ovirt-hostLast metadata expiration check: 1:33:40 ago on Sun 04 Jun 2023 09:28:39 AM EDT. Installed Packages Name : ovirt-host Version : 4.5.0 Release : 3.el8 Architecture : x86_64 Size : 11 k Source : ovirt-host-4.5.0-3.el8.src.rpm Repository : @System From repo : centos-ovirt45 The host has 32GB of RAM, and there's only 1 VM on this host. When I try to add more CPUs to the VM from the manager UI, I get the following error: - The requested number of vCPUs is not available on the host the VM is running on What's going on here, and why can I not add more vCPUs to this VM? Sent with Proton Mail secure email.

2 3

oVirt 4.4 - Integrate event notifications with System Center Operations Manager
by angus＠ajct.uk 02 Jun '23

02 Jun '23

Hello I am looking to integrate oVirt 4.4 event notifications with an incident management tool - M$ System Center Operations Manager. I need to give examples to SCOM of what an unhealthy email looks like and what a recover/healthy email looks like for each event I want it to manage. Is there a way of triggering sample notifications (something failed/something recovered) for events or perhaps I can see the email templates used somewhere? (I did try a grep -Hr on the engine VM for "alertMessage" and "resolveMessage" for a VM migration notification but only found an entry in the in the notifier log. Thanks Angus

1 0

Regarding oVirt IP Address Change
by Pro Cloudguru 02 Jun '23

02 Jun '23

Hello oVIrt Community, Presently, I've a healthy & running oVirt Hosting that includes single DC, Cluster, SPM & Storage. The LAN IP Address range is 10.151.65.0/24. As we're in the process of migrating office premises, I'm worried about the existing oVirt IP Address Schema as the new range is 10.101.160/0/20. In this scenario, I'd like to know how the migration happens successfully without disturbing the oVirt Hosting & all hosted VMs. Please Guide, *Nishith N. Vyas*

1 0

novnc console error: promise.js missing?
by karl.morgan＠gmail.com 02 Jun '23

02 Jun '23

Seeing the following on the engine when attempting to start a novnc console 2023-03-31 11:57:34,988-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-29) [307c22a9] START, SetVmTicketVDSCommand(HostName = ov2node02-mn, SetVmTicketVDSCommandParameters:{hostId='19a92de3-c6e4-4f4e-be31-1d5533a2b6b6', vmId='4481b0e9-a96c-4ee7-8bd2-572558eb9fda', protocol='VNC', ticket='LMl903dd', validTime='120', userName='admin@ovirt', userId='9e88a363-34cb-466a-8ba9-25e46819423b', disconnectAction='LOCK_SCREEN', consoleDisconnectActionDelay='0'}), log id: 1d6520d5 2023-03-31 11:57:35,031-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-29) [307c22a9] FINISH, SetVmTicketVDSCommand, return: , log id: 1d6520d5 2023-03-31 11:57:35,044-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [307c22a9] EVENT_ID: VM_SET_TICKET(164), User admin@ovirt@internalkeycloak-authz initiated console session for VM first 2023-03-31 11:57:35,158-07 INFO [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29) [] Can't read file '/usr/share/ovirt-engine/files/novnc/vendor/promise.js' for request '/ovirt-engine/services/files/novnc/vendor/promise.js' -- 404 Curious if this is obvious to anyone? How to resolve? ovirt-engine-webadmin-portal-4.5.4-1.el9.noarch ovirt-engine-4.5.4-1.el9.noarch

2 1

troubleshooting SHE - Run engine-setup with answerfile - ?
by lejeczek 01 Jun '23

01 Jun '23

Hi guys. I'm revisiting my failed attempt to make friends with oVirt - novice so go easy on me. Deployment fails sooner that what can troubleshoot - at least I manged to find in docs so far - and I wanted to ask hot to troubleshot such failure as this: ... INFO ] TASK [ovirt.ovirt.engine_setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> 192.168.1.209]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:08:05.997322", "end": "2023-06-01 13:07:15.932517", "msg": "non-zero return code", "rc": 1, "start": "2023-06-01 12:59:09.935195", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ INFO ] Stage: Environment setup\n Configuration files:\n ... Start with setting up Keycloak for Ovirt Engine", "[ ERROR ] Failed to execute stage 'Closing up': Command '/usr/share/ovirt-engine-keycloak/bin/kk_cli.sh' failed to execute", "[ INFO ] Stage: Clean up", " Log file is located at", " /var/log/ovirt-engine/setup/ovirt-engine-setup-20230601125911-448xvj.log", ... [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up ... Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20230601123237-rhwx8e.log Logfile to which 'stdout' points, shows nothing or I fail to find anything in it and/or understand it: ... 2023-06-01 13:07:17,716+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.1.209]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:08:05.997322", "end": "2023-06-01 13:07:15.932517", "msg": "non-zero return code", "rc": 1, "start": "2023-06-01 12:59:09.935195", "stderr": "", "stderr_lines": [], "stdout": ... or Ovirt Engine\n[ ERROR ] Failed to execute stage 'Closing up': Command '/usr/share/ovirt-engine-keycloak/bin/kk_cli.sh' failed to execute\n[ INFO ] Stage: Clean up\n Log file is located at\n /var/log/ovirt-engine/setup/ovirt-engine-setup-20230601125911-448xvj.log\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20230601130714-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ INFO ] Stage: Environment setup", " Configuration files:", " /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf,", " /etc/ovirt-engine-setup.conf.d/10-packaging.conf," ... ... 2023-06-01 13:08:52,946+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': "The tas k includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined. 'local_vm_ip' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_ma chine.yml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appear s to be:\n\n---\n- name: Set the name for add_host\n ^ here\n", '_ansible_no_log': False} 2023-06-01 13:08:53,047+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 ignored: [localh ost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined. 'local _vm_ip' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_eng ine_setup/tasks/sync_on_engine_machine.yml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax prob lem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for add_host\n ^ here\n"} ... 2023-06-01 13:09:16,818+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': True, 'stdout': '', 'stderr': "error: Failed to destroy pool 9ab14cca-78e0-4a8e-8a1b-00e98c300208\nerror: Requested operation is not valid: storage pool '9ab14cca-78e0-4a8e-8a1b-00e98c300208' is not active", 'rc': 1, 'cmd': ['virsh', '-c', 'qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf', 'pool-destroy', '9ab14cca-78e0-4a8e-8a1b-00e98c300208'], 'start': '2023-06-01 13:09:16.614978', 'end': '2023-06-01 13:09:16.672260', 'delta': '0:00:00.057282', 'msg': 'non-zero return code', 'invocation': {'module_args': {'_raw_params': 'virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf pool-destroy 9ab14cca-78e0-4a8e-8a1b-00e98c300208', '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ['error: Failed to destroy pool 9ab14cca-78e0-4a8e-8a1b-00e98c300208', "error: Requested operation is not valid: storage pool '9ab14cca-78e0-4a8e-8a1b-00e98c300208' is not active"], '_ansible_no_log': None} 2023-06-01 13:09:16,918+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 ignored: [localhost]: FAILED! => {"changed": true, "cmd": ["virsh", "-c", "qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf", "pool-destroy", "9ab14cca-78e0-4a8e-8a1b-00e98c300208"], "delta": "0:00:00.057282", "end": "2023-06-01 13:09:16.672260", "msg": "non-zero return code", "rc": 1, "start": "2023-06-01 13:09:16.614978", "stderr": "error: Failed to destroy pool 9ab14cca-78e0-4a8e-8a1b-00e98c300208\nerror: Requested operation is not valid: storage pool '9ab14cca-78e0-4a8e-8a1b-00e98c300208' is not active", "stderr_lines": ["error: Failed to destroy pool 9ab14cca-78e0-4a8e-8a1b-00e98c300208", "error: Requested operation is not valid: storage pool '9ab14cca-78e0-4a8e-8a1b-00e98c300208' is not active"], "stdout": "", "stdout_lines": []} 2023-06-01 13:09:17,023+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool 9ab14cca-78e0-4a8e-8a1b-00e98c300208] 2023-06-01 13:09:17,224+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] .. I think that last two snippets-blocks, might be most useful - but what does it says? When 'installer' is finished, there is no aforementioned pool however there is: -> $ virsh pool-list | grep '9ab14cca-78e0-4a8e-8a1b-00e98c300208' 9ab14cca-78e0-4a8e-8a1b-00e98c300208-1 active yes Engine VM remains is up & running, How far from successful deployment that is & what would be advised to do next? many thanks, L.

1 0

OKD Installer Provisioned Infrastructure in oVirt > 4.3
by Fredrik Arneving 30 May '23

30 May '23

Hi, I've successfully installed OKD <= 4.8 in my ovirt 4.3 self-hosted engine setup. However, I have now found out that the imageio-proxy and/or imageio-deamon has changed it's API calls and ports to make the OKD install fail on self-hosted (all-in-one) setups on ovirt 4.4 and 4.5. Since I've upgraded to version 4.5 I can no longer install OKD with Installer Provisioned Infrastructure. I recently read throough a long thread in bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1871348) on how to get image uploads working from the GUI but haven't found any solutions for making the OKD install work. The suggested solution, engine-config -s "EnableImageioProxy=false", didn't solve my problem. Would it be possible to tweak the setup so that the OKD installer can upload it's image through imageio? I don't use the imageio service for anything else since I (almost) only kickstart my new vm's from my foreman servers so if other use cases than the OKD install would fail I can live with that. I take it the problem only appears for a self-hosted setup. If it was possible to migrate the engine to a standalone host (not a powerful compute node but somewhere with 4vCPU and 16 GB RAM) would that make the solution easier? I would lose a lot of my current infrastructure if I had to reinstall but if I can't find a better solution I will have to. Any help would be appreciated.

1 0

VM host deploy failed
by Latchezar Filtchev 30 May '23

30 May '23

Hi there, Centos Stream 8 fresh standalone install from nightly build of ovirt-engine. VM host Centos Stream 8 node nightly build repo enabled. Cannot add host to engine. The error message: Host n1 installation failed. Task Install ovirt-hosted-engine-setup package failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20230530094214-n1............. Any hint will be appreciated. Thank you! Best, Latcho 2023-05-30 09:42:26 EEST - { "uuid" : "e905de36-7b04-4b52-96b8-71855d561446", "counter" : 99, "stdout" : "fatal: [n1.aubgin.local]: FAILED! => {\"changed\": false, \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem: conflicting requests\\n - nothing provides python3-importlib-resources needed by ovirt-hosted-engine-setup-2.7.1-0.0.master.20230414113600.git340e19b.el8.noarch\", \"rc\": 1, \"results\": []}", "start_line" : 87, "end_line" : 88, "runner_ident" : "c7d833e9-8de3-4d53-87a3-72c3d80177ce", "event" : "runner_on_failed", "pid" : 41043, "created" : "2023-05-30T06:42:25.111204", "parent_uuid" : "ac162d01-a065-3587-db9e-000000000228", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "de0dd632-7d53-4e08-a06c-610334200c49", "play" : "all", "play_uuid" : "ac162d01-a065-3587-db9e-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "ac162d01-a065-3587-db9e-000000000228", "task_action" : "ansible.builtin.yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "n1.aubgin.local", "remote_addr" : "n1.aubgin.local", "res" : { "failures" : [ ], "results" : [ ], "rc" : 1, "msg" : "Depsolve Error occurred: \n Problem: conflicting requests\n - nothing provides python3-importlib-resources needed by ovirt-hosted-engine-setup-2.7.1-0.0.master.20230414113600.git340e19b.el8.noarch", "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "state" : "present", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "cacheonly" : 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, "sslverify" : true, "lock_timeout" : 30, "allowerasing" : false, "nobest" : false, "conf_file" : null, "disable_excludes" : null, "download_dir" : null, "list" : null, "releasever" : null } }, "_ansible_no_log" : null, "changed" : false }, "start" : "2023-05-30T06:42:23.217686", "end" : "2023-05-30T06:42:25.111007", "duration" : 1.893321, "ignore_errors" : null, "event_loop" : null, "uuid" : "e905de36-7b04-4b52-96b8-71855d561446" } } [root@e host-deploy]#

1 0

NIC Ordering
by Alan G 25 May '23

25 May '23

Is there any way to enforce NIC ordering so the vNICs match the ordering in the Engine UI? I found this but not clear if it was ever implemented? https://www.ovirt.org/develop/release-management/features/network/predictab…

3 6

ERROR HSMGetAllTasksStatusesVDS Cannot deactivate Logical Volume:
by parallax 25 May '23

25 May '23

Hello environment: oVirt 4.5.4-1 messages like this appear in the event log what do these errors mean? the volume 114f08c4-f864-44e1-a937-19405307e643 has 128m size ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-18) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM kvm3 command HSMGetAllTasksStatusesVDS failed: value=Cannot deactivate Logical Volume: 'error=General Storage Exception: ("5 [] [\' Logical volume 3526ebaa-31de-4c9f-b724-f0fbe5448a78/114f08c4-f864-44e1-a937-19405307e643 in use.\']\\n3526ebaa-31de-4c9f-b724-f0fbe5448a78/[\'114f08c4-f864-44e1-a937-19405307e643\']",), users={\'/dev/3526ebaa-31de-4c9f-b724-f0fbe5448a78/114f08c4-f864-44e1-a937-19405307e643\': [{\'pid\': 2227780, \'command\': \'systemd-udevd\', \'user\': \'root\', \'fd\': 7}]}' abortedcode=552

1 0

Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB
by arc＠b4restore.com 24 May '23

24 May '23

Hi, i extended 16 virtual image disks today by 1000GiB through the GUI and now we have a problem with some of them... 9 of them are shown if "edited" that they have a size of 0GiB and not 16360GiB as expected? 5 of them are not able to be extended either within the VM. we tried to power it off and then on again (not reboot, but actual power off / power on) any suggestions to get out of this weird mode? disks seems as if they have the "old" size within the VM but are shown in oVirt as if they are 0GiB.? They are relying on a posix compliant fs if that makes any difference, and they are thin-provisioned and discard-enabled. Thanks in advance.

2 3

VM causes CPU blocks and forces reboot of host
by dominik.drazyk＠blackrack.pl 23 May '23

23 May '23

Hello, I have recently migrated our customer's cluster to newer hardware (CentOS 8 Stream, 4 hypervisor nodes, 3 hosts with GlusterFS 5x 6TB SSD as JBOD with replica 3). After 1 month from the switch we encounter frequent vm locks that need host reboot in order to unlock the VM. Affected vms cannot be powered down from ovirt UI. Even if ovirt is successful in powering down affected vms, they cannot be booted again with information that OS disk is used. Once I reboot the host, vms can be turned on and everything works fine. In vdsm logs I can note the following error: 2023-05-11 19:33:12,339+0200 ERROR (qgapoller/1) [virt.periodic.Operation] <bound method QemuGuestAgentPoller._poller of <vdsm.virt.qemuguestagent.QemuGuestAgentPoller object at 0x7f553aa3e470>> operation failed (periodic:187) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py", line 185, in __call__ self._func() File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", line 476, in _poller vm_id, self._qga_call_get_vcpus(vm_obj)) File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", line 797, in _qga_call_get_vcpus if 'online' in vcpus: TypeError: argument of type 'NoneType' is not iterable /var/log/messages reports: May 11 19:35:15 kernel: task:CPU 7/KVM state:D stack: 0 pid: 7065 ppid: 1 flags: 0x80000182 May 11 19:35:15 kernel: Call Trace: May 11 19:35:15 kernel: __schedule+0x2d1/0x870 May 11 19:35:15 kernel: schedule+0x55/0xf0 May 11 19:35:15 kernel: schedule_preempt_disabled+0xa/0x10 May 11 19:35:15 kernel: rwsem_down_read_slowpath+0x26e/0x3f0 May 11 19:35:15 kernel: down_read+0x95/0xa0 May 11 19:35:15 kernel: get_user_pages_unlocked+0x66/0x2a0 May 11 19:35:15 kernel: hva_to_pfn+0xf5/0x430 [kvm] May 11 19:35:15 kernel: kvm_faultin_pfn+0x95/0x2e0 [kvm] May 11 19:35:15 kernel: ? select_task_rq_fair+0x355/0x990 May 11 19:35:15 kernel: ? sched_clock+0x5/0x10 May 11 19:35:15 kernel: ? sched_clock_cpu+0xc/0xb0 May 11 19:35:15 kernel: direct_page_fault+0x3b4/0x860 [kvm] May 11 19:35:15 kernel: kvm_mmu_page_fault+0x114/0x680 [kvm] May 11 19:35:15 kernel: ? vmx_vmexit+0x9f/0x70d [kvm_intel] May 11 19:35:15 kernel: ? vmx_vmexit+0xae/0x70d [kvm_intel] May 11 19:35:15 kernel: ? gfn_to_pfn_cache_invalidate_start+0x190/0x190 [kvm] May 11 19:35:15 kernel: vmx_handle_exit+0x177/0x770 [kvm_intel] May 11 19:35:15 kernel: ? gfn_to_pfn_cache_invalidate_start+0x190/0x190 [kvm] May 11 19:35:15 kernel: vcpu_enter_guest+0xafd/0x18e0 [kvm] May 11 19:35:15 kernel: ? hrtimer_try_to_cancel+0x7b/0x100 May 11 19:35:15 kernel: kvm_arch_vcpu_ioctl_run+0x112/0x600 [kvm] May 11 19:35:15 kernel: kvm_vcpu_ioctl+0x2c9/0x640 [kvm] May 11 19:35:15 kernel: ? pollwake+0x74/0xa0 May 11 19:35:15 kernel: ? wake_up_q+0x70/0x70 May 11 19:35:15 kernel: ? __wake_up_common+0x7a/0x190 May 11 19:35:15 kernel: do_vfs_ioctl+0xa4/0x690 May 11 19:35:15 kernel: ksys_ioctl+0x64/0xa0 May 11 19:35:15 kernel: __x64_sys_ioctl+0x16/0x20 May 11 19:35:15 kernel: do_syscall_64+0x5b/0x1b0 May 11 19:35:15 kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6 May 11 19:35:15 kernel: RIP: 0033:0x7faf1a1387cb May 11 19:35:15 kernel: Code: Unable to access opcode bytes at RIP 0x7faf1a1387a1. May 11 19:35:15 kernel: RSP: 002b:00007fa6f5ffa6e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 May 11 19:35:15 kernel: RAX: ffffffffffffffda RBX: 000055be52e7bcf0 RCX: 00007faf1a1387cb May 11 19:35:15 kernel: RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000027 May 11 19:35:15 kernel: RBP: 0000000000000000 R08: 000055be5158c6a8 R09: 00000007d9e95a00 May 11 19:35:15 kernel: R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000 May 11 19:35:15 kernel: R13: 000055be515bcfc0 R14: 00007fffec958800 R15: 00007faf1d6c6000 May 11 19:35:15 kernel: INFO: task worker:714626 blocked for more than 120 seconds. May 11 19:35:15 kernel: Not tainted 4.18.0-489.el8.x86_64 #1 May 11 19:35:15 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 11 19:35:15 kernel: task:worker state:D stack: 0 pid:714626 ppid: 1 flags:0x00000180 May 11 19:35:15 kernel: Call Trace: May 11 19:35:15 kernel: __schedule+0x2d1/0x870 May 11 19:35:15 kernel: schedule+0x55/0xf0 May 11 19:35:15 kernel: schedule_preempt_disabled+0xa/0x10 May 11 19:35:15 kernel: rwsem_down_read_slowpath+0x26e/0x3f0 May 11 19:35:15 kernel: down_read+0x95/0xa0 May 11 19:35:15 kernel: do_madvise.part.30+0x2c3/0xa40 May 11 19:35:15 kernel: ? syscall_trace_enter+0x1ff/0x2d0 May 11 19:35:15 kernel: ? __x64_sys_madvise+0x26/0x30 May 11 19:35:15 kernel: __x64_sys_madvise+0x26/0x30 May 11 19:35:15 kernel: do_syscall_64+0x5b/0x1b0 May 11 19:35:15 kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6 May 11 19:35:15 kernel: RIP: 0033:0x7faf1a138a4b May 11 19:35:15 kernel: Code: Unable to access opcode bytes at RIP 0x7faf1a138a21. May 11 19:35:15 kernel: RSP: 002b:00007faf151ea7f8 EFLAGS: 00000206 ORIG_RAX: 000000000000001c May 11 19:35:15 kernel: RAX: ffffffffffffffda RBX: 00007faf149eb000 RCX: 00007faf1a138a4b May 11 19:35:15 kernel: RDX: 0000000000000004 RSI: 00000000007fb000 RDI: 00007faf149eb000 May 11 19:35:15 kernel: RBP: 0000000000000000 R08: 00000007faf080ba R09: 00000000ffffffff May 11 19:35:15 kernel: R10: 00007faf151ea760 R11: 0000000000000206 R12: 00007faf15aec48e May 11 19:35:15 kernel: R13: 00007faf15aec48f R14: 00007faf151eb700 R15: 00007faf151ea8c0 May 11 19:35:15 kernel: INFO: task worker:714628 blocked for more than 120 seconds. May 11 19:35:15 kernel: Not tainted 4.18.0-489.el8.x86_64 #1 May 11 19:35:15 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Installed VDSM packages: vdsm-api-4.50.3.4-1.el8.noarch vdsm-network-4.50.3.4-1.el8.x86_64 vdsm-yajsonrpc-4.50.3.4-1.el8.noarch vdsm-http-4.50.3.4-1.el8.noarch vdsm-client-4.50.3.4-1.el8.noarch vdsm-4.50.3.4-1.el8.x86_64 vdsm-gluster-4.50.3.4-1.el8.x86_64 vdsm-python-4.50.3.4-1.el8.noarch vdsm-jsonrpc-4.50.3.4-1.el8.noarch vdsm-common-4.50.3.4-1.el8.noarch Libvirt: libvirt-client-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-nodedev-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-logical-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-network-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-qemu-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-scsi-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-core-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-config-network-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-iscsi-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-rbd-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-libs-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-config-nwfilter-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-secret-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-disk-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-mpath-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-gluster-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 python3-libvirt-8.0.0-2.module_el8.7.0+1218+f626c2ff.x86_64 libvirt-daemon-driver-nwfilter-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-lock-sanlock-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-interface-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-iscsi-direct-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-kvm-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 During the issue with locked vms, they do not respond from network, I cannot use VNC console (or any other) to check what is happening from VM perspective. The host cannot list running processes. There are plenty of resources left and each host runs about 30-35 vms. First I thought that it might be related to glusterfs (I use gluster on other clusters and it usually works fine), so we migrated all vms back to old storage (NFS). The problem came back today on two hosts. I do not have such issues on other cluster which runs on Rocky 8.6 with hyperconverged glusterfs. Hence as a last resort I'll be migrating to Rocky 8 from CentOS 8-stream. Has anyone observed such issues with ovirt hosts on CentOS 8-stream? Any form of help is welcome, as I'm running out of ideas.

4 4

Patching issue on RHEL 8.7-8.8
by jamesroark＠gmail.com 23 May '23

23 May '23

After applying RHEL updates for the recent upgrade from 8.7 to 8.8, I started getting some package problems on my oVirt engine and hosts. Perhaps someone can help me figure out what is going on. Environment: oVirt 4.5.4-1.el8 Stand alone engine - Red Hat Enterprise Linux release 8.7 (Ootpa) RHEL hosts - Red Hat Enterprise Linux release 8.7 (Ootpa) # yum update Updating Subscription Management repositories. Last metadata expiration check: 3:01:05 ago on Fri 19 May 2023 09:43:55 AM EDT. Error: Problem: installed package centos-stream-release-8.6-1.el8.noarch obsoletes redhat-release < 9 provided by redhat-release-8.8-0.8.el8.x86_64 - cannot install the best update candidate for package redhat-release-8.7-0.3.el8.x86_64 - problem with installed package centos-stream-release-8.6-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # yum update --nobest Updating Subscription Management repositories. Last metadata expiration check: 3:01:25 ago on Fri 19 May 2023 09:43:55 AM EDT. Dependencies resolved. Problem: installed package centos-stream-release-8.6-1.el8.noarch obsoletes redhat-release < 9 provided by redhat-release-8.8-0.8.el8.x86_64 - cannot install the best update candidate for package redhat-release-8.7-0.3.el8.x86_64 - problem with installed package centos-stream-release-8.6-1.el8.noarch Nothing to do. Complete! I've applied the https://ovirt.org/download/install_on_rhel.html suggestions. When I try to "Install nightly oVirt master snapshot" as suggested, I also get an error: # dnf copr enable -y ovirt/ovirt-master-snapshot centos-stream-8 Updating Subscription Management repositories. Enabling a Copr repository. Please note that this repository is not part of the main distribution, and quality may vary. The Fedora Project does not exercise any power over the contents of this repository beyond the rules outlined in the Copr FAQ at <https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-…>, and packages are not held to any quality or security level. Please do not file bug reports about these packages in Fedora Bugzilla. In case of problems, contact the owner of this repository. Error: Failed to connect to https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/repo/ce…: Error

2 2

Ovirt 4.5.0 Support (End of Life Date)
by masood.ahmed＠digital.mod.uk 23 May '23

23 May '23

Hi, I am working on a project and we would like to utilise (oVirt 4.5.) as the platform for our enterprise infrastructure. We have arrived at this juncture because of a range of considerations related to hardware and software availability and compatibility. My question is if there is on-going vendor \ professional support for oVirt moving forward, as one of my colleagues spoke with Red Hat, who stated they are going to end their support for the product. we will not gain security accreditation for our project unless we have professional support available, community support only is not sufficient, Any ideas of firms available for a support contract for oVirt 4.5.0? thanks

2 1

constant error in enfine lof and Ovirt dashboard.
by eevans＠digitaldatatechs.com 22 May '23

22 May '23

My setup: CentOS 7 with Gluster 9.6 managed outside of engine, includes 3 servers plusdt the engine host. engine is a standalong but controls the 3 managed gluster volumes hosts. One of the hosts manages the gluster volume. I have used this setup for years and have never seen this on the engine host, but I have on the gluster volume servers. engine.log: 2023-05-22 15:58:33,020-04 INFO [org.ovirt.engine.core.vdsbroker.gluster.Gluste rServersListVDSCommand] (DefaultQuartzScheduler6) [235e97d6] FINISH, GlusterServ ersListVDSCommand, return: [192.168.254.252/24:CONNECTED, kvm04.digitaldatatechs .com:CONNECTED, kvm02.digitaldatatechs.com:CONNECTED], log id: 513632a0 2023-05-22 15:58:33,032-04 INFO [org.ovirt.engine.core.vdsbroker.gluster.AddGlu sterServerVDSCommand] (DefaultQuartzScheduler6) [235e97d6] START, AddGlusterServ erVDSCommand(HostName = kvm02, AddGlusterServerVDSParameters:{hostId='41b5df10-e d0a-4d6a-b375-c77ae9b681b6'}), log id: 6b6b5c97 2023-05-22 15:58:36,237-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghan dling.AuditLogDirector] (DefaultQuartzScheduler6) [235e97d6] EVENT_ID: GLUSTER_S ERVER_ADD_FAILED(4,436), Failed to add host kvm02 into Cluster ovirt_cluster. Ad d host failed: rc=107 out=() err=['Probe returned with Transport endpoint is not connected'] This shows up about eveny 90 seconds. No other issues and the host is up, volume is up. Triple checked firewalld and even disabled it as a test. SELinux is disabled. I'm not sure what I'm missing. Everything looks great in the cockpit. Any help is appreciated. Thanks in advance.

1 0

Ovirt 4.5 deploy failed
by Selçuk N 22 May '23

22 May '23

Hello, I'm trying to install Ovirt 4.5 and I got the following error. FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials."} The node and hosted-engine vm password is the same and does not have any problem. Here are detailed logs. What am I doing wrong? Thank you. Regards 2023-05-18 18:49:25,924+0000 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : include_tasks kwargs 2023-05-18 18:49:26,601+0000 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': '', 'task_duration': 1} 2023-05-18 18:49:26,601+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5580> kwargs 2023-05-18 18:49:26,644+0000 DEBUG ansible on_any args /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.yml (args={} vars={}): [localhost] kwargs 2023-05-18 18:49:27,317+0000 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials'} 2023-05-18 18:49:27,317+0000 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials kwargs is_conditional:False 2023-05-18 18:49:27,318+0000 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials kwargs 2023-05-18 18:49:29,447+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970781b430> kwargs 2023-05-18 18:49:40,175+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:49:50,869+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079cb460> kwargs 2023-05-18 18:50:01,565+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:50:12,258+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707864b50> kwargs 2023-05-18 18:50:22,932+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9b80> kwargs 2023-05-18 18:50:33,638+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0370> kwargs 2023-05-18 18:50:44,319+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:50:54,990+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0370> kwargs 2023-05-18 18:51:05,683+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9b80> kwargs 2023-05-18 18:51:16,375+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0370> kwargs 2023-05-18 18:51:27,062+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:51:37,766+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0a60> kwargs 2023-05-18 18:51:48,422+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97077c3670> kwargs 2023-05-18 18:51:59,125+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97078c2a30> kwargs 2023-05-18 18:52:09,821+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5730> kwargs 2023-05-18 18:52:20,489+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707a41ac0> kwargs 2023-05-18 18:52:31,188+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970781b700> kwargs 2023-05-18 18:52:41,873+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707894580> kwargs 2023-05-18 18:52:52,559+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707894760> kwargs 2023-05-18 18:53:03,260+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079f3d00> kwargs 2023-05-18 18:53:13,923+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:53:24,622+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707a01310> kwargs 2023-05-18 18:53:35,311+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076b0700> kwargs 2023-05-18 18:53:45,964+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:53:56,661+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970771afa0> kwargs 2023-05-18 18:54:07,346+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa15e0> kwargs 2023-05-18 18:54:18,018+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5730> kwargs 2023-05-18 18:54:28,715+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5c40> kwargs 2023-05-18 18:54:39,387+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076f8cd0> kwargs 2023-05-18 18:54:50,067+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa17c0> kwargs 2023-05-18 18:55:00,773+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5730> kwargs 2023-05-18 18:55:11,426+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707a36c40> kwargs 2023-05-18 18:55:22,121+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5c40> kwargs 2023-05-18 18:55:32,809+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97077b5880> kwargs 2023-05-18 18:55:43,463+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97075dc0d0> kwargs 2023-05-18 18:55:54,157+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:56:04,841+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5c40> kwargs 2023-05-18 18:56:15,500+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9250> kwargs 2023-05-18 18:56:26,193+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076b05e0> kwargs 2023-05-18 18:56:36,875+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970787c790> kwargs 2023-05-18 18:56:47,557+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970769ba00> kwargs 2023-05-18 18:56:58,257+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:57:08,912+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076f8c10> kwargs 2023-05-18 18:57:19,612+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076f8040> kwargs 2023-05-18 18:57:30,302+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97077b5160> kwargs 2023-05-18 18:57:40,969+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970769b160> kwargs 2023-05-18 18:57:51,664+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707516b80> kwargs 2023-05-18 18:58:02,347+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97073f1c40> kwargs 2023-05-18 18:58:13,021+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970769bb20> kwargs 2023-05-18 18:58:24,784+0000 DEBUG var changed: host "localhost" var "ansible_failed_task" type "<class 'dict'>" value: "{ "action": "ovirt_auth", "any_errors_fatal": false, "args": { "_ansible_check_mode": false, "_ansible_debug": false, "_ansible_diff": false, "_ansible_keep_remote_files": false, "_ansible_module_name": "ovirt_auth", "_ansible_no_log": false, "_ansible_remote_tmp": "~/.ansible/tmp", "_ansible_selinux_special_fs": [ "fuse", "nfs", "vboxsf", "ramfs", "9p", "vfat" ], "_ansible_shell_executable": "/bin/sh", "_ansible_socket": null, "_ansible_string_conversion_action": "warn", "_ansible_syslog_facility": "LOG_USER", "_ansible_tmpdir": "/root/.ansible/tmp/ansible-tmp-1684436303.0466125-36573-187227954552032/", "_ansible_verbosity": 0, "_ansible_version": "2.13.5", "insecure": true }, "async": 0, "async_val": 0, "become": false, "become_exe": null, "become_flags": null, "become_method": "sudo", "become_user": null, "changed_when": [], "check_mode": false, "collections": [ "ovirt.ovirt", "ansible.builtin" ], "connection": "local", "debugger": null, "delay": 10, "delegate_facts": null, "delegate_to": null, "diff": false, "environment": [ { "OVIRT_PASSWORD": "**FILTERED**", "OVIRT_URL": "https://eng.xxxx.net/ovirt-engine/api", "OVIRT_USERNAME": "admin@internal" } ], "failed_when": [], "finalized": true, "ignore_errors": null, "ignore_unreachable": null, "loop": null, "loop_control": null, "loop_with": null, "module_defaults": [], "name": "Obtain SSO token using username/password credentials", "no_log": null, "notify": null, "poll": 15, "port": null, "register": "ovirt_sso_auth", "remote_user": null, "retries": 50, "run_once": null, "squashed": true, "tags": [ "never", "bootstrap_local_vm", "never" ], "throttle": 0, "timeout": 0, "until": [ "ovirt_sso_auth is succeeded" ], "uuid": "1866daab-9d24-cf71-0985-00000000181c", "vars": {}, "when": [] }" 2023-05-18 18:58:24,784+0000 DEBUG var changed: host "localhost" var "ansible_failed_result" type "<class 'dict'>" value: "{ "_ansible_no_log": null, "_ansible_parsed": true, "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_x_h__rn9/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "failed": true, "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": null, "state": "present", "timeout": 0, "token": null, "url": null, "username": null } }, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }" 2023-05-18 18:58:24,784+0000 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": null, "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_x_h__rn9/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": null, "state": "present", "timeout": 0, "token": null, "url": null, "username": null } }, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }, "ansible_task": "Obtain SSO token using username/password credentials", "ansible_type": "task", "status": "FAILED", "task_duration": 538 } 2023-05-18 18:58:24,784+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97073f1520> kwargs ignore_errors:None 2023-05-18 18:58:25,487+0000 DEBUG var changed: host "localhost" var "ovirt_sso_auth" type "<class 'dict'>" value: "{ "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_x_h__rn9/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "failed": true, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }" 2023-05-18 18:58:25,487+0000 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engine_setup : Sync on engine machine'} 2023-05-18 18:58:25,487+0000 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Sync on engine machine kwargs is_conditional:False

2 2

ovirt node
by skhurtsilava＠cellfie.ge 22 May '23

22 May '23

Hello Guys I installed oVirt Node 4.4 and I want to deploy Hosted Engine but i get this error [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Ensure the resolved address resolves only on the selected interface] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "hostname 'ovirt.bee.moitel.local' doesn't uniquely match the interface 'ens192' selected for the management bridge; it matches also interface with IP ['fe80::9a5b:2039:fe49:5252', '192.168.222.1', 'fd00:1234:5678:900::1']. Please make sure that the hostname got from the interface for the management network resolves only there.\n"} How can i fix this error?

2 1

oVirt and Oracle Linux Virtualization Manager
by Andrei Verovski 22 May '23

22 May '23

Hi, Does Oracle plan to continue active development of oVirt, since it is released as Oracle Linux Virtualization Manager ? with best regards Andrei

1 0

Re: Basic authentication to Rest api not working 4.5.4
by kishorekumar.goli＠gmail.com 22 May '23

22 May '23

Thanks Alexei for the response. I see httpd configuration is updated to use oauth. I see below configuration updated in /etc/httpd/conf.d/internalsso-openidc.conf <LocationMatch ^/ovirt-engine/api($|/)> AuthType oauth20 Require valid-user </LocationMatch> I dont see any release notes about removal of basic authentication in 4.5.x. So I wanted to know if this is mentioned anywhere in the documentation.

2 1

How to deploy a glusterFS on ovirt 4.5 cluster
by patrick.noel＠2IS.biz 18 May '23

18 May '23

Hi, I installed an ovirt 4.5 cluster with 3 nodes and a hosted engine. I would like to configure a GlusterFS cluster on the 3 nodes. I follow this procedure https://www.ovirt.org/dropped/gluster-hyperconverged/chap-Deploying_Hyperco… but the package cockpit-ovirt-dashboard does not exist. What is the procedure to follow? Thank you.

1 0

Basic authentication to Rest api not working 4.5.4
by kishorekumar.goli＠gmail.com 16 May '23

16 May '23

We are facing issue while using basic authentication . We get 401 unauthorized error . It was working in previous versions. parameters used: curl -vvk -u "admin:admin" -H "Content-type: application/xml" -X GET https://<ovirt_gui>/ovirt-engine/api/hosts/ <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html> <head> <title>401 Unauthorized</title> </head> <body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body> </html>

2 1

Failed to read or parse '/etc/pki/ovirt-engine/keys/engine.p12'
by Frank Wall 15 May '23

15 May '23

Hi, I was trying to restore a oVirt Engine Backup into a new Hosted Engine appliance (as part of an upgrade), but this failed with the following error: --== PKI CONFIGURATION ==-- [WARNING] Failed to read or parse '/etc/pki/ovirt-engine/keys/engine.p12' Perhaps it was changed since last Setup. Error was: Error outputting keys and certificates 80EBCC44677F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:373:Global default library context, Algorithm (RC2-40-CBC : 0) It looks like this is related to openssl requiring legacy mode to use the old Engine cert/key. Is there any way to workaround this? Or would it be possible to repackage the existing PCKS#12 file with new encryption (on the old Engine)? Regards - Frank

3 3