new host addition, Cannot find master domain
by david
hello
i'm adding a new host into ovirt
after the installation procces is finished I got an error: "VDSM kvm6
command ConnectStoragePoolVDS failed: Cannot find master domain".
on the vdsm server in /dev/disk/by-path/ i see the block device but
device-mapper not mappying it
then I found the master's lun in the blacklist:
/etc/multipath/conf.d/vdsm_blacklist.conf
why vdsm host put the lun wwn in blacklist and what I can do ?
addition info:
============
Ovirt-engine 4.4.7
vdsm server:
- OS Version: RHEL - 8.5 - 1.2111.el8
- OS Description: CentOS Linux 8
- Kernel Version: 4.18.0 - 348.2.1.el8_5.x86_64
- KVM Version: 6.0.0 - 33.el8
- LIBVIRT Version: libvirt-7.6.0-6.el8
- VDSM Version: vdsm-4.40.90.4-1.el8
the vdsm server has one link connection to the fc storage lun
2 years, 4 months
ovirt 4.4.x series
by Nathanaël Blanchet
Hello,
I found some informations about an upcoming ovirt 4.5 release based on
centos stream 9. Considering that Centos stream 9 will not be stable
before months, can we expect new 4.4.x releases following 4.4.9?
--
Nathanaël Blanchet
Supervision réseau
SIRE
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
2 years, 4 months
Downgrading qemu-kvm
by Gary Pedretty
So even the latest updated to qemu-kvm is still broken in regards to running VMs in Ovirt. I thought I would try Node on a new host and the current install iso, installs version 6.0 of kvm, which still works, but if you do an upgrade on the node host it sill updates to the latest 6.1 version of kvm. Question, how do you downgrade kvm on a node host, the regular yum downgrade does not seem to work on a node host.
Gary
_______________________________
Gary Pedretty
Director of IT
Ravn Alaska
2 years, 4 months
oVirt host - yum dependency error
by tferic@swissonline.ch
Hi
I have an existing oVirt host 4.4 running on CentOS 8, and I am in the
process of converting the OS to CentOS Stream.
I am getting the following errors:
```
# yum update
Last metadata expiration check: 0:03:14 ago on Wed 08 Dec 2021 01:05:55
AM CET.
Error:
Problem 1: package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires
rsyslog-openssl, but none of the providers can be installed
- package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog =
8.2102.0-5.el8, but none of the providers can be installed
- cannot install both rsyslog-8.2102.0-6.el8.x86_64 and
rsyslog-8.2102.0-5.el8.x86_64
- cannot install both rsyslog-8.2102.0-5.el8.x86_64 and
rsyslog-8.2102.0-6.el8.x86_64
- cannot install the best update candidate for package
rsyslog-8.2102.0-5.el8.x86_64
- cannot install the best update candidate for package
ovirt-host-dependencies-4.4.8-1.el8.x86_64
Problem 2: package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires
rsyslog-openssl, but none of the providers can be installed
- package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog =
8.2102.0-5.el8, but none of the providers can be installed
- cannot install both rsyslog-8.2102.0-6.el8.x86_64 and
rsyslog-8.2102.0-5.el8.x86_64
- cannot install both rsyslog-8.2102.0-5.el8.x86_64 and
rsyslog-8.2102.0-6.el8.x86_64
- package rsyslog-elasticsearch-8.2102.0-6.el8.x86_64 requires
rsyslog = 8.2102.0-6.el8, but none of the providers can be installed
- package ovirt-host-4.4.9-2.el8.x86_64 requires
ovirt-host-dependencies = 4.4.9-2.el8, but none of the providers can be
installed
- cannot install the best update candidate for package
rsyslog-elasticsearch-8.2102.0-5.el8.x86_64
- cannot install the best update candidate for package
ovirt-host-4.4.8-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages or '--nobest'
to use not only best candidate packages)
```
Does anyone know how to resolve it?
Notice: The oVirt host is also a gluster storage server (hyperconverged).
Thanks
Toni
2 years, 4 months
Q35 with BIOS broken
by mediocre.slacker@protonmail.com
I've been trying to get oVirt working for a week now with a self-hosted engine setup. Eventually, today, I decided to try a standalone engine and see if I can't at least get that to work, to maybe figure out what the issue is.
It seems the default chipset type is Q35 with BIOS. But it fails to boot a VM. I'm not sure where to even look in the logs for this. The VM just never comes up, even though it's shown as being up in the oVirt administration page. I found similar symptoms when trying to set up a hosted-engine on the same machine. The VM would fail health check, and hosted-engine --vm-status would show the VM as up, but health check failing. The VM wasn't available over the network and it never pulled a DHCP lease from my router. I've looked at the logs pretty extensively and couldn't find anything to indicate what the cause of the problem was, or that this was even the problem in the first place. As far as the logs seem to be concerned, the VM is running fine, and it's a network issue.
2 years, 4 months
no QXL ?
by lejeczek
Hi.
I've Qemu/Libvirt from
ovirt-release-master-4.5.0-0.0.master.20211206152702.gitebb0229.el9.noarch
and it seems QXL is not there.
Is that a fluke or intention?
Do you have QXL working?
many thanks, L.
2 years, 4 months
Migrated a VM from VMware to Ovirt using import ova option. Task stuck and running for day 2 now.
by sudhakar.sankaralingam@gmail.com
1. First node that was upgraded now continuously logs this error:
VDSM <node name> command Get Host Statistics failed: Internal JSON-RPC error:
{'reason': "'str' object has no attribute 'decode'"}
2. During import of two virtual machines from VMware (has done multible before upgrade)
the import seems to never finish - currently running on day 2-3... any clues how to fix
this?
Events VDSM <node name> command Get Host Statistics failed: Internal JSON-RPC error:
{'reason': "'str' object has no attribute 'decode'"} running for 2 days every 20 seconds. Please suggest
2 years, 4 months
what is the best practices to delete vdisks in 100% used gluster stoargedoamin
by dhanaraj.ramesh@yahoo.com
Hi Team
In my one of three node Hyperconverged (gluster + ovirt) setup, one of the storage domain went offline from Datacenter due to 100% storage space utilization, but luckily it is still online in Gluster. how should I properly delete some of the vdisks in that offline stoarge domain from Gluster and bring back to online?
2 years, 4 months
ovirt importing vm stuck
by Sudhakar S
Hi Team,
I have initiated a VM import from VMware using Import as OVA option in
Ovirt.
I started importing and all going good but it is stuck at the last. Please
find the below attached screenshot FYR.
Please suggest me your steps to stop this task since it is running for a
whole day.
[image: image.png]
[image: Ovirt2.PNG]
[image: Ovirt.PNG]
Regards,
Sudhakar
2 years, 4 months
Various issues
by mediocre.slacker@protonmail.com
Fresh install on CentOS Stream 8. After installing ovirt-hosted-engine-setup, I encounter the following dependency errors when trying to run dnf upgrade:
Error:
Problem 1: package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 8.2102.0-5.el8, but none of the providers can be installed
- cannot install both rsyslog-8.2102.0-6.el8.x86_64 and rsyslog-8.2102.0-5.el8.x86_64
- cannot install the best update candidate for package rsyslog-openssl-8.2102.0-5.el8.x86_64
- cannot install the best update candidate for package rsyslog-8.2102.0-5.el8.x86_64
Problem 2: package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires rsyslog-openssl, but none of the providers can be installed
- package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 8.2102.0-5.el8, but none of the providers can be installed
- cannot install both rsyslog-8.2102.0-6.el8.x86_64 and rsyslog-8.2102.0-5.el8.x86_64
- package rsyslog-elasticsearch-8.2102.0-6.el8.x86_64 requires rsyslog = 8.2102.0-6.el8, but none of the providers can be installed
- cannot install the best update candidate for package rsyslog-elasticsearch-8.2102.0-5.el8.x86_64
- cannot install the best update candidate for package ovirt-host-dependencies-4.4.9-2.el8.x86_64
Problem 3: problem with installed package rsyslog-openssl-8.2102.0-5.el8.x86_64
- package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 8.2102.0-5.el8, but none of the providers can be installed
- cannot install both rsyslog-8.2102.0-6.el8.x86_64 and rsyslog-8.2102.0-5.el8.x86_64
- package rsyslog-mmjsonparse-8.2102.0-6.el8.x86_64 requires rsyslog = 8.2102.0-6.el8, but none of the providers can be installed
- cannot install the best update candidate for package rsyslog-mmjsonparse-8.2102.0-5.el8.x86_64
Problem 4: package ovirt-host-4.4.9-2.el8.x86_64 requires ovirt-host-dependencies = 4.4.9-2.el8, but none of the providers can be installed
- package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires rsyslog-openssl, but none of the providers can be installed
- package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 8.2102.0-5.el8, but none of the providers can be installed
- cannot install both rsyslog-8.2102.0-6.el8.x86_64 and rsyslog-8.2102.0-5.el8.x86_64
- package rsyslog-mmnormalize-8.2102.0-6.el8.x86_64 requires rsyslog = 8.2102.0-6.el8, but none of the providers can be installed
- cannot install the best update candidate for package rsyslog-mmnormalize-8.2102.0-5.el8.x86_64
- cannot install the best update candidate for package ovirt-host-4.4.9-2.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Running dnf distro-sync --nobest allows it to proceed, which causes some ovirt packages to be upgraded.
Running hosted-engine --deploy and installing with nfs storage, everything goes good up until stage 5, at which point vdsm pegs a core at 100% for some minutes, until the task inevitably fails. hosted-engine --vm-status reports EngineStarting forever. No memory is consumed to indicate that the VM even started. The VM never even tries to get a DHCP lease from my router. All indicators point the vm just not starting, for some reason.
Zero useful information available on Google. Zero useful information available in the documentation. Zero useful information available in the logs. No clear cause as to why the hosted engine refuses to start. The NFS share has correct permissions, and can be mounted. The NFS share is on the same host the engine is being installed to, in the same subnet/vlan and, even through the same network adapter. The shared storage works fine for copying the local hosted engine to the shared storage during the setup process and I can see the files have been created.
2 years, 4 months