- Users - oVirt List Archives

Re: Customizing ovirt vm / user web portal
by Jorge Visentini 26 Jun '23

26 Jun '23

Following for being interesting... Em sex., 23 de jun. de 2023 às 10:01, R A <jarheadx(a)hotmail.de> escreveu: > 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 > _______________________________________________ > 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/RI23B7PVQTVHK… > -- Att, Jorge Visentini +55 55 98432-9868

3 2

HostEngine added alternate fqdn cannot be accessed
by ziyi Liu 26 Jun '23

26 Jun '23

I modified the parameter of SSO_ALTERNATE_ENGINE_FQDNS to the new fqdn in /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf. After modifying the hosts, I can use the new fqdn to open the web but cannot enter the portal management, prompting 500 Internal Server Error

1 0

Re: ovirt 4.5 VNC Failed to complete handshake Error in the pull function on Windows
by Patrick Hibbs 25 Jun '23

25 Jun '23

Hello, On 6/23/23 13:23, R A wrote: > > 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“ > Did you do that after opening console.vv manually? Or did you download a new console.vv before doing so? console.vv files are good for one use only. As they contain a one-time password that is revoked after use. > 1. 3. When i try to open via novnc a new tab opens and i get > „Something went wrong, connection is closed“ > Again, did you reuse that console.vv file? Or did you download a new one? FYI: The file should be deleted automatically after remote-viewer opens it. As it's not supposed to be reused. > > 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 > This looks like your Windows host lacks the ovirt-engine CA in it's trust store. You should try importing the CA first before opening the console.vv file. It's not possible* to use a third party CA to secure the VNC connections. As the VNC connections originate on the virtualization hosts themselves, the CA that they use is the internal ovirt-engine CA that was automatically generated by engine-setup. If you don't want to import the ovirt-engine CA on the end-user machines, your best option is to force end users through the end-user portal. Alternatively, you could disable VNC encryption entirely and secure the link via other means. *: Technically it is possible to use a third party CA cert on the VNC connections, but it will only work until VDSM reboots the host or performs a host upgrade. As there is no way to force VDSM to ignore the "invalid" custom cert. -Patrick Hibbs > The solutions provided here was not successfull > https://access.redhat.com/solutions/6217601 > > BR > > R A > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-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/XG7T…

2 1

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

25 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 24 Jun '23

24 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