[ovirt-users] Re: What is the status of the whole Ovirt Project?

[Christopher Law]

Just out of curiosity how's the live migration in oVirt hyperconverged? Last I 
heard that didn't work well if at all. ZFS+DRBD is awesome, I had also read 
these don't work well together, so that's two things that surprised me reading 
this. 

There is a migration path to OLVM, if you can stand Oracle. I also considered 
OKD, but totally agree with the sentiment we have no idea what Red Hat are 
gunna pull out of next but it doesn't look good ☹

-Original Message-
From: Alex Crow via Users  
Sent: Saturday, September 2, 2023 4:09 PM
To: users@ovirt.org
Subject: [ovirt-users] Re: What is the status of the whole Ovirt Project?

All,

I'd rather base against either Rocky or Alma in the shorter term, or 
Ubuntu/Debian for a longer view. oVirt IMHO is a superior product to anything 
else if you know your way around it. Fantastic and informative GUI, a great set 
of APIs, and pretty solid in terms of storage support. 
I'm running it hyperconverged over ZFS+DRBD with Corosync and Pacecmaker in a 2 
node cluster.

I'm currently running a cluster on Rocky 8 and it's working perfectly at the 
moment. I'm not a fan of Gluster for its small I/O performance but I'm sure 
it's still a useful option for running VMs with heavy storage requirements with 
lesser small I/O performance requirements.

Fedora would get you fired from a lot of SME or enterprise environments. 
And with the mess around IBM/RH who knows if they'll drop OpenShift next and 
pull the devs out of OKD?

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FVSMQSPYXWJC3EO4IRM72HLPO3545V3O/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/US24IAXSLI3VQIXLVYGVFMDWC2YLSS6Q/

[ovirt-users] Re: 4.4.9 -> 4.4.10 Cannot start or migrate any VM (hotpluggable cpus requested exceeds the maximum cpus supported by KVM)

[Christopher Law]

I have this same issue, it’s actually only happening on a testing machine where 
the number of total available vcpus is less than 16. I also know kernel-ml 
isn’t supported but was wanting to do some testing with nested virt live 
migration which apparently is available with the kernel 5.x line.

Does anyone know how I can manually adjust the maxcpus=16 parameter that is 
passed to qemu-kvm to start VMs on this one machine?

Cheers,

Chris.

From: Jillian Morgan 
Sent: Wednesday, March 23, 2022 5:09 PM
To: users@ovirt.org
Subject: [ovirt-users] 4.4.9 -> 4.4.10 Cannot start or migrate any VM 
(hotpluggable cpus requested exceeds the maximum cpus supported by KVM)

After upgrading the engine from 4.4.9 to 4.4.10, and then upgrading one host, 
any attempt to migrate a VM to that host or start a VM on that host results in 
the following error:

Number of hotpluggable cpus requested (16) exceeds the maximum cpus supported 
by KVM (8)

While the version of qemu is the same across hosts, 
(qemu-kvm-6.0.0-33.el8s.x86_64), I traced the difference to the upgraded kernel 
on the new host. I have always run elrepo's kernel-ml on these hosts to support 
bcache which RHEL's kernel doesn't support. The working hosts still run 
kernel-ml-5.15.12. The upgraded host ran kernel-ml-5.17.0.

In case anyone else runs kernel-ml, have you run into this issue?
Does anyone know why KVM's KVM_CAP_MAX_VCPUS value is lowered on the new kernel?
Does anyone know how to query the KVM capabilities from userspace without 
writing a program leveraging kvm_ioctl()'s?

Related to this, it seems that ovirt and/or libvirtd always runs qmu-kvm with 
an -smp argument of "maxcpus=16". This causes qemu's built-in check to fail on 
the new kernel which is supporting max_vpus of 8.

Why does ovirt always request maxcpus=16?

And yes, before you say it, I know you're going to say that running kernel-ml 
isn't supported.

--
Jillian Morgan (she/her) ️‍⚧️
Systems & Networking Specialist
Primordial Software Group & I.T. Consultancy
https://www.primordial.ca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6FU6S3VGB7VQENUIKT4VRUDM2YJPH3C4/

[ovirt-users] Re: Very long reboot times of "RH" hosts with oVirt installed

[Christopher Law]

Are you making sure to reboot the hosts via the oVirt engine?

What I tend to do is put the host into maintenance mode, login and reboot it, 
once I know it's up I take it out of maintenance mode.

It's not good to reboot a host while it's active from its terminal you will 
have issues/risks with services not stopping, so you need to do it from the 
engine or by putting it into maintenance mode first.

I've had issues with the engine detecting the host is back up after a reboot 
and taking ages, so I tend to stick them into maintenance mode and reboot from 
the terminal. Otherwise no, it reboots normally for me.

Chris.


-Original Message-
From: Peter H  
Sent: 27 February 2023 13:15
To: users 
Subject: [ovirt-users] Re: Very long reboot times of "RH" hosts with oVirt 
installed

Peter H 

2:04 PM (0 minutes ago)


Sorry, my mail got sent before it was ready, so I try again ;-)

I was just wondering if anyone else is experiencing the following issue.

On both real physical machines and on VM where I have installed a RH derivative 
like CentOS, CentOS Stream, Rocky Linux or Alma Linux the reboot times are 
initially normal.

After installation of oVirt and all the dependencies the reboot
(shutdown) increases to anywhere between 3 and 5 minutes.

If I disable and stop the service wdmd.service reboot time is normal but after 
reboot the service is enabled again.

I have then masked the watchdog service and then reboot times are normal every 
time.

But I noticed that masking the watchdog service on a "Silver crown"
caused the "Hosted Engine HA" functionality to fail and the host lost its 
engine capabilities.

Is it safe to mask wdmd.service on normal hosts?

Can the reboot times be decreased on hosted engine hosts without breaking HA?

BR
Peter
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GEPNNXVB63IS7VWHSUEECVFNULDN2O67/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KXFZPGRESAXLXFCOY56J7NRCM4DPTQIE/

[ovirt-users] Re: Virtual Machine Pools

[Christopher Law]

Thanks for this.

In our environment the engine (physical host) is on an isolated network so 
“normal” users wouldn’t have access to this, but perhaps I can find a way to 
expose it or use the APIs you mention.

Cheers,

Chris.

From: Arik Hadas 
Sent: 06 November 2022 15:10
To: Christopher Law 
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Virtual Machine Pools



On Fri, Nov 4, 2022 at 9:19 PM Christopher Law 
mailto:ch...@chrislaw.me>> wrote:
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?

It generally refers to the VM portal - users should be able to access it and 
take virtual machines there and then, when their VM is allocated and started, 
they can connect to it using RDP. But it can alternatively be done using 
scripts/tools that do this via the API:
https://ovirt.github.io/ovirt-engine-api-model/4.5/#services/vm_pool/methods/allocate_vm


Cheers,

Chris.
___
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZMSC3D3HPW4VO6ZAHCEAFSTIK5BYOQ4J/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DLDA57INPUBLLYTCL6JLX4KPNIPX6P2R/

[ovirt-users] Virtual Machine Pools

[Christopher Law]

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?

Cheers,

Chris.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZMSC3D3HPW4VO6ZAHCEAFSTIK5BYOQ4J/

[ovirt-users] The latest guest agent needs to be installed

[Christopher Law]

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.

Any ideas?

Cheers,

Chris.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VCHUNZ4FAUH4MHHQTHEQBFRKLAUQCIIK/

[ovirt-users] Re: Export to Data Domain (with TPM)

[Christopher Law]

Milan thanks for the info, I suspected as much.

Yes it's a Windows 11 VM, so TPM is locked in the on position while Windows 11 
OS selected.

I'll keep an eye on the bug and see if I can work around it for now.

I suspect it will be problem if using the TPM for something like bitlocker, 
potentially losing the TPM data will mean having to enter the decryption key 
manually at boot and re-provision the TPM on restore.

Thanks again for taking the time to reply and filing a bug.

Chris.

-Original Message-
From: Milan Zamazal  
Sent: 05 October 2022 11:05
To: Christopher Law 
Cc: users@ovirt.org
Subject: Re: Export to Data Domain (with TPM)

Christopher Law  writes:

> Anyone explain why I can't export a Virtual Machine with a TPM? Is 
> this something to do with the TPM data? I'm exporting the VM to some 
> cold storage. What's the deal here how can I export it and keep the 
> TPM data or do I have to disable TPM on it first?
>
> oVirt Error message when trying to export a VM to a Data Domain that has a 
> TPM.
> Export VM Failed
> Cannot add VM. TPM device is required by the guest OS

Hi,

it is a Windows VM, right?  It is a bug, I filed
https://github.com/oVirt/ovirt-engine/issues/702 .  The export should work.

A workaround could be temporarily switching the VM operating system in the VM 
properties to Red Hat Enterprise Linux 9 before exporting but I'm not sure it 
won't change some other VM properties, be careful if you attempt it.

Regards,
Milan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/734DD6BPIQB5BXGL5DMKWICQ2COXTTT5/

[ovirt-users] Export to Data Domain (with TPM)

[Christopher Law]

Hi -

Anyone explain why I can't export a Virtual Machine with a TPM? Is this 
something to do with the TPM data? I'm exporting the VM to some cold storage. 
What's the deal here how can I export it and keep the TPM data or do I have to 
disable TPM on it first?

oVirt Error message when trying to export a VM to a Data Domain that has a TPM.
Export VM Failed
Cannot add VM. TPM device is required by the guest OS

Cheers,

Chris.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XI7AT2UMOITJFST4TOSXXLI4MIBHQDLO/

[ovirt-users] Re: VM hangs after migration

[Christopher Law]

Looks like the suggested workaround is to downgrade the kernel. Easier said 
than done when using the oVirt Node ISO minimal installs, the downgrade path is 
more challenging.


Get Outlook for Android<https://aka.ms/AAb9ysg>

From: Arik Hadas 
Sent: Monday, June 27, 2022 7:27:54 AM
To: John ; users 
Subject: [ovirt-users] Re: VM hangs after migration

FYI, this has been reported to the kernel/virtualization team, you can follow 
this bz:
https://bugzilla.redhat.com/show_bug.cgi?id=2079311

On Mon, Jun 27, 2022 at 1:55 AM John 
mailto:jmru...@gmail.com>> wrote:

I'm seeing this too on oVirt 4.5.1 using CentOS Stream 8 for the hosts. The 
console is blank, no response to ping and I have to power off the VM and power 
it back on again to recover it.

On 26/06/2022 19:53, Christopher Law wrote:

I have this exact same issue, did you guys get anywhere with this, or find the 
cause?



It’s difficult to debug because as far as the engine and hosts involved are 
concerned it was successful. It’s just the VM stops responding to pings etc 
after migration and the console freezes exactly as described here.



I’m using oVirt 4.5.1 Cluster 4.7. I’ve even reinstalled oVirt Node on the 
problem host still behaves the same. I’ve tried removing all VirtIO devices 
from the VM, I’ve tried with lower CPU family profiles, I’ve tried with 
different BIOS/UEFI settings.



In some cases the VM freezes moving away from the problem host as well which is 
interesting.



From: Arik Hadas <mailto:aha...@redhat.com>
Sent: 31 March 2022 15:11
To: Moshe Sheena <mailto:mshe...@redhat.com>
Cc: users <mailto:users@ovirt.org>
Subject: [ovirt-users] Re: VM hangs after migration



Moshe, this sounds similar to what we've seen in your environment, no?

Did you manage to resolve it?



On Thu, Mar 31, 2022 at 12:57 PM Giorgio Biacchi 
mailto:gior...@di.unimi.it>> wrote:

Hi,
I have a fresh Ovirt installation (4.4.10.7-1.el8 engine and oVirt Node
4.4.10) on a Dell VRTX chassis. There are 3 blades, two of them are
identical hardware (PowerEdge M630) and the third is a little newer
(PowerEdge M640). The third has different CPUs, more RAM, and slower
NICs. I also have a bunch of data domains some on the shared PERC
internal storage and others on an external iSCSI storage, all seems
configured correctly and all the hosts are operational.

I can migrate a VM back and forth from the first two blades without any
problem, I can migrate a VM to the third blade but when I migrate a VM
from the third blade to any of the other two the task terminate
successfully, the VM is marked as up on the target host but the VM
hangs, the console is frozen and the VM stops to respond to ping.

I have no clues about why this is happening and I'm looking for
suggestions about how to debug and hopefully fix this issue.

Thanks in advance
--
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
___
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HYHAVG3KDHMNVWNYROIIX2CTHSLFPVU3/



___
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VUOMGXGHJ46G2LY4D4SZPFQZ55M7RK3Z/


[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif]<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
  Virus-free. 
www.avast.com<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
___
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HT2DZWHJYZ36DHJGAMYRQO63FJYEFV3Z/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/co

[ovirt-users] Re: VM hangs after migration

[Christopher Law]

I have this exact same issue, did you guys get anywhere with this, or find the 
cause?

It’s difficult to debug because as far as the engine and hosts involved are 
concerned it was successful. It’s just the VM stops responding to pings etc 
after migration and the console freezes exactly as described here.

I’m using oVirt 4.5.1 Cluster 4.7. I’ve even reinstalled oVirt Node on the 
problem host still behaves the same. I’ve tried removing all VirtIO devices 
from the VM, I’ve tried with lower CPU family profiles, I’ve tried with 
different BIOS/UEFI settings.

In some cases the VM freezes moving away from the problem host as well which is 
interesting.

From: Arik Hadas 
Sent: 31 March 2022 15:11
To: Moshe Sheena 
Cc: users 
Subject: [ovirt-users] Re: VM hangs after migration

Moshe, this sounds similar to what we've seen in your environment, no?
Did you manage to resolve it?

On Thu, Mar 31, 2022 at 12:57 PM Giorgio Biacchi 
mailto:gior...@di.unimi.it>> wrote:
Hi,
I have a fresh Ovirt installation (4.4.10.7-1.el8 engine and oVirt Node
4.4.10) on a Dell VRTX chassis. There are 3 blades, two of them are
identical hardware (PowerEdge M630) and the third is a little newer
(PowerEdge M640). The third has different CPUs, more RAM, and slower
NICs. I also have a bunch of data domains some on the shared PERC
internal storage and others on an external iSCSI storage, all seems
configured correctly and all the hosts are operational.

I can migrate a VM back and forth from the first two blades without any
problem, I can migrate a VM to the third blade but when I migrate a VM
from the third blade to any of the other two the task terminate
successfully, the VM is marked as up on the target host but the VM
hangs, the console is frozen and the VM stops to respond to ping.

I have no clues about why this is happening and I'm looking for
suggestions about how to debug and hopefully fix this issue.

Thanks in advance
--
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to 
users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HYHAVG3KDHMNVWNYROIIX2CTHSLFPVU3/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VUOMGXGHJ46G2LY4D4SZPFQZ55M7RK3Z/

[ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted

[Christopher Law]

Hi Francesco –

I was using the latest oVirt Node ISO Image 4.4.10 (released on 3rd March), I 
believe this is a genuine bug in the oVirt Node ISO they have included libvirt 
8!

I reinstalled with the February release of oVirt Node ISO (same version 4.4.10) 
which has libvirt 7.10.0 and this has worked! So, my problem is resolved.

I’ll look to raise a bug report when I get a minute.

Cheers,

Chris.

From: Francesco Lorenzini 
Sent: 15 March 2022 08:14
To: Christopher Law ; Milan Zamazal 
Cc: francesco--- via Users 
Subject: Re: [ovirt-users] Re: Console - VNC password is 12 characters long, 
only 8 permitted

Hi Chris (sorry for the previous mispel),

I installed oVirt 4.4.8 on top on CentOS 8 (Stream and standard), never used 
Node ISO. Maybe enabling external repo? In a "test" server try to install the 
following rpm and then downgrade libvirt:

http://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm

Regards,
Francesco
Il 14/03/2022 18:31, Christopher Law ha scritto:
Thanks Francesco, it looks like a fix has been put into oVirt 4.5 which is 
scheduled for general release on the 12th April.

I’m using an oVirt Node ISO (4.4.10) install on the host are you doing the same 
or did you install oVirt on top of a standard centos install yourself?

I did try a dnf downgrade libvirt but it said there were no previous packages 
available. Just doing a re-install so will try your provided commands in a 
moment.

Cheers,

Chris.

From: Francesco Lorenzini 
<mailto:france...@shellrent.com>
Sent: 14 March 2022 17:23
To: Christopher Law <mailto:ch...@chrislaw.me>; Milan 
Zamazal <mailto:mzama...@redhat.com>
Cc: francesco--- via Users <mailto:users@ovirt.org>
Subject: Re: [ovirt-users] Re: Console - VNC password is 12 characters long, 
only 8 permitted

Hi Crhis,

I didn't resolve properly, I found that downgrading libvirt was the fastest 
workaround.

Just downgrade libvirt via yum/dnf to to version 7.10.  I added the downgrade 
in an Ansible task, if you are practical:

- name: Ensure libvirt-7.10.0 is installed
  yum:
name: libvirt-7.10.0
state: present
update_cache: true
allow_downgrade: true
  ignore_errors: true

or via cli :

yum install libvirt-7.10.0


Post dowgrade we performed a restart of vdsm (or super-vdsm, or both, I don't 
remember). The downgrade is quite safe, we didn't encounter any problem with 
existing hosts and new deployed one.

Francesco


Il 14/03/2022 15:58, Christopher Law ha scritto:

Hi -



Did anyone get a solution to this. I just upgraded our physical ovirt-engine to 
4.4.10 and added a freshly installed oVirt Node 4.4.10, and I'm getting this 
issue.



Given libvirt8 is part of oVirt Node 4.4.10 base install I was hoping for a 
fix. Also seen a fix applied here: 
https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b701105f9e1066b09f
 but not sure if this has been released?



What are my options, not quite sure how to downgrade libvirt in oVirt Node. I 
was planning on trying to install 4.4.9, but not sure if the ansible scripts 
will update it automatically when adding it to the cluster.



Francesco - Did you get this resolved?



Cheers,



Chris.



-Original Message-

From: Milan Zamazal <mailto:mzama...@redhat.com>

Sent: 14 February 2022 18:04

To: Francesco Lorenzini 
<mailto:france...@shellrent.com>

Cc: francesco--- via Users <mailto:users@ovirt.org>

Subject: [ovirt-users] Re: Console - VNC password is 12 characters long, only 8 
permitted



Francesco Lorenzini <mailto:france...@shellrent.com> 
writes:



Hi Milan,



thank you for your answer.



So there is no other way/workaround? We must wait the fix in the

engine and then upgrade? Maybe a downgrade of libvirt(?).



I can't think about any other workaround, without modifying sources, than 
downgrading libvirt, until the fixed Engine is installed.



I was looking up some config file in the host under /etc/libvirt and

found the parameters vnc_password in qemu.conf file. I'm not sure that

setting a password per host in this config file works, casue it is

still passed via xml...



In theory, you could set the default password there and remove passwords from 
the domain XMLs using Vdsm hooks.  You would have to do it on all the hosts or 
handle migrations accordingly.  Downgrading libvirt looks much easier.



The default VNC password. Only 8 bytes are significant for # VNC

passwords. This parameter is only used if the per-domain # XML config

does not already provide a password.



Francesco



Il 14/02/2022 12:41, Milan Zamazal ha scritto:

francesco--- via Users<mailto:users@ovirt.org>  writes:



Hi all,



I'm using websockify + noVNC for expose the vm console via browser getting  the 
graphicsconsoles ticket via API. Everything works fine for every other host 
that I have (more than 200), the console works either via oVirt engine and via 
browser) but just for a single host (CentOS Stream release 8

[ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted

[Christopher Law]

Thanks Francesco, it looks like a fix has been put into oVirt 4.5 which is 
scheduled for general release on the 12th April.

I’m using an oVirt Node ISO (4.4.10) install on the host are you doing the same 
or did you install oVirt on top of a standard centos install yourself?

I did try a dnf downgrade libvirt but it said there were no previous packages 
available. Just doing a re-install so will try your provided commands in a 
moment.

Cheers,

Chris.

From: Francesco Lorenzini 
Sent: 14 March 2022 17:23
To: Christopher Law ; Milan Zamazal 
Cc: francesco--- via Users 
Subject: Re: [ovirt-users] Re: Console - VNC password is 12 characters long, 
only 8 permitted

Hi Crhis,

I didn't resolve properly, I found that downgrading libvirt was the fastest 
workaround.

Just downgrade libvirt via yum/dnf to to version 7.10.  I added the downgrade 
in an Ansible task, if you are practical:

- name: Ensure libvirt-7.10.0 is installed
  yum:
name: libvirt-7.10.0
state: present
update_cache: true
allow_downgrade: true
  ignore_errors: true

or via cli :

yum install libvirt-7.10.0


Post dowgrade we performed a restart of vdsm (or super-vdsm, or both, I don't 
remember). The downgrade is quite safe, we didn't encounter any problem with 
existing hosts and new deployed one.

Francesco

Il 14/03/2022 15:58, Christopher Law ha scritto:

Hi -



Did anyone get a solution to this. I just upgraded our physical ovirt-engine to 
4.4.10 and added a freshly installed oVirt Node 4.4.10, and I'm getting this 
issue.



Given libvirt8 is part of oVirt Node 4.4.10 base install I was hoping for a 
fix. Also seen a fix applied here: 
https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b701105f9e1066b09f
 but not sure if this has been released?



What are my options, not quite sure how to downgrade libvirt in oVirt Node. I 
was planning on trying to install 4.4.9, but not sure if the ansible scripts 
will update it automatically when adding it to the cluster.



Francesco - Did you get this resolved?



Cheers,



Chris.



-Original Message-

From: Milan Zamazal <mailto:mzama...@redhat.com>

Sent: 14 February 2022 18:04

To: Francesco Lorenzini 
<mailto:france...@shellrent.com>

Cc: francesco--- via Users <mailto:users@ovirt.org>

Subject: [ovirt-users] Re: Console - VNC password is 12 characters long, only 8 
permitted



Francesco Lorenzini <mailto:france...@shellrent.com> 
writes:



Hi Milan,



thank you for your answer.



So there is no other way/workaround? We must wait the fix in the

engine and then upgrade? Maybe a downgrade of libvirt(?).



I can't think about any other workaround, without modifying sources, than 
downgrading libvirt, until the fixed Engine is installed.



I was looking up some config file in the host under /etc/libvirt and

found the parameters vnc_password in qemu.conf file. I'm not sure that

setting a password per host in this config file works, casue it is

still passed via xml...



In theory, you could set the default password there and remove passwords from 
the domain XMLs using Vdsm hooks.  You would have to do it on all the hosts or 
handle migrations accordingly.  Downgrading libvirt looks much easier.



The default VNC password. Only 8 bytes are significant for # VNC

passwords. This parameter is only used if the per-domain # XML config

does not already provide a password.



Francesco



Il 14/02/2022 12:41, Milan Zamazal ha scritto:

francesco--- via Users<mailto:users@ovirt.org>  writes:



Hi all,



I'm using websockify + noVNC for expose the vm console via browser getting  the 
graphicsconsoles ticket via API. Everything works fine for every other host 
that I have (more than 200), the console works either via oVirt engine and via 
browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the 
console works only via engine but when I try the connection via browser I get 
the following error (vdsm log of the host):



  ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 
characters long, only 8 permitted

  Traceback (most recent call last):

File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in 
method

  ret = func(*args, **kwargs)

File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in 
updateDevice

  return self.vm.updateDevice(params)

File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in 
updateDevice

  return self._updateGraphicsDevice(params)

File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in 
_updateGraphicsDevice

  params['params']

File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in 
_setTicketForGraphicDev

  self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0)

File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, 
in f

[ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted

[Christopher Law]

Hi -

Did anyone get a solution to this. I just upgraded our physical ovirt-engine to 
4.4.10 and added a freshly installed oVirt Node 4.4.10, and I'm getting this 
issue.

Given libvirt8 is part of oVirt Node 4.4.10 base install I was hoping for a 
fix. Also seen a fix applied here: 
https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b701105f9e1066b09f
 but not sure if this has been released?

What are my options, not quite sure how to downgrade libvirt in oVirt Node. I 
was planning on trying to install 4.4.9, but not sure if the ansible scripts 
will update it automatically when adding it to the cluster.

Francesco - Did you get this resolved?

Cheers,

Chris.

-Original Message-
From: Milan Zamazal  
Sent: 14 February 2022 18:04
To: Francesco Lorenzini 
Cc: francesco--- via Users 
Subject: [ovirt-users] Re: Console - VNC password is 12 characters long, only 8 
permitted

Francesco Lorenzini  writes:

> Hi Milan,
>
> thank you for your answer.
>
> So there is no other way/workaround? We must wait the fix in the 
> engine and then upgrade? Maybe a downgrade of libvirt(?).

I can't think about any other workaround, without modifying sources, than 
downgrading libvirt, until the fixed Engine is installed.

> I was looking up some config file in the host under /etc/libvirt and 
> found the parameters vnc_password in qemu.conf file. I'm not sure that 
> setting a password per host in this config file works, casue it is 
> still passed via xml...

In theory, you could set the default password there and remove passwords from 
the domain XMLs using Vdsm hooks.  You would have to do it on all the hosts or 
handle migrations accordingly.  Downgrading libvirt looks much easier.

>> The default VNC password. Only 8 bytes are significant for # VNC 
>> passwords. This parameter is only used if the per-domain # XML config 
>> does not already provide a password.
>
> Francesco
>
> Il 14/02/2022 12:41, Milan Zamazal ha scritto:
>> francesco--- via Users  writes:
>>
>>> Hi all,
>>>
>>> I'm using websockify + noVNC for expose the vm console via browser getting  
>>> the graphicsconsoles ticket via API. Everything works fine for every other 
>>> host that I have (more than 200), the console works either via oVirt engine 
>>> and via browser) but just for a single host (CentOS Stream release 8, oVirt 
>>> 4.4.9) the console works only via engine but when I try the connection via 
>>> browser I get the following error (vdsm log of the host):
>>>
>>>   ERROR FINISH updateDevice error=unsupported configuration: VNC password 
>>> is 12 characters long, only 8 permitted
>>>   Traceback (most recent call last):
>>> File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, 
>>> in method
>>>   ret = func(*args, **kwargs)
>>> File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in 
>>> updateDevice
>>>   return self.vm.updateDevice(params)
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in 
>>> updateDevice
>>>   return self._updateGraphicsDevice(params)
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in 
>>> _updateGraphicsDevice
>>>   params['params']
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in 
>>> _setTicketForGraphicDev
>>>   self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0)
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 
>>> 101, in f
>>>   ret = attr(*args, **kwargs)
>>> File 
>>> "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 
>>> 131, in wrapper
>>>   ret = f(*args, **kwargs)
>>> File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 
>>> 94, in wrapper
>>>   return func(inst, *args, **kwargs)
>>> File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in 
>>> updateDeviceFlags
>>>   raise libvirtError('virDomainUpdateDeviceFlags() failed')
>>>   libvirt.libvirtError: unsupported configuration: VNC password is 
>>> 12 characters long, only 8 permitted
>>>
>>>
>>> The error is pretty much self explanatory but, I can't manage to 
>>> figure out why only on this server
>> Hi,
>>
>> this happens with libvirt 8.0.
>>
>>> and I wonder if I can set the length of the generated vnc password 
>>> somewhere.
>> I don't think so, it must be fixed in Engine.  See 
>> https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b7
>> 01105f9e1066b09f
>> for more details.
>>
>> Regards,
>> Milan
>> ___
>> Users mailing list --users@ovirt.org
>> To unsubscribe send an email tousers-le...@ovirt.org Privacy 
>> Statement:https://www.ovirt.org/privacy-policy.html
>> oVirt Code of 
>> Conduct:https://www.ovirt.org/community/about/community-guidelines/
>> List
>> Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/messag
>> e/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/

[ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

[Christopher Law]

I should have pointed out that in my case the hosted engine failed to install. 
After the Local VM came up the host was marked as non-operational because the 
cluster (which I had given a custom name via ansible input) was set to 
compatibility 4.5 and was not changeable. No idea why the cluster was created 
at 4.5 if that is not supposed to be available yet or marked for some sort of 
future release. This caused the host to be non-operational with a warning that 
the “host” needed upgrading, so perhaps it’s a slightly different issue to that 
faced below.

If you have faced this issue though I would appreciated some advice on how to 
resolve it. I noticed the default cluster was marked as 4.4. My plan is 
therefore to re-install the hosted engine and use the “Default” datacentre and 
cluster names and changes these later.

From: Christopher Law 
Sent: 12 November 2020 09:21
To: Ritesh Chikatwar ; shadow emy 
Cc: users 
Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

I’ve also faced this issue, which is surprising since I used an ovirt node 
download for 4.4.

How did you resolve it? How can you upgrade to CentOS 8.3 or downgrade the 
cluster?

Thanks,

Chris.

From: Ritesh Chikatwar mailto:rchik...@redhat.com>>
Sent: 12 November 2020 05:10
To: shadow emy mailto:shadow.e...@gmail.com>>
Cc: users mailto:users@ovirt.org>>
Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

Hello,

To upgrade to cluster 4.5 you need a 8.3 host.
I guess still CentOS 8.3 is not available. I am not sure on CentOS 8.3 
availability.
If it's available please make sure your host is upgraded to 8.3 .


On Thu, Nov 12, 2020, 5:38 AM shadow emy 
mailto:shadow.e...@gmail.com>> wrote:

Just to confirm i face similar problem.
Yes i saw that  warning too :  "Upgrade Cluster Compatibility Level"   to 
upgrade the Cluster to version 4.5.
Though when i try to do that there are a lot of errors.

In GUI :

Error while executing action: Cannot change Cluster Compatibility Version to 
higher version when there are active Hosts with lower version.
-Please move Host host1, host2, host3  with lower version to maintenance first.

In engine.log :

WARN  [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-163) 
[2c681b74-8666-4f2f-b2e0-6b20e98f417e] Validation of action 'UpdateCluster' 
failed for user admin@internal-authz. Reasons: 
VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,$host host1, host2, 
host3,CLUSTER_CANNOT_UPDATE_COMPATIBILITY_VERSION_WITH_LOWER_HOSTS

I did not find any documentation for 4.5 cluster compatibility,  so i like as 
well to understand why is that option present there.
It will be used when ovirt 4.5.x will be released ?

___
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to 
users-le...@ovirt.org<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3UGQ6HPT2HTEGEP6GZUZ737SXR4K7TTJ/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/L3I25C6UC3YIHM3EDYW5YD5524OZYOFZ/

[ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

[Christopher Law]

I’ve also faced this issue, which is surprising since I used an ovirt node 
download for 4.4.

How did you resolve it? How can you upgrade to CentOS 8.3 or downgrade the 
cluster?

Thanks,

Chris.

From: Ritesh Chikatwar 
Sent: 12 November 2020 05:10
To: shadow emy 
Cc: users 
Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

Hello,

To upgrade to cluster 4.5 you need a 8.3 host.
I guess still CentOS 8.3 is not available. I am not sure on CentOS 8.3 
availability.
If it's available please make sure your host is upgraded to 8.3 .


On Thu, Nov 12, 2020, 5:38 AM shadow emy 
mailto:shadow.e...@gmail.com>> wrote:

Just to confirm i face similar problem.
Yes i saw that  warning too :  "Upgrade Cluster Compatibility Level"   to 
upgrade the Cluster to version 4.5.
Though when i try to do that there are a lot of errors.

In GUI :

Error while executing action: Cannot change Cluster Compatibility Version to 
higher version when there are active Hosts with lower version.
-Please move Host host1, host2, host3  with lower version to maintenance first.

In engine.log :

WARN  [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-163) 
[2c681b74-8666-4f2f-b2e0-6b20e98f417e] Validation of action 'UpdateCluster' 
failed for user admin@internal-authz. Reasons: 
VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,$host host1, host2, 
host3,CLUSTER_CANNOT_UPDATE_COMPATIBILITY_VERSION_WITH_LOWER_HOSTS

I did not find any documentation for 4.5 cluster compatibility,  so i like as 
well to understand why is that option present there.
It will be used when ovirt 4.5.x will be released ?

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to 
users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3UGQ6HPT2HTEGEP6GZUZ737SXR4K7TTJ/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6RTFYBUKKDAEN5KHFY4HXLOYKTLXPCPA/