- Users - oVirt List Archives

Failed to migrate VM to Host ovirt3.XXX.cz due to an Error: Fatal error during migration. Trying to migrate to another Host.
by Jirka Simon 14 Dec '23

14 Dec '23

Hello there, after today's update I have problem with live migration to this host. with message 2023-12-14 10:00:01,089+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [67218183] VM '77f85710-45e7-43ca-b0f4-69f87766cc43'(ca1.access.prod.hq.sldev.cz) was unexpectedly detected as 'Down' on VDS '044b7175-ca36-49b2-b01b-0253f9af7e4f'(ovirt3.corp.sldev.cz) (expected on '858b8951-9b5a-4b8f-994e-4e11788c34d6') 2023-12-14 10:00:01,090+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-11) [67218183] START, DestroyVDSCommand(HostName = ovirt3.corp.sldev.cz, DestroyVmV DSCommandParameters:{hostId='044b7175-ca36-49b2-b01b-0253f9af7e4f', vmId='77f85710-45e7-43ca-b0f4-69f87766cc43', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 696e7f0e 2023-12-14 10:00:01,336+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-11) [67218183] FINISH, DestroyVDSCommand, return: , log id: 696e7f0e 2023-12-14 10:00:01,337+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [67218183] VM '77f85710-45e7-43ca-b0f4-69f87766cc43'(ca1.access.prod.hq.sldev.cz) was unexpectedly detected as 'Down' on VDS '044b7175-ca36-49b2-b01b-0253f9af7e4f'(ovirt3.corp.sldev.cz) (expected on '858b8951-9b5a-4b8f-994e-4e11788c34d6') 2023-12-14 10:00:01,337+01 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [67218183] Migration of VM 'ca1.access.prod.hq.sldev.cz' to host 'ovirt3.corp.sldev.c z' failed: VM destroyed during the startup. When I stop a VM and start it again it starts on affected without any problem, but migration doesn't work. thank you for any help. Jirka

3 6

Grafana - Origin Not Allowed
by Maton, Brett 14 Dec '23

14 Dec '23

oVirt 4.5.0.8-1.el8 I tried to connect to grafana via the monitoring portal link from the dash and all panels are failing to display any data with varying error messages, but all include 'Origin Not Allowed' I navigated to Data Sources and ran a test on the PostgreSQL connection (localhost) which threw the same Origin Not Allowed error message. Any suggestions?

6 8

virsh console support
by marek 13 Dec '23

13 Dec '23

hi, is it possible use virsh console on ovirt host? [root@server ~]# virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf console 21 --safe Connected to domain 'server-dev-1' Escape character is ^] (Ctrl + ]) error: internal error: character device ua-e4d8f97d-a7dd-4769-972c-27412212b955 is not using a PTY dumpxml 21 shows <console type='unix'> <source mode='bind' path='/var/run/ovirt-vmconsole-console/5a06d390-431c-48b5-9fb6-ebc34af73a88.sock'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> Marek

1 0

Move SHE to a LUN on another storage appliance
by Colin Coe 12 Dec '23

12 Dec '23

Hi all I'm decommissioning an old SAN that holds our DEV/TST RHV instance. I'm following https://access.redhat.com/solutions/6529691 (How to move the Hosted-Engine storage to a new storage domain) and I'm on step 9 (Make sure that the self-hosted engine is shut down). hosted-engine --vm-status is reporting: hosted-engine --vm-status | grep -E 'Engine status|Hostname' Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : rhvh01.example.com Engine status : {"vm": "down_unexpected", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : rhvh02.example.com Even though the vm is definitely shut down. The instructions say call Red Hat but its nearly 6PM and we only have standard support for this environment. Any ideas on how to resolve this? I'm not sure if it's a big issue but I don't want to cause myself more problems later. Thanks

1 0

Migrate Hosted-Engine to different cluster
by Michaal R 12 Dec '23

12 Dec '23

I know this question pops up on a regular with this forum, but my best search engine manipulation turned up only to back up the engine configuration to a shared storage, then restore it on the other cluster using hosted-engine --deploy --restore-from-file=backup.tar.gz. While this is workable (it's by no means the end of the world for me), I wanted to ask if a different or better way has been or will be implemented. Here's why: I am trying to move to oVirt from ESXi (the latter has outgrown its usefulness to me and has become increasingly more difficult to maintain for my purposes, as VMware is intent on pushing newer CPU technologies with each new version, leaving perfectly good systems with perfectly good processors and hardware out in the cold. On top of that, VMware won't let you easily do vGPU or GPU passthrough without significant risk to the system stability.). I started with a VM on the ESXi host as a proof-of-concept for setting up and configuring oVirt to run the hosted engine and a couple of VMs. This worked after some great work from the members here on the forum (shout out to Tomas and Arik!). This initial cluster is an Intel CPU based cluster, as the server its VM is running on is an R720. This is the server I need to migrate off of (I have a plan). So I set up in VMware Workstation on my PC a second host in its own cluster (as that machine is an AMD CPU machine). Now, I know I can't live migr ate between clusters to begin with, but I was hoping there was an easier way to move the hosted-engine to the shared NAS storage, put the hosted-engine in maintenance mode, shut it down, change a variable or three with the --set-shared-config option (if that applies), run some script on the other host that starts the hosted-engine on that host in that cluster, bringing it out of maintenance mode automatically once up and verified stable. I understand that process COULD be slower and more fraught with danger than just simply backing up the config to shared storage and deploying on the AMD host with the restored config, but on the off-chance it ISN'T I wanted to explore that possibility. Besides, it would be a nice feature of the hosted-engine and oVirt as a whole if you could eventually right-click the hosted-engine VM in the portal and click "Move to new cluster...", which would automate that entire process for you. All that said, I'm working on one last problematic VM import before I start the arduous process of pulling everything off of ESXi and reformatting the R720 for oVirt. Hopefully that goes smoother than my start with oVirt. :)

2 1

[ANN] oVirt 4.5.5 is now generally available
by Sandro Bonazzola 12 Dec '23

12 Dec '23

oVirt 4.5.5 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.5.5, as of December 1st, 2023. Important notes before you install / upgrade If you’re going to install oVirt 4.5.5 on RHEL or similar, please read Installing on RHEL or derivatives <https://ovirt.org/download/install_on_rhel.html> f irst. Suggestion to use nightly As discussed in oVirt Users mailing list <https://lists.ovirt.org/archives/list/users@ovirt.org/thread/DMCC5QCHL6ECXN…> we suggest the user community to use oVirt master snapshot repositories <https://ovirt.org/develop/dev-process/install-nightly-snapshot.html> ensuring that the latest fixes for the platform regressions will be promptly available. This oVirt 4.5.5 release is meant to provide what has been made available in nightly repositories as base for new installations. If you are already using oVirt master snapshot you should already have received this release content. Documentation Be sure to follow instructions for oVirt 4.5! - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.5.5 Release? This release is available now on x86_64 architecture for: - oVirt Node NG (based on CentOS Stream 8) - oVirt Node NG (based on CentOS Stream 9) - CentOS Stream 8 - CentOS Stream 9 - RHEL 8 and derivatives - RHEL 9 and derivatives Experimental builds are also available for ppc64le and aarch64. See the release notes for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.5.5 release highlights: https://www.ovirt.org/release/4.5.5/ - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ -- Sandro* Bonazzola* oVirt Project

9 12

ovirt node NonResponsive
by carlos.mendes＠mgo.cv 12 Dec '23

12 Dec '23

Hello, I have ovirt with two nodes and one that are NonResponsive and and cant manage them because they are in Unknown state. It seems that nodes lost connection for a while with their gateway. The node (ovirt2) however is having consistent problems. The follow sequence of events is reproducible and is causing the host to enter a "NonOperational" state on the cluster: What is the proper way of restoring management? I have a two-node cluster with the ovirt manager running standlone on the virtual maachine CentOS-Stream-9 and the ovirt node running the most recent oVirt Node 4.5.4 software. I can then re-activate ovirt2, which appears as green for approximately 5 minutes and then repeats all of the above issues. What can I do to troubleshoot this?

1 0

How can I list virtual disk using python sdk
by biancasantanaes＠gmail.com 11 Dec '23

11 Dec '23

Hi, how can I list all disk attached/detached to a virtual machine in OLVM, using Python SDK?

1 0

Something went wrong, connection is closed web vnc console
by antonio.riggio＠mail.com 11 Dec '23

11 Dec '23

After our admin updated the cert for ovirt after getting PKIK path validation failed:java.security.cert when trying to login. I get Something went wrong, connection is closed when trying to access console with noVnc. Any ideas what can cause this ? Thank you

1 1

Installing MS server 2022 on Software Version:4.5.3.2-1.el8
by antonio.riggio＠mail.com 05 Dec '23

05 Dec '23

Im pretty knew to ovirt we are running in our env . I am having trouble getting MS server 2022 installed I get error Boot0002 "UFEI QUMU QEMU HARDISK

2 2