Hi,
this is already fixed in oVirt 4.5 [0]. Possible workaround might be to
downgrade the iproute-tc package below version 5.15.0-3.
Regards,
Ales
[0]
https://github.com/oVirt/vdsm/commit/503a98139d65daed856d97a8c6d7f875bcbe42df
On Fri, Mar 25, 2022 at 1:15 PM Christoph Timm wrote:
> Hello
Hi Ales,
thank you so much for the feedback and for the possible workaround.
For the moment I have tweaked the bridge to perform the port mirror.
Best regards
Christoph
Am 28.03.22 um 07:08 schrieb Ales Musil:
Hi,
this is already fixed in oVirt 4.5 [0]. Possible workaround might be
to
Hi Derek,
Many thanks for your email, it has helped me a lot for troubleshooting my
certificates issues on my homelab.
I don't know if you solved the san issue, but I have made it work using
--san=DNS:host.na.me
I found this somewhere although I can't remember where (probably in between
my
On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote:
> That information message is incorrect, both OVAs that are created by
> oVirt/RHV and OVAs that are created by VMware are supported It could
> work for OVAs that are VMware-compatible though
"VMware-compatible" is doing a bit of work
On Sun, Mar 27, 2022 at 9:09 PM Richard W.M. Jones wrote:
>
>
> On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote:
> > That information message is incorrect, both OVAs that are created by
> > oVirt/RHV and OVAs that are created by VMware are supported It could
> > work for OVAs that are
On Wed, Mar 23, 2022 at 3:09 PM wrote:
> We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
> v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page?
https://github.com/brimstone/metasploitable3/releases
If not, can you share the image? It will help if we
On Sun, Mar 27, 2022 at 12:24 PM Nir Soffer wrote:
> On Wed, Mar 23, 2022 at 3:09 PM wrote:
> > We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
> > v.3, FWIW)
>
> Is it Metasploitable3-0.1.4.ova from the github releases page?
>
You can reinstall your node - it will be assigned ryzen-based model for the
cluster.Once you import the storage domains, all VMs should be visible. Then
you can edit each VM, verify NIC, MAC address and change the CPU type of the
VM to the one that is available in the Cluster (respectfully the
8 matches
Mail list logo