- Users - oVirt List Archives

Bad volume specification
by Facundo Garat 18 Sep '20

18 Sep '20

Hi all, I'm having some issues with one VM. The VM won't start and it's showing problems with the virtual disks so I started the VM without any disks and trying to hot adding the disk and that's fail too. The servers are connected thru FC, all the other VMs are working fine. Any ideas?. Thanks!! PS: The engine.log is showing this: 2020-09-15 20:10:37,926-03 INFO [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (default task-168) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Lock Acquired to object 'EngineLock:{exclusiveLocks='[f5bd2e15-a1ab-4724-883a-988b4dc7985b=DISK]', sharedLocks='[71db02c2-df29-4552-8a7e-cb8bb429a2ac=VM]'}' 2020-09-15 20:10:38,082-03 INFO [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Running command: HotPlugDiskToVmCommand internal: false. Entities affected : ID: 71db02c2-df29-4552-8a7e-cb8bb429a2ac Type: VMAction group CONFIGURE_VM_STORAGE with role type USER 2020-09-15 20:10:38,117-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] START, HotPlugDiskVDSCommand(HostName = nodo2, HotPlugDiskVDSParameters:{hostId='1c24c269-76c3-468d-a7ce-d0332beb7aef', vmId='71db02c2-df29-4552-8a7e-cb8bb429a2ac', diskId='f5bd2e15-a1ab-4724-883a-988b4dc7985b', addressMap='null'}), log id: f57ee9e 2020-09-15 20:10:38,125-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Disk hot-plug: <?xml version="1.0" encoding="UTF-8"?><hotplug> <devices> <disk snapshot="no" type="block" device="disk"> <target dev="vda" bus="virtio"/> <source dev="/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f"> <seclabel model="dac" type="none" relabel="no"/> </source> <driver name="qemu" io="native" type="qcow2" error_policy="stop" cache="none"/> <alias name="ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b"/> <serial>f5bd2e15-a1ab-4724-883a-988b4dc7985b</serial> </disk> </devices> <metadata xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:vm> <ovirt-vm:device devtype="disk" name="vda"> <ovirt-vm:poolID>00000001-0001-0001-0001-000000000311</ovirt-vm:poolID> <ovirt-vm:volumeID>bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f</ovirt-vm:volumeID> <ovirt-vm:imageID>f5bd2e15-a1ab-4724-883a-988b4dc7985b</ovirt-vm:imageID> <ovirt-vm:domainID>55327311-e47c-46b5-b168-258c5924757b</ovirt-vm:domainID> </ovirt-vm:device> </ovirt-vm:vm> </metadata> </hotplug> 2020-09-15 20:10:38,289-03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Failed in 'HotPlugDiskVDS' method 2020-09-15 20:10:38,295-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM nodo2 command HotPlugDiskVDS failed: General Exception: ("Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'block', 'specParams': {}, 'alias': 'ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'domainID': '55327311-e47c-46b5-b168-258c5924757b', 'imageID': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'poolID': '00000001-0001-0001-0001-000000000311', 'volumeID': 'bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'path': '/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'discard': False, 'format': 'cow', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'virtio', 'name': 'vda', 'serial': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'index': 0}",) 2020-09-15 20:10:38,295-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand' return value 'StatusOnlyReturn [status=Status [code=100, message=General Exception: ("Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'block', 'specParams': {}, 'alias': 'ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'domainID': '55327311-e47c-46b5-b168-258c5924757b', 'imageID': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'poolID': '00000001-0001-0001-0001-000000000311', 'volumeID': 'bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'path': '/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'discard': False, 'format': 'cow', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'virtio', 'name': 'vda', 'serial': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'index': 0}",)]]' 2020-09-15 20:10:38,295-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] HostName = nodo2 2020-09-15 20:10:38,295-03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Command 'HotPlugDiskVDSCommand(HostName = nodo2, HotPlugDiskVDSParameters:{hostId='1c24c269-76c3-468d-a7ce-d0332beb7aef', vmId='71db02c2-df29-4552-8a7e-cb8bb429a2ac', diskId='f5bd2e15-a1ab-4724-883a-988b4dc7985b', addressMap='null'})' execution failed: VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = General Exception: ("Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'block', 'specParams': {}, 'alias': 'ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'domainID': '55327311-e47c-46b5-b168-258c5924757b', 'imageID': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'poolID': '00000001-0001-0001-0001-000000000311', 'volumeID': 'bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'path': '/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'discard': False, 'format': 'cow', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'virtio', 'name': 'vda', 'serial': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'index': 0}",), code = 100 2020-09-15 20:10:38,296-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] FINISH, HotPlugDiskVDSCommand, return: , log id: f57ee9e 2020-09-15 20:10:38,296-03 ERROR [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Command 'org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = General Exception: ("Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'block', 'specParams': {}, 'alias': 'ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'domainID': '55327311-e47c-46b5-b168-258c5924757b', 'imageID': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'poolID': '00000001-0001-0001-0001-000000000311', 'volumeID': 'bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'path': '/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'discard': False, 'format': 'cow', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'virtio', 'name': 'vda', 'serial': 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'index': 0}",), code = 100 (Failed with error GeneralException and code 100) 2020-09-15 20:10:38,307-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-36528) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] EVENT_ID: USER_FAILED_HOTPLUG_DISK(2,001), Failed to plug disk owncloud_Disk0 to VM owncloud (User: admin@internal-authz).

4 9

Low Performance (KVM Vs VMware Hypervisor) When running multi-process application
by Rav Ya 17 Sep '20

17 Sep '20

Hello Everyone, Please advice. Any help will be highly appreciated. Thank you in advance. Test Setup: 1. oVirt Centos 7.8 Virtulization Host 2. Guest VM Centos 7.8 (Mutiqueue enabled 6 vCPUs with 6 Rx Tx Queues) 3. The vCPUs are configured for host pass through (Pinned CPU). The Guest VM runs the application in userspace. The Application consists of the parent process that reads packets in raw socket mode from the interface and forwards then to child processes (~vCPUs) via IPC (shared memory – pipes). *The performance (throughput / CPU utilization) that I get with KVM is half of what I get with VMware.* Any thoughts on the below observations? Any suggestions? - KVM Guest VMs degraded performance when running multi-process applications. - High FUTEX time (Seen on the Guest VM when passing traffic). - *High SY: *System CPU time spent in kernel space (Seen on both Hypervisor and the Guest VMs only when running my application.) -Rav Ya

3 6

[ANN] oVirt 4.4.3 First Release Candidate is now available for testing
by Lev Veyde 17 Sep '20

17 Sep '20

oVirt 4.4.3 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 First Release Candidate for testing, as of September 17th, 2020. This update is the third in a series of stabilization updates to the 4.4 series. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) 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 Linux 8 - oVirt Node NG will be available soon for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.3 release highlights: http://www.ovirt.org/release/4.4.3/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.3/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

UPN suffix and my SAM account do not have the sames domains
by dominique.deschenes＠gcgenicom.com 17 Sep '20

17 Sep '20

I have a SSO authentication question. In my Active Directory, my UPN suffix login and my SAM account do not have the sames domains. Example : UPN : dominique.test(a)abc.com Sam account : domtest(a)local.lan On the VM portal, I am able to connect with dominique.test(a)abc.com but not with domtest(a)local.lan (I have the following message:server_error: Cannot resolve principal 'domtest(a)local.lan' If I connect to the VM PORTAL with dominique.test(a)abc.com, when I click on "RDP Console" to get the link, the login of the RDP is dominique.test(a)local.lan. So I have to manually change the login to dominique.test(a)abc.com. Is it possible to use the Sam account domtes(a)local.lan instead of the UPN ? if not, is it possible to adjust the consol.rdp configuration and include the domain abc.com instead of local.lan ? In research I found this, but I don't have access. How to authenticate with Active directory when UPN suffix and Forest Name are different using AAA LDAP extension - Red Hat C https://access.redhat.com/solutions/2332561 Thank you

1 0

Re: Random hosts disconnects
by Anton Louw 17 Sep '20

17 Sep '20

Hi Everybody, Did some digging around, and saw a few things regarding “vdsHeartbeatInSeconds” I had a look at the properties file located at /etc/ovirt-engine/engine-config/engine-config.properties, and do not see an entry for “vdsHeartbeatInSeconds.type=Integer”. Seeing as these data centers are geographically split, could the “vdsHeartbeatInSeconds” potentially be the issue? Is it safe to increase this value after I add “vdsHeartbeatInSeconds.type=Integer” into my engine-config.properties file? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za From: Anton Louw via Users <users(a)ovirt.org> Sent: 16 September 2020 09:01 To: users(a)ovirt.org Subject: [ovirt-users] Random hosts disconnects Hi All, I have a strange issue in my oVirt environment. I currently have a standalone manager which is running in VMware. In my oVirt environment, I have two Data Centers. The manager is currently sitting on the same subnet as DC1. Randomly, hosts in DC2 will say “Not Responding” and then 2 seconds later, the hosts will activate again. The strange thing is, when the manager was sitting on the same subnet as DC2, hosts in DC1 will randomly say “Not Responding” I have tried going through the logs, but I cannot see anything out of the ordinary regarding why the hosts would drop connection. I have attached the engine.log for anybody that would like to do a spot check. Thanks Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<http://www.vox.co.za> [F]<https://www.facebook.com/voxtelecomZA> [T]<https://www.twitter.com/voxtelecom> [I]<https://www.instagram.com/voxtelecomza> [L]<https://www.linkedin.com/company/voxtelecom> [Y]<https://www.youtube.com/user/VoxTelecom> [#VoxBrand]<https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> Disclaimer The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here<https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>.

1 0

Ovirt legacy migration policy is missing
by ovirtand-cnj342＠yahoo.com 16 Sep '20

16 Sep '20

Hello, We have many cases of failed migrations, and reducing the load on the respective VMs made migration possible. Using "Suspend workload when needed" did not help either with the migrations, which only worked when stopping services on the VMs, thus reducing load. I was therefore trying to tweak the migration downtime setting. The suggested way of doing this is by using the Legacy migration policy. That being said, I am unable to find the Legacy migration policy in the VM Host tab, nor in the cluster's "Migration policy" tab. I cannot find any mention of it being left out of our current version (4.3.6.1) - moreover, the setting "Use custom migration downtime" (only available when using the Legacy migration policy) does exist in the interface - but I cannot find the Legacy policy itself. The only policies present are Minimal downtime (default for cluster), Post-copy migration and Suspend workload when needed. Is there a way to make the Legacy migration policy available if it's missing? Thanks! Best regards, Andy PS. Setting DefaultMaximumMigrationDowntime=20000 as default did not have any effect, presumably because the system uses one of the 3 pre-defined policies and ignores the "default"

1 0

Low Performance (KVM Vs VMware Hypervisor) When running multi-process application
by Ravin Ya 16 Sep '20

16 Sep '20

Hello Everyone, Please advice. Any help will be highly appreciated. Thank you in advance. Test Setup: oVirt Centos 7.8 Virtulization Host Guest VM Centos 7.8 (Mutiqueue enabled 6 vCPUs with 6 Rx Tx Queues) The vCPUs are configured for host pass through (Pinned CPU). The Guest VM runs the application in userspace. The Application consists of the parent process that reads packets in raw socket mode from the interface and forwards then to child processes (~vCPUs) via IPC (shared memory – pipes). The performance (throughput / CPU utilization) that I get with KVM is half of what I get with VMware. Any thoughts on the below observations? Any suggestions? KVM Guest VMs degraded performance when running multi-process applications. High FUTEX time (Seen on the Guest VM when passing traffic). High SY: System CPU time spent in kernel space (Seen on both Hypervisor and the Guest VMs only when running my application.) -Rav Ya

2 1

cpu QoS doesn't work
by pub.virtualization＠gmail.com 16 Sep '20

16 Sep '20

Hello, I set cpu QoS as 10 and applied it to VM on oVirt 4.2, but it doesn't seem to work. compared to VM without QoS, there wasn't any difference in cpu usage. Also, there wasn't any <period>...</period> or <quota>...</quota> field related to QoS in libvirt file. is it right result?? Thanks,

2 1

Unable to create a node in oVirt 4.0
by Rodrigo G. López 16 Sep '20

16 Sep '20

Hi there, We are trying to setup a node in the same machine where we are running the engine, and noticed that the vdsmd service fails because the supervdsmd daemon can't authenticate against libvirtd afaict. The error is the following on supervdsmd: daemonAdapter[17803]: libvirt: XML-RPC error : authentication failed: authentication failed ... and in libvirtd: Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.410+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.612+0000: 17776: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757) Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.612+0000: 17776: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.612+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.814+0000: 17778: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757) Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.814+0000: 17778: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.815+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error Sep 15 03:34:19 ovirt-test libvirtd[17775]: 2020-09-15 07:34:19.017+0000: 17780: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757) Sep 15 03:34:19 ovirt-test libvirtd[17775]: 2020-09-15 07:34:19.017+0000: 17780: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed Sep 15 03:34:19 ovirt-test libvirtd[17775]: 2020-09-15 07:34:19.020+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error Is there any way to work around that? We have working infra on top of 4.0 in CentOS 7 systems, and we would like to replicate the exact same environment for availability purposes, in case anything bad happened. Best regards, -rodri

3 4

Removal of deprecated init-scripts (network-scripts)
by Ales Musil 16 Sep '20

16 Sep '20

Hello, network-scripts for host networking were deprecated since oVirt 4.4. It will be removed completely in the 4.4.3 release. There is no action required for setups that did not change the configuration to use network-scripts backend (net_nmstate_enabled = false). Users that did disable nmstate should redeploy all affected hosts before 4.4.3. Also can you please tell us what was the reason to use network-scripts, if that is the case? Thank you. Best regards, Ales Musil -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 0

Random hosts disconnects
by Anton Louw 16 Sep '20

16 Sep '20

Hi All, I have a strange issue in my oVirt environment. I currently have a standalone manager which is running in VMware. In my oVirt environment, I have two Data Centers. The manager is currently sitting on the same subnet as DC1. Randomly, hosts in DC2 will say "Not Responding" and then 2 seconds later, the hosts will activate again. The strange thing is, when the manager was sitting on the same subnet as DC2, hosts in DC1 will randomly say "Not Responding" I have tried going through the logs, but I cannot see anything out of the ordinary regarding why the hosts would drop connection. I have attached the engine.log for anybody that would like to do a spot check. Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

1 0

Enable a cluster node to run the hosted engine
by rap＠isogmbh.de 16 Sep '20

16 Sep '20

Hi there, currently my team is evaluating oVirt and we're also testing several fail scenarios, backup and so on. One scenario was: - hyperconverged oVirt cluster with 3 nodes - self-hosted engine - simulate the break down of one of the nodes by power off - to replace it make a clean install of a new node and reintegrate it in the cluster Actually everything worked out fine. The new installed node and related bricks (vmstore, data, engine) were added to the existing Gluster storage and it was added to the oVirt cluster (as host). But there's one remaining problem: The new host doesn't have the grey crown, which means it's unable to run the hosted engine. How can I achieve that? I also found out that the ovirt-ha-agent and ovirt-ha-broker isn't started/enabled on that node. Reason is that the /etc/ovirt-hosted-engine/hosted-engine.conf doesn't exist. I guess this is not only a problem concerning the hosted engine, but also for HA VM's. Thank you for any advice and greetings, Marcus

3 7

Random hosts disconnects
by anton.louw＠voxtelecom.co.za 16 Sep '20

16 Sep '20

Hi All, I have a strange issue in my oVirt environment. I currently have a standalone manager which is running in VMware. In my oVirt environment, I have two Data Centers. The manager is currently sitting on the same subnet as DC1. Randomly, hosts in DC2 will say “Not Responding” and then 2 seconds later, the hosts will activate again. The strange thing is, when the manager was sitting on the same subnet as DC2, hosts in DC1 will randomly say “Not Responding” I have tried going through the logs, but I cannot see anything out of the ordinary regarding why the hosts would drop connection. I have attached the engine.log for anybody that would like to do a spot check. Thanks

1 0

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"

3 3

Gluster quorum issue on 3-node HCI with extra 5-nodes as compute and storage nodes
by thomas＠hoberg.net 15 Sep '20

15 Sep '20

Yes, I've also posted this on the Gluster Slack. But I am using Gluster mostly because it's part of oVirt HCI, so don't just send me away, please! Problem: GlusterD refusing to start due to quorum issues for volumes where it isn’t contributing any brick (I've had this before on a different farm, but there it was transitory. Now I have it in a more observable manner, that's why I open a new topic) In a test farm with recycled servers, I started running Gluster via oVirt 3node-HCI, because I got 3 machines originally. They were set up as group A in a 2:1 (replica:arbiter) oVirt HCI setup with 'engine', 'vmstore' and 'data' volumes, one brick on each node. I then got another five machines with hardware specs that were rather different to group A, so I set those up as group B to mostly act as compute nodes, but also to provide extra storage, mostly to be used externally as GlusterFS shares. It took a bit of fiddling with Ansible but I got these 5 nodes to serve two more Gluster volumes 'tape' and 'scratch' using dispersed bricks (4 disperse:1 redundancy), RAID5 in my mind. The two groups are in one Gluster, not because they serve bricks to the same volumes, but because oVirt doesn't like nodes to be in different Glusters (or actually, to already be in a Gluster when you add them as host node). But the two groups provide bricks to distinct volumes, there is no overlap. After setup things have been running fine for weeks, but now I needed to restart a machine from group B, which has ‘tape’ and ‘scratch’ bricks, but none from original oVirt ‘engine’, ‘vmstore’ and ‘data’ in group A. Yet the gluster daemon refuses to start, citing a loss of quorum for these three volumes, even if it has no bricks in them… which makes no sense to me. I am afraid the source of the issue is concept issues: I clearly don't really understand some design assumptions of Gluster. And I'm afraid the design assumptions of Gluster and of oVirt (even with HCI), are not as related as one might assume from the marketing materials on the oVirt home-page. But most of all I'd like to know: How do I fix this now? I can't heal 'tape' and 'scratch', which are growing ever more apart while the glusterd on this machine in group B refuses to come online for lack of a quorum on volumes where it is not contributing bricks.

3 2

What is the purpose of memory deflation in oVirt memory ballooning?
by pub.virtualization＠gmail.com 15 Sep '20

15 Sep '20

Hi, guys Why does momd(ballooning manager in oVirt) explicitly deflate the balloon when host gets plenty of memory? as far as I know, momd is supporting memory ballooning with setMemory API to inflate/deflate the balloon in guest and I've just checked the memory change in the guest after inflating the balloon. as expected, memory(total, free, available) in the guest was reduced just after inflating the balloon, but it was "automatically" restored to its initial memory after a few seconds. So, here I'm wondering why deflation is additionally required even though it can be restored automatically just after seconds. Thanks.

1 1

Posts not updating on lists.ovirt.org web site since September 10th?
by thomas＠hoberg.net 15 Sep '20

15 Sep '20

I can see new posts coming in via e-mail, but updates on the web sites have stopped and posts don't disappear?

2 1

Any eta for 4.4.2 final?
by Gianluca Cecchi 15 Sep '20

15 Sep '20

Hello, I would like to upgrade a 4.4.0 environment to the latest 4.4.2 when available. Any indication if there are any show stoppers after the rc5 released on 27th of August or any eta about other release candidates? Thanks, Gianluca

4 3

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