Unable to create VMs under ovirt 4.4
by Dirk Streubel
Hello List,
after a few Problems with the package "java-client-kubevirt" and some
updates Problems on my Hypervisor and my ovirt-engine i make a totally
fresh installation of ovirt 4.4.
So, after the new installation i can't create a Linux VM. I get a
message that i don't understand:
Feb 13 10:44:12 hypervisor vdsm[6644]: WARN Attempting to add an
existing net user: ovirtmgmt/9ab115dd-1c21-476d-955f-d4164e4bc5c7
Feb 13 10:44:14 hypervisor journal[2698]: the CPU is incompatible with
host CPU: Host-CPU stellt nicht die erforderlichen Funktionen bereit:
hle, rtm
Feb 13 10:44:15 hypervisor vdsm[6644]: WARN Attempting to remove a non
existing network: ovirtmgmt/9ab115dd-1c21-476d-955f-d4164e4bc5c7
Feb 13 10:44:15 hypervisor vdsm[6644]: WARN Attempting to remove a non
existing net user: ovirtmgmt/9ab115dd-1c21-476d-955f-d4164e4bc5c7
So, which function are missing? I don't know what "hle" and "rtm" stands
for? And searching with Google get no Results.
And it is interesting before the new Installation i was possible to
create a Debian and CentOS VM under ovirt 4.4
Regards
Dirk
4 years, 9 months
Reimport disks
by Christian Reiss
Hey folks,
I created a new cluster with a new engine, everything is green and
running again (3 HCI, Gluster, this time Gluster 7.0 and CentOS7 hosts).
I do have a backup of the /images/ directory from the old installation.
I tried copying (and preserving user/ permissions) into the new images
gluster dir and trying a domain -> scan to no avail.
What is the correct way to introduce oVirt to "new" (or unknown) images?
-Chris.
--
with kind regards,
mit freundlichen Gruessen,
Christian Reiss
4 years, 9 months
Re: Cannot Increase Hosted Engine VM Memory
by Serhiy Morhun
Hello, did anyone find a resolution for this issue? I'm having exactly the
same problem:
Hosted Engine VM is running with 5344MB of RAM, when trying to increase to
8192 it would not accept the change because the difference is not divisible
by 256.
When trying to increase to 8160 the change is accepted but log shows
"Hotset memory: changed the amount of memory on VM HostedEngine from 5344
to 5344" at the same time amount of guaranteed memory does increase to 8160
which, in turn, starts generating error messages that VM does not have all
the guaranteed RAM.
Serhiy Morhun
--
*-----------------------------------------------------------------------------------***
*THE INFORMATION CONTAINED IN THIS MESSAGE (E-MAIL AND ANY ATTACHMENTS) IS
INTENDED ONLY FOR THE INDIVIDUAL AND CONFIDENTIAL USE OF THE DESIGNATED
RECIPIENT(S).*
If any reader of this message is not an intended recipient
or any agent responsible for delivering it to an intended recipient, you
are hereby notified that you have received this document in error, and that
any review, dissemination, distribution, copying or other use of this
message is prohibited. If you have received this message in error, please
notify us immediately by reply e-mail message or by telephone and delete
the original message from your e-mail system and/or computer database.
Thank you.
*-----------------------------------------------------------------------------------*
**NOTICE**:
*You are advised that e-mail correspondence and attachments
between the public and the Ridgewood Board of Education are obtainable by
any person who files a request under the NJ Open Public Records Act (OPRA)
unless it is subject to a specific OPRA exception. You should have no
expectation that the content of e-mails sent to or from school district
e-mail addresses, or between the public and school district officials and
employees, will remain private.*
*-----------------------------------------------------------------------------------*
4 years, 9 months
Administrative portal host creation installaFailed
by krisibo01＠gmail.com
Hello,
I am a student and as a school project i have to make virtual environment using oVirt.I am still confused how exactly oVirt is working i just installed its engine with the default settings that are recomended in the guide and i am trying ot make a new host with the default data center and cluster. The host is created but it is staying in installFailed mode.
http://prntscr.com/r0u2eo
I am using the ip address of the device (It is headless server) that has the oVirt-engine. I already checked if the virtualization is enabled in the bios because i thought it might be the problem.
When i checked the engine.log file for test1(it is the name of the host i am trying to make) i got this:
2020-02-11 11:21:29,582-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-5) [602685d9-6eb3-415f-b705-f94a76b1f77a] Failed to authenticate session with host 'test1': SSH authentication to 'root(a)192.168.66.1' failed. Please verify provided credentials. Make sure host is configured for password authentication
2020-02-11 11:22:10,555-05 INFO [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-5) [2919924c] START, RemoveVdsVDSCommand(HostName = test1, RemoveVdsVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec'}), log id: 32419129
2020-02-11 11:22:10,562-05 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-5) [2919924c] START, AddVdsVDSCommand(HostName = test1, AddVdsVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec'}), log id: 2697f96
2020-02-11 11:22:10,602-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [2919924c] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Power Management configuration for Host test1.
2020-02-11 11:22:10,652-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [2919924c] EVENT_ID: USER_ADD_VDS(42), Host test1 was added by admin@internal-authz.
2020-02-11 11:22:10,722-05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] Before Installation host 6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec, test1
2020-02-11 11:22:10,785-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] START, SetVdsStatusVDSCommand(HostName = test1, SetVdsStatusVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec', status='Installing', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2a396f44
2020-02-11 11:22:10,877-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Connected to host 192.168.66.76 with SSH key fingerprint: SHA256:UPDIq/SAKblGbU7sQ/vAkOiMraW0fmwi/kJ0mX0yanM.
2020-02-11 11:22:12,644-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Initializing.
2020-02-11 11:22:12,776-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Environment setup.
2020-02-11 11:22:13,436-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Environment packages setup.
2020-02-11 11:22:28,470-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Programs detection.
2020-02-11 11:22:28,504-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Environment customization.
2020-02-11 11:22:31,715-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Kdump supported.
2020-02-11 11:22:32,182-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Logs at host located at: '/tmp/ovirt-host-deploy-20200211112211-a6mgfh.log'.
2020-02-11 11:22:32,303-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS_WARNING(510), Host test1 installation in progress . Aborted.
2020-02-11 11:22:32,315-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Clean up.
2020-02-11 11:22:32,327-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Pre-termination.
2020-02-11 11:22:32,363-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Retrieving installation logs to: '/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20200211112232-192.168.66.76-1de230f5.log'.
2020-02-11 11:22:32,633-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Termination.
2020-02-11 11:22:32,777-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host test1: Command returned failure code 1 during SSH session 'root(a)192.168.66.76'.
2020-02-11 11:22:32,791-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] Host installation failed for host '6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec', 'test1': Host 192.168.66.76 reports unique id which already registered for test
2020-02-11 11:22:32,795-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] START, SetVdsStatusVDSCommand(HostName = test1, SetVdsStatusVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 6fba93de
2020-02-11 11:22:32,831-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] EVENT_ID: VDS_INSTALL_FAILED(505), Host test1 installation failed. Host 192.168.66.76 reports unique id which already registered for test.
4 years, 9 months
DataAccessResourceFailureException from one to to the next
by gregor
After one day I'm not able to login to the ovirt-engine webinterface
with the following error message:
"org.springframework.dao.DataAccessResourceFailureException: Error
retrieving database metadata; nested exception is
org.springframework.jdbc.support.MetaDataAccessException: Error while
extracting DatabaseMetaData; nested exception is
org.postgresql.util.PSQLException: This connection has been closed."
Things I tried which didn't help:
- engine: check if the database is up
- eninge: reboot
- hosts: reboot
- engine: xfs_repair
Any ideas?
regards
gregor
4 years, 9 months
Ovirt with Ceph
by systems＠oisystems.co.uk
is it possible to crate a storage pool on the same Centos hosts as the Gluster Storage ?
if we use Gluster for the Hosted engine and use Ceph for VM's ?
it seems Ceph is much more stable than Gluster and I like the way storage is more transparent in Ceph
4 years, 9 months
Compatibility version for VmPools
by nicolas＠devels.es
Hi,
We recently upgraded to 4.3.8 from 4.1.9. In the update process we set
Cluster and DataCenter compatibility versions to 4.3, but now we're
facing a problem with VmPools. They cannot be edited and 4.1 as
compatibility level is still forcibly set.
That means that when new machines are added to the pool, compatibility
version 4.1 is set on them and they cannot be started as a message
stating the following pops up:
Failed to run VM XXX-34 due to a failed validation: [Cannot run VM.
The Custom Compatibility Version of VM XXX-34 (4.1) is not supported in
Data Center compatibility version 4.3.] (User: admin@internal).
Is there a workaround to start those machines, or a way to fix the
problem?
Thanks.
4 years, 9 months
Update hosted engine to 4.3.8 from 4.3.7 questions
by d03＠bornfree.org
I'd like to update my hosted engine to version 4.3.8 from 4.3.7, but have concerns.
First, on the hosted engine, yum reports that several packages are version locked. Specifically:
0:ovirt-engine-webadmin-portal-4.3.8.2-1.el7.*
0:ovirt-engine-dwh-4.3.8-1.el7.*
0:ovirt-engine-tools-backup-4.3.8.2-1.el7.*
0:ovirt-engine-restapi-4.3.8.2-1.el7.*
0:ovirt-engine-dbscripts-4.3.8.2-1.el7.*
0:ovirt-engine-4.3.8.2-1.el7.*
0:ovirt-engine-backend-4.3.8.2-1.el7.*
0:ovirt-engine-tools-4.3.8.2-1.el7.*
Is this normal and is it okay to proceed with the update? If it is not normal, what can I do to correct the problem?
Also, what is the correct procedure to update the engine? Although I tried to read the documentation, I have encountered conflicting documents so I must ask. Sorry.
This is how I understand it, but am not confident that it is correct:
1. Enable Global HA Maintenance mode.
2. On the engine, run # yum update ovirt*
3. On the engine, run # engine-setup
4. On the engine, run # yum update
4. Reboot the hosted engine. Is "systemctl reboot" acceptable or do I have to do a "hosted-engine --vm-restart" from a host?
5. Disable Global HA Maintenance mode.
Your expert guidance is much appreciated.
4 years, 9 months
issue connecting 4.3.8 node to nfs domain
by Jorick Astrego
Hi,
Something weird is going on with our ovirt node 4.3.8 install mounting a
nfs share.
We have a NFS domain for a couple of backup disks and we have a couple
of 4.2 nodes connected to it.
Now I'm adding a fresh cluster of 4.3.8 nodes and the backupnfs mount
doesn't work.
(annoying you cannot copy the text from the events view)
The domain is up and working
ID:f5d2f7c6-093f-46d6-a844-224d92db5ef9
Size:10238 GiB
Available:2491 GiB
Used:7747 GiB
Allocated:3302 GiB
Over Allocation Ratio:37%
Images:7
Path:*.*.*.*:/data/ovirt
NFS Version:AUTO
Warning Low Space Indicator:10% (1023 GiB)
Critical Space Action Blocker:5 GiB
But somehow the node appears to thin thinks it's an LVM volume? It tries
to find the VGs volume group but fails... which is not so strange as it
is an NFS volume:
2020-02-05 14:17:54,190+0000 WARN (monitor/f5d2f7c) [storage.LVM]
Reloading VGs failed (vgs=[u'f5d2f7c6-093f-46d6-a844-224d92db5ef9']
rc=5 out=[] err=[' Volume group
"f5d2f7c6-093f-46d6-a844-224d92db5ef9" not found', ' Cannot process
volume group f5d2f7c6-093f-46d6-a844-224d92db5ef9']) (lvm:470)
2020-02-05 14:17:54,201+0000 ERROR (monitor/f5d2f7c)
[storage.Monitor] Setting up monitor for
f5d2f7c6-093f-46d6-a844-224d92db5ef9 failed (monitor:330)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py",
line 327, in _setupLoop
self._setupMonitor()
File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py",
line 349, in _setupMonitor
self._produceDomain()
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 159,
in wrapper
value = meth(self, *a, **kw)
File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py",
line 367, in _produceDomain
self.domain = sdCache.produce(self.sdUUID)
File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line
110, in produce
domain.getRealDomain()
File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line
51, in getRealDomain
return self._cache._realProduce(self._sdUUID)
File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line
134, in _realProduce
domain = self._findDomain(sdUUID)
File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line
151, in _findDomain
return findMethod(sdUUID)
File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line
176, in _findUnfetchedDomain
raise se.StorageDomainDoesNotExist(sdUUID)
StorageDomainDoesNotExist: Storage domain does not exist:
(u'f5d2f7c6-093f-46d6-a844-224d92db5ef9',)
The volume is actually mounted fine on the node:
On NFS server
Feb 5 15:47:09 back1en rpc.mountd[4899]: authenticated mount
request from *.*.*.*:673 for /data/ovirt (/data/ovirt)
On the host
mount|grep nfs
*.*.*.*:/data/ovirt on /rhev/data-center/mnt/*.*.*.*:_data_ovirt
type nfs
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,nolock,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=*.*.*.*,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=*.*.*.*)
And I can see the files:
ls -alrt /rhev/data-center/mnt/*.*.*.*:_data_ovirt
total 4
drwxr-xr-x. 5 vdsm kvm 61 Oct 26 2016
1ed0a635-67ee-4255-aad9-b70822350706
-rwxr-xr-x. 1 vdsm kvm 0 Feb 5 14:37 __DIRECT_IO_TEST__
drwxrwxrwx. 3 root root 86 Feb 5 14:37 .
drwxr-xr-x. 5 vdsm kvm 4096 Feb 5 14:37 ..
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
----------------
Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180
Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
----------------
4 years, 9 months
Failed to add vm as host (CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION)
by Ritesh Chikatwar
Hello,
error is Host host moved to Non-Operational state as host CPU type is not
supported in this cluster compatibility version or is not supported at all.
Vm is running centos 8:
enabled nested virtualization by this way:
cat /sys/module/kvm_intel/parameters/nested
vi /etc/modprobe.d/kvm-nested.conf
---> Contains
options kvm-intel nested=1
options kvm-intel enable_shadow_vmcs=1
options kvm-intel enable_apicv=1
options kvm-intel ept=1
modprobe -r kvm_intel
modprobe -a kvm_intel
cat /sys/module/kvm_intel/parameters/nested
--> 1
Engine Log:
https://pastebin.com/hgrwzRhE
Ovirt-engine Cluster Version is 4.4
I am running ovirt engine on fedora 30.
Cluster CPU Type Intel Nehlam Family.
Any thoughts will be appreciated.
Rit
4 years, 9 months
