Hi
We have been using LXC, before we went to oVirt 4.0. We started with 3.6, but
production use was 4.0.
The problem we had with LXC was the missing live migration feature and the
biggest issue was the shared storage on NFS.
With all the hundred millions of files on the NFS storage, the perform
Good morning,
I think the location of the client lease file has changed from 16.04 to 18.04
when moving to netplan.
I think, after creating a template, this file should be deleted, otherwise the
client may reuse the old IP...
18.04 and above: /run/systemd/netif/leases/
below: /var/lib/dhcp/
B
Hello Pavel,
we are also using 4.3 and for us, cloud-init is working on 20.04.
We are using the unmodified Ubuntu 20.04 cloud image and cloud-init is adding
ssh keys to root user and is setting IP address.
The rest is then done via ansible on our side.
Br Florian
- Ursprüngliche Mail -
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 t
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
S
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
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
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 package
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
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 |
https://bugzilla.redhat.com/show_bug.cgi?id=184574
Von: "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, 202
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
Von:
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:
[
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BGGFBU24SQAJICU5OR7VOZLBQU
gt; Gesendet: 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
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
&
attachments contained 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
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@o
2020 г. 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-ag
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 t
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:
20 matches
Mail list logo
