From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Issues about domU suspending/resuming Date: Thu, 28 Jul 2011 18:32:57 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gustavo Pimentel Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 28/07/2011 18:16, "Gustavo Pimentel" wrote= : > It's not really a bug, but a performance analysis. > I'm using remus for a HA system and after a system analysis using remus l= og, I > notice that suspending a the guest can oscillate between 0.299ms to 812.9= 09ms. > And the resuming of the same guest oscillates between 0.387ms to 1745,579= ms. > The guest it's a virtual machine with 64MB of RAM, without CPU load. >=20 > It's very strange this large range of values of the suspend/resuming of a > guest. First point of contact would be the listed Remus maintainer. More data woul= d be useful I expect -- e.g., does the variation occur with basic live migration (no Remus)? -- Keir >> -----Original Message----- >> From: Keir Fraser [mailto:keir.xen@gmail.com] >> Sent: quinta-feira, 28 de Julho de 2011 18:00 >> To: Gustavo Pimentel >> Cc: xen-devel@lists.xensource.com >> Subject: Re: Issues about domU suspending/resuming >>=20 >> On 28/07/2011 17:13, "Gustavo Pimentel" wr= ote: >>=20 >>> Hi, I have looked into the MAINTAINERS file on the xen source, but I di= dn=B9t >>> find the specific maintainer for responsible for issues about domU >>> suspending/resuming procedure. >>> Can you point me to the right person? >>=20 >> It crosses multiple subsystems. It could be a guest kernel bug for examp= le, >> or a toolstack bug. Post a bug report to xen-devel and we can try to tri= age >> it. >>=20 >> -- Keir >>=20 >>=20 >>=20 >>=20 >=20 >=20