Description of problem: After upgrading engine & hosts and trying to migrate vm from not yet updated host, vm fails to migrate. Also, vm create multiple coredumps on each attempt to migrate, which in turn filled entire disk space on host (100%) and as result vdsm service failed. Version-Release number of selected component (if applicable): ovirt-engine-4.1.0.4-0.1.el7.noarch vdsm-4.19.4-1.el7ev.x86_64 How reproducible: None Steps to Reproduce: 1. 2. 3. Actual results: Disk 100% full with coredumps, vdsm service failer, engine lost connection to host. Expected results: Show error/warning, limit coredumps size/number to not fill entire disk space. Additional info:
Not sure why it's virt - I believe host-deploy should fix and set it? (also on RHVH - a separate bug?)
there is core_dump_enable vdsm.conf parameter controlling this. I just thought it's disabled by default, but apparently it is not. Danken, do you recall more? I only know of the outstanding ABRT integration (bug 917062) which would change this, but that's not finished. (since that other bug is infra I think the best owner is infra team)
core_dump_enable is on by default because qemu core dumps are rare and hard to reproduce. If users do not catch them at first crash, qemu-kvm team has nothing to work with. But yes, proper ABRT integration would be much better than ovirt-specific tricks.
ok, then this is intentional and RFE bug 917062 is tracking improvements in better debug information without a need for full memory dump that particular crash is reported and tracked separately as bug 1421788 *** This bug has been marked as a duplicate of bug 917062 ***