- Users - oVirt List Archives

Updates Failing
by Gary Pedretty 06 Jul '21

06 Jul '21

Getting errors trying to run dnf/yum update due to a vdsm issue. yum update Last metadata expiration check: 0:17:33 ago on Tue 06 Jul 2021 11:17:05 AM AKDT. Error: Running QEMU processes found, cannot upgrade Vdsm. Current running version of vdsm is vdsm-4.40.60.7-1.el8 CentOS Stream RHEL - 8.5 - 3.el8 kernel 4.18.0 - 310.el8.x86_64 _______________________________ Gary Pedretty IT Manager Ravn Alaska Office: 907-266-8451 Mobile: 907-388-2247 Email: gary.pedretty(a)ravnalaska.com <mailto:gary.pedretty@ravnalaska.com>

2 1

Any way to terminate stuck export task
by Gianluca Cecchi 06 Jul '21

06 Jul '21

Hello, in oVirt 4.3.10 an export job to export domain takes too long, probably due to the NFS server slow. How can I stop in a clean way the task? I see the exported file remains always at 4,5Gb of size. Command vmstat on host with qemu-img process gives no throughput but blocked processes procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 1 2 0 170208752 474412 16985752 0 0 719 72 2948 5677 0 0 96 4 0 0 2 0 170207184 474412 16985780 0 0 3580 99 5043 6790 0 0 96 4 0 0 2 0 170208800 474412 16985804 0 0 1379 41 2332 5527 0 0 96 4 0 and the generated file refreshes its timestamp but not the size # ll -a /rhev/data-center/mnt/172.16.1.137: _nas_EXPORT-DOMAIN/20433d5d-9d82-4079-9252-0e746ce54106/images/125ad0f8-2672-468f-86a0-115a7be287f0/ total 4675651 drwxr-xr-x. 2 vdsm kvm 1024 Jul 3 14:10 . drwxr-xr-x. 12 vdsm kvm 1024 Jul 3 14:10 .. -rw-rw----. 1 vdsm kvm 4787863552 Jul 3 14:33 bb94ae66-e574-432b-bf68-7497bb3ca9e6 -rw-r--r--. 1 vdsm kvm 268 Jul 3 14:10 bb94ae66-e574-432b-bf68-7497bb3ca9e6.meta # du -sh /rhev/data-center/mnt/172.16.1.137: _nas_EXPORT-DOMAIN/20433d5d-9d82-4079-9252-0e746ce54106/images/125ad0f8-2672-468f-86a0-115a7be287f0/ 4.5G /rhev/data-center/mnt/172.16.1.137: _nas_EXPORT-DOMAIN/20433d5d-9d82-4079-9252-0e746ce54106/images/125ad0f8-2672-468f-86a0-115a7be287f0/ The VM has two disks, 35Gb and 300GB, not full but quite occupied. Can I simply kill the qemu-img processes on the chosen hypervisor (I suppose the SPM one)? Any way to track down why it is so slow? Thanks, Gianluca

3 15

Failing to migrate hosted engine from 4.4.6 host to 4.4.7 host
by Sandro Bonazzola 06 Jul '21

06 Jul '21

Hi, I update the hosted engine to 4.4.7 and one of the 2 nodes where the engine is running. Current status is: - Hosted engine at 4.4.7 running on Node 0 - Node 0 at 4.4.6 - Node 1 at 4.4.7 Now, moving Node 0 to maintenance successfully moved the SPM from Node 0 to Node 1 but while trying to migrate hosted engine I get on Node 0 vdsm.log: 2021-07-06 12:25:07,882+0000 INFO (jsonrpc/5) [vdsm.api] START repoStats(domains=()) from=::ffff:10.46.8.133,35048, task_id=f12d7694-d2b5-4658-9e0d-3f0dc54aca93 (api:48) 2021-07-06 12:25:07,882+0000 INFO (jsonrpc/5) [vdsm.api] FINISH repoStats return={'1996dc3b-d33f-49cb-b32a-8f7b1d50af5e': {'code': 0, 'lastCheck': '3.0', 'delay': '0.00114065', 'valid': True, 'version': 5, 'acq uired': True, 'actual': True}} from=::ffff:10.46.8.133,35048, task_id=f12d7694-d2b5-4658-9e0d-3f0dc54aca93 (api:54) 2021-07-06 12:25:07,882+0000 INFO (jsonrpc/5) [vdsm.api] START multipath_health() from=::ffff:10.46.8.133,35048, task_id=6515fac9-830a-4b6a-904e-cc1262e87f01 (api:48) 2021-07-06 12:25:07,882+0000 INFO (jsonrpc/5) [vdsm.api] FINISH multipath_health return={} from=::ffff:10.46.8.133,35048, task_id=6515fac9-830a-4b6a-904e-cc1262e87f01 (api:54) 2021-07-06 12:25:07,883+0000 ERROR (migsrc/b2072331) [virt.vm] (vmId='b2072331-1558-4186-86b4-fa83af8eba95') can't connect to virtlogd: Unable to open system token /run/libvirt/common/system.token: Permission de nied (migration:294) 2021-07-06 12:25:07,888+0000 INFO (jsonrpc/5) [api.host] FINISH getStats return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} from=::ffff:10.46.8.133,35048 (api:54) 2021-07-06 12:25:08,166+0000 ERROR (migsrc/b2072331) [virt.vm] (vmId='b2072331-1558-4186-86b4-fa83af8eba95') Failed to migrate (migration:467) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 441, in _regular_run time.time(), machineParams File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 537, in _startUnderlyingMigration self._perform_with_conv_schedule(duri, muri) File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 626, in _perform_with_conv_schedule self._perform_migration(duri, muri) File "/usr/lib/python3.6/site-packages/vdsm/virt/migration.py", line 555, in _perform_migration self._migration_flags) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 159, in call return getattr(self._vm._dom, name)(*a, **kw) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2119, in migrateToURI3 raise libvirtError('virDomainMigrateToURI3() failed') libvirt.libvirtError: can't connect to virtlogd: Unable to open system token /run/libvirt/common/system.token: Permission denied 2021-07-06 12:25:08,197+0000 INFO (jsonrpc/6) [api.virt] START getMigrationStatus() from=::ffff:10.46.8.133,35048, flow_id=4e86b85d, vmId=b2072331-1558-4186-86b4-fa83af8eba95 (api:48) 2021-07-06 12:25:08,197+0000 INFO (jsonrpc/6) [api.virt] FINISH getMigrationStatus return={'status': {'code': 0, 'message': 'Done'}, 'migrationStats': {'status': {'code': 12, 'message': 'Fatal error during migr ation'}, 'progress': 0}} from=::ffff:10.46.8.133,35048, flow_id=4e86b85d, vmId=b2072331-1558-4186-86b4-fa83af8eba95 (api:54) On node 0: # ls -lZ /run/libvirt/common/system.token ls: cannot access '/run/libvirt/common/system.token': No such file or directory On node 1: # ls -lZ /run/libvirt/common/system.token -rw-------. 1 root root system_u:object_r:virt_var_run_t:s0 32 Jul 6 09:29 /run/libvirt/common/system.token any clue? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 7

Re: Issue With HE HA after upgrading to 4.4.7
by Yedidyah Bar David 06 Jul '21

06 Jul '21

On Tue, Jul 6, 2021 at 5:08 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > Hi, Recently I’m upgrading our server cluster from 4.4.6 to 4.4.7 After upgrading HE, and several Hosts, every single Host that upgraded and activated have an issue with HA Score. It always shows HA Score 0, rebooting the host doesn’t help. Any idea how to check this issue ? Calculating the score takes time, and spreading this around the cluster also takes time. You should find more information in the ovirt-hosted-engine-ha logs (both agent and broker). Good luck and best regards, -- Didi

1 0

Issue With HE HA after upgrading to 4.4.7
by Nur Imam Febrianto 06 Jul '21

06 Jul '21

Hi, Recently I’m upgrading our server cluster from 4.4.6 to 4.4.7 After upgrading HE, and several Hosts, every single Host that upgraded and activated have an issue with HA Score. It always shows HA Score 0, rebooting the host doesn’t help. Any idea how to check this issue ? Thanks. Regards, Nur Imam Febrianto

1 0

Re: How to Upgrade Node with Local Storage ?
by Vojtech Juranek 06 Jul '21

06 Jul '21

On Wednesday, 21 April 2021 16:40:29 CEST Nur Imam Febrianto wrote: > Set global maintenance and then turn off all vm, do yum update but it > completed with failed. Am I missing something ? can you share the details? What failed, wthat was the error? > From: Adam Xu<mailto:adam_xu@adagene.com.cn> > Sent: 20 April 2021 7:36 > To: users(a)ovirt.org<mailto:users@ovirt.org> > Subject: [ovirt-users] Re: How to Upgrade Node with Local Storage ? > > > For oVirt Node that using Local Storage, I think you should shutdown all > your vms before you upgrade the Node. 在 2021/4/19 22:09, Nur Imam Febrianto > 写道: > Hi, > > How we can upgrade oVirt Node that using Local Storage ? Seems I cant find > any good documentation about this. Planning to upgrade one 4.4.4 node with > local storage to 4.4.5. > Thanks before. > > Regards, > Nur Imam Febrianto > > > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> > > To unsubscribe send an email to > users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> > > Privacy Statement: > https://www.ovirt.org/privacy-policy.html<https://apac01.safelinks.protecti > on.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.html&data=0 > 4%7C01%7C%7C2817620cd2134104f81908d90394654e%7C84df9e7fe9f640afb435aaaaaaaaa > aaa%7C1%7C0%7C637544758156873163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VV663qDHl6C24C0 > XTZLoUF4n%2Bm4umP4dkG1EsKS895E%3D&reserved=0> > > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/<https://apac01. > safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunit > y%2Fabout%2Fcommunity-guidelines%2F&data=04%7C01%7C%7C2817620cd2134104f81908 > d90394654e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637544758156883118%7 > CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL > CJXVCI6Mn0%3D%7C1000&sdata=XF1vC3JCyVjQCsD1x%2FDQinfKOImw5VJbZIryDg9sKKg%3D& > reserved=0> > > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZOCHCAJPXO4LT > IMA4JHK3WMR5CTKR37C/<https://apac01.safelinks.protection.outlook.com/?url=ht > tps%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage% > 2FZOCHCAJPXO4LTIMA4JHK3WMR5CTKR37C%2F&data=04%7C01%7C%7C2817620cd2134104f819 > 08d90394654e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637544758156883118 > %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw > iLCJXVCI6Mn0%3D%7C1000&sdata=raH9RGOWlZIWlj%2FCWFJUbqI94y0U2TR9lUukXhzi2B8%3 > D&reserved=0>

3 2

CentOS 8 to Stream conversion
by Gary Pedretty 06 Jul '21

06 Jul '21

I have moved all my hosts from CentOS 8 to Stream, but the hosted engine is still Centos 8. Is it safe to use the same conversion of the hosted-engine from 8 to Stream while in global maintenance mode? IE: dnf swap centos-{linux,stream}-repos dnf distro-sync Thanks Gary _______________________________ Gary Pedretty IT Manager Ravn Alaska Office: 907-266-8451 Mobile: 907-388-2247 Email: gary.pedretty(a)ravnalaska.com

2 1

Windows 10 Guest with nvidia Tesla P40 vGpu Bluescreens when I enable nested virtualization
by domw＠live.ca 06 Jul '21

06 Jul '21

Hi all, I have this issue when I go to create a VM, I want to run WSL2 but when I install it or windows defender application guard the computer bluescreens. So I am using CentOS 8 stream host connected to a VirtIO cluster the hardware is 2 Nvidia Tesla P40 graphics cards installed on a poweredge R480. My windows 10 20H2 Image would bluescreen after the nvidia drivers are installed. I did some testing and discovered after installing a clean ISO windows 10 20H2 that it worked fine even after installing the drivers for the vGPU but the master image does have WSL2 installed out of the box so I installed it on my Vanilla image and it would bluescreen. I imagine this is due to the nested virtualization and the installation of some hyper-v service maybe it is trying to initialize some hardware acceleration. Has anyone had this issue I really need WSL and would love to use version 2. Tesla Version I have tried is 450.12 and the latest 460.32 Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`5e800000 PsLoadedModuleList = 0xfffff805`5f42a490 Debug session time: Sat Jun 26 04:58:37.807 2021 (UTC - 7:00) System Uptime: 0 days 0:00:09.469 Loading Kernel Symbols ............................................................... ...........................Page 799b not present in the dump file. Type ".hh dbgerr004" for details ..................................... ......................... Loading User Symbols PEB is paged out (Peb.Ldr = 0000002e`f91fa018). Type ".hh dbgerr001" for details Loading unloaded module list ....... For analysis of this file, run !analyze -v 3: kd> !analyze -v ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80567d55b24, Address of the instruction which caused the bugcheck Arg3: ffff8487974646a0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ Page fd6196 not present in the dump file. Type ".hh dbgerr004" for details Page fd6196 not present in the dump file. Type ".hh dbgerr004" for details KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on BCCO050 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 27 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff80567d55b24 BUGCHECK_P3: ffff8487974646a0 BUGCHECK_P4: 0 CONTEXT: ffff8487974646a0 -- (.cxr 0xffff8487974646a0) rax=0000000000000000 rbx=ffffb406f7d85000 rcx=e17f3f1e8efe0000 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffb406f1667270 rip=fffff80567d55b24 rsp=ffff8487974650a0 rbp=0000000000000002 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=ffff848797465040 r12=fffff80568511c80 r13=ffffb406f1667270 r14=ffffb406f194c660 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202 nvlddmkm+0x1d5b24: fffff805`67d55b24 4c8b80c8220000 mov r8,qword ptr [rax+22C8h] ds:002b:00000000`000022c8=???????????????? Resetting default scope PROCESS_NAME: csrss.exe STACK_TEXT: ffff8487`974650a0 fffff805`67cab38a : ffffb406`f7d85000 ffffb406`f194c660 00000000`ffffffff ffff8487`97465220 : nvlddmkm+0x1d5b24 ffff8487`974650e0 fffff805`67cdb663 : 00000000`00000000 ffffb406`f7d85000 ffff8487`97465220 ffffb406`f1989000 : nvlddmkm+0x12b38a ffff8487`97465160 fffff805`67cb5df8 : ffffb406`f7d85000 ffffb406`f7d85000 ffffb406`f7d85000 ffff8487`97465220 : nvlddmkm+0x15b663 ffff8487`97465190 fffff805`67ca3ce5 : ffffb406`f1a3b000 00000000`00000001 ffffb406`00000001 ffffb406`f7d85000 : nvlddmkm+0x135df8 ffff8487`974651c0 fffff805`67ca4e8c : 00000000`00000800 ffffb406`f7d85000 ffffb406`f194c660 ffffb406`f1a3b000 : nvlddmkm+0x123ce5 ffff8487`974651f0 fffff805`67c8a41c : ffffb406`f1b8271c 00000002`00000001 ffffb406`00000007 00000000`00000000 : nvlddmkm+0x124e8c ffff8487`97465260 fffff805`67c90f8b : 00000000`00000060 fffff805`684baeb8 00000000`00000060 ffffb406`f1b826b8 : nvlddmkm+0x10a41c ffff8487`97466440 fffff805`67c284f3 : ffffb406`f1b81000 ffff8487`97466640 ffffb406`00000002 ffffa001`ce6c4d80 : nvlddmkm+0x110f8b ffff8487`97466540 fffff805`67bffa83 : 00000000`00000016 00000000`00000000 00000000`00000001 ffffb406`f1b81000 : nvlddmkm+0xa84f3 ffff8487`974666a0 fffff805`68795711 : ffffb406`f1b81000 ffff8487`97466d91 ffff8487`97466f88 00000000`00000001 : nvlddmkm+0x7fa83 ffff8487`97466d10 fffff805`686aa75d : 00000000`00000000 ffffb406`f1943bfc ffff8487`97466f88 ffffb406`f1b18bf0 : nvlddmkm+0xc15711 ffff8487`97466df0 fffff805`6403fab3 : ffffb406`f1b81000 ffffb406`f190f3e0 ffffb406`f1b18bf0 ffffb406`f1943030 : nvlddmkm+0xb2a75d ffff8487`97466e30 fffff805`6404188e : ffffb406`f1b18bf0 ffffffff`fffffffd ffffb406`f1943180 ffffb406`00000000 : dxgkrnl!DpiDxgkDdiStartDevice+0x6b ffff8487`97466e90 fffff805`6403f5d8 : ffffffff`fffffffd ffffb406`f1943180 00000000`00000001 00000000`00000001 : dxgkrnl!DpiFdoStartAdapter+0x58e ffff8487`97467010 fffff805`64058d40 : ffffb113`9a011040 00000000`00000000 ffffb406`f14b6260 00000000`00000000 : dxgkrnl!DpiFdoStartAdapterThreadImpl+0x308 ffff8487`974671c0 fffff805`6402a9ea : fffff805`63f7fa00 00000000`00000000 ffffffff`fffffffd ffffb406`f14b6260 : dxgkrnl!DpiFdoStartAdapterThread+0x30 ffff8487`974671f0 fffff805`6402a94f : 00000000`00000000 ffffffff`fffffffd ffffb406`f14b6260 00000000`00000000 : dxgkrnl!DpiSessionCreateCallback+0x52 ffff8487`97467230 fffff805`64aee722 : 00000000`00000000 00000000`0000014c 00000000`0000014c 00000000`00000148 : dxgkrnl!DxgkNotifySessionStateChange+0xbf ffff8487`97467280 ffffb113`9a2c12d2 : ffffb406`ed7d4940 00000000`0020001e ffffb113`9b6073b0 00000000`00000148 : watchdog!SMgrNotifySessionChange+0x92 ffff8487`974672b0 ffffb113`99e0e5ea : 00000000`00000010 00000000`00050246 ffff8487`97467308 00000000`00000018 : win32k!SysEntrySMgrNotifySessionChange+0x12 ffff8487`974672e0 ffffb113`99e0dfdb : 00000000`00000000 00000000`00050246 ffff8487`97467338 00000000`00000018 : win32kbase!DrvNotifySessionStateChange+0x8a ffff8487`97467310 ffffb113`99e15bc4 : 00000000`00000000 00000000`0000014c 00000000`00000148 ffffb406`f1871b60 : win32kbase!InitializeGreCSRSS+0x1b ffff8487`97467340 ffffb113`9a2c1466 : ffffb406`f7d24080 ffff8487`97467440 00000000`00000001 00000000`00000001 : win32kbase!Win32kBaseUserInitialize+0x124 ffff8487`97467390 fffff805`5ec075b5 : ffffb406`f7d24000 00000000`00100000 ffff8487`97467440 ffffb406`00000000 : win32k!NtUserInitialize+0x16 ffff8487`974673c0 00007ff9`d13b9b44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 0000002e`f8fbf5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`d13b9b44 SYMBOL_NAME: nvlddmkm+1d5b24 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr 0xffff8487974646a0 ; kb BUCKET_ID_FUNC_OFFSET: 1d5b24 FAILURE_BUCKET_ID: 0x3B_c0000005_nvlddmkm!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {63c41bff-3ea4-15a0-a72c-26a548d17abe} Followup: MachineOwner --------- 3: kd> lmvm nvlddmkm Browse full module list start end module name fffff805`67b80000 fffff805`6938d000 nvlddmkm (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\System32\DriverStore\FileRepository\nvgridsw.inf_amd64_bc3d1d075a43d1ac\nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Mon Apr 5 11:28:32 2021 (606B56D0) CheckSum: 017A33BA ImageSize: 0180D000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables: 3: kd> .cxr 0xffff8487974646a0 rax=0000000000000000 rbx=ffffb406f7d85000 rcx=e17f3f1e8efe0000 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffb406f1667270 rip=fffff80567d55b24 rsp=ffff8487974650a0 rbp=0000000000000002 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=ffff848797465040 r12=fffff80568511c80 r13=ffffb406f1667270 r14=ffffb406f194c660 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202 nvlddmkm+0x1d5b24: fffff805`67d55b24 4c8b80c8220000 mov r8,qword ptr [rax+22C8h] ds:002b:00000000`000022c8=????????????????

2 1

migrate hosted engine
by Harry O 06 Jul '21

06 Jul '21

Hi, I get the following when trying to migrate my HostedEngine VM to a new node in the cluster, I just did node reinstall via HostedEngine and rebuild of the gluster array on that node, bacause its a replacement for a crashed dead old node. ID: 120 Migration failed due to an Error: Failed to connect to remote libvirt URI qemu+tls://hej3.5ervers.lan/system: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory (VM: HostedEngine, Source: hej1.5ervers.lan, Destination: hej3.5ervers.lan)

2 2

oVirt 4.4.7 is now generally available
by Sandro Bonazzola 06 Jul '21

06 Jul '21

oVirt 4.4.7 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.7 , as of July 6th, 2021. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.7 Release? This update is the seventh in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.4 - CentOS Linux (or similar) 8.4 - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.4 - CentOS Linux (or similar) 8.4 - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream oVirt Node and Appliance have been updated, including: - oVirt 4.4.7: https://www.ovirt.org/release/4.4.7/ - CentOS Stream 8 latest updates - Ansible 2.9.23: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Advanced Virtualization 8.4.0.1 - Gluster 8.5: https://docs.gluster.org/en/latest/release-notes/8.5/ - Wildfly 23.0.2: https://www.wildfly.org/news/2021/04/29/WildFly2302-Released/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Stream 8 - oVirt Node NG is already available for CentOS Stream 8 Additional resources: - Read more about the oVirt 4.4.7 release highlights: https://www.ovirt.org/release/4.4.7/ <https://www.ovirt.org/release/4.4.7/> - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.7/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0