- Devel - oVirt List Archives

Vdsm: ovirt-4.4.2 branch created
by Milan Zamazal 19 Aug '20

19 Aug '20

Hi, ovirt-4.4.2 branch has been created in Vdsm repository. Any future changes for 4.4.2 must be backported there. You can merge non-4.4.2 stuff to master now. Regards, Milan

1 0

Max running ansible-playbook
by Tommaso - Shellrent 19 Aug '20

19 Aug '20

Hi to all. on our angine we always see max 1 ansible-playbook running on the same time. We use OVA export to make some backup, but the whole task takes a lot of time because only one ansible-playbook "/usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml" run at the same time. How can we ingrease this value? -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.11.4)
by Tal Nisan 18 Aug '20

18 Aug '20

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.2.3)
by Tal Nisan 18 Aug '20

18 Aug '20

1 0

KVM with RDP using RDPMux for oVirt?
by Neal Gompa 17 Aug '20

17 Aug '20

Hello, At the urging of Sandro Bonazzola, I'm bringing up something that was being discussed on Twitter earlier today: supporting RDP with KVM directly. As it turns out, about four years ago, Datto developed support for QEMU to display to RDP in a similar fashion to what was done for SPICE years ago. The way this was done was by patching QEMU[1] to send buffers to a service called RDPMux[2], which would provide RDP connections. Additionally, libvirt was adjusted to support this[3]. Now, a couple years ago, I attempted to start rebasing this to QEMU 2.12.0 for my own use[4], but while I was able to make it compile[5], it always hung when I tried to use the functionality. This came up on Twitter earlier today when talking about how KVM lacks RDP but had SPICE (which didn't catch on, and is apparently deprecated now[6]?!?) Is anyone interested in potentially helping me get this working with the latest QEMU and libvirt? I'd be happy to package up RDPMux for Fedora and get that in the distribution for people to use in that case... Best regards, Neal [1]: https://pagure.io/virt-with-rdp/blob/master/f/qemu-2.5 [2]: https://github.com/datto/RDPMux [3]: https://pagure.io/virt-with-rdp/blob/master/f/libvirt-1.3.1 [4]: https://pagure.io/virt-with-rdp/blob/master/f/qemu-2.12.0 [5]: https://copr.fedorainfracloud.org/coprs/ngompa/virt-with-rdp/build/774882/ [6]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-be… -- 真実はいつも一つ！/ Always, there's only one truth!

4 7

Improving VM behavior in case of IO errors
by Shubha Kulkarni 16 Aug '20

16 Aug '20

Hello, In OVirt, we have a property propagate_error at the disk level that decides in case of an error, how this error be propagated to the VM. This value is maintained in the database table with the default value set as Off. The default setting(Off) results in a policy that ends up pausing the VM rather than propagating the errors to VM. There is no provision in the UI currently to configure this property for disk (images or luns). So there is no easy way to set this value. Further, even if the value is manually set to "On" in db, it gets overwriiten by UI everytime some other property is updated as described here - https://bugzilla.redhat.com/show_bug.cgi?id=1669367 Setting the value to "Off" is not ideal for multipath devices where a single path failure causes vm to pause. It puts serious restrictions for the DR situation and unlike VMWare * Hyper-V, oVirt is not able to support the DR functionality - https://bugzilla.redhat.com/show_bug.cgi?id=1314160 While we wait for RFE, the proposal here is to revise the out of the box behavior for LUNs. For LUNs, we should propagate the errors to VM rather than directly stopping those. This will allow us to handle short-term multipath outages and improve availability. This is a simple change in behavior but will have good positive impact. I would like to seek feedback about this to make sure that everyone is ok with the proposal. Thanks, Shubha

3 11

ovirt-engine 4.4.2 has been branched
by Tal Nisan 13 Aug '20

13 Aug '20

I've now branched oVirt 4.4.2, this will allow us to start working on 4.4.3 bugs/features and also maintain the stability of 4.4.2 before the final build. How does it affect you: If you are working on 4.4.3 content you can now submit your work to master and it will be included in 4.4.3 If you are working on 4.4.2 content you will have to push it to master first and then backport it to the ovirt-engine-4.4.2.z branch

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.2.2)
by Tal Nisan 13 Aug '20

13 Aug '20

3 4

192.168.200.90 unreachable (was: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1696 - Still Failing!)
by Yedidyah Bar David 12 Aug '20

12 Aug '20

On Tue, Aug 4, 2020 at 6:40 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1696/ This is failing for a few days now, all with the same error: > FAILED: 004_basic_sanity.hotplug_disk > > Error Message: > False != True after 180 seconds > -------------------- >> begin captured logging << -------------------- > lago.ssh: DEBUG: start task:cef1ecf3-76fd-4aad-a1fb-093eeda8193a:Get ssh client for lago-he-basic-suite-master-host-1: > lago.ssh: DEBUG: end task:cef1ecf3-76fd-4aad-a1fb-093eeda8193a:Get ssh client for lago-he-basic-suite-master-host-1: > lago.ssh: DEBUG: Running 833afb8a on lago-he-basic-suite-master-host-1: ping -4 -c 1 192.168.200.90 > lago.ssh: DEBUG: Command 833afb8a on lago-he-basic-suite-master-host-1 returned with 1 > lago.ssh: DEBUG: Command 833afb8a on lago-he-basic-suite-master-host-1 output: > PING 192.168.200.90 (192.168.200.90) 56(84) bytes of data. > From 192.168.200.3 icmp_seq=1 Destination Host Unreachable This is after Michal pushed a patch to restore the removed function (and related) get_vm0_ip_address, which failed build 1691. I guess this patch was not enough - either the VM now gets a different IP address, not 192.168.200.90, or its network is down, or whatever. Any idea? Thanks, -- Didi

4 5

Latest RHEL-8.2.1 link is broken
by Eyal Shenitzky 06 Aug '20

06 Aug '20

Hi, The link for latest RHEL 8.2.1 seems to be broke [1], can someone please have a look? [1] http://download.eng.tlv.redhat.com/rhel-8/nightly/RHEL-8/latest-RHEL-8.2.1/… -- Regards, Eyal Shenitzky

1 0