Dear Eitan, You misunderstood me, we use the LATEST version of ovirt, but this problem exist since we started to use (3.4). Have a nice day, Regards, Tibor ----- 2018. dec.. 9., 10:04, Eitan Raviv eraviv(a)redhat.com írta: > Hi Tibor, > > I don't know what would cause such issues as you describe, but since > you are using a very old version of oVirt, the best I can recommend is > to upgrade to 4.2. > > HTH > > On Thu, Dec 6, 2018 at 6:24 PM Demeter Tibor <tdemeter(a)itsmart.hu&gt; wrote: >> >> Dear All, >> >> I've using ovirt from 3.4 and we have a strange, rarely problem with live >> migrations. >> >> - In most of case impossible to do a live migrate of VMs that have a lot of >> memory (16 gigs and more up to 40 GB) . >> - Those are need to try and try until the migration will be successful >> - impossible to understand why does working in a case and doesn't in another >> - it is happening always if there bigger load on vms, but only on big memory >> VM-s >> - The small VMs (2-4-8 gigs) can migrate without problems >> - In very rarely cases possible to migrate on first try. >> - We using the memory ballooning function on all of VMs. >> >> We using dedicated migration network with separated vlans, but on same physical >> lan (1gbe) with ovirtmgmt. >> At this moment, we don't use QoS for dedicate bandwidth. >> >> What can I do ? >> >> Thanks in advance, >> Regards, >> >> Tibor >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/ORTLVGYDPUJ...