Return-Path: <dfediuck@redhat.com> X-Original-To: infra@ovirt.org Delivered-To: infra@ovirt.org Received: from mx4-phx2.redhat.com (mx4-phx2.redhat.com [209.132.183.25]) by lists.ovirt.org (Postfix) with ESMTP id EE09C17449F for <infra@ovirt.org>; Sun, 14 Jul 2013 10:06:57 -0400 (EDT) Received: from zmail20.collab.prod.int.phx2.redhat.com (zmail20.collab.prod.int.phx2.redhat.com [10.5.83.23]) by mx4-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r6EApaKH027664 for <infra@ovirt.org>; Sun, 14 Jul 2013 06:51:36 -0400 Date: Sun, 14 Jul 2013 06:51:35 -0400 (EDT) From: Doron Fediuck <dfediuck@redhat.com> To: infra <infra@ovirt.org> Message-ID: <1380187446.247110.1373799095914.JavaMail.root@redhat.com> In-Reply-To: <201307141019.r6EAJfAd032464@mx3-phx2.redhat.com> References: <201307141019.r6EAJfAd032464@mx3-phx2.redhat.com> Subject: Fwd: Warning: could not send message for past 4 hours MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_247108_1255273089.1373799095913" X-Priority: 1 Importance: high X-Originating-IP: [10.5.82.12] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC27 (Linux)/8.0.3_GA_5664) Thread-Topic: Warning: could not send message for past 4 hours Thread-Index: 2qO3KgFfL12SZSId+aPOnjRAobbZtw== X-BeenThere: infra@ovirt.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "List for ovirt.org infrastructure team" <infra.ovirt.org> List-Unsubscribe: <http://lists.ovirt.org/mailman/options/infra>, <mailto:infra-request@ovirt.org?subject=unsubscribe> List-Archive: <http://lists.ovirt.org/pipermail/infra/> List-Post: <mailto:infra@ovirt.org> List-Help: <mailto:infra-request@ovirt.org?subject=help> List-Subscribe: <http://lists.ovirt.org/mailman/listinfo/infra>, <mailto:infra-request@ovirt.org?subject=subscribe> X-List-Received-Date: Sun, 14 Jul 2013 14:06:58 -0000 ------=_Part_247108_1255273089.1373799095913 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Guys, we have a storage issue in linode01.ovirt.org, which causes the users list to hang. Can someone please take a look? ----- Forwarded Message ----- | From: "Mail Delivery Subsystem" <MAILER-DAEMON@redhat.com> | To: dfediuck@redhat.com | Sent: Sunday, July 14, 2013 1:19:41 PM | Subject: Warning: could not send message for past 4 hours | | ********************************************** | ** THIS IS A WARNING MESSAGE ONLY ** | ** YOU DO NOT NEED TO RESEND YOUR MESSAGE ** | ********************************************** | | The original message was received at Sun, 14 Jul 2013 02:02:53 -0400 | from zmail20.collab.prod.int.phx2.redhat.com [10.5.83.23] | | ----- Transcript of session follows ----- | ... while talking to linode01.ovirt.org.: | >>> MAIL From:<dfediuck@redhat.com> SIZE=1970 | <<< 452 4.3.1 Insufficient system storage | <users@ovirt.org>... Deferred: 452 4.3.1 Insufficient system storage | Warning: message still undelivered after 4 hours | Will keep trying until message is 5 days old | ------=_Part_247108_1255273089.1373799095913 Content-Type: message/rfc822 Content-Disposition: attachment Return-Path: <dfediuck@redhat.com> Received: from zmail20.collab.prod.int.phx2.redhat.com (zmail20.collab.prod.int.phx2.redhat.com [10.5.83.23]) by mx3-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r6E62riE029178; Sun, 14 Jul 2013 02:02:53 -0400 Date: Sun, 14 Jul 2013 02:02:52 -0400 (EDT) From: Doron Fediuck <dfediuck@redhat.com> To: Joop <jvdwege@xs4all.nl> Cc: users@ovirt.org Message-ID: <1523320829.231446.1373781772593.JavaMail.root@redhat.com> In-Reply-To: <51E1C4D0.1080107@xs4all.nl> References: <51E1C4D0.1080107@xs4all.nl> Subject: Re: [Users] Limit migration bandwidth MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.5.82.12] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC27 (Linux)/8.0.3_GA_5664) Thread-Topic: Limit migration bandwidth Thread-Index: fI/8RaGsezIrPH1llXclCTwElBJA/Q== ----- Original Message ----- | From: "Joop" <jvdwege@xs4all.nl> | To: users@ovirt.org | Sent: Sunday, July 14, 2013 12:21:20 AM | Subject: [Users] Limit migration bandwidth | | Hi All, | | I have seen this question asked before and seen it answered but can't | find it back on either the mailinglist or IRC, probably because I don't | use the correct search term but can't dream up any new ones so I'm asking: | How to limit the amount of VM's that can simultaneously be migrated and | how to limit the bandwidth used by migrating VM's? | Looked at vdc_options, engine-config but have run out of ides. | | Thanks in advance, | | Joop | -- | irc: jvandewege | Hi Joop, Currently it is possible to hard-limit the migration using The /usr/share/doc/<vdsm-version>/vdsm.conf.sample file with # Maximum bandwidth for migration, in mbps, 0 means libvirt's default (30mbps?). # migration_max_bandwidth = 0 Change 0 to something else (5 does magic IIRC) to see how it works. In the coming oVirt 3.3 we should be able to handle this by separating the migration network, and then use- http://www.ovirt.org/Features/Network_QoS Doron ------=_Part_247108_1255273089.1373799095913--