I've try to install new hosted-engine version but deploy process finish with an error after vm start on shared storage (FC disks from SAN storage).
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check engine VM health]
this cuz Jboos web page not working
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
I open console to VM engine and...
disk dm-6 and dm-3 was corrupted - LOL - must fix by xfs_repair.
But after restart hosted-engne.service wont start.
● ovirt-engine.service - oVirt Engine
Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2022-10-31 15:35:30 CET; 4min 11s ago
Process: 1469 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE)
Main PID: 1469 (code=exited, status=1/FAILURE)
Oct 31 15:35:23 ovirt systemd: Starting oVirt Engine...
Oct 31 15:35:23 ovirt systemd: Started oVirt Engine.
Oct 31 15:35:26 ovirt ovirt-engine.py: 2022-10-31 15:35:26,606+0100 ovirt-engine: INFO _detectJBossVersion:186 Detecting JBoss version. Running: /usr/lib/jvm/jre-11-openjdk-11.0.>
Oct 31 15:35:30 ovirt ovirt-engine.py: 2022-10-31 15:35:30,369+0100 ovirt-engine: INFO _detectJBossVersion:206 Return code: -6, | stdout: '['#', '# A fatal error has been detect>
Oct 31 15:35:30 ovirt ovirt-engine.py: 2022-10-31 15:35:30,370+0100 ovirt-engine: ERROR run:543 Error: Cannot detect JBoss version
Oct 31 15:35:30 ovirt.pogodno systemd: ovirt-engine.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 15:35:30 ovirt.pogodno systemd: ovirt-engine.service: Failed with result 'exit-code'.
I even try to downgrade postgresql-jdbc to 42.2.3 but no effect.
If I stop deploy process when VM start from local storage and I dont continue it - engine VM start with no error but VM start without HA IP configured - not usefully.
So I still witing to good working - ovirt-engine-appliance 4.5
after setting up a new oVirt Cluster with buildin keycloak i have issues login in as admin@ovirt, looks like i saved the wrong password in my password manager, now i have issues finding a way to reset the password of this user to do administration in the keycloak admin console, i tried changing the password with:
/usr/share/ovirt-engine-keycloak/bin/add-user-keycloak.sh and /usr/share/ovirt-engine-wildfly/bin/add-user-keycloak.sh. Both without success, i found i can create a new "keycloak-add-user.json" with the second command and i can copy it over to the right place where the old file was, after rebooting the hosted engine this has no effect.
Is there a known way to reset admin@ovirt with the internal keycloak? i cant find anything in the docs.
We decided to run the oVirt engine (Oracle flavor) outside the infrastructure. (Medium infrastructure, 10 Hosts, iSCSI storage arrays)
We created a second, smaller infrastructure (Single host, local storage) for management (engine) and monitoring (nagios, Dell storage manager etc..) . .
This secondary infrastructure's engine runs in the first infrastructure.
So, If you picture it, we're facing a "bootstrap" cross-dependency problem where each engine need the other one to start.
This is actually a design we had when we were using Xen (Oracle's).
Xen provides the "xen create" command to start a VM, even w/o a manager. Bootstrap problem solved.
We're moving to oVirt and I understand that oVirt does not support out-of-the-box starting a VM w/o the engine.
I've found a workaround that seems to work and would like your advice :
- keep a dump of XML of the engine VM
# virsh -r dumpxml prodEngine > prodEngine.xml
- When necessary use virsh to start the engine
# virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf create prodEngine.xml
The only visible problem is a warning at the VM that was started manually saying "Newer configuration for next run". A restart clears the warning and there's does not seem to be consequences with the VM that had been started from a dump xml.
Note : I understand that there is the "self-hosted" engine architecture that solves that "bootstrap" problem. We're no into that for now. We had bad experience with that design in the past.
Christopher Law <chris(a)chrislaw.me> writes:
> I've got a couple of VMs giving me this error message, "the latest
> guest agent needs to be installed and running". These VMs have the
> latest guest agent installed and it is running (virtio-win-1.9.24.iso)
You're probably hitting https://bugzilla.redhat.com/2120381. It should
get fixed in the next release.
I just discovered that my default management network has the "VM Network" checkbox toggled (on the page where you navigate to Network -> Networks and select the management network).
There are no virtual machines associated with the management network.
Is it safe to simply edit the management network and uncheck the "VM Network" box? Will anything break (even temporarily) if I do this?
Sent with Proton Mail secure email.
Hopefully, someone can clarify this a bit for me...
From the redhat instructions...
"In principle, virtual machines in a pool are started when taken by a user, and shut down when the user is finished. However, virtual machine pools can also contain pre-started virtual machines. Pre-started virtual machines are kept in an up state, and remain idle until they are taken by a user. This allows users to start using such virtual machines immediately, but these virtual machines will consume system resources even while not in use due to being idle."
How do users request "take" virtual machines from the pool? For example with a windows machine where we want them to remote desktop into it using RDP? Or does this have to happen through some other portal? Do we have to give users access to the VM Portal?
I've got a couple of VMs giving me this error message, "the latest guest agent needs to be installed and running". These VMs have the latest guest agent installed and it is running (virtio-win-1.9.24.iso)
The only change to the environment recently was one host has been upgraded from 4.5.2 to 4.5.3. It seems to be the VMs that had at one point ran on this updated host. However, that host is currently turned off they are running on 4.5.2 hosts and have been rebooted. These are Windows Server 2022, 2019 and Windows 11 VMs.
I will be updating the rest of the hosts this weekend so can see what happens then. The qemu-guest-agent tools is the same version running elsewhere even tried to repair it no change.
Hello, can you pls help me with creating my oVirt system. I installed Centos 7 on one VM and on one physical server. I succesfully configured my VM for oVirtEngie and I can access to web interface.
Now I want to configure my physical server to use it as virtualization server(kvm01). My VM has 2 disks, one for system and one for ISO images. My phisycal server also has 2 disks(actually 4 but in 2 Raid1). One for system and one for virtualization storage. Its the second time I try to install everything properly, 1st time I had some issues and decided to reinstall everything. 1st time I successfully added my kvm01 to my ovirtengine, but I couldnt create any VM because I had error with my Data Center, that had status uninitialized, and it seems like I cant initialize it because I have no domain. I'm already confused and decided to ask forum for a correct answer and advices. What shell I do first? I havent added kvm01 to my ovirtEngine yet.
Good morning gentlemen.
I have a weird problem with a setup I finished.
I'm using oVirt 4.4 Hosted Engine with NFS as Storage Domain, it happens
that, if the Storage disconnects, in a few minutes the machine restarts and
the red LED lights up as if there had been a crash.
I managed to capture a screenshot of this moment once, OOM-Killer killed
modprobe which doesn't make much sense as there is no VM other than the
Hosted Engine and there is 128G of RAM on the machine.
is there anybody else out there having problems to connect to a vm console via vnc or is it just me?
We are running ovirt-engine 184.108.40.206-1.el8 on up to date ovirt-nodes. I can connect to every virtual machine by spice, but am unable to connect via vnc due to a tls handshake error.
Remote-viever just shows "Failed to complete handshake Error in the pull function" (on windows and linux clients).
Wireshark tls handshake capture looks supicious to me, server hello message is just 182 bytes long and doesn't coantain a server certificate. Is this normal?