- Users - oVirt List Archives

oVirt disk disappeared after importing iSCSI domain
by gantonjo-ovirt＠yahoo.com 15 Sep '20

15 Sep '20

Hi all oVirt experts. So, I managed to f.. up a VM today. I had one VM running on a oVirt 4.3 cluster, where the disk was located on an iSCSI data domain. I stopped the VM, put the storage domain in maintenance mode, detached adn removed the storage domain from the ovirt 4.3 cluster. Then I imported the storage domain to our new oVirt 4.4.1 cluster, let the process convert it from V4 to V5 format and activated the storage domain in the new cluster. Entering the information page for the imported storage domain, I expected to see "Import VM" and "Import Disk" menus, but these menues did not appear as they did for other storage domains that I successfully had moved from old to new cluster. Clicking "Scan Disks" did not help either. So, now I am stuck with a storage domain where the VM's disk is located, but oVirt is not able to see the disk. What can I do to recover the lost disk from the storage domain? Any CLI commands available in ovirt 4.4.1 would be nice. Thanks in advance for your quick and good help.

2 1

Disconnected Server has closed the connection.
by info＠worldhostess.com 15 Sep '20

15 Sep '20

It seems that the installation is all done, but I have a problem. it takes very long to open the web pages, plus it disconnect all the time. it is impossible to do anything. I can ping the hostname as I set up a sub-domain for it. to be honest, I am new to this and it took me days to get to this point. I think there are some issues with my network settings. if there are any oVirt experts that can check my installation and give me advice about how to improve it, it will be greatly appreciated. I have done an "Installing oVirt as a self-hosted engine using the Cockpit web interface"

1 0

Multiple GPU Passthrough with NVLink (Invalid I/O region)
by Vinícius Ferrão 14 Sep '20

14 Sep '20

Hello, here we go again. I’m trying to passthrough 4x NVIDIA Tesla V100 GPUs (with NVLink) to a single VM; but things aren’t that good. Only one GPU shows up on the VM. lspci is able to show the GPUs, but three of them are unusable: 08:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] (rev a1) 09:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] (rev a1) 0a:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] (rev a1) 0b:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] (rev a1) There are some errors on dmesg, regarding a misconfigured BIOS: [ 27.295972] nvidia: loading out-of-tree module taints kernel. [ 27.295980] nvidia: module license 'NVIDIA' taints kernel. [ 27.295981] Disabling lock debugging due to kernel taint [ 27.304180] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 27.364244] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 [ 27.579261] nvidia 0000:09:00.0: enabling device (0000 -> 0002) [ 27.579560] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:09:00.0) [ 27.579560] NVRM: The system BIOS may have misconfigured your GPU. [ 27.579566] nvidia: probe of 0000:09:00.0 failed with error -1 [ 27.580727] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:0a:00.0) [ 27.580729] NVRM: The system BIOS may have misconfigured your GPU. [ 27.580734] nvidia: probe of 0000:0a:00.0 failed with error -1 [ 27.581299] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:0b:00.0) [ 27.581300] NVRM: The system BIOS may have misconfigured your GPU. [ 27.581305] nvidia: probe of 0000:0b:00.0 failed with error -1 [ 27.581333] NVRM: The NVIDIA probe routine failed for 3 device(s). [ 27.581334] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 450.51.06 Sun Jul 19 20:02:54 UTC 2020 [ 27.649128] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 450.51.06 Sun Jul 19 20:06:42 UTC 2020 The host is Secure Intel Skylake (x86_64). VM is running with Q35 Chipset with UEFI (pc-q35-rhel8.2.0) I’ve tried to change the I/O mapping options on the host, tried with 56TB and 12TB without success. Same results. Didn’t tried with 512GB since the machine have 768GB of system RAM. Tried blacklisting the nouveau on the host, nothing. Installed NVIDIA drivers on the host, nothing. In the host I can use the 4x V100, but inside a single VM it’s impossible. Any suggestions?

3 7

Testing ovirt 4.4.1 Nested KVM on Skylake-client (core i5) does not work
by wodel youchi 14 Sep '20

14 Sep '20

Hi, I've been using my core i5 6500 (skylake-client) for some time now to test oVirt on my machine. However this is no longer the case. I am using Fedora 32 as my base system with nested-kvm enabled, when I try to install oVirt 4.4 as HCI single node, I get an error in the last phase which consists of copying the VM-Manager to the engine volume and boot it. It is the boot that causes the problem, I get an error about the CPU : *the CPU is incompatible with host CPU: Host CPU does not provide required features: mpx* *This is the CPU part from virsh domcapabilities on my physical machine* <cpu> <mode name='host-passthrough' supported='yes'/> <mode name='host-model' supported='yes'> *<model fallback='forbid'>Skylake-Client-IBRS</model> * <vendor>Intel</vendor> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='clflushopt'/> <feature policy='require' name='umip'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='xsaves'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='invtsc'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> </mode> <mode name='custom' supported='yes'> <model usable='yes'>qemu64</model> <model usable='yes'>qemu32</model> <model usable='no'>phenom</model> <model usable='yes'>pentium3</model> <model usable='yes'>pentium2</model> <model usable='yes'>pentium</model> <model usable='yes'>n270</model> <model usable='yes'>kvm64</model> <model usable='yes'>kvm32</model> <model usable='yes'>coreduo</model> <model usable='yes'>core2duo</model> <model usable='no'>athlon</model> <model usable='yes'>Westmere-IBRS</model> <model usable='yes'>Westmere</model> <model usable='no'>Skylake-Server-IBRS</model> <model usable='no'>Skylake-Server</model> <model usable='yes'>Skylake-Client-IBRS</model> <model usable='yes'>Skylake-Client</model> <model usable='yes'>SandyBridge-IBRS</model> <model usable='yes'>SandyBridge</model> <model usable='yes'>Penryn</model> <model usable='no'>Opteron_G5</model> <model usable='no'>Opteron_G4</model> <model usable='no'>Opteron_G3</model> <model usable='yes'>Opteron_G2</model> <model usable='yes'>Opteron_G1</model> <model usable='yes'>Nehalem-IBRS</model> <model usable='yes'>Nehalem</model> <model usable='yes'>IvyBridge-IBRS</model> <model usable='yes'>IvyBridge</model> <model usable='no'>Icelake-Server</model> <model usable='no'>Icelake-Client</model> <model usable='yes'>Haswell-noTSX-IBRS</model> <model usable='yes'>Haswell-noTSX</model> <model usable='yes'>Haswell-IBRS</model> <model usable='yes'>Haswell</model> <model usable='no'>EPYC-IBPB</model> <model usable='no'>EPYC</model> <model usable='no'>Dhyana</model> <model usable='yes'>Conroe</model> <model usable='no'>Cascadelake-Server</model> <model usable='yes'>Broadwell-noTSX-IBRS</model> <model usable='yes'>Broadwell-noTSX</model> <model usable='yes'>Broadwell-IBRS</model> <model usable='yes'>Broadwell</model> <model usable='yes'>486</model> </mode> </cpu> *Here is the lscpu of my physical machine* # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 94 Model name: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Stepping: 3 CPU MHz: 954.588 CPU max MHz: 3600.0000 CPU min MHz: 800.0000 BogoMIPS: 6399.96 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 1 MiB L3 cache: 6 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled Vulnerability Mds: Mitigation; Clear CPU buffers; SMT disabled Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling Vulnerability Srbds: Vulnerable: No microcode Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT disabled 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 constan t_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 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm *mpx* rdseed adx smap clflushopt in tel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d *Here is the CPU part from virsh dumpxml of my ovirt hypervisor* <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client-IBRS</model> <vendor>Intel</vendor> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='clflushopt'/> <feature policy='require' name='umip'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='xsaves'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='disable' name='mpx'/> </cpu> *Here is the lcpu of my ovirt hypervisor* [root@node1 ~]# lscpu Architecture : x86_64 Mode(s) opératoire(s) des processeurs : 32-bit, 64-bit Boutisme : Little Endian Processeur(s) : 4 Liste de processeur(s) en ligne : 0-3 Thread(s) par cœur : 1 Cœur(s) par socket : 1 Socket(s) : 4 Nœud(s) NUMA : 1 Identifiant constructeur : GenuineIntel Famille de processeur : 6 Modèle : 94 Nom de modèle : Intel Core Processor (Skylake, IBRS) Révision : 3 Vitesse du processeur en MHz : 3191.998 BogoMIPS : 6383.99 Virtualisation : VT-x Constructeur d'hyperviseur : KVM Type de virtualisation : complet Cache L1d : 32K Cache L1i : 32K Cache L2 : 4096K Cache L3 : 16384K Nœud NUMA 0 de processeur(s) : 0-3 Drapaux : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc rep_go od nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnow prefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap clflushopt xs aveopt xsavec xgetbv1 xsaves arat umip md_clear arch_capabilities it seems not all the flags are presented to the hypervisor especially the mpx which causes the error Is there a workaround for this? Regards.

4 6

oVirt HCI issue: GlusterD refusing to start due to quorum issues for volumes where it isn’t contributing any brick
by thomas＠hoberg.net 14 Sep '20

14 Sep '20

Sorry if it's a duplicate: I go an error on post... And yes I posted it on the Gluster slack first, but I am using Gluster only because the marketing on oVirt HCI worked so well... I got 3 recycled servers for an oVirt test environment first and set those up as 3-node HCI using defaults mostly, 2 replica + 1 arbiter, 'engine', 'vmstore' and 'data' volumes with single bricks for each node. I call these group A. Then I got another set of five machines, let's call them group B, with somewhat different hardware characteristics than group A, but nicely similar between themselves. I wanted to add these to the farm as compute nodes but also use their storage as general GlusterFS storage for a wider use. Group B machines were added as hosts and set up to run hosted-engine, but they do not contribute bricks to the normal oVirt volumes 'engine', 'vmstore' or 'data'. With some Ansible trickery I managed to set up two dispersed volumes (4 data: 1 redundancy) on group B 'scratch' and 'tape', mostly for external GlusterFS use. oVirt picked them up automagically, so I guess they could also be used with VMs. I expect to get more machines and adding them one-by-one to dispersed volumes with a fine balance between capacity and redundancy made me so enthusiastic about oVirt HCI in the first place... After some weeks of fine operation I had to restart a machine from group B for maintenance. When it came back up, GlusterD refuses to come online, because it doesn't have "quorum for volumes 'engine', 'vmstore' and 'data'".... It's a small surprise it doesn't *have* quorum, what's a bigger surprise is that it *asks* for quorum in a volume where it's not contributing any bricks. What's worse is that it then refuses to start serving its bricks for 'scratch' and 'tape', which are now growing apart without any chance of healing. How do I fix this? Is this a bug (my interpretation) or do I fundamentlly misunderstand how Gluster as a hyper scale out file system is supposed to work with potentially thousands of hosts contributing each dozens of bricks to each of hundreds of volumes in a single name space?

1 0

Probably dns problem: Internal JSON-RPC error
by jan.kleefeld＠jan-home.de 14 Sep '20

14 Sep '20

I have a clean installed CentOS 8.2 2004 on my server. The self hosted engine deploy (ovirt-4.4) aborts with the following message: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The host has been set in non_operational status, deployment errors: code 505: Host red.colors.ovirt.local installation failed. Failed to configure management network on the host., code 1120: Failed to configure management network on host red.colors.ovirt.local due to setup networks failure., code 9000: Failed to verify Power Management configuration for Host red.colors.ovirt.local., code 10802: VDSM red.colors.ovirt.local command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': ' desired ======= --- dns-resolver: search: [] server: - 192.168.2.150 - fe80::1%eno1 current ======= --- dns-resolver: search: [] server: - 192.168.2.150 difference ========== --- desired +++ current @@ -3,4 +3,3 @@ search: [] server: - 192.168.2.150 - - fe80::1%eno1 '}, fix accordingly and re-deploy."} ~# cat /etc/resolv.conf # Generated by NetworkManager search colors.ovirt.local nameserver 192.168.2.150 nameserver fe80::1%eno1 I am confused, because the probalby missing line is present. Is there maybe another config file, where this last line could be missing? Maybe I can force somehow the installer, to reload the resolv conf, so it can fetch ne new line? I appreciate your help. Jan

3 3

OVN Geneve tunnels not been established
by Konstantinos B 11 Sep '20

11 Sep '20

Hi all We have a small installation based on OVIRT 4.3. 1 Cluster is based on Centos 7 and the other on OVIRT NG Node image. The environment was stable till an upgrade took place a couple of months ago. As such we had to re-install one of the Centos 7 node and start from scratch. Even though the installation completed successfully and VMs are created, the following are not working as expected: 1. ovn geneve tunnels are not established with the other Centos 7 node in the cluster. 2. Centos 7 node is configured by ovirt engine however no geneve tunnel is established when "ovn-sbctl show" is issued on the engine. 3. no flows are shown on the engine on port 6642 for the ovs db. Does anyone have any experience on how to troubleshoot OVN on ovirt? Thank you

2 1

"Add NFS storage domain", "status": "FAILED",
by info＠worldhostess.com 10 Sep '20

10 Sep '20

I am new to oVirt and this is my first installation https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_us ing_the_cockpit_web_interface/ Everything seems fine, but then when I tried step 5, "Hosted Engine Deployment" it keep giving me this error. This information might be too much, but I am not familiar to know what is important. 2020-09-08 06:53:58,991+0200 DEBUG var changed: host "localhost" var "datacenter_name" type "<class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>" value: ""Default"" 2020-09-08 06:53:58,991+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Fetch Datacenter name', 'task_duration': 0} 2020-09-08 06:53:58,991+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f825fb425c0> kwargs 2020-09-08 06:53:59,242+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Add NFS storage domain'} 2020-09-08 06:53:59,242+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Add NFS storage domain kwargs is_conditional:False 2020-09-08 06:53:59,242+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Add NFS storage domain kwargs 2020-09-08 06:56:04,962+0200 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2020-09-08 06:56:04,963+0200 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2020-09-08 06:56:04,963+0200 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2020-09-08 06:56:04,963+0200 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_storage_domain_payload_ir_v98cz/ansible_ovirt_storage_d omain_payload.zip/ansible/modules/cloud/ovirt/ovirt_storage_domain.py\", line 792, in main\n File \"/tmp/ansible_ovirt_storage_domain_payload_ir_v98cz/ansible_ovirt_storage_d omain_payload.zip/ansible/module_utils/ovirt.py\", line 623, in create\n **kwargs\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py\", line 26097, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 232, in _internal_add\n return future.wait() if wait else future\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 55, in wait\n return self._code(response)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 229, in callback\n self._check_fault(response)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 132, in _check_fault\n self._raise_error(response, body)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 118, in _raise_error\n raise error\novirtsdk4.Error: Fault reason is \"Operation Failed\". Fault detail is \"[Problem while trying to mount target]\". HTTP response code is 400.\n", "invocation": { "module_args": { "backup": null, "comment": null, "critical_space_action_blocker": null, "data_center": "Default", "description": null, "destroy": null, "discard_after_delete": null, "domain_function": "data", "fcp": null, "fetch_nested": false, "format": null, "glusterfs": null, "host": "host.worldhostess.co.za", "id": null, "iscsi": null, "localfs": null, "managed_block_storage": null, "name": "hosted_storage", "nested_attributes": [], "nfs": { "address": "storage01.worldhostess.co.za", "mount_options": null, "path": "/data/nfs", "version": "auto" }, "poll_interval": 3, "posixfs": null, "state": "unattached", "timeout": 180, "wait": true, "warning_low_space": null, "wipe_after_delete": null } }, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Problem while trying to mount target]\". HTTP response code is 400." }, "ansible_task": "Add NFS storage domain", "ansible_type": "task", "status": "FAILED", "task_duration": 125 } 2020-09-08 06:56:04,963+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f825f9c3a58> kwargs ignore_errors:None 2020-09-08 06:56:04,964+0200 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "02:16 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 14, 'failures': 1, 'unreachable': 0, 'changed': 0, 'skipped': 2, 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" } 2020-09-08 06:56:04,964+0200 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ < 1 sec ] Check local VM dir stat [ < 1 sec ] Obtain SSO token using username/password credentials [ < 1 sec ] Fetch host facts [ < 1 sec ] Fetch cluster ID [ < 1 sec ] Fetch cluster facts [ < 1 sec ] Fetch Datacenter facts [ < 1 sec ] Fetch Datacenter ID [ < 1 sec ] Fetch Datacenter name [ FAILED ] Add NFS storage domain 2020-09-08 06:56:04,965+0200 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7f826252ef60> kwargs Yours Sincerely, Dr Henni Appelgryn PhD DBA MBA AEP MDP WorldHostess Skype: genie_za WeChat: HenniAppelgryn LinkedIn: https://www.linkedin.com/in/henni-appelgryn/ Hosting with a difference

4 7

Failed to create a new VM in ovirt due to "The host did not satisfy internal filter Memory" error
by KISHOR K 10 Sep '20

10 Sep '20

Hi All, I'm new to Ovirt and not having a perfect experience with Ovirt yet. I ran into a strange issue today when I tried to create a new VM with 32GB in ovirt. VM creation basically due to an error, pasted below. Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host host-01 did not satisfy internal filter Memory., The host host-01 did not satisfy internal filter Memory. After some troubleshooting, I found that there was enough available memory (around 120 GB free ) in the host to host new VM and there were around 10 VMs already running on this host. But, I noticed that ovirt is actually scheduling and creating VM based on "Max free Memory for scheduling new VMs" value, which seems to be set/updated based on total allocated memory for all VMs running on the host and it's not really the then consumed memory by running VMs. Can anyone help to explain if it is some kind of bug in ovirt or it expected behavior? If it is expected behavior, is there any possibility to change it to make sure VM is created based on actual free memory? Thanks a lot in advance for your support. /Kishore /Kishore

4 8

Diskless oVirt Nodes
by harryo.dk＠gmail.com 10 Sep '20

10 Sep '20

Hi, why does my ovirt hypervisor node crash when i pull the hypervisor boot drive? The following thread claims that the oVirt node hypervisor should lodad into memory, so boot disk failure shouldn't have any impact on a running node. https://lists.ovirt.org/pipermail/users/2014-December/029771.html Only memory failure should have a impact, and if RAM fails there is a possibility that the hypervisor OS would have crashed regardless. If you load the hypervisor OS into memory there will be moved/combined a point of failure (the boot disk) with another(the RAM). RAM=memory

3 6