- Devel - oVirt List Archives

manipulating VM configuration via Python SDK disables serial console
by Denis Karpov 08 May '19

08 May '19

Hello, I have hit what seems to be a bug in oVIrt Python SDK, when deploying OpenStack 14 (Rocky) in configuration virtualized controllers, oVirt VMs; Ironic oVirt driver is used in this case, which uses oVirt Python SDK to talk to manipulate VMs. The driver seem to work in such a way that at certain stages it retrieves a VM configuration and updates it (e.g. changes the boot device). However during such update some other changes in configuration of the VM happen: e.g. if the VM had VirtIO serial console enabled, after the update that serial console becomes disabled. Perhaps when a VMs config is updated some XML fields of its configuration are not written back as they should be? We have noticed that since the OpenStack deployment fails on controllers if it cannot output to the serial console. I would appreciate any help/workaround for this issue. Thanks, Denis

1 0

Fedora 29 support?
by Nir Soffer 08 May '19

08 May '19

Fedora 28 will be EOL in few month, and at this point people are migration to Fedora 29. I tried yesterday to build engine development setup on Fedora 29 VM, and found that it does not work: - some packages are missing on engine side - after hacking the ovirt.repo files, pointing to "28" instead of "$releasever", I got the packages... - but then adding a host fail with "Python is missing" on the host, which is working Fedora 28 host used with engine before. What are our plans for supporting Fedora 29 on engine and host? I hope that the work we did for Fedora 28 will make it easier to port to Fedora 29. Nir

3 5

OST broken - looks like https://gerrit.ovirt.org/c/99717 is the reason
by Nir Soffer 07 May '19

07 May '19

Investigating unrelated OST failue with: https://gerrit.ovirt.org/c/99293 I found that This patch fail in OST: https://gerrit.ovirt.org/c/99717 Failed build: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4630/ 2019-05-02 15:46:07,258::ssh.py::ssh::96::lago.ssh::DEBUG::Command 650bdf66 on lago-basic-suite-master-host-0 errors: + yum -y install ovirt-host Error: Package: vdsm-common-4.40.0-202.git9757d7c.el7.noarch (alocalsync) Requires: python2-enum34 Dan, can you take a look at this? Nir

4 5

Jenkins is very slow now - can someone restart it?
by Nir Soffer 05 May '19

05 May '19

$ time curl -s https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ >/dev/null real 0m27.380s user 0m0.038s sys 0m0.028s For reference: $ time curl -s https://travis-ci.org/oVirt/vdsm/builds >/dev/null real 0m0.614s user 0m0.027s sys 0m0.015s Can someone restart jenkins?

3 4

ovirt-engine has been tagged (ovirt-engine-4.3.3.7)
by Tal Nisan 05 May '19

05 May '19

2 1

Jenkins restart
by Evgheni Dereveanchin 03 May '19

03 May '19

Hi everyone, We received reports that Jenkins is performing slowly so I'm going to restart it now to to apply some updates. During the outage no new builds will be started. I will announce once it is back up and running. -- Regards, Evgheni Dereveanchin

1 1

Thin provisioning??
by Hetz Ben Hamo 02 May '19

02 May '19

Hi, I've migrated few Linux VM's from virt-manager to oVirt. Other than the famous bug that it insist to have an ISO domain - it worked well. My problem is simple: on virt-manager, I created the virtual disks as thin provisioning. ls -l shows the full size of the QCOW2 file and du -hs shows the actual size. So far, so good. After migrating those VM's to oVirt, the disks appear both in the web UI and in the meta file as "Thin Provisioning" and "sparse" - however, digging into the directory which holds the virtual disk and running du -hs - shows it's a full size disk. Why is this happening? (the storage on the oVirt is NFS)

2 5

Taking over safelease maintainership
by Sandro Bonazzola 02 May '19

02 May '19

Not having former maintainers around and no volunteers to take over maintainership for safelease, I'm taking over its maintainership ad interim. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 1

Fwd: Fedora 30 officially released!
by Sandro Bonazzola 30 Apr '19

30 Apr '19

FYI ---------- Forwarded message --------- Da: Matthew Miller <mattdm(a)fedoraproject.org> Date: mar 30 apr 2019 alle ore 16:02 Subject: Fedora 30 officially released! To: <announce(a)lists.fedoraproject.org> Cc: <devel-announce(a)lists.fedoraproject.org> It's been six months, and like clockwork, we release Fedora 30 today! Thank you to the thousands of people who worked to bring this release together. Fedora doesn't happen by magic: it happens because of you! Read the official announcement at: * https://fedoramagazine.org/announcing-fedora-30/ or just go ahead and grab it from: * https://getfedora.org/ -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Some feedback of an upgrade from 4.2 to 4.3 (EPYC Cluster)
by Tobias Scheinert 30 Apr '19

30 Apr '19

Hi, 1) Thank you all for the official support of the AMD EPYC processors in version 4.3! :-) 2) During the upgrade process I removed the old guest ISO file and replaced it with the new one (different filename of course). As I moved a virtual machine with the old ISO file mounted, the vm crashed. "Migration failed: Lost connection with qemu process (VM: <vmname>, Source: <ovirt-node-host>)." Yes I know this is not real bug (dumb user), but maybe it is good preventing the users for doing something stupid ;-) 3) The log contains following messages after upgrading the node: "VDSM <ovirt-node-host> command Get Host Statistics failed: Internal JSON-RPC error: {'reason': '[Errno 19] genev_sys_6081 is not present in the system'}" This stops after some time ~20-30 minutes, but comes back after a restart of a node. And disappears again after some time. At the moment we have no problems and not taking this as a real issue. 4) If we are running Windows 10 guests newer than build version 1709, the vm crashes on our EPYC cluster, on the SandyBridge cluster the issue doesn't exists. The reason is the wrong CPU model of QEMU, see: <https://bugzilla.redhat.com/show_bug.cgi?id=1593190> We fixed this problem with a line in "/etc/modprobe.d/kvm.conf" "options kvm ignore_msrs=1". Thank you all for this great piece of software :-) Regard Tobias

3 2