Hi,
it seems that the config values in your database are not correct or up to
date - it might be worth trying to run the engine-setup again (it should
insert the correct values).
Lucia
On Wed, Nov 18, 2020 at 10:07 AM wrote:
> Hi,
> After updating to the latest version of ovirt (standalone
On Thu, Nov 19, 2020 at 6:17 PM Alex McWhirter wrote:
> I'm not sure if I' missing something, but it seems there is no way built
> in to oVirt to manage OVN outside of network / subnet creation. In
> particular routing both between networks and to external networks.
>
> Of course you have the
Hi,
oVirt CPU detection depends on libvirt (and that depends on qemu) CPU
models. Could you please run the following command to see what libvirt
reports?
virsh domcapabilities
That should give you the list of CPUs known to libvirt with a usability
flag for each CPU.
If you find out that the
Hello Wodel,
This might be helpful for you iguess
https://ovirt.org/documentation/data_warehouse_guide/
On Fri, Nov 20, 2020 at 3:09 AM wodel youchi wrote:
> Hi,
>
> Is there any documentation explaining how to use grafana portal to extract
> metrics data from ovirt ?
>
> Regards.
>
On Wed, Nov 18, 2020 at 7:30 PM Facundo Badaracco
wrote:
> Hi everyone!
>
> Hope someone can help me with this..
>
> I have 3 servers with centos 8 and ovirt 4 installed. Each server has 2
> nic.
> Server A = HE (HA)
> Nic1= 192.169.2.24 Nic2=no ip
> Server B = HE (HA)
> Nic1= 192.169.2.25
Hello,
I needed to rename all domain names from my NFS storage. VM data and
seconds data domains was no problem. But when I try to rename the domain
from export domain, a red popup on top opens with this message:
Uncaught exception occurred. Please try reloading the page. Details:
Hi,
I today tested the steps. Actually it worked but I needed to add a few things.
0. Gluster snapshots on all volumes
I did not need that.
1. Set a node in maintenance
2. Create a full backup of the engine
3. Set global maintenance and power off the current engine
4. Backup all gluster
Following the above, I was seeing that OVN provider connectivity test was
failing due to some certificate issue and had to do the following to fix
it:
names="ovirt-provider-ovn"
subject="$(\
openssl x509 \
-in /etc/pki/ovirt-engine/certs/apache.cer \
-noout \
-subject | \
Once upon a time, Strahil Nikolov said:
> I would recommend you to check this one:
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/administration_guide/chap-event_notifications
Thanks, that's exactly what I needed!
--
Chris Adams
Hi Lucia,
I had to create an user for virsh:
# saslpasswd2 -a libvirt test
Password:
Again (for verification):
With that in mind, here’s the outputs:
/usr/libexec/qemu-kvm
kvm
pc-i440fx-rhel7.6.0
x86_64
/usr/share/OVMF/OVMF_CODE.secboot.fd
rom
I found it much easier to ignore all the DataWarehouse stuff and used a
project called prometheus Ovirt Exporter, spun up in a docker host, and use
the prom datasource in Grafana. I was up and running with good Ovirt
metrics in minutes.
*Vincent Royer*
*778-825-1057*
Hi,
I was trying to move a disk between glusters domain storage without success.
# gluster --version
glusterfs 6.10
Now have a VM with this message:
The VM has snapshot(s) with disk(s) in illegal status. Please don't shutdown
the VM before successfully retrying the snapshot delete
Additionally you can also install official Prometheus Node_Exporter on each of
your KVM hosts and that will give you tons of operating system metrics. This is
not "ovirt aware", so you will not see any ovirt objects related metrics but
will allow you to keep an eye on your kvm hosts
Can you try a live migration ?
I got a similar case and the live migration somehow triggered a fix.
Best Regards,
Strahil Nikolov
В петък, 20 ноември 2020 г., 21:04:13 Гринуич+2,
написа:
Hi,
I was trying to move a disk between glusters domain storage without success.
# gluster
I tried to move the VM disk with the VM up
I also tried to move or copy the disk with the VM down, and get the same error.
Strange is, I have a gluster storage domain, with an older gluster version,
that worked. I was able to move the disk to this older gluster and also I was
able to copy the
I can recommend you to:
- enable debug level of gluster's bricks
- try to reproduce the issue
I had similar issue with gluster v6.6 and above.
Best Regards,
Strahil Nikolov
В петък, 20 ноември 2020 г., 23:35:14 Гринуич+2,
написа:
I tried to move the VM disk with the VM up
I also
16 matches
Mail list logo
