[ovirt-users] Re: Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB
It's IBM Spectrum Scale formerly known as GPFS. the limit for files or filesystems are way beyond any limits within the linux vm so that is definatly not an issue from the GPFS filesystem. The disks are formatted as xfs within the VM so that limit should be 500TiB right? the funny thing is that we have 16 disks attached from the storage domain, some of them extended perfectly fine. others did not, or atleast they dont seem to show it, we got no errors other than the volumes was modified correctly and now some of them are shown with a size in ovirt of 0GiB but are ok within the VM, not extendable within the VM but the original size is still the same. if i click on the storage domain and go to Events i see alot of the below messages : May 23, 2023, 9:37:11 AM Size of the disk 'b4chl407_T1B2_SPS115' was successfully updated to 0 GB by SYSTEM. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:37:11 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:37:11 AM Size of the disk 'b4chl407_T1B2_SPS109' was successfully updated to 0 GB by SYSTEM. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:37:11 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS110' was successfully updated to 16360 GB by SYSTEM. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS113' was successfully updated to 16360 GB by SYSTEM. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS109' was successfully updated to 16360 GB by SYSTEM. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:36:34 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS115' was successfully updated to 16360 GB by SYSTEM. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:36:33 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:36:33 AM Size of the disk 'b4chl407_T1B2_SPS114' was successfully updated to 16360 GB by SYSTEM. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:36:33 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:36:18 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:35:48 AM Size of the disk 'b4chl407_T1B2_SPS106' was successfully updated to 16360 GB by SYSTEM. 3e051b49-b02b-43f3-909c-cebbcfbbaeaa oVirt May 23, 2023, 9:35:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:35:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:35:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:35:29 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 98f6e3a0-1f03-4aa5-b477-66defeaa5eb1 oVirt May 23, 2023, 9:35:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:35:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:35:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:34:59 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:34:30 AM Size of the disk 'b4chl407_T1B2_SPS116' was successfully updated to 0 GB by SYSTEM. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:34:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:34:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:34:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:34:29 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:34:01 AM Size of the disk 'b4chl40
[ovirt-users] Re: VM causes CPU blocks and forces reboot of host
Hi, I got the following feedback on my bug report (https://bugzilla.redhat.com/show_bug.cgi?id=2208878): === For RHEL-8.8, you should wait for the 1st Z-stream batch (GA around 2023-06-27), as the issue is being dealt with by backport work via Bug 2189629 (I'm closing this ticket as a DUP of that) In CentOS-Stream-8, please update your kernel to kernel-4.18.0-492.el8, or newer. *** This bug has been marked as a duplicate of bug 2189629 *** === So it should be fixed in the 492 kernel in CentOS Stream, and will be fixed in a month in RHEL 8.8 Regards, Rik On 5/21/23 23:25, John wrote: Same here, very frustrating. On 21/05/2023 21:11, Rik Theys wrote: Hi, We are experiencing the same issue. We've migrated one host from CentOS Stream 8 to Rocky 8.8 and now see the same issue with the EL 8.8 kernel. We don't see this issue on our 8.7 hosts. Regards, Rik On 5/15/23 22:48, Jeff Bailey wrote: Sounds exactly like some trouble I was having. I downgraded the kernel to 4.18.0-448 and everything is fine. There have been a couple of kernel releases since I had problems but I haven't had a chance to try them yet. I believe it was in 4.18.0-485 that I noticed it but that's just from memory. On 5/11/2023 2:26 PM, dominik.dra...@blackrack.pl wrote: 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] of 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: 0x8182 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:7fa6f5ffa6e8 EFLAGS: 0246 ORIG_RAX: 0010 May 11 19:35:15 kernel: RAX: ffda RBX: 55be52e7bcf0 RCX: 7faf1a1387cb May 11 19:35:15 kernel: RDX: RSI: ae80 RDI: 0027 May 11 19:35:15 kernel: RBP: R08: 55be5158c6a8 R09: 0007d9e95a00 May 11 19:35:15 kernel: R10: 0002 R11: 0246 R12: May 11 19:35:15 kernel: R13: 55be515bcfc0 R14: 7fffec958800 R15:
[ovirt-users] Re: Patching issue on RHEL 8.7-8.8
Hi Konstantin, Your response helped me immensely. I was very confused about the requirement and use of centos-stream-release-8.6-1.el8.noarch on RHEL mentioned at https://ovirt.org/download/install_on_rhel.html. I followed your advice and ran the following on my RHEL oVirt systems: rpm -e --justdb --nodeps centos-stream-release-8.6-1.el8.noarch yum clean all dnf update These completed without issues and now I'm happily running oVirt under the latest RHEL 8.8 release. Thank you, James ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/UKUSAWSVJ3GOUDCIXDH2LZKRAZMB2LQS/
[ovirt-users] NIC Ordering
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/predictable-vnic-order.html___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/I3CSHZWQBSIGPKZKJBGVQUIJEGLHZNF3/
[ovirt-users] Re: Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB
On Tue, May 23, 2023 at 2:27 PM wrote: > title should have said "actual size is +10TB" not 1TB. > > What kind of posix compliant fs? What are its capabilities and limits? Because for example max size of a single file is 16Tb on ext4... and after extension your VM disk file size would go near or after this limit https://access.redhat.com/solutions/1532 Just to be sure you are not hitting a side effect caused by fs instead... HIH, Gianluca ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/PUBSBRNWKNJWVMSH7MP6ADLW7RIURLII/
[ovirt-users] Re: Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB
title should have said "actual size is +10TB" not 1TB. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/6A74KE7YJHGCKBBOVWN3TB5OSHKKBNOE/
[ovirt-users] Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB
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. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/OIBM3FUSYBZ3B43UH2KICGREG6LIOZ57/
[ovirt-users] Re: Ovirt 4.5.0 Support (End of Life Date)
I believe Oracle offer their spin of oVirt called Oracle Linux Virtualization Manager. https://www.oracle.com/uk/a/ocom/docs/oracle-linux-virtualization-manager-ds-final.pdf On Fri, 21 Apr 2023 10:14:39 +0100 masood.ahmed--- via Users wrote --- 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 ___ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto:users-le...@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/J5SCZEZCKKAYSF7RNLN2EKXPEMIMS4HF/___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/WOS2M6XQA2WZILKU5AX5CO4JQDTSWLSR/