Any other suggestions ? I'm already running a later version of qemu (qemu-kvm-ev-2.12.0-33.1.el7_7.4) than the one referenced (qemu-kvm-rhev-2.9.0-16) in https://access.redhat.com/solutions/3423481 (from what I can see on that page without a subscription).
Regards, Brett On Tue, 7 Apr 2020 at 11:56, Maton, Brett <[email protected]> wrote: > I haven't got an active RHEL subscription so I can't view that solution > unfortunately. > > > Thanks for the log pointers though, looking in the qemu log I'm not > surprised it's crashing... > > tcmalloc: large alloc 562949953421312 bytes == (nil) @ 0x7f93c080b4ef > 0x7f93c082b367 0x7f93d8310736 0x55efa0670ac8 0x55efa06718e5 0x55efa0621bae > 0x55efa06287b6 0x55efa07f0de5 0x55efa07ecbdf 0x7f93bf7b3e65 0x7f93bf4dc88d > > (process:1374): GLib-ERROR **: 09:26:39.525: gmem.c:135: *failed to > allocate 562949953421312 bytes* > 2020-04-06 08:26:43.036+0000: shutting down, reason=crashed > ... > libvirt version: 4.5.0, package: 23.el7_7.6 (CentOS BuildSystem < > http://bugs.centos.org>, 2020-03-17-23:39:10, x86-01.bsys.centos.org), > qemu version: 2.12.0qemu-kvm-ev-2.12.0-33.1.el7_7.4, kernel: > 3.10.0-1062.18.1.el7.x86_64 > > 562949953421312 bytes is mighty big, nigh on 563 TB! > The VM in question is allocated 4GB RAM and has a 60GB disk... > > Couldn't see any errors in the VDSM log at the time that qemu failed. > > On Tue, 7 Apr 2020 at 10:52, Shani Leviim <[email protected]> wrote: > >> Hi Brett, >> According to [1], you can try to update the package qemu-kvm-rhev. >> (Or yum update if there're more packages related need to be upgraded). >> >> You may also find some more information about that error on the vdsm log >> (/var/log/vdsm/vdsm.log) >> and the qemu log (/var/log/libvirt/qemu/vm_name.log) >> >> [1] https://access.redhat.com/solutions/3423481 >> >> >> *Regards,* >> >> *Shani Leviim* >> >> >> On Mon, Apr 6, 2020 at 12:09 PM Maton, Brett <[email protected]> >> wrote: >> >>> I recently added a Windows 10 Pro 64 bit (release 1909) VM, and I'm >>> seeing a lot of failures when oVirt tries to move the VM to another host >>> (triggered by load balancing), >>> >>> These errors are showing up in the UI event log >>> >>> Migration failed (VM: <vm label>, Source: <host 1>, Destination: <host >>> 2>). >>> >>> Followed by: >>> >>> VM <host> is down with error. Exit message: Lost connection with qemu >>> process. >>> >>> Google returned some references to 'options kvm ignore_msrs=1' which >>> I've added to /etc/modprobe/d/kvm.conf and restarted the hosts but that >>> doesn't appear to have made a difference. >>> >>> Is this a known issue with Windows 10 guests? >>> _______________________________________________ >>> Users mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> 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/[email protected]/message/QNJ7GFDXKBVREHJY4FBIORLBVEBO353R/ >>> >>
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/JNNOKV3N6E3BZ2FGLYCO2UULDLF6WENN/
