[ovirt-users] Question about cloud-init

2021-07-30 Thread tommy 
Hello, I have a question about cloud-init: 

After installing vm, I installed cloud-init immediately, and enabled its
four services, and then I can use cloud-init in the admin interface.  

 

However, I don't know how cloud-init knows where to get the relevant
information (such as host name, SSH secret key, etc.) that I configured on
the admin interface ?  For I haven't configured the data source for
cloud-init.  

Why it can works ?

 

Thanks!

___
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/O5NKQO5642X3WYES3QQBSSDZUQN6N5XX/

[ovirt-users] Re: Changing the Password Expiration for a User

2021-07-30 Thread louisb 
It worked great thanks for you help.
___
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/7Y2ODH4DA4WSVP6WTGJVQTK3B4WXKFKK/

[ovirt-users] Re: Host not becoming active due to VDSM failure

2021-07-30 Thread Nir Soffer 
On Fri, Jul 30, 2021 at 7:41 PM Vinícius Ferrão via Users
 wrote:
...
> restore-net::ERROR::2021-07-30 
> 12:34:56,167::restore_net_config::462::root::(restore) restoration failed.
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", 
> line 460, in restore
> unified_restoration()
>   File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", 
> line 112, in unified_restoration
> classified_conf = _classify_nets_bonds_config(available_config)
>   File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", 
> line 237, in _classify_nets_bonds_config
> net_info = NetInfo(netswitch.configurator.netinfo())
>   File 
> "/usr/lib/python3.6/site-packages/vdsm/network/netswitch/configurator.py", 
> line 323, in netinfo
> _netinfo = netinfo_get(vdsmnets, compatibility)
>   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 
> 268, in get
> return _get(vdsmnets)
>   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 
> 76, in _get
> extra_info.update(_get_devices_info_from_nmstate(state, devices))
>   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 
> 165, in _get_devices_info_from_nmstate
> nmstate.get_interfaces(state, filter=devices)
>   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 
> 164, in 
> for ifname, ifstate in six.viewitems(
>   File "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/api.py", line 
> 228, in is_dhcp_enabled
> return util_is_dhcp_enabled(family_info)
>   File 
> "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/bridge_util.py", line 
> 137, in is_dhcp_enabled
> return family_info[InterfaceIP.ENABLED] and family_info[InterfaceIP.DHCP]
> KeyError: 'dhcp'

Looks like a mnstate or NetworkManager bug.

You did not mention any version - are you running the latest ovirt version?

Nir
___
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/AR64DVBKB5ZZBMVPTDKOCNIZ4IYIHAS4/

[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-07-30 Thread regloff 
Re-installation using the 'VirtIO-SCSI' interface along with the appropriate 
driver installs took care of the issue! It's still a little bit slow - but what 
I would expect for a 5400 RPM drive :)

The performance had improved greatly!

Thanks for the suggestions!
___
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/FFYNR43QMGCI75YYGOB4JB3VQE6HBOBJ/

[ovirt-users] Host not becoming active due to VDSM failure

2021-07-30 Thread Vinícius Ferrão via Users 
Hello,

I have a host that's failing to bring up VDSM, the logs don't say anything 
specific, but there's a Python error about DHCP on it. Is there anyone with a 
similar issue?

[root@rhvpower ~]# systemctl status vdsmd
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor 
preset: disabled)
   Active: inactive (dead)

Jul 30 01:53:40 rhvpower.local.versatushpc.com.br systemd[1]: Dependency failed 
for Virtual Desktop Server Manager.
Jul 30 01:53:40 rhvpower.local.versatushpc.com.br systemd[1]: vdsmd.service: 
Job vdsmd.service/start failed with result 'dependency'.
Jul 30 12:34:12 rhvpower.local.versatushpc.com.br systemd[1]: Dependency failed 
for Virtual Desktop Server Manager.
Jul 30 12:34:12 rhvpower.local.versatushpc.com.br systemd[1]: vdsmd.service: 
Job vdsmd.service/start failed with result 'dependency'.
[root@rhvpower ~]# systemctl start vdsmd
A dependency job for vdsmd.service failed. See 'journalctl -xe' for details.


On the logs I got the following messages:

==> /var/log/vdsm/upgrade.log <==
MainThread::DEBUG::2021-07-30 12:34:55,143::libvirtconnection::168::root::(get) 
trying to connect libvirt
MainThread::INFO::2021-07-30 
12:34:55,167::netconfpersistence::238::root::(_clearDisk) Clearing netconf: 
/var/lib/vdsm/staging/netconf
MainThread::INFO::2021-07-30 
12:34:55,178::netconfpersistence::188::root::(save) Saved new config 
RunningConfig({'ovirtmgmt': {'netmask': '255.255.255.0', 'bonding': 'bond0', 
'ipv6autoconf': False, 'bridged': True, 'ipaddr': '10.20.0.106', 
'defaultRoute': True, 'dhcpv6': False, 'gateway': '10.20.0.1', 'mtu': 1500, 
'switch': 'legacy', 'stp': False, 'bootproto': 'none', 'nameservers': 
['10.20.0.1']}, 'servers': {'vlan': 172, 'bonding': 'bond0', 'ipv6autoconf': 
False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'xcat-other': {'vlan': 2020, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'xcat-nodes1': {'vlan': 2021, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'xcat-nodes3': {'vlan': 2023, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'xcat-nodes2': {'vlan': 2022, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'nfs': {'vlan': 200, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': 
True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 
'stp': False, 'bootproto': 'none', 'nameservers': []}, 'storage': {'vlan': 192, 
'netmask': '255.255.255.240', 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': False, 'ipaddr': '192.168.10.6', 'dhcpv6': False, 'mtu': 1500, 
'switch': 'legacy', 'defaultRoute': False, 'bootproto': 'none', 'nameservers': 
[]}, 'xcat-nodes4': {'vlan': 2024, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}}, 
{'bond0': {'nics': ['enP48p1s0f2', 'enP48p1s0f3'], 'options': 'mode=4', 
'switch': 'legacy', 'hwaddr': '98:be:94:78:cc:72'}}, {}) to 
[/var/lib/vdsm/staging/netconf/nets,/var/lib/vdsm/staging/netconf/bonds,/var/lib/vdsm/staging/netconf/devices]
MainThread::INFO::2021-07-30 
12:34:55,179::netconfpersistence::238::root::(_clearDisk) Clearing netconf: 
/var/lib/vdsm/persistence/netconf
MainThread::INFO::2021-07-30 
12:34:55,188::netconfpersistence::188::root::(save) Saved new config 
PersistentConfig({'ovirtmgmt': {'netmask': '255.255.255.0', 'bonding': 'bond0', 
'ipv6autoconf': False, 'bridged': True, 'ipaddr': '10.20.0.106', 
'defaultRoute': True, 'dhcpv6': False, 'gateway': '10.20.0.1', 'mtu': 1500, 
'switch': 'legacy', 'stp': False, 'bootproto': 'none', 'nameservers': 
['10.20.0.1']}, 'servers': {'vlan': 172, 'bonding': 'bond0', 'ipv6autoconf': 
False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'xcat-other': {'vlan': 2020, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 
'xcat-nodes1': {'vlan': 2021, 'bonding': 'bond0', 'ipv6autoconf': False, 
'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 
'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []},

[ovirt-users] Re: VM CPU Topology

2021-07-30 Thread Strahil Nikolov via Users 
I guess it's pretty obvious that I miss my qwerty hardware keyboard :D
Best Regards,Strahil Nikolov
 
 
  On Fri, Jul 30, 2021 at 15:31, Strahil Nikolov via Users 
wrote:   ___
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/YFSWPK7YKOFB2XF5Z3FPCWK4SLTDT5AY/
  
___
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/53RWMQH5EQY3NCH5GWTNJMZBH4VEN6X7/

[ovirt-users] .htpasswd for ovirt web-ui

2021-07-30 Thread marc . pfaendler 
Hello

I want to add a password using .htpasswd file on my ovirt web-ui. 
I tried - htpasswd -cm ./.htpasswd username - to add a .htpasswd file in 
/usr/share/ovirt-engine/ovirt-web-ui.war.
This doesn't work though would have been to easy right. ; ) 

Any ideas how I could achieve this?

Thx
___
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/2DRM77KNP4UN36HQ43DPRLUGIC2XVUXC/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-30 Thread Merlin Timm 

Ah okay, i figured it out.

root@mypc:/home/merlin/Documents/Ovirt-0.06# perl set_ovirt_vnc_pw.pl
LWP Status line : 500 Can't connect to my.ovirt.manager.com:443 
(certificate verify failed) at /usr/local/share/perl/5.26.1/Ovirt/VM.pm 
line 195.


it seems to work but it cant connect to the ovirt manager :/

Am 30.07.2021 14:54 schrieb Milan Zamazal:

Merlin Timm  writes:


actually I rather wanted to know how to generate a config with
Ovirt::Display. I didn't really understand what I have to do to
generate a config.


I've never tried it but I think you should fetch the perl library and
then run a perl script according to the example in Synopis section of
https://metacpan.org/pod/Ovirt::Display


Am 30.07.2021 14:04 schrieb Milan Zamazal:

Merlin Timm  writes:


Hey,
Thanks for the answers!
I want to try the perl solution. One, maybe stupid, question: how
do i run this perl module?
Do i run it on the Host or from my local machne? I am a litte bit
confused.

As I understand it, you can run it from anywhere where Engine REST
API
is reachable from.
Regards,
Milan


Could someone explain it to me?
Best regarda
Am 8. Juli 2021 16:05:42 MESZ schrieb Milan Zamazal
:

Sandro Bonazzola  writes:


Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:


+Milan Zamazal  , +Arik Hadas
 , +Michal
Skrivanek  any hint?


I found https://metacpan.org/pod/Ovirt::Display but I think there
should be
an easier way within the engine to configure this.



Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm

ha scritto:


Good day to all,
I have a question about the console configuration of the VMs:
By default, for each console connection to a VM, a password is
set for
120 seconds, after that you can't use it again. We currently
have the
following concern:
We want to access and control the VMs via the VNC/Spice of the
Ovirt
host. We have already tried to use the password from the
console.vv for
the connection and that works so far. Unfortunately we have to
do this
every 2 minutes when we want to connect again. We are currently
building
an automatic test pipeline and for this we need to access the 
VMs

remotely before OS start and we want to be independent of a VNC
server
on the guest. This is only possible if we could connect to the
VNC/Spice
server from the Ovirt host.
My question: would it be possible to fix the password or read
it out via
api every time you want to connect?

A one time password is set every time the console is opened, for
those
120 seconds.  Unfortunately, the 120 seconds limit seems to be
hardwired
in Engine sources.  So apparently the only chance would be to set 
the

password directly on the host using VM.updateDevice VDSM API call.
It
looks like this normally:
 VM.updateDevice(params={'deviceType': 'graphics', 'password':
'', 'disconnectAction': 'NONE', 'params': {'vncUsername':
'vnc-630b9cae-a983-4ab0-a9ac-6b8728f8014d', 'fips': 'false',
'userName': 'admin', 'userId':
'fd2c5e14-a8c3-11eb-951c-2a9574de53b6'}, 'ttl': 120, 
'graphicsType':

'spice'})
This way it's possible to set a password and its lifetime (`ttl'
parameter).  Of course, it's needed to find out the host the VM
runs on,
a way to call the API (running vdsm-client directly on the host
may be
the easiest way), how to make/use the *.vv ticket (you can use the
same
password all the time) and to accept collisions with different
settings
if someone opens the console from the web UI.
In the end result, using the Perl library mentioned by Sandro
above may
be an easier solution.
Or another option is to submit a patch to Engine to make the
timeout
configurable (look for TICKET_VALIDITY_SECONDS in the sources).
Regards,
Milan


I would appreciate a reply very much!
Best regards
Merlin Timm
___
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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/



--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
Red Hat EMEA 
sbona...@redhat.com

*Red Hat respects your work life balance. Therefore there is no
need to
answer this email out of your office hours.
*





___
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/GYNC72W3P5TEN3EOQSYPPKCQZ4TGIRDC/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-30 Thread Merlin Timm 
actually I rather wanted to know how to generate a config with 
Ovirt::Display. I didn't really understand what I have to do to generate 
a config.


Am 30.07.2021 14:04 schrieb Milan Zamazal:

Merlin Timm  writes:


Hey,

Thanks for the answers!

I want to try the perl solution. One, maybe stupid, question: how do i 
run this perl module?


Do i run it on the Host or from my local machne? I am a litte bit 
confused.


As I understand it, you can run it from anywhere where Engine REST API
is reachable from.

Regards,
Milan


Could someone explain it to me?

Best regarda

Am 8. Juli 2021 16:05:42 MESZ schrieb Milan Zamazal 
:

Sandro Bonazzola  writes:


Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:

+Milan Zamazal  , +Arik Hadas 
 , +Michal

Skrivanek  any hint?



I found https://metacpan.org/pod/Ovirt::Display but I think there 
should be

an easier way within the engine to configure this.





Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 


ha scritto:


Good day to all,

I have a question about the console configuration of the VMs:

By default, for each console connection to a VM, a password is set 
for
120 seconds, after that you can't use it again. We currently have 
the

following concern:

We want to access and control the VMs via the VNC/Spice of the 
Ovirt
host. We have already tried to use the password from the 
console.vv for
the connection and that works so far. Unfortunately we have to do 
this
every 2 minutes when we want to connect again. We are currently 
building

an automatic test pipeline and for this we need to access the VMs
remotely before OS start and we want to be independent of a VNC 
server
on the guest. This is only possible if we could connect to the 
VNC/Spice

server from the Ovirt host.

My question: would it be possible to fix the password or read it 
out via

api every time you want to connect?


A one time password is set every time the console is opened, for 
those
120 seconds.  Unfortunately, the 120 seconds limit seems to be 
hardwired

in Engine sources.  So apparently the only chance would be to set the
password directly on the host using VM.updateDevice VDSM API call.  
It

looks like this normally:

 VM.updateDevice(params={'deviceType': 'graphics', 'password':
'', 'disconnectAction': 'NONE', 'params': {'vncUsername':
'vnc-630b9cae-a983-4ab0-a9ac-6b8728f8014d', 'fips': 'false',
'userName': 'admin', 'userId':
'fd2c5e14-a8c3-11eb-951c-2a9574de53b6'}, 'ttl': 120, 'graphicsType':
'spice'})

This way it's possible to set a password and its lifetime (`ttl'
parameter).  Of course, it's needed to find out the host the VM runs 
on,
a way to call the API (running vdsm-client directly on the host may 
be
the easiest way), how to make/use the *.vv ticket (you can use the 
same
password all the time) and to accept collisions with different 
settings

if someone opens the console from the web UI.

In the end result, using the Perl library mentioned by Sandro above 
may

be an easier solution.

Or another option is to submit a patch to Engine to make the timeout
configurable (look for TICKET_VALIDITY_SECONDS in the sources).

Regards,
Milan


I would appreciate a reply very much!

Best regards
Merlin Timm
___
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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/




--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no 
need to

answer this email out of your office hours.
*






___
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/V62IP2PVTQP5YATSSV2QEB77P2PAJTY4/

[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-07-30 Thread Gianluca Cecchi 
On Fri, Jul 30, 2021 at 4:17 PM  wrote:

>
> I think I'll deploy a new Windows guest and try the 'VirtIO-SCSI'
> interface and see if my performance is any better. It's just a default
> install of Windows at this point, so that'll be easy. :)
>
>
>
I think it should work also this way:
. hot add a disk to your Windows VM with size small as you want (eg 1Gb)
and configure it as virtio-scsi.
. in windows os when it asks for a driver, you provide what you need (the
virtio-win iso) and let windows configure
. eventually restart windows to verify all is ok
. shutdown the vm and set the boot disk as virtio-scsi
. power on the vm
. windows should auto configure it and perhaps reboot and you are then done
. remove the second disk

Gianluca
___
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/T4WMPVNIL7QQ54OITFZQ7KW6DOUBB5WR/

[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-07-30 Thread regloff 
This is a simple one desktop setup I use at home for being a nerd :)

So it's a single host 'cluster' using local storage. 

Host Info:
CentOS Linux 8 - 4.18.0-305.10.2.el8_4.x86_64 (I keep fairly well updated)
Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz [Kaby Lake] {Skylake}, 14nm
The disk it's on is: WDC WD40EZRZ-00G (5400 RPM platter disk) - it's not the 
fastest thing in the world, but it should be sufficient. 

VM info:
Windows 10 Professional (Desktop not server)
6144 MB of RAM
2 Virtual CPUS
 - Some settings I ran across for 'Performance' mode and a couple I had seen on 
some similar issues (the similar issues were quite dated)
Running in headless mode
I/O Threads enabled = 1
Multi-Queues enabled
Virt-IO-SCSI enabled
Random Number generator enabled
Added a custom property of 'viodiskcache' = writeback  (Didn't seem to make any 
significant improvement)

As I type this though - I was going to add this link as it's what I followed to 
install the storage driver during the Windows install and then in the OS after 
that:

https://access.redhat.com/solutions/17463

I did notice something.. it says to create a new VM with the 'VirtIO disk 
interface' and I just noted my VM is setup as 'SATA'. 

Perhaps that is it. This is just my first attempt at running something other 
than a Linux Distro under oVirt. When I first installed the Windows guest, I 
didn't have the Virt-IO package downloaded initially. When Windows couldn't 
find a storage driver, I found this info out. 

I think I'll deploy a new Windows guest and try the 'VirtIO-SCSI' interface and 
see if my performance is any better. It's just a default install of Windows at 
this point, so that'll be easy. :)

Will update this thread either way!
___
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/4YC5E3MRPKJPFAAQDCTH5CWGPTTN77SU/

[ovirt-users] Change lease storage domain while VM running

2021-07-30 Thread Gianluca Cecchi 
Hello,
on a 4.4.6 environment where I'm moving storage I want to change the lease
domain for an HA VM.
The VM is running and if I go and edit, change sd and then press ok button,
I get a window with:

"
Changes that can be applied immediately:

VM Lease
"

I don't select the "apply later" check box. But then instead when I
confirm, I get an error window with:

"
vm_name:

Cannot edit VM. Hot swapping of VM leases is not supported, please
remove the current lease and then set a new one.
"

Possibly it is possible to hot add a lease but not swap? So I think the
first window should be changed. Is this a known issue?
No problem if I change the lease storage domain while the VM is powered off.

I don't know if it is already fixed in 4.4.7... I'm going to check next
days..

Gianluca
___
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/2T75KL33773P3QVF7ZHITEPOZYEIKTUH/

[ovirt-users] Upload Image to NFS Storage Domain Doesn't Work

2021-07-30 Thread Nur Imam Febrianto 
Hi,

Lastly in 4.4.6, I have a problem that I couldn’t upload any image to storage 
domain without clicking Test Connection. Well, after it was acknowledge as a 
bug and solved at 4.4.7 now I have similar issue. If I upload any image to 
Storage Domain that uses NFS it only show locked, and then showing OK even if 
no data are uploaded (can confirm 5GB ISO showing OK after only 1 second). This 
issue only occurs with NFS backend, another storage domain that uses iSCSI work 
fine though. Any idea how to solve this ? I’m using NFS Storage Domain for 
storing ISO and this issue bugged me all the time.

Thanks before.

Regards,

Nur Imam Febrianto


___
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/ACUKBWAM2ORQZL3SUH523B7JFWRC7XT3/

[ovirt-users] [ANN] oVirt 4.4.8 Third Release Candidate is now available for testing

2021-07-30 Thread Lev Veyde 
oVirt 4.4.8 Third Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.8
Third Release Candidate for testing, as of July 30th, 2021.

This update is the eighth in a series of stabilization updates to the 4.4
series.
Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download  page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation .
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   .
   -

   For a general overview of oVirt, see About oVirt
   .

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.4 or similar

* CentOS Stream 8

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.4 or similar

* CentOS Stream 8

* oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available based on CentOS Stream 8

- oVirt Node NG is already available based on CentOS Stream 8

Additional Resources:

* Read more about the oVirt 4.4.8 release highlights:
http://www.ovirt.org/release/4.4.8/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.8/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
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/FELCB33V7P43Z3MVHQIZ2HTP3W6VO5B2/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-30 Thread Milan Zamazal 
Merlin Timm  writes:

> actually I rather wanted to know how to generate a config with
> Ovirt::Display. I didn't really understand what I have to do to
> generate a config.

I've never tried it but I think you should fetch the perl library and
then run a perl script according to the example in Synopis section of
https://metacpan.org/pod/Ovirt::Display

> Am 30.07.2021 14:04 schrieb Milan Zamazal:
>> Merlin Timm  writes:
>> 
>>> Hey,
>>> Thanks for the answers!
>>> I want to try the perl solution. One, maybe stupid, question: how
>>> do i run this perl module?
>>> Do i run it on the Host or from my local machne? I am a litte bit 
>>> confused.
>> As I understand it, you can run it from anywhere where Engine REST
>> API
>> is reachable from.
>> Regards,
>> Milan
>> 
>>> Could someone explain it to me?
>>> Best regarda
>>> Am 8. Juli 2021 16:05:42 MESZ schrieb Milan Zamazal 
>>> :
 Sandro Bonazzola  writes:
 
> Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
> sbona...@redhat.com> ha scritto:
> 
>> +Milan Zamazal  , +Arik Hadas
>>  , +Michal
>> Skrivanek  any hint?
>> 
> I found https://metacpan.org/pod/Ovirt::Display but I think there 
> should be
> an easier way within the engine to configure this.
> 
> 
>> Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 
>> 
>> ha scritto:
>> 
>>> Good day to all,
>>> I have a question about the console configuration of the VMs:
>>> By default, for each console connection to a VM, a password is
>>> set for
>>> 120 seconds, after that you can't use it again. We currently
>>> have the
>>> following concern:
>>> We want to access and control the VMs via the VNC/Spice of the 
>>> Ovirt
>>> host. We have already tried to use the password from the
>>> console.vv for
>>> the connection and that works so far. Unfortunately we have to
>>> do this
>>> every 2 minutes when we want to connect again. We are currently
>>> building
>>> an automatic test pipeline and for this we need to access the VMs
>>> remotely before OS start and we want to be independent of a VNC
>>> server
>>> on the guest. This is only possible if we could connect to the
>>> VNC/Spice
>>> server from the Ovirt host.
>>> My question: would it be possible to fix the password or read
>>> it out via
>>> api every time you want to connect?
 A one time password is set every time the console is opened, for 
 those
 120 seconds.  Unfortunately, the 120 seconds limit seems to be
 hardwired
 in Engine sources.  So apparently the only chance would be to set the
 password directly on the host using VM.updateDevice VDSM API call.
 It
 looks like this normally:
  VM.updateDevice(params={'deviceType': 'graphics', 'password':
 '', 'disconnectAction': 'NONE', 'params': {'vncUsername':
 'vnc-630b9cae-a983-4ab0-a9ac-6b8728f8014d', 'fips': 'false',
 'userName': 'admin', 'userId':
 'fd2c5e14-a8c3-11eb-951c-2a9574de53b6'}, 'ttl': 120, 'graphicsType':
 'spice'})
 This way it's possible to set a password and its lifetime (`ttl'
 parameter).  Of course, it's needed to find out the host the VM
 runs on,
 a way to call the API (running vdsm-client directly on the host
 may be
 the easiest way), how to make/use the *.vv ticket (you can use the
 same
 password all the time) and to accept collisions with different
 settings
 if someone opens the console from the web UI.
 In the end result, using the Perl library mentioned by Sandro
 above may
 be an easier solution.
 Or another option is to submit a patch to Engine to make the
 timeout
 configurable (look for TICKET_VALIDITY_SECONDS in the sources).
 Regards,
 Milan
 
>>> I would appreciate a reply very much!
>>> Best regards
>>> Merlin Timm
>>> ___
>>> 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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/
>>> 
>> 
>> --
>> Sandro Bonazzola
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>> Red Hat EMEA 
>> sbona...@redhat.com
>> 
>> *Red Hat respects your work life balance. Therefore there is no 
>> need to
>> answer this email out of your office hours.
>> *
>> 
>> 
 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:

[ovirt-users] Re: This year conference community updates

2021-07-30 Thread Sandro Bonazzola 
Renewing the call to oVirt downstreams to let the community know about
their existence.


Il giorno ven 4 giu 2021 alle ore 11:13 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:

> Hi,
> as announced we are going to have oVirt online conference coming in
> September.
> I would like to give usual community updates in and as part of that I'd
> like to report about oVirt downstream products (such as Red Hat
> Virtualization and Oracle Linux Virtualization Manager) and about companies
> using oVirt.
> I could just go googling and guessing by e-mail traffic on oVirt users
> list but I want to try a different approach this year.
> So, if you are shipping an oVirt downstream or if you're using oVirt and
> you'd like to get the company nominated during the community reports please
> let me know off-list.
> Also I'd like to remind that oVirt site has a section dedicated to user
> stories, if you want to share yours you can either push it to
> https://github.com/oVirt/ovirt-site or get in touch with me off-list to
> get help getting your story published.
>
> Thanks,
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
*
___
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/BL7FX6WKK55HDJNQPR5LT5A4DB24YD7W/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-30 Thread Strahil Nikolov via Users 
I'm not sure, but you can create your own vdsm hook that can alter the VM's xml 
before powering up.
Best Regards,Strahil Nikolov
 
 
  On Fri, Jul 30, 2021 at 15:23, Merlin Timm wrote:   
___
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/V67PVYR54J7PVP44UMV3MURUEQKLF3CM/
  
___
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:

[ovirt-users] Re: VM CPU Topology

2021-07-30 Thread Strahil Nikolov via Users 
Based on my experience, just set 1 thread:1core:as many sockets you need.
You can still match the vortual sockets to numa nodes, butlater it will bwcome 
harder as most probably the Hypervisor won't be dedicated to the VM.
Best Regards,Strahil Nikolov
 
 
  On Fri, Jul 30, 2021 at 13:00, Milan Zamazal wrote:   
nelson.lamei...@lyra-network.com writes:

> Hello,
>
> We are currently running oVirt 4.3.10
> Our oVirt hypervisors (HV) have 2 cpu sockets * 6 cores * HT = 24 vcpu
> Our VMs (centos7) range globally from 2vcpu to 8vcpu
> oVirt allows to configure - per VM - the following 3 advanced
> parameters : virtual_sockets : cores_per_virtual_socket :
> threads_per_core
>
> We make sure that threads per core is always 1 (so no question there)
> But, for the other 2 parameters, we are unsure of the correct
> configuration, and if there is a performance penalty on bad
> configuration.
>
> Let's consider a 4vcpu VM
>
> 1- Is there a performance difference betwenn 1:4:1 and 4:1:1 configuration ?
> 2- When should we opt for one or another configuration ?
> 2- Our VMs total CPU provisionning sum is twice the hypervisors
> capacity, but they are mostly idle so it is not an issue, but can this
> influence configuration choice above ?

I'm not sure anybody knows an ultimate answer and/or a simple rule of
thumb.  My guess would be that generally there should be no significant
difference.  But there may be application specific considerations,
especially when NUMA or something similar is involved.

I think the best what can be done is to test both the configurations
with your particular applications and setup and see if any of them
provides a systematically better performance than the other one.

Regards,
Milan

> Thank you for any information that can enlighthen us, since we are
> worried that we are suffering from bad performance due to naive cpu
> configuration choices.
___
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/4WUNPQ5WNUVJQAHAJTH4GAJYOTTYTIMB/
  
___
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/YFSWPK7YKOFB2XF5Z3FPCWK4SLTDT5AY/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-30 Thread Merlin Timm 
Hey, 

Thanks for the answers! 

I want to try the perl solution. One, maybe stupid, question: how do i run this 
perl module?

Do i run it on the Host or from my local machne? I am a litte bit confused.

Could someone explain it to me?

Best regarda

Am 8. Juli 2021 16:05:42 MESZ schrieb Milan Zamazal :
>Sandro Bonazzola  writes:
>
>> Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
>> sbona...@redhat.com> ha scritto:
>>
>>> +Milan Zamazal  , +Arik Hadas  , 
>>> +Michal
>>> Skrivanek  any hint?
>>>
>>
>> I found https://metacpan.org/pod/Ovirt::Display but I think there should be
>> an easier way within the engine to configure this.
>>
>>
>>
>>>
>>> Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 
>>> ha scritto:
>>>
 Good day to all,

 I have a question about the console configuration of the VMs:

 By default, for each console connection to a VM, a password is set for
 120 seconds, after that you can't use it again. We currently have the
 following concern:

 We want to access and control the VMs via the VNC/Spice of the Ovirt
 host. We have already tried to use the password from the console.vv for
 the connection and that works so far. Unfortunately we have to do this
 every 2 minutes when we want to connect again. We are currently building
 an automatic test pipeline and for this we need to access the VMs
 remotely before OS start and we want to be independent of a VNC server
 on the guest. This is only possible if we could connect to the VNC/Spice
 server from the Ovirt host.

 My question: would it be possible to fix the password or read it out via
 api every time you want to connect?
>
>A one time password is set every time the console is opened, for those
>120 seconds.  Unfortunately, the 120 seconds limit seems to be hardwired
>in Engine sources.  So apparently the only chance would be to set the
>password directly on the host using VM.updateDevice VDSM API call.  It
>looks like this normally:
>
>  VM.updateDevice(params={'deviceType': 'graphics', 'password': '', 
> 'disconnectAction': 'NONE', 'params': {'vncUsername': 
> 'vnc-630b9cae-a983-4ab0-a9ac-6b8728f8014d', 'fips': 'false', 'userName': 
> 'admin', 'userId': 'fd2c5e14-a8c3-11eb-951c-2a9574de53b6'}, 'ttl': 120, 
> 'graphicsType': 'spice'})
>
>This way it's possible to set a password and its lifetime (`ttl'
>parameter).  Of course, it's needed to find out the host the VM runs on,
>a way to call the API (running vdsm-client directly on the host may be
>the easiest way), how to make/use the *.vv ticket (you can use the same
>password all the time) and to accept collisions with different settings
>if someone opens the console from the web UI.
>
>In the end result, using the Perl library mentioned by Sandro above may
>be an easier solution.
>
>Or another option is to submit a patch to Engine to make the timeout
>configurable (look for TICKET_VALIDITY_SECONDS in the sources).
>
>Regards,
>Milan
>
 I would appreciate a reply very much!

 Best regards
 Merlin Timm
 ___
 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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/

>>>
>>>
>>> --
>>>
>>> Sandro Bonazzola
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> 
>>>
>>> *Red Hat respects your work life balance. Therefore there is no need to
>>> answer this email out of your office hours.
>>> *
>>>
>>>
>>>
>

-- 
Merlin Timm___
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/V67PVYR54J7PVP44UMV3MURUEQKLF3CM/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-30 Thread Milan Zamazal 
Merlin Timm  writes:

> Hey, 
>
> Thanks for the answers! 
>
> I want to try the perl solution. One, maybe stupid, question: how do i run 
> this perl module?
>
> Do i run it on the Host or from my local machne? I am a litte bit confused.

As I understand it, you can run it from anywhere where Engine REST API
is reachable from.

Regards,
Milan

> Could someone explain it to me?
>
> Best regarda
>
> Am 8. Juli 2021 16:05:42 MESZ schrieb Milan Zamazal :
>>Sandro Bonazzola  writes:
>>
>>> Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
>>> sbona...@redhat.com> ha scritto:
>>>
 +Milan Zamazal  , +Arik Hadas  , 
 +Michal
 Skrivanek  any hint?

>>>
>>> I found https://metacpan.org/pod/Ovirt::Display but I think there should be
>>> an easier way within the engine to configure this.
>>>
>>>
>>>

 Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 
 ha scritto:

> Good day to all,
>
> I have a question about the console configuration of the VMs:
>
> By default, for each console connection to a VM, a password is set for
> 120 seconds, after that you can't use it again. We currently have the
> following concern:
>
> We want to access and control the VMs via the VNC/Spice of the Ovirt
> host. We have already tried to use the password from the console.vv for
> the connection and that works so far. Unfortunately we have to do this
> every 2 minutes when we want to connect again. We are currently building
> an automatic test pipeline and for this we need to access the VMs
> remotely before OS start and we want to be independent of a VNC server
> on the guest. This is only possible if we could connect to the VNC/Spice
> server from the Ovirt host.
>
> My question: would it be possible to fix the password or read it out via
> api every time you want to connect?
>>
>>A one time password is set every time the console is opened, for those
>>120 seconds.  Unfortunately, the 120 seconds limit seems to be hardwired
>>in Engine sources.  So apparently the only chance would be to set the
>>password directly on the host using VM.updateDevice VDSM API call.  It
>>looks like this normally:
>>
>>  VM.updateDevice(params={'deviceType': 'graphics', 'password':
>> '', 'disconnectAction': 'NONE', 'params': {'vncUsername':
>> 'vnc-630b9cae-a983-4ab0-a9ac-6b8728f8014d', 'fips': 'false',
>> 'userName': 'admin', 'userId':
>> 'fd2c5e14-a8c3-11eb-951c-2a9574de53b6'}, 'ttl': 120, 'graphicsType':
>> 'spice'})
>>
>>This way it's possible to set a password and its lifetime (`ttl'
>>parameter).  Of course, it's needed to find out the host the VM runs on,
>>a way to call the API (running vdsm-client directly on the host may be
>>the easiest way), how to make/use the *.vv ticket (you can use the same
>>password all the time) and to accept collisions with different settings
>>if someone opens the console from the web UI.
>>
>>In the end result, using the Perl library mentioned by Sandro above may
>>be an easier solution.
>>
>>Or another option is to submit a patch to Engine to make the timeout
>>configurable (look for TICKET_VALIDITY_SECONDS in the sources).
>>
>>Regards,
>>Milan
>>
> I would appreciate a reply very much!
>
> Best regards
> Merlin Timm
> ___
> 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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/
>


 --

 Sandro Bonazzola

 MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

 Red Hat EMEA 

 sbona...@redhat.com
 

 *Red Hat respects your work life balance. Therefore there is no need to
 answer this email out of your office hours.
 *



>>
___
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/AJYHDJBZCPHMHVM3ZDYINMYE5HKQ4WES/

[ovirt-users] Re: Happy SysAdmin Day!

2021-07-30 Thread Sandro Bonazzola 
Happy SysAdmin Day to our @infra   and all the sysadmin in
this list!

Il giorno ven 30 lug 2021 alle ore 11:52 Strahil Nikolov via Users <
users@ovirt.org> ha scritto:

> Happy SysAdmin Day!
>
> I want to thank Duck and wish to all fellow SysAdmins in the oVirt
> community a Happy Holliday !
>
>
> Best Regards,
> Strahil Nikolov
> ___
> 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/BO3NWMPHAQ35PWJ2EAHR3DO7EIB7XFFK/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/QTYMA6MWI57ZEUG2LO5RQOZQCJ2QTJIP/

[ovirt-users] Re: VM CPU Topology

2021-07-30 Thread Milan Zamazal 
nelson.lamei...@lyra-network.com writes:

> Hello,
>
> We are currently running oVirt 4.3.10
> Our oVirt hypervisors (HV) have 2 cpu sockets * 6 cores * HT = 24 vcpu
> Our VMs (centos7) range globally from 2vcpu to 8vcpu
> oVirt allows to configure - per VM - the following 3 advanced
> parameters : virtual_sockets : cores_per_virtual_socket :
> threads_per_core
>
> We make sure that threads per core is always 1 (so no question there)
> But, for the other 2 parameters, we are unsure of the correct
> configuration, and if there is a performance penalty on bad
> configuration.
>
> Let's consider a 4vcpu VM
>
> 1- Is there a performance difference betwenn 1:4:1 and 4:1:1 configuration ?
> 2- When should we opt for one or another configuration ?
> 2- Our VMs total CPU provisionning sum is twice the hypervisors
> capacity, but they are mostly idle so it is not an issue, but can this
> influence configuration choice above ?

I'm not sure anybody knows an ultimate answer and/or a simple rule of
thumb.  My guess would be that generally there should be no significant
difference.  But there may be application specific considerations,
especially when NUMA or something similar is involved.

I think the best what can be done is to test both the configurations
with your particular applications and setup and see if any of them
provides a systematically better performance than the other one.

Regards,
Milan

> Thank you for any information that can enlighthen us, since we are
> worried that we are suffering from bad performance due to naive cpu
> configuration choices.
___
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/4WUNPQ5WNUVJQAHAJTH4GAJYOTTYTIMB/

[ovirt-users] Happy SysAdmin Day!

2021-07-30 Thread Strahil Nikolov via Users 
Happy SysAdmin Day!
I want to thank Duck and wish to all fellow SysAdmins in the oVirt community a 
Happy Holliday !

Best Regards,Strahil Nikolov___
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/BO3NWMPHAQ35PWJ2EAHR3DO7EIB7XFFK/

[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread tommy 
You have a point. I am increasingly aware of the importance of
documentation, especially good documentation that clearly illustrates the
history of development, which can help readers quickly get started with
software systems.




-Original Message-
From: Vojtech Juranek  
Sent: Friday, July 30, 2021 4:21 PM
To: tommy 
Cc: users@ovirt.org
Subject: Re: [ovirt-users] About the cluster compatibility version

On Friday, 30 July 2021 09:51:08 CEST you wrote:
> I still find a lot of errors in the document, but I don't know how to
help?
> Can you tell me the steps to improve the documentation?

you need to find appropriate document, fix it and send a pull request.
There's a README [1] with the step in oVirt site git repo [1] or if you want
to send a pull request, you can find guide how to do it on [2].

Looking more into the original question you asked, it's maybe correct. I
don't know if we have any strict rules when cluster version is bumped, but
it seems in the past it was done mainly to ensure OS has specific features
provided advanced virtualization packages, which are usually available only
on specific OS version and higher. So in this case the documentation is
correct (and I was wrong in my previous answer), as OS version determines
packages available on the host and these determines capabilities of tools
(like libvirt, qemu) which oVirt is build upon.

Hopefully makes sense.


[1] https://github.com/oVirt/ovirt-site/blob/master/README.md
[2] https://docs.github.com/en/github/collaborating-with-pull-requests/
proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

> I'd like to help in any way I can.
> 
> 
> 
> -Original Message-
> From: Vojtech Juranek 
> Sent: Friday, July 30, 2021 3:01 PM
> To: 'users' 
> Cc: tommy 
> Subject: Re: [ovirt-users] About the cluster compatibility version
> 
> On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> > From the document:
> > 
> > oVirt clusters have a compatibility version. The cluster 
> > compatibility version indicates the features of oVirt supported by 
> > all of the hosts in the cluster.
> > 
> > The cluster compatibility is set according to the version of the 
> > least capable host operating system in the cluster.
> > 
> > 
> > 
> > I didn't quite understand the last sentence.
> > 
> > How can the version of the cluster be determined based on the 
> > operating system version of the host?
> > 
> > Should the cluster compatibility version be determined based on the 
> > version of the oVirt engine on the host?
> 
> yes, it's not operating system version, but installed oVirt version on 
> the host (but not oVirt engine, there's only one engine and host 
> haven't engine installed).
> 
> Could you please improve the doc [1]?
> Thanks
> Vojta
> 
> 
> [1] 
> https://github.com/oVirt/ovirt-site/edit/master/source/documentation/
> upgrade_guide/index.adoc


___
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/AAIUOOLETDIMKX7BQNK6EQQTO5WUAXQE/

[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread Vojtech Juranek 
On Friday, 30 July 2021 09:51:08 CEST you wrote:
> I still find a lot of errors in the document, but I don't know how to help?
> Can you tell me the steps to improve the documentation?

you need to find appropriate document, fix it and send a pull request. There's 
a 
README [1] with the step in oVirt site git repo [1] or if you want to send a 
pull request, you can find guide how to do it on [2].

Looking more into the original question you asked, it's maybe correct. I don't 
know if we have any strict rules when cluster version is bumped, but it seems 
in the past it was done mainly to ensure OS has specific features provided 
advanced virtualization packages, which are usually available only on specific 
OS version and higher. So in this case the documentation is correct (and I was 
wrong in my previous answer), as OS version determines packages available on 
the host and these determines capabilities of tools (like libvirt, qemu) which 
oVirt is build upon.

Hopefully makes sense.


[1] https://github.com/oVirt/ovirt-site/blob/master/README.md
[2] https://docs.github.com/en/github/collaborating-with-pull-requests/
proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

> I'd like to help in any way I can.
> 
> 
> 
> -Original Message-
> From: Vojtech Juranek 
> Sent: Friday, July 30, 2021 3:01 PM
> To: 'users' 
> Cc: tommy 
> Subject: Re: [ovirt-users] About the cluster compatibility version
> 
> On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> > From the document:
> > 
> > oVirt clusters have a compatibility version. The cluster compatibility
> > version indicates the features of oVirt supported by all of the hosts
> > in the cluster.
> > 
> > The cluster compatibility is set according to the version of the least
> > capable host operating system in the cluster.
> > 
> > 
> > 
> > I didn't quite understand the last sentence.
> > 
> > How can the version of the cluster be determined based on the
> > operating system version of the host?
> > 
> > Should the cluster compatibility version be determined based on the
> > version of the oVirt engine on the host?
> 
> yes, it's not operating system version, but installed oVirt version on the
> host (but not oVirt engine, there's only one engine and host haven't engine
> installed).
> 
> Could you please improve the doc [1]?
> Thanks
> Vojta
> 
> 
> [1] https://github.com/oVirt/ovirt-site/edit/master/source/documentation/
> upgrade_guide/index.adoc



signature.asc
Description: This is a digitally signed message part.
___
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/3NLRI4TADHYF7AQ4S7TPOP6D7UPV6LPM/

[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread Staniforth, Paul 

Hello Tommy,

You can use github to report issues or edit the pages

if you look at the bottom of
https://www.ovirt.org/documentation/

Regards,
   Paul S.

From: tommy 
Sent: 30 July 2021 08:51
To: 'Vojtech Juranek' ; 'users' 
Subject: [ovirt-users] Re: About the cluster compatibility version

Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

I still find a lot of errors in the document, but I don't know how to help?
Can you tell me the steps to improve the documentation?
I'd like to help in any way I can.



-Original Message-
From: Vojtech Juranek 
Sent: Friday, July 30, 2021 3:01 PM
To: 'users' 
Cc: tommy 
Subject: Re: [ovirt-users] About the cluster compatibility version

On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> From the document:
>
> oVirt clusters have a compatibility version. The cluster compatibility
> version indicates the features of oVirt supported by all of the hosts
> in the cluster.
>
> The cluster compatibility is set according to the version of the least
> capable host operating system in the cluster.
>
>
>
> I didn't quite understand the last sentence.
>
> How can the version of the cluster be determined based on the
> operating system version of the host?
>
> Should the cluster compatibility version be determined based on the
> version of the oVirt engine on the host?

yes, it's not operating system version, but installed oVirt version on the
host (but not oVirt engine, there's only one engine and host haven't engine
installed).

Could you please improve the doc [1]?
Thanks
Vojta


[1] 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FoVirt%2Fovirt-site%2Fedit%2Fmaster%2Fsource%2Fdocumentation%2Fdata=04%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Ca4180ef06a604dbfdb9308d9533131ba%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637632293161677057%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=LNDPkmAjx1LJ5ptkaUWkTJqCzVGUaEhVaEl6HvP0g%2BU%3Dreserved=0
upgrade_guide/index.adoc

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.htmldata=04%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Ca4180ef06a604dbfdb9308d9533131ba%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637632293161677057%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=WH25F1DnDPUIK2ykU2ncoRhH7eaXVNJ08Dzjr89vl3Q%3Dreserved=0
oVirt Code of Conduct: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=04%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Ca4180ef06a604dbfdb9308d9533131ba%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637632293161677057%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=vg2urL2TK5xD4YqzvV%2F1p9fasHbtrrs0EGl9KGuq4Hg%3Dreserved=0
List Archives: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FOYINP64U3A6RVGXYQDFJXLRP2GYTTBSS%2Fdata=04%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Ca4180ef06a604dbfdb9308d9533131ba%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637632293161677057%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=VFaRoF3nkpDKQU7KdgeGxdo2LpjyNJlJNI1tkF0HoxE%3Dreserved=0
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
___
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/NHST6VEQ7KFRTFFQZFZO6OQGS7OJSO7S/

[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread tommy 

I still find a lot of errors in the document, but I don't know how to help?
Can you tell me the steps to improve the documentation?
I'd like to help in any way I can.



-Original Message-
From: Vojtech Juranek  
Sent: Friday, July 30, 2021 3:01 PM
To: 'users' 
Cc: tommy 
Subject: Re: [ovirt-users] About the cluster compatibility version

On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> From the document:
> 
> oVirt clusters have a compatibility version. The cluster compatibility 
> version indicates the features of oVirt supported by all of the hosts 
> in the cluster.
> 
> The cluster compatibility is set according to the version of the least 
> capable host operating system in the cluster.
> 
> 
> 
> I didn't quite understand the last sentence.
> 
> How can the version of the cluster be determined based on the 
> operating system version of the host?
> 
> Should the cluster compatibility version be determined based on the 
> version of the oVirt engine on the host?

yes, it's not operating system version, but installed oVirt version on the
host (but not oVirt engine, there's only one engine and host haven't engine
installed).

Could you please improve the doc [1]?
Thanks
Vojta


[1] https://github.com/oVirt/ovirt-site/edit/master/source/documentation/
upgrade_guide/index.adoc

___
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/OYINP64U3A6RVGXYQDFJXLRP2GYTTBSS/

[ovirt-users] Re: Error when trying to change master storage domain

2021-07-30 Thread Matthew Benstead 
Thanks Shani - yes we plan to upgrade to 4.4 in the future, but we're on
4.3 right now due to only running CentOS 7 at the moment.

I was able to clear the job from the SPM:

[root@daccs01 ~]# vdsm-client Host getAllTasksStatuses
{
    "5fa9edf0-56c3-40e4-9327-47bf7764d28d": {
    "message": "1 jobs completed successfully",
    "code": 0,
    "taskID": "5fa9edf0-56c3-40e4-9327-47bf7764d28d",
    "taskResult": "success",
    "taskState": "finished"
    }
}
[root@daccs01 ~]# vdsm-client Task clear
taskID=5fa9edf0-56c3-40e4-9327-47bf7764d28d
true
[root@daccs01 ~]# vdsm-client Host getAllTasksStatuses
{}

And confirm there were no async_tasks:

engine=# select * from async_tasks;
 task_id | action_type | status | result | step_id | command_id |
started_at | storage_pool_id | task_type | vdsm_task_id |
root_command_id | user_id
-+-+++-+++-+---+--+-+-
(0 rows)


However, when putting the vm-storage-ssd domain into maintenance mode,
it failed again:









Here are some the logs entries - anything else I can look at?


2021-07-29 10:30:37,848-07 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] EVENT_ID:
VDS_BROKER_COMMAND_FAILURE(10,802),
 VDSM compute7.pcic.uvic.ca command ConnectStoragePoolVDS failed: Wrong
Master domain or its version: u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8,
pool=f72ec125-69a1-4c1b-a5e1-313fcb70b6ff'
2021-07-29 10:30:37,848-07 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] Command
'org.ovirt.engine.core.vdsbroker.vd
sbroker.ConnectStoragePoolVDSCommand' return value 'StatusOnlyReturn
[status=Status [code=324, message=Wrong Master domain or its version:
u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8, pool=f72ec125-69a1-4c1b-a5e1-
313fcb70b6ff']]'
...
2021-07-29 10:30:37,848-07 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] HostName =
compute7.pcic.uvic.ca
2021-07-29 10:30:37,849-07 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] Command
'ConnectStoragePoolVDSCommand(HostN
ame = compute7.pcic.uvic.ca,
ConnectStoragePoolVDSCommandParameters:{hostId='51769733-0cf6-4270-8288-ec96474b7609',
vdsId='51769733-0cf6-4270-8288-ec96474b7609',
storagePoolId='f72ec125-69a1-4c1b-a5e1-313fcb70b6
ff', masterVersion='288'})' execution failed: IRSGenericException:
IRSErrorException: IRSNoMasterDomainException: Wrong Master domain or
its version: u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8, pool=f72ec125-69a1
-4c1b-a5e1-313fcb70b6ff'
...
2021-07-29 10:30:37,849-07 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47]
IrsBroker::Failed::DeactivateStorageDomainVDS: IRSGener
icException: IRSErrorException: IRSNoMasterDomainException: Wrong Master
domain or its version: u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8,
pool=f72ec125-69a1-4c1b-a5e1-313fcb70b6ff'
2021-07-29 10:30:37,855-07 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.DeactivateStorageDomainVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] FINISH,
DeactivateStorageDomainVDSComm
and, return: , log id: 1c215ca4
2021-07-29 10:30:37,855-07 ERROR
[org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47]
DeactivateStorageDomainVDS failed 'a5a83df
1-47e2-4927-9add-079199ca7ef8':
org.ovirt.engine.core.common.errors.EngineException: EngineException:
org.ovirt.engine.core.vdsbroker.irsbroker.IRSNoMasterDomainException:
IRSGenericException: IRSErrorException:
 IRSNoMasterDomainException: Wrong Master domain or its version:
u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8,
pool=f72ec125-69a1-4c1b-a5e1-313fcb70b6ff' (Failed with error
StoragePoolWrongMaster and code 324)
    at
org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:118)
[bll.jar:]
    at
org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33)
[bll.jar:]
    at
org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2112)
[bll.jar:]
    at
org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainCommand.dectivateStorageDomain(DeactivateStorageDomainCommand.java:340)
[bll.jar:]
...
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[rt.jar:1.8.0_292]
    at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_292]
    at
org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
[javax.enterprise.concurrent-1.0.jar:]
Caused by:

[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread Vojtech Juranek 
On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> From the document:
> 
> oVirt clusters have a compatibility version. The cluster compatibility
> version indicates the features of oVirt supported by all of the hosts in the
> cluster.
> 
> The cluster compatibility is set according to the version of the least
> capable host operating system in the cluster.
> 
> 
> 
> I didn't quite understand the last sentence.
> 
> How can the version of the cluster be determined based on the operating
> system version of the host?
> 
> Should the cluster compatibility version be determined based on the version
> of the oVirt engine on the host?

yes, it's not operating system version, but installed oVirt version on the 
host (but not oVirt engine, there's only one engine and host haven't engine 
installed).

Could you please improve the doc [1]?
Thanks
Vojta


[1] https://github.com/oVirt/ovirt-site/edit/master/source/documentation/
upgrade_guide/index.adoc


signature.asc
Description: This is a digitally signed message part.
___
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/JYKFI3ZRLGEOP2R7PNKRUHFCKXH465XO/