QEMU error qemuDomainAgentAvailable in /var/log/messages
by souvaliotimaria＠mail.com
Hello everyone and a happy new year!
I have a question which might be silly but I am stumped. I keep getting the following error in my /var/log/messages
Jan 5 12:20:30 ovno3 libvirtd: 2021-01-05 10:20:30.481+0000: 5283: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected
This entry appears on the arbitrary node only and it has a recurrence of 5 minutes.
I have GlusterFS on the ovirt environment (production environment) and it's serving several vital services. The VMs are running ok and I haven't noticed any discrepancy. Almost a week ago there was a disconnection on the gluster storage but since then everything works as expected.
Does anyone know what this error is and if there is a guide or something to fix it? I have no idea what to search and where.
Thank you all very much for your time!
3 years, 10 months
how to build oVirt engine on eclipse?
by Henry lol
hello,
I've just only imported existing maven projects from engine's git, but
there were so many errors and failed to build.
Should I do some configurations before importing?
3 years, 10 months
Re: VMs shut down after backup: "moved from 'Up' --> 'Down'" only on RHEL hosts
by Nir Soffer
On Thu, Jan 7, 2021, 16:48 Łukasz Kołaciński <l.kolacinski(a)storware.eu>
wrote:
...
> *2020-12-08 10:18:35,451+01 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-31) [] VM
> '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'*
> *2020-12-08 10:18:35,466+01 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is
> down with error. Exit message: Lost connection with qemu process.*
>
Looks like qemu crashed when stopping the backup.
Can you file a bug for this, and attach logs?
We these logs from host the vm was running on:
- /var/log/vdsm/vdsm.log (the right log showing the time backup was stopped)
- /var/log/ovirt-imageio/daemon.log
- /var/log/libvirt/libvird.log (may be missing)
- /var/log/libvirt/qemu/<vm-name>.log
Also the vm xml (virsh -r dumpxml vm-name).
...
> The environment of faulty host is:
> OS Version: RHEL - 8.3 - 1.0.el8
> OS Description: Red Hat Enterprise Linux 8.3 (Ootpa)
> Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64
> KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69
> LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5
>
I never had any issue with these version:
# rpm -q libvirt-daemon qemu-kvm
libvirt-daemon-6.6.0-8.module+el8.3.1+8648+130818f2.x86_64
qemu-kvm-5.1.0-13.module+el8.3.0+8424+e82f331d.x86_64
Looks like you run older libvirt version, but have newer qemu version.
Where did you got these packages?
Are you running on RHEL or Centos?
Nir
3 years, 10 months
VMs shut down after backup: "moved from 'Up' --> 'Down'" only on RHEL hosts
by Łukasz Kołaciński
Hello,
I still haven't solved the problem with vms turning off.
The original message:
We have RHV manager with several different hosts. After the backup, vm placed on RHEL shuts down. In engine.log I found where this happen: "VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'". I attached whole logs to email. It doesn't matter if it's a full or incremental, results are always the same. RHVH hosts works properly.
Log fragment:
2020-12-08 10:18:33,845+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-76) [60da31e3-92f6-4555-8c43-2f8afee272e0] Updating image transfer 87bdb42e-e64c-460d-97ac-218e923336a1 (image e57e4af0-5d0b-4f60-9e6c-e217c666e5e6) phase to Finalizing Success
2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Running command: StopVmBackupCommand internal: false. Entities affected : ID: 35183baa-1c70-4016-b7cd-528889876f19 Type: VMAction group BACKUP_DISK with role type ADMIN, ID: e57e4af0-5d0b-4f60-9e6c-e217c666e5e6 Type: DiskAction group BACKUP_DISK with role type ADMIN
2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Stopping VmBackup 'aae03819-cea6-45a1-9ee5-0f831af8464d'
2020-12-08 10:18:33,952+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] START, StopVmBackupVDSCommand(HostName = rhv-2, VmBackupVDSParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', backupId='aae03819-cea6-45a1-9ee5-0f831af8464d'}), log id: 78b2c27a
2020-12-08 10:18:33,958+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] FINISH, StopVmBackupVDSCommand, return: , log id: 78b2c27a
2020-12-08 10:18:33,975+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] EVENT_ID: VM_BACKUP_FINALIZED(10,794), Backup <UNKNOWN> for VM stor2rrd finalized (User: admin@internal-authz).
2020-12-08 10:18:35,221+01 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-73) [] User admin@internal successfully logged out
2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-81) [1b35276c] Running command: TerminateSessionsForTokenCommand internal: true.
2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.SessionDataContainer] (default task-81) [1b35276c] Not removing session '90TxdK0PBueLijy+sCrFoHC/KNUGNzNpZuYMK/yKDAkbAefFr+8wOJsATsDKv18LxpyxCl+eX7hTHNxN23anAw==', session has running commands for user 'admin@internal-authz'.
2020-12-08 10:18:35,447+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19' was reported as Down on VDS 'afad6b8b-78a6-4e9a-a9bd-783ad42a2d47'(rhv-2)
2020-12-08 10:18:35,448+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] START, DestroyVDSCommand(HostName = rhv-2, DestroyVmVDSCommandParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', vmId='35183baa-1c70-4016-b7cd-528889876f19', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 4f473135
2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] FINISH, DestroyVDSCommand, return: , log id: 4f473135
2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'
2020-12-08 10:18:35,466+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is down with error. Exit message: Lost connection with qemu process.
2020-12-08 10:18:35,484+01 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-34085) [3da40159] Running command: ProcessDownVmCommand internal: true.
The environment of faulty host is:
OS Version: RHEL - 8.3 - 1.0.el8
OS Description: Red Hat Enterprise Linux 8.3 (Ootpa)
Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64
KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69
LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5
VDSM Version: vdsm-4.40.26.3-1.el8ev
SPICE Version: 0.14.3 - 3.el8
GlusterFS Version: [N/A]
CEPH Version: librbd1-12.2.7-9.el8
Open vSwitch Version: openvswitch-2.11-7.el8ev
Nmstate Version: nmstate-0.3.4-13.el8_3
Regards,
Łukasz Kołaciński
Junior Java Developer
e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu>
<mailto:m.helbert@storware.eu>
[STORWARE]<http://www.storware.eu/>
ul. Leszno 8/44
01-192 Warszawa
www.storware.eu <https://www.storware.eu/>
[facebook]<https://www.facebook.com/storware>
[twitter]<https://twitter.com/storware>
[linkedin]<https://www.linkedin.com/company/storware>
[Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw>
Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.
3 years, 10 months
Spliting login pages
by ozmen62＠hotmail.com
Hi,
We want to split admin, user and grafana login pages.
As you know all in main page.
So, this might get users attention and they may try to login and get their accounts locked or worse :)
Thanks
3 years, 10 months
OVirt 4.4.4 repository dependencies
by lars.stolpe＠bvg.de
Hi,
in OVirt 4.3 and earlier i had to activate many repositorys beside OVirt4.3 repo because of dependencies.
centos-sclo-rh-release
ovirt-4.3
ovirt-4.3-centos-gluster5
ovirt-4.3-centos-opstools
ovirt-4.3-centos-ovirt43
ovirt-4.3-centos-qemu-ev
ovirt-4.3-epel
ovirt-4.3-virtio-win-latest
in OVirt 4.4.4 documentation it is mentioned to enable only this 3 repos
sudo subscription-manager repos --enable="rhel-8-for-x86_64-baseos-rpms"
sudo subscription-manager repos --enable="rhel-8-for-x86_64-appstream-rpms"
sudo subscription-manager repos --enable="ansible-2-for-rhel-8-x86_64-rpms"
ovirt-release44.rpm installs ovirt-4.4 repo
I don't want to run into any trouble when i start upgrading, so are that really all repos i need for OVirt 4.4.4?
3 years, 10 months
Re: Can NFV (Network Functions Virtualization) work on oVirt?
by Dominik Holler
On Tue, Jan 5, 2021 at 9:34 AM fukumoto.shinya(a)fujitsu.com <
fukumoto.shinya(a)fujitsu.com> wrote:
> Hello Gianluca,
>
>
>
> Thank you for the links.
>
> I read the documents and understood SR-IOV is supported.
>
>
>
> This is a question apart from NFV, I need RDMA (InfiniBand) and RDMA
> (Ethernet) using Mellanox ConnextX-6 cards.
>
> Do you (or does anyone) know if RDMA (InfiniBand) and RDMA (Ethernet) work
> on oVirt environment?
>
>
>
Should RDMA be used inside the VM, or on the oVirt host directly?
On host level only IPoIB should work on CentOS 7 and on CentOS >= 8.4, RDMA
is not supported.
But it would be interesting to know if RDMA would work on a SR-IOV VF
inside a VM.
> I found following MLNX_OFED documentation and it seems that RDMA will work
> with SR-IOV.
>
> https://docs.mellanox.com/pages/viewpage.action?pageId=39264752
>
>
>
> Regards,
>
> Fukumoto
>
>
>
> *From:* Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
> *Sent:* Monday, January 4, 2021 6:26 PM
> *To:* Fukumoto, Shinya/福本 真也 <fukumoto.shinya(a)fujitsu.com>
> *Cc:* users(a)ovirt.org
> *Subject:* Re: [ovirt-users] Can NFV (Network Functions Virtualization)
> work on oVirt?
>
>
>
> On Mon, Jan 4, 2021 at 10:04 AM fukumoto.shinya(a)fujitsu.com <
> fukumoto.shinya(a)fujitsu.com> wrote:
>
> Hello everyone,
>
> I've checked the documentation of oVirt, but cannot find if following
> function can work on oVirt or not.
> - NFV (Network Functions Virtualization)
>
> Does someone know NFV can work on oVirt?
>
> For your reference, Red Hat OpenStack Platform seems to support NFV as
> follows
>
> https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/...
>
> Regards,
> Fukumoto
>
>
>
> I think you can find useful information here for RHV 4.4, that should be
> applicable to oVirt 4.4 too:
>
>
>
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/...
>
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/...
>
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/...
>
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/...
>
>
>
> I don't know if it is supported to also use NFV with OVN external provider
> in oVirt/RHV
>
>
>
> HIH,
>
> Gianluca
> _______________________________________________
> 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
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GIOGKOQRLCM...
>
3 years, 10 months
Re: Hosts are non responsive Ovirt 3.6
by Yedidyah Bar David
On Wed, Jan 6, 2021 at 5:01 PM Gary Lloyd <g.lloyd(a)keele.ac.uk> wrote:
>
> I ended up cheating in the end.
> I copied vdsmcert.pem and vdsmkey.pem from the host that is still working to the others and did a chown on the files.
> All the hosts are back online without downtime. I must have rebuilt that server a couple of years after the other ones.
Nice hack! :-)
Please note that you take a risk here. The cert includes the hostname,
and now it's not matching the hostname that the client (the engine, in
this case, or another host, e.g. for VM migration) expects. So if some
piece of software checks this, it might fail. Personally, I wouldn't
stay in this state for long.
Best regards,
--
Didi
3 years, 10 months
Re: Hosts are non responsive Ovirt 3.6
by Strahil Nikolov
Have you tried to put a host into maintenance, remove and then readd it ?
You can access all Red Hat solutions with their free developer subscription.
Best Regards,
Strahil Nikolov
В сряда, 6 януари 2021 г., 13:17:42 Гринуич+2, Gary Lloyd <g.lloyd(a)keele.ac.uk> написа:
Hi please could someone point me in the right direction to renew ssl certificates for vdsm to communicate with ovirt 3.6 ?
I’m aware that this version hasn’t been supported for some time, this is a legacy environment which we are working towards decommissioning.
There seems to be a fix article for RHEV but we don’t have a subscription to view this information:
How to update expired RHEV certificates when all RHEV hosts got 'Non-responsive' - Red Hat Customer Portal
These are what the vdsm hosts are showing:
Reactor thread::ERROR::2021-01-06 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read) Error during handshake: sslv3 alert certificate expired
I have rerun engine-setup but this only seems to have fixed one of the vdsm hosts and the others are non responsive.
The others are in different clusters and we have some important services still running on these.
Thanks
Gary Lloyd
IT Infrastructure Manager
Information and Digital Services
01782 733063
Innovation Centre 2 | Keele University | ST5 5NH
_______________________________________________
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
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HT6Z3WHPFTB...
3 years, 10 months
