[ovirt-users] Re: lxd, openvz in kvm have issues connecting to public phys network

2021-02-11 Thread Florian Schmid via Users
Hi David I don't have oVirt 4.4 yet, but on oVirt 4.3, there is a default filter on the vNic profiles, called vdsm-no-mac-spoofing, which is preventing any MAC, except for the configured VM MAC to be able to connect to outside of the VM. We have also some LXD running inside VMs and you have

[ovirt-users] Re: CentOS 8 is dead

2021-01-23 Thread Florian Schmid via Users
Hi Strahil, thank you very much for the information. Now the question is, will oVirt stay 100 % compatible to RH? As I understood it, is that oVirt will be developed for CentOS Stream and will be tested against it. RH doesn't have the same application versions than CentOS Stream, because

[ovirt-users] Re: CentOS 8 is dead

2020-12-26 Thread Florian Schmid via Users
Hello Simon, would you be so kind and explain me, why OLVM is so far behind RHV or oVirt? It would be also great to know, if you backport fixes from oVirt 4.3.7+ back to OLVM 4.3.6? I have seen, that there are some newer packages on your repo server for 4.3.6, which seem newer than the oVirt

[ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available

2020-12-22 Thread Florian Schmid via Users
Il giorno mar 22 dic 2020 alle ore 13:57 Florian Schmid via Users < [ mailto:users@ovirt.org | users@ovirt.org ] > ha scritto: Hi, I think the big question is: Will ovirt be tested against such EL-based clones. Well, it will be tested for those EL-based clones a few months before the

[ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available

2020-12-22 Thread Florian Schmid via Users
Hi, I think the big question is: Will ovirt be tested against such EL-based clones. Is ovirt then still 100% compatible to EL, when it will be developed for Stream, because Stream will be ahead EL. Next question is, how stable will be CentOS stream? At the moment, ovirt is using a lot a

[ovirt-users] Re: VM with illegal snapshots

2020-11-17 Thread Florian Schmid via Users
Hi, I have also sometimes the issue with snapshots or disk move, which is also related to snapshots, when the engine process is running for a longer time. After restarting the engine service, then it is working again for several weeks, until it gets too long and issues starting again to

[ovirt-users] Re: rhv 4.3.11 but not ovirt 4.3.11

2020-11-12 Thread Florian Schmid via Users
Hi Sandro, will those patches in 4.3.11 also find the way into ovirt 4.4? I had also these troubles when upgrading to 4.3.8 and it would be great not having them, when upgrading to 4.4. [ https://bugzilla.redhat.com/show_bug.cgi?id=1845747 |

[ovirt-users] Re: Removal of dpdk

2020-11-04 Thread Florian Schmid via Users
: "Dominik Holler" An: "Florian Schmid" CC: "Ales Musil" , "users" , "devel" Gesendet: Mittwoch, 4. November 2020 12:15:47 Betreff: Re: [ovirt-users] Re: Removal of dpdk Hi Florian, thanks for your thoughts! On Tue, Nov 3, 2020 at

[ovirt-users] Re: Removal of dpdk

2020-11-03 Thread Florian Schmid via Users
Hi Ales, what do you mean with "not maintained for a long time"? DPDK is heavily developed and make the linux network extremely fast. I don't think, that SR-IOV can replace it, because packets must be still processed by the kernel, which is really slow and CPU demanding. BR Florian

[ovirt-users] Re: Guest agent ubuntu 20.04

2020-08-13 Thread Florian Schmid via Users
Hi Carl, for Ubuntu 20.04, you have to use the qemu-guest-agent alone. OGA was not ported to python 3 and is deprecated in 4.4. You can also have a look here, when you want to have FQDN in your engine: [

[ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN

2020-07-24 Thread Florian Schmid via Users
esendet: Donnerstag, 23. Juli 2020 08:37:21 > Betreff: Re: [ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN > > On Wed, Jul 22, 2020 at 5:34 PM Florian Schmid via Users > wrote: > >> > >> Hi, > >> > >> after digging a bit deeper, i

[ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN

2020-07-23 Thread Florian Schmid via Users
et: Donnerstag, 23. Juli 2020 08:37:21 Betreff: Re: [ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN On Wed, Jul 22, 2020 at 5:34 PM Florian Schmid via Users wrote: >> >> Hi, >> >> after digging a bit deeper, it looks like it is the problem with the &g

[ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN

2020-07-22 Thread Florian Schmid via Users
ntained in this message. Von: "Sandro Bonazzola" An: "Florian Schmid" , "Tomas Golembiovsky" CC: "users" Gesendet: Freitag, 17. Juli 2020 09:21:37 Betreff: Re: [ovirt-users] qemu-guest-agent on Ubuntu doesn't report FQDN Il giorno gio 16 l

[ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN

2020-07-20 Thread Florian Schmid via Users
chmid" , "Tomas Golembiovsky" CC: "users" Gesendet: Freitag, 17. Juli 2020 09:21:37 Betreff: Re: [ovirt-users] qemu-guest-agent on Ubuntu doesn't report FQDN Il giorno gio 16 lug 2020 alle ore 15:55 Florian Schmid via Users < [ mailto:users@ovirt.org | users@ovirt.

[ovirt-users] Re: qemu-guest-agent on Ubuntu doesn't report FQDN

2020-07-16 Thread Florian Schmid via Users
г. 16:53:36 GMT+03:00, Florian Schmid via Users написа: >Hi, > >I have a problem with Ubuntu 20.04 VM reporting the correct FQDN to the >engine. >Starting with this release, the ovirt-guest-agent is not available >anymore. > >Therefore, I have installed qemu-geust-agent w

[ovirt-users] qemu-guest-agent on Ubuntu doesn't report FQDN

2020-07-16 Thread Florian Schmid via Users
Hi, I have a problem with Ubuntu 20.04 VM reporting the correct FQDN to the engine. Starting with this release, the ovirt-guest-agent is not available anymore. Therefore, I have installed qemu-geust-agent with package defaults. Now in the Engine, I only see the hostname under FQDN tab, instead

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

2020-06-12 Thread Florian Schmid via Users
Hi, we are using cloud-init for several years now and it looks like, that cloud-init needs a config for every boot, otherwise, it will use the default network config, which is DHCP. We come around this issue by adding this file: cat /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg network: