random adapter (NIC) resets on oVirt Node 4.4.6
by Tivon Häberlein
Hi,
I've been trying to get oVirt Node 4.4.6 up and running on my Dell r620
hosts but am facing a strange issue where seemingly all network adapters
get reset at random times after install.
The interfaces reset as soon as a bit of traffic is flowing through them.
Also the logs show nfs timeouts.
This only happens after I have installed the host using the oVirt engine
and it also only happens when the host is connected to the engine. When
the host is in maintenance mode it also seems to work fine.
The host and networks work fine when its by itself (I tested right after
install using the ISO and also after I have removed the host from the
cluster)
I cant figure why this is happening. Am I missing something?
I've been stuck on this for the last couple of weeks, a bit of help
would be much appreciated.
Thank you!
My cluster is looking like this:
Engine: oVirt 4.4.6 - CentOS Linux release 8.3.2011
host1: oVirt 4.4 repository on CentOS Linux release 8.4.2105
host2: oVirt 4.4 repository on CentOS Linux release 8.4.2105
host3 (this is the one I'm trying to install): oVirt node 4.4.6
--
Best regards
Tivon Häberlein
3 years, 8 months
Re: oVirt and ARM
by Milan Zamazal
Marko Vrgotic <M.Vrgotic(a)activevideo.com> writes:
> Dear Arik and Milan,
>
> In the meantime, I was asked to check if in current 4.4 version or
> coming 4.5, are/will there any capabilities or options of emulating
> aarch64 on x86_64 platform and if so, what would be the steps to
> test/enable it.
>
> Can you provide some information?
Hi Marko,
I don't think there is a way to emulate a non-native architecture.
Engine doesn't have ARM support and it cannot handle ARM (native or
emulated) hosts. You could try to run emulated ARM VMs presented as x86
to Engine using Vdsm hooks but I doubt it would work.
I'm afraid the only way is to add ARM support to oVirt. My former
colleague has played with running oVirt on Raspberry Pi hosts some years
ago (there are traces of that effort in Vdsm) and I think adding ARM
support should be, at least in theory, possible. Particular features
available would be mostly dependent on ARM support in QEMU and libvirt.
Regards,
Milan
> -----
> kind regards/met vriendelijke groeten
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
> ActiveVideo
> o: +31 (35) 6774131
> m: +31 (65) 5734174
> e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com>
> w: www.activevideo.com<http://www.activevideo.com>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein
> 1.1217 WJ Hilversum, The Netherlands. The information contained in
> this message may be legally privileged and confidential. It is
> intended to be read only by the individual or entity to whom it is
> addressed or by their designee. If the reader of this message is not
> the intended recipient, you are on notice that any distribution of
> this message, in any form, is strictly prohibited. If you have
> received this message in error, please immediately notify the sender
> and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> delete or destroy any copy of this message.
>
>
>
> From: Sandro Bonazzola <sbonazzo(a)redhat.com>
> Date: Friday, 9 July 2021 at 15:37
> To: Marko Vrgotic <M.Vrgotic(a)activevideo.com>, Arik Hadas
> <ahadas(a)redhat.com>, Milan Zamazal <mzamazal(a)redhat.com>
> Cc: Evgheni Dereveanchin <ederevea(a)redhat.com>, Zhenyu Zheng
> <zhengzhenyulixi(a)gmail.com>, Joey Ma <majunjiev(a)gmail.com>,
> users(a)ovirt.org <users(a)ovirt.org>
> Subject: Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you recognize the
> sender!!!***
>
>
> Il giorno ven 9 lug 2021 alle ore 11:00 Marko Vrgotic
> <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> ha
> scritto:
> Hi Sandro and the rest of oVirt gurus,
>
> My managers are positive regarding helping provide some ARM hardware,
> but it would not happened earlier than three months from now, as we
> are in process of establishing certain relationship with ARM HW
> vendor.
>
> T news!
>
>
> In the meantime, I was asked to check if in current 4.4 version or
> coming 4.5, are/will there any capabilities or options of emulating
> aarch64 on x86_64 platform and if so, what would be the steps to
> test/enable it.
>
> +Arik Hadas<mailto:ahadas@redhat.com> , +Milan Zamazal<mailto:mzamazal@redhat.com> ?
>
>
> Kindly awaiting your reply.
>
> Marko Vrgotic
>
> From: Marko Vrgotic <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>
> Date: Monday, 28 June 2021 at 15:38
> To: Sandro Bonazzola
> <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>>, Evgheni
> Dereveanchin <ederevea(a)redhat.com<mailto:ederevea@redhat.com>>
> Cc: Zhenyu Zheng
> <zhengzhenyulixi(a)gmail.com<mailto:zhengzhenyulixi@gmail.com>>, Joey Ma
> <majunjiev(a)gmail.com<mailto:majunjiev@gmail.com>>,
> users(a)ovirt.org<mailto:users@ovirt.org>
> <users(a)ovirt.org<mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] oVirt and ARM
> Hi Sandro,
>
> I will check with my managers if we have and could spare some hardware
> to contribute developing for oVirt.
>
>
> -----
> kind regards/met vriendelijke groeten
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
> ActiveVideo
> o: +31 (35) 6774131
> m: +31 (65) 5734174
> e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com>
> w: www.activevideo.com<http://www.activevideo.com>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein
> 1.1217 WJ Hilversum, The Netherlands. The information contained in
> this message may be legally privileged and confidential. It is
> intended to be read only by the individual or entity to whom it is
> addressed or by their designee. If the reader of this message is not
> the intended recipient, you are on notice that any distribution of
> this message, in any form, is strictly prohibited. If you have
> received this message in error, please immediately notify the sender
> and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> delete or destroy any copy of this message.
>
>
>
> From: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>>
> Date: Friday, 25 June 2021 at 15:26
> To: Marko Vrgotic
> <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, Evgheni
> Dereveanchin <ederevea(a)redhat.com<mailto:ederevea@redhat.com>>
> Cc: Zhenyu Zheng
> <zhengzhenyulixi(a)gmail.com<mailto:zhengzhenyulixi@gmail.com>>, Joey Ma
> <majunjiev(a)gmail.com<mailto:majunjiev@gmail.com>>,
> users(a)ovirt.org<mailto:users@ovirt.org>
> <users(a)ovirt.org<mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you recognize the
> sender!!!***
>
>
> Il giorno ven 25 giu 2021 alle ore 14:20 Marko Vrgotic
> <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> ha
> scritto:
> Hi Sandro,
>
> Thank you for the update. I am not equipped to help on development
> side, but I can most certainly do test deployments, once there is
> something available.
>
> We are big oVirt shop and moving to ARM64 with new product, it would
> be great if oVirt would start supporting it.
>
> If we are able to help somehow, let me know.
>
> I guess a start could be adding some arm64 machine to oVirt
> infrastructure so developers can build for it.
> You can have a look at
> https://ovirt.org/community/get-involved/donate-hardware.html<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.o...>
> Looping in +Evgheni Dereveanchin<mailto:ederevea@redhat.com> in case you can share some resources.
>
>
>
>
> -----
> kind regards/met vriendelijke groeten
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
> ActiveVideo
> e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com>
> w: www.activevideo.com<http://www.activevideo.com>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein
> 1.1217 WJ Hilversum, The Netherlands. The information contained in
> this message may be legally privileged and confidential. It is
> intended to be read only by the individual or entity to whom it is
> addressed or by their designee. If the reader of this message is not
> the intended recipient, you are on notice that any distribution of
> this message, in any form, is strictly prohibited. If you have
> received this message in error, please immediately notify the sender
> and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> delete or destroy any copy of this message.
>
>
>
> From: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>>
> Date: Thursday, 24 June 2021 at 18:21
> To: Marko Vrgotic
> <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, Zhenyu
> Zheng <zhengzhenyulixi(a)gmail.com<mailto:zhengzhenyulixi@gmail.com>>,
> Joey Ma <majunjiev(a)gmail.com<mailto:majunjiev@gmail.com>>
> Cc: users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you recognize the
> sender!!!***
>
>
> Il giorno gio 24 giu 2021 alle ore 16:34 Marko Vrgotic
> <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> ha
> scritto:
> Hi oVirt,
>
> Where can I find if there are any information about oVirt supporting arm64 CPU architecture?
>
> Right now oVirt is not supporting arm64. There was an initiative about
> supporting it started some time ago from openEuler ovirt SIG.
> I didn't got any further updates on this topic, looping in those who I remember being looking into it.
> I think that if someone contributes arm64 support it would also be a feature worth a 4.5 release :-)
>
>
> -----
> kind regards/met vriendelijke groeten
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
> ActiveVideo
> o: +31 (35) 6774131
> m: +31 (65) 5734174
> e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com>
> w: www.activevideo.com<http://www.activevideo.com>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein
> 1.1217 WJ Hilversum, The Netherlands. The information contained in
> this message may be legally privileged and confidential. It is
> intended to be read only by the individual or entity to whom it is
> addressed or by their designee. If the reader of this message is not
> the intended recipient, you are on notice that any distribution of
> this message, in any form, is strictly prohibited. If you have
> received this message in error, please immediately notify the sender
> and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> delete or destroy any copy of this message.
>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org>
> Privacy Statement:
> https://www.ovirt.org/privacy-policy.html<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MQ3XND2NKIL...<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat
> EMEA<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>
> Error! Filename not
> specified.<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
> Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat
> EMEA<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>
> Error! Filename not
> specified.<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
> Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>
> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmojo.re...>
3 years, 8 months
Automatic Shutdown / Startup for Hosted-Engine
by Eugène Ngontang
Hi,
I understood we have to put hosted-engine into maintenance mode and
shutdown the VMs if we want to power off the host (otherwise it will
reboot). I'm setting up a process to
- put the HestedEngine in global maintenance mode (*hosted-engine
--set-maintenance --mode=global*)
- shutdown the HostedEngine (*hosted-engine --vm-shutdown*)
- PowerOff the HostedEngine (*hosted-engine --vm-poweroff*)
- Power off the server (*shutdown -P*)
Everything works fine and I can start the server back up, remove the
HostedEngine from maintenance mode, and it will start automatically
running. The issue is when bringing up hosted-engine: all VMs come up but
one (*BigIP*) and I am trying to see if there is way to bring it up without
having to store the engine password (using the *ovirt_vm* API).
At the moment, I am having to look for the BigIP VM and then use
credentials to bring it up: it will not come up with 'hosted-engine
--vm-start'
Is there to make this specific VM start the same time as the others VM
automatically when HostedEngine starts?
Thanks for your help.
Regards,
Eugène NG
--
LesCDN <http://lescdn.com>
engontang(a)lescdn.com
------------------------------------------------------------
*Aux hommes il faut un chef, et au*
* chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te
voit on te juge!*
3 years, 8 months
[ANN] Async oVirt Node release for oVirt 4.4.7.1
by Lev Veyde
On July 14th 2021 the oVirt project released an async update of oVirt Node
(4.4.7.1)
Changes:
-
Updated ovirt-hosted-engine-setup-2.5.2
-
Updated imgbased to 1.2.23 (Fixes BZ#1979624
<https://bugzilla.redhat.com/show_bug.cgi?id=1979624>)
-
Uses 5.2.0 Qemu packages (Fixes BZ#1981005
<https://bugzilla.redhat.com/show_bug.cgi?id=1981005>)
ovirt-node-4.4.7
ovirt-node-4.4.7.1
NetworkManager 1.32.0-1.el8
1.32.2-1.el8
NetworkManager-config-server 1.32.0-1.el8
1.32.2-1.el8
NetworkManager-libnm 1.32.0-1.el8
1.32.2-1.el8
NetworkManager-ovs 1.32.0-1.el8
1.32.2-1.el8
NetworkManager-team 1.32.0-1.el8
1.32.2-1.el8
NetworkManager-tui 1.32.0-1.el8
1.32.2-1.el8
autofs 5.1.4-71.el8
5.1.4-74.el8
glib2 2.56.4-13.el8
2.56.4-14.el8
glibc 2.28-160.el8
2.28-161.el8
glibc-common 2.28-160.el8
2.28-161.el8
glibc-langpack-en 2.28-160.el8
2.28-161.el8
imgbased 1.2.21-1.el8
1.2.23-1.el8
kexec-tools 2.0.20-52.el8
2.0.20-53.el8
libblockdev 2.24-6.el8
2.24-7.el8
libblockdev-crypto 2.24-6.el8
2.24-7.el8
libblockdev-dm 2.24-6.el8
2.24-7.el8
libblockdev-fs 2.24-6.el8
2.24-7.el8
libblockdev-kbd 2.24-6.el8
2.24-7.el8
libblockdev-loop 2.24-6.el8
2.24-7.el8
libblockdev-lvm 2.24-6.el8
2.24-7.el8
libblockdev-mdraid 2.24-6.el8
2.24-7.el8
libblockdev-mpath 2.24-6.el8
2.24-7.el8
libblockdev-nvdimm 2.24-6.el8
2.24-7.el8
libblockdev-part 2.24-6.el8
2.24-7.el8
libblockdev-plugins-all 2.24-6.el8
2.24-7.el8
libblockdev-swap 2.24-6.el8
2.24-7.el8
libblockdev-utils 2.24-6.el8
2.24-7.el8
libblockdev-vdo 2.24-6.el8
2.24-7.el8
libepoxy 1.5.3-1.el8
1.5.8-1.el8
libipa_hbac 2.5.1-1.el8
2.5.1-2.el8
libjpeg-turbo 1.5.3-10.el8
1.5.3-11.el8
librados2 16.2.4-1.el8s
16.2.5-1.el8s
librbd1 16.2.4-1.el8s
16.2.5-1.el8s
librepo 1.14.0-1.el8
1.14.0-2.el8
libsss_autofs 2.5.1-1.el8
2.5.1-2.el8
libsss_certmap 2.5.1-1.el8
2.5.1-2.el8
libsss_idmap 2.5.1-1.el8
2.5.1-2.el8
libsss_nss_idmap 2.5.1-1.el8
2.5.1-2.el8
libsss_simpleifp 2.5.1-1.el8
2.5.1-2.el8
libsss_sudo 2.5.1-1.el8
2.5.1-2.el8
llvm-compat-libs
11.0.1-1.module_el8.5.0+840+21214faf
llvm-libs
12.0.0-1.module_el8.5.0+840+21214faf
mesa-dri-drivers 21.1.3-1.el8
21.1.3-1.el8.0.1
mesa-filesystem 21.1.3-1.el8
21.1.3-1.el8.0.1
mesa-libEGL 21.1.3-1.el8
21.1.3-1.el8.0.1
mesa-libGL 21.1.3-1.el8
21.1.3-1.el8.0.1
mesa-libgbm 21.1.3-1.el8
21.1.3-1.el8.0.1
mesa-libglapi 21.1.3-1.el8
21.1.3-1.el8.0.1
nettle 3.4.1-4.el8_3
3.4.1-5.el8
nmstate 1.1.0-0.5.alpha4.el8
1.1.0-0.6.alpha6.el8
nmstate-plugin-ovsdb 1.1.0-0.5.alpha4.el8
1.1.0-0.6.alpha6.el8
nss 3.67.0-2.el8_4
3.67.0-4.el8_4
nss-softokn 3.67.0-2.el8_4
3.67.0-4.el8_4
nss-softokn-freebl 3.67.0-2.el8_4
3.67.0-4.el8_4
nss-sysinit 3.67.0-2.el8_4
3.67.0-4.el8_4
nss-tools 3.67.0-2.el8_4
3.67.0-4.el8_4
nss-util 3.67.0-2.el8_4
3.67.0-4.el8_4
ovirt-hosted-engine-setup 2.5.1-1.el8
2.5.2-1.el8
ovirt-node-ng-image-update-placeholder 4.4.7-1.el8
4.4.7.1-1.el8
ovirt-openvswitch 2.11-0.2021060703.el8
2.11-1.el8
ovirt-openvswitch-ovn 2.11-0.2021060703.el8
2.11-1.el8
ovirt-openvswitch-ovn-common 2.11-0.2021060703.el8
2.11-1.el8
ovirt-openvswitch-ovn-host 2.11-0.2021060703.el8
2.11-1.el8
ovirt-python-openvswitch 2.11-0.2021060703.el8
2.11-1.el8
ovirt-release-host-node 4.4.7-1.el8
4.4.7.1-1.el8
ovirt-release44 4.4.7-1.el8
4.4.7.1-1.el8
pacemaker-cluster-libs 2.1.0-2.el8
2.1.0-3.el8
pacemaker-libs 2.1.0-2.el8
2.1.0-3.el8
pacemaker-schemas 2.1.0-2.el8
2.1.0-3.el8
python3-blockdev 2.24-6.el8
2.24-7.el8
python3-imgbased 1.2.21-1.el8
1.2.23-1.el8
python3-libipa_hbac 2.5.1-1.el8
2.5.1-2.el8
python3-libnmstate 1.1.0-0.5.alpha4.el8
1.1.0-0.6.alpha6.el8
python3-sss 2.5.1-1.el8
2.5.1-2.el8
python3-sss-murmur 2.5.1-1.el8
2.5.1-2.el8
python3-sssdconfig 2.5.1-1.el8
2.5.1-2.el8
qemu-guest-agent 6.0.0-19.el8s
5.2.0-16.el8s
qemu-img 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-block-curl 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-block-gluster 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-block-iscsi 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-block-rbd 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-block-ssh 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-common 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-core 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-ui-opengl 6.0.0-19.el8s
5.2.0-16.el8s
qemu-kvm-ui-spice 6.0.0-19.el8s
5.2.0-16.el8s
selinux-policy 3.14.3-71.el8
3.14.3-72.el8
selinux-policy-targeted 3.14.3-71.el8
3.14.3-72.el8
sssd-client 2.5.1-1.el8
2.5.1-2.el8
sssd-common 2.5.1-1.el8
2.5.1-2.el8
sssd-common-pac 2.5.1-1.el8
2.5.1-2.el8
sssd-dbus 2.5.1-1.el8
2.5.1-2.el8
sssd-ipa 2.5.1-1.el8
2.5.1-2.el8
sssd-kcm 2.5.1-1.el8
2.5.1-2.el8
sssd-krb5-common 2.5.1-1.el8
2.5.1-2.el8
sssd-tools 2.5.1-1.el8
2.5.1-2.el8
--
Lev Veyde
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com>
lev(a)redhat.com | lveyde(a)redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
3 years, 8 months
Re: oVirt and ARM
by Arik Hadas
On Tue, Jul 13, 2021 at 10:45 PM Marko Vrgotic <M.Vrgotic(a)activevideo.com>
wrote:
> Dear Arik and Milan,
>
>
>
> In the meantime, I was asked to check if in current 4.4 version or coming
> 4.5, are/will there any capabilities or options of emulating aarch64 on
> x86_64 platform and if so, what would be the steps to test/enable it.
>
>
>
> Can you provide some information?
>
oVirt doesn't support fully emulated workloads out of the box.
The architecture of the guest is determined by that of the cluster [1] and
the latter is either set automatically based on the hosts in the cluster or
set explicitly by the user in which case we enforce the hosts to comply
with that setting.
It could be nice to see it picked up by someone in the community if fully
emulated workloads are desired.
We don't have anything about this in our backlog at this point.
In the meantime, the easiest way to have fully emulated AArch64 workloads
would probably be by using a VDSM hook that modifies the VM configuration
before it starts (e.g., changing the 'emulator' to
/usr/bin/qemu-system-aarch64, changing the 'os' tag, etc). See [2] for how
it was suggested to emulate ARM.
[1]
https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.4.8/backend/man...
[2]
https://fedoraproject.org/wiki/Architectures/ARM/HowToQemu#Installing_the...
>
>
> -----
>
> kind regards/met vriendelijke groeten
>
>
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
>
> ActiveVideo
>
> *o: *+31 (35) 6774131
>
> *m: +*31 (65) 5734174
>
> *e:* m.vrgotic(a)activevideo.com
> *w: *www.activevideo.com
>
>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217
> WJ Hilversum, The Netherlands. The information contained in this message
> may be legally privileged and confidential. It is intended to be read only
> by the individual or entity to whom it is addressed or by their designee.
> If the reader of this message is not the intended recipient, you are on
> notice that any distribution of this message, in any form, is strictly
> prohibited. If you have received this message in error, please immediately
> notify the sender and/or ActiveVideo Networks, LLC by telephone at +1
> 408.931.9200 and delete or destroy any copy of this message.
>
>
>
>
>
>
>
> *From: *Sandro Bonazzola <sbonazzo(a)redhat.com>
> *Date: *Friday, 9 July 2021 at 15:37
> *To: *Marko Vrgotic <M.Vrgotic(a)activevideo.com>, Arik Hadas <
> ahadas(a)redhat.com>, Milan Zamazal <mzamazal(a)redhat.com>
> *Cc: *Evgheni Dereveanchin <ederevea(a)redhat.com>, Zhenyu Zheng <
> zhengzhenyulixi(a)gmail.com>, Joey Ma <majunjiev(a)gmail.com>, users(a)ovirt.org
> <users(a)ovirt.org>
> *Subject: *Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender!!!***
>
>
>
>
>
> Il giorno ven 9 lug 2021 alle ore 11:00 Marko Vrgotic <
> M.Vrgotic(a)activevideo.com> ha scritto:
>
> Hi Sandro and the rest of oVirt gurus,
>
>
>
> My managers are positive regarding helping provide some ARM hardware, but
> it would not happened earlier than three months from now, as we are in
> process of establishing certain relationship with ARM HW vendor.
>
>
>
> T news!
>
>
>
>
>
> In the meantime, I was asked to check if in current 4.4 version or coming
> 4.5, are/will there any capabilities or options of emulating aarch64 on
> x86_64 platform and if so, what would be the steps to test/enable it.
>
>
>
> +Arik Hadas <ahadas(a)redhat.com> , +Milan Zamazal <mzamazal(a)redhat.com> ?
>
>
>
>
>
> Kindly awaiting your reply.
>
>
>
> Marko Vrgotic
>
>
>
> *From: *Marko Vrgotic <M.Vrgotic(a)activevideo.com>
> *Date: *Monday, 28 June 2021 at 15:38
> *To: *Sandro Bonazzola <sbonazzo(a)redhat.com>, Evgheni Dereveanchin <
> ederevea(a)redhat.com>
> *Cc: *Zhenyu Zheng <zhengzhenyulixi(a)gmail.com>, Joey Ma <
> majunjiev(a)gmail.com>, users(a)ovirt.org <users(a)ovirt.org>
> *Subject: *Re: [ovirt-users] oVirt and ARM
>
> Hi Sandro,
>
>
>
> I will check with my managers if we have and could spare some hardware to
> contribute developing for oVirt.
>
>
>
>
>
> -----
>
> kind regards/met vriendelijke groeten
>
>
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
>
> ActiveVideo
>
> *o: *+31 (35) 6774131
>
> *m: +*31 (65) 5734174
>
> *e:* m.vrgotic(a)activevideo.com
> *w: *www.activevideo.com
>
>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217
> WJ Hilversum, The Netherlands. The information contained in this message
> may be legally privileged and confidential. It is intended to be read only
> by the individual or entity to whom it is addressed or by their designee.
> If the reader of this message is not the intended recipient, you are on
> notice that any distribution of this message, in any form, is strictly
> prohibited. If you have received this message in error, please immediately
> notify the sender and/or ActiveVideo Networks, LLC by telephone at +1
> 408.931.9200 and delete or destroy any copy of this message.
>
>
>
>
>
>
>
> *From: *Sandro Bonazzola <sbonazzo(a)redhat.com>
> *Date: *Friday, 25 June 2021 at 15:26
> *To: *Marko Vrgotic <M.Vrgotic(a)activevideo.com>, Evgheni Dereveanchin <
> ederevea(a)redhat.com>
> *Cc: *Zhenyu Zheng <zhengzhenyulixi(a)gmail.com>, Joey Ma <
> majunjiev(a)gmail.com>, users(a)ovirt.org <users(a)ovirt.org>
> *Subject: *Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender!!!***
>
>
>
>
>
> Il giorno ven 25 giu 2021 alle ore 14:20 Marko Vrgotic <
> M.Vrgotic(a)activevideo.com> ha scritto:
>
> Hi Sandro,
>
>
>
> Thank you for the update. I am not equipped to help on development side,
> but I can most certainly do test deployments, once there is something
> available.
>
>
>
> We are big oVirt shop and moving to ARM64 with new product, it would be
> great if oVirt would start supporting it.
>
>
>
> If we are able to help somehow, let me know.
>
>
>
> I guess a start could be adding some arm64 machine to oVirt infrastructure
> so developers can build for it.
>
> You can have a look at
> https://ovirt.org/community/get-involved/donate-hardware.html
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.o...>
>
>
> Looping in +Evgheni Dereveanchin <ederevea(a)redhat.com> in case you can
> share some resources.
>
>
>
>
>
>
>
>
>
> -----
>
> kind regards/met vriendelijke groeten
>
>
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
>
> ActiveVideo
>
> *e:* m.vrgotic(a)activevideo.com
> *w: *www.activevideo.com
>
>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217
> WJ Hilversum, The Netherlands. The information contained in this message
> may be legally privileged and confidential. It is intended to be read only
> by the individual or entity to whom it is addressed or by their designee.
> If the reader of this message is not the intended recipient, you are on
> notice that any distribution of this message, in any form, is strictly
> prohibited. If you have received this message in error, please immediately
> notify the sender and/or ActiveVideo Networks, LLC by telephone at +1
> 408.931.9200 and delete or destroy any copy of this message.
>
>
>
>
>
>
>
> *From: *Sandro Bonazzola <sbonazzo(a)redhat.com>
> *Date: *Thursday, 24 June 2021 at 18:21
> *To: *Marko Vrgotic <M.Vrgotic(a)activevideo.com>, Zhenyu Zheng <
> zhengzhenyulixi(a)gmail.com>, Joey Ma <majunjiev(a)gmail.com>
> *Cc: *users(a)ovirt.org <users(a)ovirt.org>
> *Subject: *Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender!!!***
>
>
>
>
>
> Il giorno gio 24 giu 2021 alle ore 16:34 Marko Vrgotic <
> M.Vrgotic(a)activevideo.com> ha scritto:
>
> Hi oVirt,
>
>
>
> Where can I find if there are any information about oVirt supporting arm64
> CPU architecture?
>
>
>
> Right now oVirt is not supporting arm64. There was an initiative about
> supporting it started some time ago from openEuler ovirt SIG.
>
> I didn't got any further updates on this topic, looping in those who I
> remember being looking into it.
>
> I think that if someone contributes arm64 support it would also be a
> feature worth a 4.5 release :-)
>
>
>
>
>
> -----
>
> kind regards/met vriendelijke groeten
>
>
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
>
> ActiveVideo
>
> *o: *+31 (35) 6774131
>
> *m: +*31 (65) 5734174
>
> *e:* m.vrgotic(a)activevideo.com
> *w: *www.activevideo.com
>
>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217
> WJ Hilversum, The Netherlands. The information contained in this message
> may be legally privileged and confidential. It is intended to be read only
> by the individual or entity to whom it is addressed or by their designee.
> If the reader of this message is not the intended recipient, you are on
> notice that any distribution of this message, in any form, is strictly
> prohibited. If you have received this message in error, please immediately
> notify the sender and/or ActiveVideo Networks, LLC by telephone at +1
> 408.931.9200 and delete or destroy any copy of this message.
>
>
>
>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MQ3XND2NKIL...
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>
>
>
>
> --
>
> *Sandro Bonazzola*
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> sbonazzo(a)redhat.com
>
> *Error! Filename not specified.*
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>
>
>
>
> --
>
> *Sandro Bonazzola*
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> sbonazzo(a)redhat.com
>
> *Error! Filename not specified.*
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>
>
>
>
> --
>
> *Sandro Bonazzola*
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
> sbonazzo(a)redhat.com
>
>
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.red...>
>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmojo.re...>*
>
>
>
3 years, 8 months
How to remove "VM is being cloned" flag in a failed clone VM operation
by Richard Chan
Hello list,
I had an unsuccessful zombie clone VM task -
1. Target: was able to unlock the disks and delete the target VM
2. Source: able to unlock the disks.
Now I cannot do anything with the source as it is flagged as "VM is being
clone".
Is there a way to remove this flag manually?
vdms-client Host -> this does not show any tasks outstanding.
Thank you.
Richard Chan
3 years, 8 months
upgrading to 4.4.6 with Rocky Linux 8
by Jason Keltz
Hi..
I'm looking to migrate soon from CentOS 7.9 with oVirt 4.3.10 to Rocky
Linux 8.4 with oVirt 4.4.6. I'm working on my kickstart of my
standalone engine in a VM at the moment.
So far, with minimal experience with Rocky Linux, after my kickstart, I
was able to run "engine-setup", follow all the defaults and then access
my "new" engine via web. I have to explore the actual procedure for
installing on my current engine host, and restoring my data.
When oVirt team releases new releases, I'm just wondering if you test
going from the last previous release (4.3.10 in this case) to each
latest release? I know that the documentation says we always need to
make sure we update to each individaul major release, but I'm just
wondering if this is something that oVirt team tests with each release?
I'm very concerned for potential of failed upgrade, and the potential
headaches that it could cause.
I see the 4.4.6 was released in time with RHEL 8.3. I'd like to use
Rocky Linux 8.4 because I believe RHEL has re-enabled mptsas (though I
know still unsupported) from 8.4+ which will make things easier.
Any additional suggestions or caveats of the upgrade?
Thanks for any feedback,
Jason.
3 years, 8 months
