Hello,
Can you provide more details how you performed the conversion and export? The
size could be due to it being thin provisioned.
I guess you could just take the vmdk image from VMware and convert it to qcow2
with something like this:
qemu-img convert -p -f vmdk -O qcow2 testvm.vmdk
Hey,
This post is confusing. I'm assuming you installed a couple of Rocky Linux
servers. This would have happened after June 21, 2021, when the first stable
release of Rock Linux was released.
You write that oVirt 4.3.10.4-1.el7, released on 2020-05-22, was chosen to
manage those servers. Why
Thats a brilliant catch... noted for future use :-) It looks like you make
engine-setup ignore that check, suggesting something is not right somewhere in
the HE environment. But it fixes the cert problem and as there is nothing else
the matter, it serves a purpose :-)
oVirt definitely involves a lot of paddling. I see now that you are right about
HCI (Hyper Converged Platform), it was never specifically documented how to
upgrade it. I have stepped away from HCI a long time ago, after testing and
working with it in oVirt 3.x. There were just too many
Hello. I just encountered this myself last night. I found the solution on red
hats customer portal. It was suggested to run setup-engine once more, as it
will renew the self-signed certficates. It worked for me, though I'm running on
oVirt 4.5.4-1.el8.
Remember to run this command on a oVirt
Hey guys,
I have tried to write on the IRC channel, regarding this issue, but I'm no sure
if I'm not doing it right or maybe there are not many people watching the
#ovirt channel.
We have deployed a 6 node oVirt cluster, and have moved roughly 100 VMs on
them. We started the cluster with NFS
6 matches
Mail list logo
