[ovirt-users] Re: cloud-init: reverts on reboot

[Nathanaël Blanchet]

Sure it is possible, use "run once" setting with cloud-init checkbox to fetch 
cloud-init settings when you decide and not only at the first boot. 

- Mail original -
De: "Jp" 
À: "users" 
Envoyé: Jeudi 11 Juin 2020 04:36:16
Objet: [ovirt-users] cloud-init: reverts on reboot

cloud-init settings entered into Hosted Engine are reverting after reboot, so 
what's the correct workflow for using the UI form?

I'd like a workflow where I can:
1. start with Template (covers most settings)
2. create VM 
3. use cloud-init in the UI (for a few settings, like static IP)
4. start/reboot VM and have cloud-init settings stick

How is the above possible?
___
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/ECHLM4E4Z327XAPDJS5RM6DRM3V4T2JS/
___
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/YY72LPGSJM5CUETKAXXEUOUUOEMKBP4I/

[ovirt-users] Re: ovirt 4.3.10 Web UI constantly "finished activating host"

[Yedidyah Bar David]

On Thu, Jun 11, 2020 at 6:55 AM Strahil Nikolov via Users
 wrote:
>
> I'm not sure if this one is related to "time shift" in the DB (as I found 
> that dwh_history_timekeeping had some entries 1 month ahead/ETL service 
> issues also/, but I keep getting spammed that the host has been activated.
>
>
> Any hint ?

I'd start with:

1. Check (in /var/log) if you had a case of time moving forward and
than backward for some weird reason

2. Dump the entire db (engine, perhaps also dwh if you want) and
search for future dates. If you only find a few, it might be easier to
handle them one-by-one (hopefully by updating the relevant entity from
the UI, not directly in the db). If it's many, it might require
something more significant.

In 4.4, that's just:

su - postgres -c 'pg_dump engine' | less

In 4.3:

su - postgres -c 'scl enable rh-postgresql10 "pg_dump engine"' | less

Then search e.g. '2020-07', or '2020-06-2', etc.

Best regards,
-- 
Didi
___
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/XREOMRKOGY54G64EUEDF6R35T324ZLN4/

[ovirt-users] Re: Host has time-drift of xxx seconds

[Strahil Nikolov via Users]

I just found entries in the db pointing to 11 July (1  month ahead) and I 
rebooted the engine.It seems that time-drift is somehow related to all the 
issues I have observed after patching from 4.3.9  to 4.3.10:
1. ovirt1  started  to slow down - solved by stopping chrony, wiping 
/var/lib/chrony/drift and a reboot
2. HE stopped  logging in the dwh tables and spamming me with ETL service 
stopped ...
I hope I fixed it by using:
https://bugzilla.redhat.com/show_bug.cgi?id=1277591#c5

(note I have typed the link,  so it might have a typo)
3. Constantly being spammed about host has been activated - most probably that 
one is also 1  month ahead  in the DB :)

Not fixed yet.

Best Regards,
Strahil Nikolov

At least the events now show real time.

Best Regards

На 11 юни 2020 г. 6:00:52 GMT+03:00, Strahil Nikolov  
написа:
>Hello All,
>
>I have a strange error that should be fixed but the event log is  still
>filling with the following after the latest patching (4.3.10):
>
>Host ovirt2.localdomain has time-drift of 2909848 seconds while maximum
>configured value is 300 seconds.
>Host ovirt3.localdomain has time-drift of 2909848 seconds while maximum
>configured value is 300 seconds.
>
>As  it blamed only 2  out of 3 systems,  I checked what has happened 
>on ovirt1 and that one was far behind the other servers.
>
>Once I fixed the issue, I kept receiving those errors despite tthe fact
>that I fixed the time drift on ovirt1 several days ago.
>Currently the hosts and the engine are OK, but I got no idea how to
>'fix' the issue.
>
>I have also noticed that the 2  errors had a  date  of 2 PM which is
>not possible with my current timezone.
>
>Here  is a one-shot query from all nodes:
>
>[root@ovirt1 ~]# for i in ovirt{1..3}; do ssh $i "ntpdate -q
>office.ipacct.com"; done
>server 195.85.215.8, stratum 1, offset 0.001233, delay 0.03105
>11 Jun 05:48:16 ntpdate[5224]: adjust time server 195.85.215.8 offset
>0.001233 sec
>server 195.85.215.8, stratum 1, offset -0.000200, delay 0.02821
>11 Jun 05:48:23 ntpdate[6637]: adjust time server 195.85.215.8 offset
>-0.000200 sec
>server 195.85.215.8, stratum 1, offset 0.000243, delay 0.02914
>11 Jun 05:48:30 ntpdate[14215]: adjust time server 195.85.215.8 offset
>0.000243 sec
>[root@ovirt1 ~]# ssh engine 'ntpdate -q office.ipacct.com'
>root@engine's password:
>server 195.85.215.8, stratum 1, offset 0.000291, delay 0.02888
>11 Jun 05:49:15 ntpdate[13911]: adjust time server 195.85.215.8 offset
>0.000291 sec
>
>Any ideas ?
>
>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/QN7VIVOZFOTUQY3GFUWWW6CJZUQDN4ES/

[ovirt-users] Host has time-drift of xxx seconds

[Strahil Nikolov via Users]

Hello All,

I have a strange error that should be fixed but the event log is  still filling 
with the following after the latest patching (4.3.10):

Host ovirt2.localdomain has time-drift of 2909848 seconds while maximum 
configured value is 300 seconds.
Host ovirt3.localdomain has time-drift of 2909848 seconds while maximum 
configured value is 300 seconds.

As  it blamed only 2  out of 3 systems,  I checked what has happened  on ovirt1 
and that one was far behind the other servers.

Once I fixed the issue, I kept receiving those errors despite tthe fact that I 
fixed the time drift on ovirt1 several days ago.
Currently the hosts and the engine are OK, but I got no idea how to 'fix' the 
issue.

I have also noticed that the 2  errors had a  date  of 2 PM which is not 
possible with my current timezone.

Here  is a one-shot query from all nodes:

[root@ovirt1 ~]# for i in ovirt{1..3}; do ssh $i "ntpdate -q 
office.ipacct.com"; done
server 195.85.215.8, stratum 1, offset 0.001233, delay 0.03105
11 Jun 05:48:16 ntpdate[5224]: adjust time server 195.85.215.8 offset 0.001233 
sec
server 195.85.215.8, stratum 1, offset -0.000200, delay 0.02821
11 Jun 05:48:23 ntpdate[6637]: adjust time server 195.85.215.8 offset -0.000200 
sec
server 195.85.215.8, stratum 1, offset 0.000243, delay 0.02914
11 Jun 05:48:30 ntpdate[14215]: adjust time server 195.85.215.8 offset 0.000243 
sec
[root@ovirt1 ~]# ssh engine 'ntpdate -q office.ipacct.com'
root@engine's password:
server 195.85.215.8, stratum 1, offset 0.000291, delay 0.02888
11 Jun 05:49:15 ntpdate[13911]: adjust time server 195.85.215.8 offset 0.000291 
sec

Any ideas ?

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/B2IGFLACF66RX2SUWBTAX66GZTJJ4T4L/

[ovirt-users] cloud-init: reverts on reboot

[Jp]

cloud-init settings entered into Hosted Engine are reverting after reboot, so 
what's the correct workflow for using the UI form?

I'd like a workflow where I can:
1. start with Template (covers most settings)
2. create VM 
3. use cloud-init in the UI (for a few settings, like static IP)
4. start/reboot VM and have cloud-init settings stick

How is the above possible?
___
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/ECHLM4E4Z327XAPDJS5RM6DRM3V4T2JS/

[ovirt-users] Re: teaming vs bonding

[Christopher Cox]

On 6/10/20 1:30 PM, Diggy Mc wrote:

Does 4.4.x support adapter teaming?  If yes, which is preferred, teaming or 
bonding?


(just an informational post)

Linux (not necessarily oVirt), supports various "bond modes", see:


https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-using_channel_bonding

(you are welcome to Google other sources besides Red Hat)


Linux bond mode 4, is LACP, 802.3ad, what traditionally you'd want and is for 
sure supported in oVirt host nodes (because we use it, so I know it works).   We 
use this for the non-SAN side of the fence and using multiple VLAN tags. 
Essentially, due to limitation of ports on the nodes, we run everything non-SAN 
on the LACP bond.


With that said, iSCSI multipathing (as in oVirt), which is not a "bond" as 
discussed thus far, but was called "bonding" in early oVirt is just 
multipathing.  And is what you'd use for storage coming off a SAN.  I mention 
this because of the historical confusion of what this was called in early oVirt. 
 In our case, we have 4 x 10Gbit paths on each node going to our SAN.


LACP requires cooperation of the switches involved (I say switches because 
multi-chassis link aggregation is often supported).  Usually you work with your 
network admin to configure the switch side (of course, one could be wearing all 
of the hats).


Microsoft Teaming has various configurations, some of these map closely to Linux 
bond modes (default is either like mode 2 or mode 6 in Linux I think, but there 
may not be anything close to a direct mapping) and obviously, there's still the 
ubiquitous LACP, which certainly is the "standard" present in both OS's.  I 
mention this, because usually when I hear someone say "teaming" they are coming 
from a Microsoft background.

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

[ovirt-users] Re: teaming vs bonding

[Asaf Rachmani]

Teaming is not supported in 4.4, please use bonding instead.

Regards,
Asaf

On Thu, Jun 11, 2020 at 12:31 AM Chris Adams  wrote:

> Once upon a time, Louis Bohm  said:
> > Unless I have learned wrong all these years Teaming is the Windows term
> for Linux Bonding.
>
> Linux has two methods (or maybe, at least two methods?) to support
> ethernet link aggregation: the original bonding and the newer team
> modules.  The primary difference is that bonding is done entirely in the
> kernel, while team management is in userspace.  The team setup is more
> flexible and IIRC easier to programatically monitor.
>
> --
> Chris Adams 
> ___
> 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/JCZULPVDELIDG6E2XVPN5GWNDFYHGL3P/
>
___
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/R3MMIP4SKW7V7K5XDVMZTIIVJBBCEQCI/

[ovirt-users] Re: teaming vs bonding

[Chris Adams]

Once upon a time, Louis Bohm  said:
> Unless I have learned wrong all these years Teaming is the Windows term for 
> Linux Bonding.

Linux has two methods (or maybe, at least two methods?) to support
ethernet link aggregation: the original bonding and the newer team
modules.  The primary difference is that bonding is done entirely in the
kernel, while team management is in userspace.  The team setup is more
flexible and IIRC easier to programatically monitor.

-- 
Chris Adams 
___
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/JCZULPVDELIDG6E2XVPN5GWNDFYHGL3P/

[ovirt-users] Re: teaming vs bonding

[Gabi C]

Redhat POV



https://www.redhat.com/en/blog/if-you-bonding-you-will-love-teaming

On Wed, Jun 10, 2020 at 9:39 PM Louis Bohm  wrote:

> Unless I have learned wrong all these years Teaming is the Windows term
> for Linux Bonding.
>
> And its the underlying OS that needs to support it.  Unless you mean to do
> the Teaming/Bonding in the VM.  Which it would then be the VM’s OS that
> needs to support it.
>
> Not sure if Ovirt support LACP bonding in the VM.  It probably does.
>
> Louis
> -<<—->>-
> Louis Bohm
> louisb...@gmail.com
>
>
> 
>
> 
>
> On Jun 10, 2020, at 2:30 PM, Diggy Mc  wrote:
>
> Does 4.4.x support adapter teaming?  If yes, which is preferred, teaming
> or bonding?
> ___
> 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/THMDPSFEX4GAISJ5ELGEWBEFMLKGQVE5/
>
>
> ___
> 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/KSQIS4BGLRTDKKALHCGENAXKHBLBISHI/
>
___
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/AQWX77EEJVA5K6ZEYUSUXZ5DM4E2H643/

[ovirt-users] Re: teaming vs bonding

[Vinícius Ferrão via Users]

Only bonding, teaming is not supported on the by the hypervisor.

This was valid up to 4.3; not sure if something changed on 4.4, since I didn’t 
checked it.


> On 10 Jun 2020, at 15:30, Diggy Mc  wrote:
> 
> Does 4.4.x support adapter teaming?  If yes, which is preferred, teaming or 
> bonding?
> ___
> 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/THMDPSFEX4GAISJ5ELGEWBEFMLKGQVE5/

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

[ovirt-users] Re: teaming vs bonding

[Louis Bohm]

Unless I have learned wrong all these years Teaming is the Windows term for 
Linux Bonding.

And its the underlying OS that needs to support it.  Unless you mean to do the 
Teaming/Bonding in the VM.  Which it would then be the VM’s OS that needs to 
support it.

Not sure if Ovirt support LACP bonding in the VM.  It probably does.

Louis
-<<—->>-
Louis Bohm
louisb...@gmail.com

 

 


> On Jun 10, 2020, at 2:30 PM, Diggy Mc  wrote:
> 
> Does 4.4.x support adapter teaming?  If yes, which is preferred, teaming or 
> bonding?
> ___
> 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/THMDPSFEX4GAISJ5ELGEWBEFMLKGQVE5/
>  
> 

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

[ovirt-users] teaming vs bonding

[Diggy Mc]

Does 4.4.x support adapter teaming?  If yes, which is preferred, teaming or 
bonding?
___
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/THMDPSFEX4GAISJ5ELGEWBEFMLKGQVE5/

[ovirt-users] Re: Deploy host engine error: The task includes an option with an undefined variable

[Angel R. Gonzalez]

Hello!
Thanks for your answers.

First, I try to modify 01_create_target_hosted_engine_vm.yml file with 
the below code, and Redeploy. The process don't run. I've typed the code 
again with carefully, and the result is same. I've eliminated the code 
and Redeploy start again until find the error.


After this, I've checked the mails with subject: Issues deploying 
4.4.with HE on new EPYC hosts, and I think that is a problem with AMD 
processors.


The scenario:
serverlabs-engine -> 8x Intel(R) Xeon(R) CPU E5410 @ 2.33GHz. This node 
execute wizard Hosted engine
serverlabs-node2 -> 8x Intel(R) Xeon(R) CPU E31230 @ 3.20GHz. This node 
has configured glusterfs storage

Both CentOS-8.1.1911-x86_64 ISO LIVE DVD
kernel 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Thu Apr 9 13:49:54 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux


# rpm -q qemu-kvm libvirt
qemu-kvm-4.1.0-23.el8.1.x86_64
libvirt-5.6.0-10.el8.x86_64

The process running in host node (serverlabs-engine) in storage phase 
deployment:


qemu  8455 1 52 17:46 ?    00:31:09 /usr/libexec/qemu-kvm 
-name guest=HostedEngineLocal,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/master-key.aes 
-machine pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off -cpu 
Penryn,vme=on,ss=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc-adjust=on,arch-capabilities=on,skip-l1dfl-vmentry=on,kvmclock=on 
-m 8192 -overcommit mem-lock=off -smp 4,sockets=4,cores=1,threads=1 
-uuid 4af397d7-4c81-4044-934f-90138288e09a -no-user-config -nodefaults 
-chardev socket,id=charmonitor,fd=37,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot 
menu=off,strict=on -device 
pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 
-device 
pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 
-device 
pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 
-device 
pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 
-device 
pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 -drive 
file=/var/tmp/localvmaodqdyv8/images/6c7c4d4b-9c11-485d-98e0-466a09888515/c16b87ac-f9d4-491d-a972-7dc333a324a0,format=qcow2,if=none,id=drive-virtio-disk0 
-device 
virtio-blk-pci,scsi=off,bus=pci.3,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 
-drive 
file=/var/tmp/localvmaodqdyv8/seed.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on 
-device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0 -netdev 
tap,fd=39,id=hostnet0,vhost=on,vhostfd=40 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:5a:57:25,bus=pci.1,addr=0x0 
-chardev pty,id=charserial0 -device 
isa-serial,chardev=charserial0,id=serial0 -chardev 
socket,id=charchannel0,fd=41,server,nowait -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 
-vnc 127.0.0.1:0 -device VGA,id=video0,vgamem_mb=16,bus=pcie.0,addr=0x1 
-object rng-random,id=objrng0,filename=/dev/random -device 
virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.4,addr=0x0 -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny 
-msg timestamp=on




Finally, I've searched server_cpu_list and server_cpu_dist from 
ovirt-hosted-engine-setup-ansible-create_target_vm-2020510182419-vkgvze.log 
file:



2020-06-10 18:24:22,516+0200 DEBUG var changed: host "localhost" var 
"he_graphics_device" type "'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""vnc""
2020-06-10 18:24:22,516+0200 DEBUG var changed: host "localhost" var 
"he_vm_name" type "'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""HostedEngine""
2020-06-10 18:24:22,516+0200 DEBUG var changed: host "localhost" var 
"he_host_name" type "'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""serverlabs-engine""
2020-06-10 18:24:22,517+0200 DEBUG var changed: host "localhost" var 
"he_console_type" type "'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""vnc""
2020-06-10 18:24:22,517+0200 DEBUG var changed: host "localhost" var 
"he_cpu_type" type "'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""model_Penryn""
2020-06-10 18:24:22,517+0200 DEBUG var changed: host "localhost" var 
"he_smtp_server" type "'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""localhost""



.
2020-06-10 18:24:26,064+0200 DEBUG var changed: host "localhost" var 
"ansible_mounts" type "" value: "[

    {
    "block_available": 43397299,
    "block_size": 4096,
    "block_total": 51343866,
    "block_used": 7946567,
    "device": "/dev/sda1",
    "fstype": "ext4",
    "inode_available": 13025816,
    "inode_total": 13107200,
    "inode_used": 81384,
    "mount": "/",
    "options": "rw,seclabel,relatime",
    "size_available": 177755336704,
 

[ovirt-users] Re: Advise Needed - Hosted Engine Minor Update

[Strahil Nikolov via Users]

I use  Gluster  snapshots before patching the engine.
Usually the flow is:
1. Global Maintenance
2. Power off the HostedEngine VM
3. Gluster snapshot
4. Power on HE
5. Upgrade  of the setup packages
6. Run the hosted-engine upgrade  script
7. Patch the OS of HE
8. Reboot
9. Remove Global Maintenance


If you need to revert a snapshot, you need to stop the gluster volume , so you 
need to follow the rule and keep the engine on a separate gluster volume.


Best Regards,
Strahil Nikolov

На 10 юни 2020 г. 13:21:08 GMT+03:00, Yedidyah Bar David  
написа:
>On Wed, Jun 10, 2020 at 1:05 PM  wrote:
>>
>> Hi Guys!
>>
>> How do you usually backup your hosted engine prior minor updates?
>>
>> I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently.
>I’ve used engine-backup before updating and for restore. However, the
>problem I’m encountering now is that, it looks like the hosted-engine
>settings are only being restored. The version is still 4.3.9 when I’m
>trying to revert it to 4.3.8.
>>
>> Am I missing some steps aside from engine-backup —restore? I saw on
>old posts that snapshots of hosted engine is not a recommended step
>before upgrade/update.
>
>engine-backup --mode=restore only restores the data. If you want 4.3.8
>packages, you have to install them. For rolling back packages on an
>existing machine, you can usually find the relevant yum transactions
>and 'yum history undo $ID' on them.
>
>If you installed and set up e.g. 4.3.8, and take a backup, then try to
>restore this backup on 4.3.9, the next engine-setup you run (which is
>a required step after restore) will upgrade your database
>schema/content to 4.3.9.
>
>Hope this helps,
___
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/SZ4NSSMKDBQIK6VJX7YMZBFDB7SKOPDC/

[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4

[Joop]

On 8-6-2020 19:55, Joop wrote:
> On 8-6-2020 17:52, Strahil Nikolov wrote:
>> Are you using ECC ram ?
> No, but what are the chances that starting a VM by using Run directly vs
> using the Boot wait menu and it hitting that bad bit each and every time?
> BTW: this setup worked perfectly for over 9 months using 4.3.X.
>
> Joop
>
Correction, we are using ecc and ran memtest and didn't find anything wrong.

Reinstalled the server and I have the same problem again.

Started reading up on vdsm-hooks because I could get my VM up
consistently when using bootmenu=enabled.
So wrote this small piece of code, most of it is copy pasted:

#!/usr/bin/python3
#
#
from __future__ import absolute_import

import os
import sys
import subprocess
import hooking


if hooking.tobool(os.environ.get('boot_timeout', True)):
  domxml = hooking.read_domxml()

  os = domxml.getElementsByTagName('os')[0]
  bootelem = domxml.createElement('bootmenu')
  bootelem.setAttribute('timeout', '1000')
  bootelem.setAttribute('enable', 'yes')
  os.appendChild(bootelem)

  hooking.write_domxml(domxml)
#  pretty_xml_as_string = os.toprettyxml()
#  sys.stderr.write('%s\n' % pretty_xml_as_string)

Saved it in /usr/libexec/vdsm/hooks/before_vm_start as 90_wait
Played around with the timeout but lower than 1000 (1sec) and the
problem reappears.
For the time being I'm going forward with this workaround.

For good measure I'll include my versions of ovirt/vdsm/gluster/engine
cockpit-ovirt-dashboard-0.14.6-1.el8.noarch
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch
ovirt-host-4.4.1-1.el8.x86_64
ovirt-host-dependencies-4.4.1-1.el8.x86_64
ovirt-hosted-engine-ha-2.4.3-1.el8.noarch
ovirt-hosted-engine-setup-2.4.4-1.el8.noarch
ovirt-imageio-client-2.0.6-0.el8.x86_64
ovirt-imageio-common-2.0.6-0.el8.x86_64
ovirt-imageio-daemon-2.0.6-0.el8.x86_64
ovirt-provider-ovn-driver-1.2.30-1.el8.noarch
ovirt-release44-4.4.0-2.el8.noarch
ovirt-vmconsole-1.0.8-1.el8.noarch
ovirt-vmconsole-host-1.0.8-1.el8.noarch
python3-ovirt-engine-sdk4-4.4.3-1.el8.x86_64
python3-ovirt-setup-lib-1.3.0-1.el8.noarch

vdsm-4.40.16-1.el8.x86_64
vdsm-api-4.40.16-1.el8.noarch
vdsm-client-4.40.16-1.el8.noarch
vdsm-common-4.40.16-1.el8.noarch
vdsm-gluster-4.40.16-1.el8.x86_64
vdsm-hook-ethtool-options-4.40.16-1.el8.noarch
vdsm-hook-fcoe-4.40.16-1.el8.noarch
vdsm-hook-openstacknet-4.40.16-1.el8.noarch
vdsm-hook-vhostmd-4.40.16-1.el8.noarch
vdsm-hook-vmfex-dev-4.40.16-1.el8.noarch
vdsm-http-4.40.16-1.el8.noarch
vdsm-jsonrpc-4.40.16-1.el8.noarch
vdsm-network-4.40.16-1.el8.x86_64
vdsm-python-4.40.16-1.el8.noarch
vdsm-yajsonrpc-4.40.16-1.el8.noarch

gluster-ansible-cluster-1.0.0-1.el8.noarch
gluster-ansible-features-1.0.5-6.el8.noarch
gluster-ansible-infra-1.0.4-10.el8.noarch
gluster-ansible-maintenance-1.0.1-3.el8.noarch
gluster-ansible-repositories-1.0.1-2.el8.noarch
gluster-ansible-roles-1.0.5-12.el8.noarch
glusterfs-7.5-1.el8.x86_64
glusterfs-api-7.5-1.el8.x86_64
glusterfs-cli-7.5-1.el8.x86_64
glusterfs-client-xlators-7.5-1.el8.x86_64
glusterfs-events-7.5-1.el8.x86_64
glusterfs-fuse-7.5-1.el8.x86_64
glusterfs-geo-replication-7.5-1.el8.x86_64
glusterfs-libs-7.5-1.el8.x86_64
glusterfs-rdma-7.5-1.el8.x86_64
glusterfs-server-7.5-1.el8.x86_64
libvirt-daemon-driver-storage-gluster-5.6.0-10.el8.x86_64
python3-gluster-7.5-1.el8.x86_64
qemu-kvm-block-gluster-4.1.0-23.el8.1.x86_64
vdsm-gluster-4.40.16-1.el8.x86_64

ipxe-roms-qemu-20181214-3.git133f4c47.el8.noarch
libvirt-daemon-driver-qemu-5.6.0-10.el8.x86_64
qemu-img-4.1.0-23.el8.1.x86_64
qemu-kvm-4.1.0-23.el8.1.x86_64
qemu-kvm-block-curl-4.1.0-23.el8.1.x86_64
qemu-kvm-block-gluster-4.1.0-23.el8.1.x86_64
qemu-kvm-block-iscsi-4.1.0-23.el8.1.x86_64
qemu-kvm-block-rbd-4.1.0-23.el8.1.x86_64
qemu-kvm-block-ssh-4.1.0-23.el8.1.x86_64
qemu-kvm-common-4.1.0-23.el8.1.x86_64
qemu-kvm-core-4.1.0-23.el8.1.x86_64

libvirt-admin-5.6.0-10.el8.x86_64
libvirt-bash-completion-5.6.0-10.el8.x86_64
libvirt-client-5.6.0-10.el8.x86_64
libvirt-daemon-5.6.0-10.el8.x86_64
libvirt-daemon-config-network-5.6.0-10.el8.x86_64
libvirt-daemon-config-nwfilter-5.6.0-10.el8.x86_64
libvirt-daemon-driver-interface-5.6.0-10.el8.x86_64
libvirt-daemon-driver-network-5.6.0-10.el8.x86_64
libvirt-daemon-driver-nodedev-5.6.0-10.el8.x86_64
libvirt-daemon-driver-nwfilter-5.6.0-10.el8.x86_64
libvirt-daemon-driver-qemu-5.6.0-10.el8.x86_64
libvirt-daemon-driver-secret-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-core-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-disk-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-gluster-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-iscsi-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-iscsi-direct-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-logical-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-mpath-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-rbd-5.6.0-10.el8.x86_64
libvirt-daemon-driver-storage-scsi-5.6.0-10.el8.x86_64
libvirt-daemon-kvm-5

[ovirt-users] Re: Advise Needed - Hosted Engine Minor Update

[Yedidyah Bar David]

On Wed, Jun 10, 2020 at 1:05 PM  wrote:
>
> Hi Guys!
>
> How do you usually backup your hosted engine prior minor updates?
>
> I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently. I’ve used 
> engine-backup before updating and for restore. However, the problem I’m 
> encountering now is that, it looks like the hosted-engine settings are only 
> being restored. The version is still 4.3.9 when I’m trying to revert it to 
> 4.3.8.
>
> Am I missing some steps aside from engine-backup —restore? I saw on old posts 
> that snapshots of hosted engine is not a recommended step before 
> upgrade/update.

engine-backup --mode=restore only restores the data. If you want 4.3.8
packages, you have to install them. For rolling back packages on an
existing machine, you can usually find the relevant yum transactions
and 'yum history undo $ID' on them.

If you installed and set up e.g. 4.3.8, and take a backup, then try to
restore this backup on 4.3.9, the next engine-setup you run (which is
a required step after restore) will upgrade your database
schema/content to 4.3.9.

Hope this helps,
-- 
Didi
___
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/BDTL3DUQYRI62S2JOYGEUWTRAEKG3TUK/

[ovirt-users] Re: how to test incremental backup in 4.4

[Eyal Shenitzky]

It is always better to use the latest version for testing this feature.
If I remember correctly 4.2 contains some fixes for incremental backup so
better to use it.

On Wed, 10 Jun 2020 at 11:28, Gianluca Cecchi 
wrote:

> On Wed, Jun 10, 2020 at 10:18 AM Eyal Shenitzky 
> wrote:
>
>> Hopefully yes, just validate that the libvirt version is >= 6.0.0.
>>
>>
> While do you confirm that Qemu 4.1 vs 4.2 is not essential for the feature?
>
> Gianluca
>
>

-- 
Regards,
Eyal Shenitzky
___
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/NIYU4TZCZB7N3VJKCPBTTROBS6EJD5BJ/

[ovirt-users] Re: What happens when shared storage is down?

[Strahil Nikolov via Users]

Hi  Vinicius,

If you don't  have too much VMs and you have local storage (like a  raid 
controller) or NFS/iSCSI - you can also move the VMs there temporarily (live 
storage  migration) without any interruption.

Best Regards,
Strahil Nikolov

На 10 юни 2020 г. 12:14:38 GMT+03:00, Jayme  написа:
>This is of course not recommended but there has been times where I have
>lost network access to storage or storage sever while vms were running.
>They paused and came back up when storage was available again without
>causing any problems. This doesn’t mean it’s 100% safe but from my
>experience it has not caused any issue.
>
>Personally I would shutdown vms or live migrate the disk to secondary
>storage then migrate it back after the updates are performed.
>
>On Wed, Jun 10, 2020 at 2:22 AM Vinícius Ferrão via Users
>
>wrote:
>
>>
>>
>> > On 7 Jun 2020, at 08:34, Strahil Nikolov 
>wrote:
>> >
>> >
>> >
>> > На 7 юни 2020 г. 1:58:27 GMT+03:00, "Vinícius Ferrão via Users" <
>> users@ovirt.org> написа:
>> >> Hello,
>> >>
>> >> This is a pretty vague and difficult question to answer. But what
>> >> happens if the shared storage holding the VMs is down or
>unavailable
>> >> for a period of time?
>> > Once  a  pending I/O is blocked, libvirt will pause the VM .
>> >
>> >> I’m aware that a longer timeout may put the VMs on pause state,
>but how
>> >> this is handled? Is it a time limit? Requests limit? Who manages
>this?
>> > You got sanlock.service that notifies the engine when a storage
>domain
>> is unaccessible for  mode than 60s.
>> >
>> > Libvirt also will pause  a  VM when a pending I/O cannot be done.
>> >
>> >> In an event of self recovery of the storage backend what happens
>next?
>> > Usually the engine should resume the VM,  and from application
>> perspective nothing has happened.
>>
>> Hmm thanks Strahil. I was thinking to upgrade the storage backend of
>one
>> of my oVirt clusters without powering off the VM’s, just to be lazy.
>>
>> The storage does not have dual controllers, so downtime is needed.
>I’m
>> trying to understand what happens so I can evaluate this update
>without
>> turning off the VMs.
>>
>> >> Manual intervention is required? The VMs may be down or they just
>> >> continue to run? It depends on the guest OS running like in
>XenServer
>> >> where different scenarios may happen?
>> >>
>> >> I’ve looked here:
>> >> https://www.ovirt.org/documentation/admin-guide/chap-Storage.html
>but
>> >> there’s nothing that goes about this question.
>> >>
>> >> Thanks,
>> >>
>> >> Sent from my iPhone
>>
>> ___
>> 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/BVZAG2V3KBB364U5VBRCBIU42LJNGCI6/
>>
___
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/FH7XKNDBVD7CETKM4KN5BSO7IRTOCNYF/

[ovirt-users] Advise Needed - Hosted Engine Minor Update

[jrbdeguzman05]

Hi Guys!

How do you usually backup your hosted engine prior minor updates?

I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently. I’ve used 
engine-backup before updating and for restore. However, the problem I’m 
encountering now is that, it looks like the hosted-engine settings are only 
being restored. The version is still 4.3.9 when I’m trying to revert it to 
4.3.8.

Am I missing some steps aside from engine-backup —restore? I saw on old posts 
that snapshots of hosted engine is not a recommended step before upgrade/update.

Appreciate your help in advance!
___
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/6GUJ7DMLLDYCKQ52FO5FE3NPNDFQYFIS/

[ovirt-users] Re: What happens when shared storage is down?

[Jayme]

This is of course not recommended but there has been times where I have
lost network access to storage or storage sever while vms were running.
They paused and came back up when storage was available again without
causing any problems. This doesn’t mean it’s 100% safe but from my
experience it has not caused any issue.

Personally I would shutdown vms or live migrate the disk to secondary
storage then migrate it back after the updates are performed.

On Wed, Jun 10, 2020 at 2:22 AM Vinícius Ferrão via Users 
wrote:

>
>
> > On 7 Jun 2020, at 08:34, Strahil Nikolov  wrote:
> >
> >
> >
> > На 7 юни 2020 г. 1:58:27 GMT+03:00, "Vinícius Ferrão via Users" <
> users@ovirt.org> написа:
> >> Hello,
> >>
> >> This is a pretty vague and difficult question to answer. But what
> >> happens if the shared storage holding the VMs is down or unavailable
> >> for a period of time?
> > Once  a  pending I/O is blocked, libvirt will pause the VM .
> >
> >> I’m aware that a longer timeout may put the VMs on pause state, but how
> >> this is handled? Is it a time limit? Requests limit? Who manages this?
> > You got sanlock.service that notifies the engine when a storage domain
> is unaccessible for  mode than 60s.
> >
> > Libvirt also will pause  a  VM when a pending I/O cannot be done.
> >
> >> In an event of self recovery of the storage backend what happens next?
> > Usually the engine should resume the VM,  and from application
> perspective nothing has happened.
>
> Hmm thanks Strahil. I was thinking to upgrade the storage backend of one
> of my oVirt clusters without powering off the VM’s, just to be lazy.
>
> The storage does not have dual controllers, so downtime is needed. I’m
> trying to understand what happens so I can evaluate this update without
> turning off the VMs.
>
> >> Manual intervention is required? The VMs may be down or they just
> >> continue to run? It depends on the guest OS running like in XenServer
> >> where different scenarios may happen?
> >>
> >> I’ve looked here:
> >> https://www.ovirt.org/documentation/admin-guide/chap-Storage.html but
> >> there’s nothing that goes about this question.
> >>
> >> Thanks,
> >>
> >> Sent from my iPhone
>
> ___
> 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/BVZAG2V3KBB364U5VBRCBIU42LJNGCI6/
>
___
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/TKGXPENNO7RTW3S7G3GZODMNOHPULEMR/

[ovirt-users] Re: Ovirt Manager HA

[Yedidyah Bar David]

On Wed, Jun 10, 2020 at 11:29 AM Joseph Goldman  wrote:
>
> As the other response alluded to - proper HA ovirt engine is a hosted VM 
> ovirt-engine.
>
> But the way oVirt is designed is that it just pushes configuration to the 
> hosts - if your ovirt-engine dies, redeploying from backup should be fairly 
> quick and painless - just some features may be unavailable like hot migrate 
> etc, but importantly your existing VM's will continue to run as they were 
> until you can re-deploy your engine.
>
> If you are worried about performance and resources - you could simply create 
> a new cluster for just Hosted Engine stuff and deploy it there, so 2 servers 
> in HA for engine separate from the rest of your VM clusters.
>
> On 10/06/2020 4:20 pm, Vijay Sachdeva via Users wrote:
>
> Hi All,
>
>
>
> Is there a documentation on creating Ovirt-Manager in HA or is it possible to 
> make the manager to run in HA environment. Since it seems to be a single 
> point of failure..!!

In addition to what others (correctly) said, we heard also of a few
setups using pacemaker etc. on bare-metal hosts for the engine.

I'd say, if you or your team are comfortable with pacemaker, have
conf/processes/experience around it, and can spare the extra hardware
and rack space, it might be a valid option.

Biggest con of ovirt-hosted-engine-ha, IMO, is the rather bad feeling
some people have about having less control on the disk image, etc.,
what to do when it dies, how to debug/fix issues. Of course, if you
are very experienced with oVirt's HA, know how to debug/fix corrupt
disk images, VM boot problems, etc., and have no experience with
pacemaker, oVirt HA will be better for you. In any case, for important
setups, keep good backups (and test them routinely!).

Best regards,
-- 
Didi
___
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/26LERAZ4L53GUSOKUD34K2ZQ2YYJFBAA/

[ovirt-users] Re: how to test incremental backup in 4.4

[Gianluca Cecchi]

On Wed, Jun 10, 2020 at 10:18 AM Eyal Shenitzky  wrote:

> Hopefully yes, just validate that the libvirt version is >= 6.0.0.
>
>
While do you confirm that Qemu 4.1 vs 4.2 is not essential for the feature?

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/G2FZ3OHD5B4ZHNPGH7XTLT7GRNPQFTMT/

[ovirt-users] Re: Ovirt Manager HA

[Joseph Goldman]

As the other response alluded to - proper HA ovirt engine is a hosted VM 
ovirt-engine.


But the way oVirt is designed is that it just pushes configuration to 
the hosts - if your ovirt-engine dies, redeploying from backup should be 
fairly quick and painless - just some features may be unavailable like 
hot migrate etc, but importantly your existing VM's will continue to run 
as they were until you can re-deploy your engine.


If you are worried about performance and resources - you could simply 
create a new cluster for just Hosted Engine stuff and deploy it there, 
so 2 servers in HA for engine separate from the rest of your VM clusters.


On 10/06/2020 4:20 pm, Vijay Sachdeva via Users wrote:


Hi All,

Is there a documentation on creating Ovirt-Manager in HA or is it 
possible to make the manager to run in HA environment. Since it seems 
to be a single point of failure..!!


Thanks

Vijay Sachdeva


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


___
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/2WXR6EOIMRUB6D2KSLIUYGEOW6EW3YNY/

[ovirt-users] Re: how to test incremental backup in 4.4

[Eyal Shenitzky]

Hopefully yes, just validate that the libvirt version is >= 6.0.0.

On Wed, 10 Jun 2020 at 11:07, Gianluca Cecchi 
wrote:

> On Wed, Jun 10, 2020 at 9:51 AM Eyal Shenitzky 
> wrote:
>
>>
>>
>> On Tue, 9 Jun 2020 at 13:44, Nir Soffer  wrote:
>>
>>> On Tue, Jun 9, 2020 at 11:51 AM Gianluca Cecchi
>>>  wrote:
>>> >
>>> > On Tue, Jun 9, 2020 at 10:39 AM Joseph Goldman 
>>> wrote:
>>> >>
>>> >> I could be wrong but i believe you need to push libvirt / qemu to a
>>> newer release on your hosts to enable the feature. This may be a 4.3 only
>>> thing though.
>>> >>
>>> >
>>> > I have 4.4 and currently on host:
>>> > qemu-kvm-4.1.0-23.el8.1.x86_64
>>> > libvirt-daemon-5.6.0-10.el8.x86_64
>>>
>>> Too old, you need RHEL 8.2, best RHEL 8.2.1 nightly build.
>>>
>>> Using ovirt-release-master.rpm:
>>> dnf install
>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
>>>
>>> You should get newer enough libvirt and qemu on CentOS 8.1, but it is
>>> not tested
>>> with incremental backup.
>>>
>>
>> Should work also with RHEL-8.2 (libvirt >= 6.0.0)
>>
>> Try it.
>>
>
>
> So probably, remaining in CentOS, we will be able to test with a
> combination of 4.4.1 + CentOS 8.2?
> I will keep track of this:
> https://wiki.centos.org/About/Building_8.x#Current_Timeline_8.2.2004
> and when the node image will be based on it
>
> Gianluca
>
>

-- 
Regards,
Eyal Shenitzky
___
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/5KAG6P4PAA24QVL2UHSTT5JC77QOXJKR/

[ovirt-users] Re: how to test incremental backup in 4.4

[Gianluca Cecchi]

On Wed, Jun 10, 2020 at 9:51 AM Eyal Shenitzky  wrote:

>
>
> On Tue, 9 Jun 2020 at 13:44, Nir Soffer  wrote:
>
>> On Tue, Jun 9, 2020 at 11:51 AM Gianluca Cecchi
>>  wrote:
>> >
>> > On Tue, Jun 9, 2020 at 10:39 AM Joseph Goldman 
>> wrote:
>> >>
>> >> I could be wrong but i believe you need to push libvirt / qemu to a
>> newer release on your hosts to enable the feature. This may be a 4.3 only
>> thing though.
>> >>
>> >
>> > I have 4.4 and currently on host:
>> > qemu-kvm-4.1.0-23.el8.1.x86_64
>> > libvirt-daemon-5.6.0-10.el8.x86_64
>>
>> Too old, you need RHEL 8.2, best RHEL 8.2.1 nightly build.
>>
>> Using ovirt-release-master.rpm:
>> dnf install
>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
>>
>> You should get newer enough libvirt and qemu on CentOS 8.1, but it is not
>> tested
>> with incremental backup.
>>
>
> Should work also with RHEL-8.2 (libvirt >= 6.0.0)
>
> Try it.
>


So probably, remaining in CentOS, we will be able to test with a
combination of 4.4.1 + CentOS 8.2?
I will keep track of this:
https://wiki.centos.org/About/Building_8.x#Current_Timeline_8.2.2004
and when the node image will be based on it

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/QC7L4DCOQQJGBWBI2IDERUMGHCDT4Z4L/

[ovirt-users] Re: how to test incremental backup in 4.4

[Eyal Shenitzky]

On Tue, 9 Jun 2020 at 13:44, Nir Soffer  wrote:

> On Tue, Jun 9, 2020 at 11:51 AM Gianluca Cecchi
>  wrote:
> >
> > On Tue, Jun 9, 2020 at 10:39 AM Joseph Goldman 
> wrote:
> >>
> >> I could be wrong but i believe you need to push libvirt / qemu to a
> newer release on your hosts to enable the feature. This may be a 4.3 only
> thing though.
> >>
> >
> > I have 4.4 and currently on host:
> > qemu-kvm-4.1.0-23.el8.1.x86_64
> > libvirt-daemon-5.6.0-10.el8.x86_64
>
> Too old, you need RHEL 8.2, best RHEL 8.2.1 nightly build.
>
> Using ovirt-release-master.rpm:
> dnf install
> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
>
> You should get newer enough libvirt and qemu on CentOS 8.1, but it is not
> tested
> with incremental backup.
>

Should work also with RHEL-8.2 (libvirt >= 6.0.0)

Try it.


> It should work on Fedora 30 host, but Fedora 30 is EOL now. New enough
> libvirt and
> qemu are available in Fedora 31 and 32 (using virt-preview repo), but
> installing oVirt
> there is a challenge and I don't think anyone tested it yet.
>
> > Possibly needed sw pieces will be only in 4.4.1?
>
> 4.4.1 will include important fixes and new features in oVirt, but it
> will not help with libvirt
> and qemu.
>
> 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/6EARICHQFSP6BPNEYPPJOVIENFGVMJPJ/
>


-- 
Regards,
Eyal Shenitzky
___
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/EHNLA46J54ZVZ7FGDHE7TCBB6VZGSIEL/

[ovirt-users] Re: Cannot start ppc64le VM's

[Michal Skrivanek]

> On 10 Jun 2020, at 07:00, Vinícius Ferrão  wrote:
> 
> 
> 
>> On 8 Jun 2020, at 07:43, Michal Skrivanek > > wrote:
>> 
>> 
>> 
>>> On 5 Jun 2020, at 20:23, Vinícius Ferrão >> > wrote:
>>> 
>>> Hi Michal
>>> 
 On 5 Jun 2020, at 04:39, Michal Skrivanek >>> > wrote:
 
 
 
> On 5 Jun 2020, at 08:19, Vinícius Ferrão via Users  > wrote:
> 
> Hello, I’m trying to run ppc64le VM’s on POWER9 but qemu-kvm fails 
> complaining about NUMA issues:
 
 that is not a line you should be looking at, it’s just a harmless warning.
 I suppose it’s the other one, about spectre fixes
> 
> VM ppc64le.local.versatushpc.com.br 
>  is down with error. Exit 
> message: internal error: qemu unexpectedly closed the monitor: 
> 2020-06-05T06:16:10.716052Z qemu-kvm: warning: CPU(s) not present in any 
> NUMA nodes: CPU 4 [core-id: 4], CPU 5 [core-id: 5], CPU 6 [core-id: 6], 
> CPU 7 [core-id: 7], CPU 8 [core-id: 8], CPU 9 [core-id: 9], CPU 10 
> [core-id: 10], CPU 11 [core-id: 11], CPU 12 [core-id: 12], CPU 13 
> [core-id: 13], CPU 14 [core-id: 14], CPU 15 [core-id: 15] 
> 2020-06-05T06:16:10.716067Z qemu-kvm: warning: All CPU(s) up to maxcpus 
> should be described in NUMA config, ability to start up with partial NUMA 
> mappings is obsoleted and will be removed in future 
> 2020-06-05T06:16:11.155924Z qemu-kvm: Requested safe indirect branch 
> capability level not supported by kvm, try cap-ibs=fixed-ibs.
> 
> Any idea of what’s happening?
> 
> I found some links, but I’m not sure if they are related or not:
> https://bugzilla.redhat.com/show_bug.cgi?id=1732726 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1592648 
> 
 yes, they look relevant if that’s the hw you have. We do use 
 pseries-rhel7.6.0-sxxm machine type in 4.3 (not in 4.4. that would be the 
 preferred solution, to upgrade).
 If you don’t care about security you can also modify the machine type per 
 VM (or in engine db for all VMs) to "pseries-rhel7.6.0"
>>> 
>>> I’m using an AC922 machine.
>> 
>> and is it oVirt  4.3 or 4.4?
>> Bug 1732726 is on RHEL 8, so relevant only for oVirt 4.4, i.e. you’d have to 
>> have a 4.3 cluster level?
>> if you really want to keep using -sxxm you need to modify it to add the 
>> extra flag the bug talks about
>> 
>> this shouldn’t be needed in 4.4 cluster level though
> 
> Hi Michal, I’m running 4.3.10. Not in 4.4 yet.
> 
> So the workaround would be add cap-ibs=fixed-ibs to VM parameters so sxxm 
> would work? Where do I add this? Do you know?

you could try custom emulated machine in VM configuration. If it doesn’t work 
you’d need to write a vdsm hook to alter the libvirt xml accordingly


> 
> Thanks.
> 
>> 
>>> 
>>> In fact I can boot the VMs with pseries-rhel7.6.0 but not with 
>>> pseries-rhel7.6.0-sxxm; how do you made pseries-rhel7.6.0-sxxm works on 4.3 
>>> release?
>>> 
>>> # lscpu
>>> Architecture:  ppc64le
>>> Byte Order:Little Endian
>>> CPU(s):128
>>> On-line CPU(s) list:   0-127
>>> Thread(s) per core:4
>>> Core(s) per socket:16
>>> Socket(s): 2
>>> NUMA node(s):  6
>>> Model: 2.2 (pvr 004e 1202)
>>> Model name:POWER9, altivec supported
>>> CPU max MHz:   3800.
>>> CPU min MHz:   2300.
>>> L1d cache: 32K
>>> L1i cache: 32K
>>> L2 cache:  512K
>>> L3 cache:  10240K
>>> NUMA node0 CPU(s): 0-63
>>> NUMA node8 CPU(s): 64-127
>>> NUMA node252 CPU(s):   
>>> NUMA node253 CPU(s):   
>>> NUMA node254 CPU(s):   
>>> NUMA node255 CPU(s): 
>>> 
>>> Thank you for helping out.
>>> 
 
 Thanks,
 michal
> 
> 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/PVVQDBO2XJYBQN7EUDMM74QZJ2UTLRJ2/
>  
> 

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.