[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] RE: Issues about domU suspending/resuming

  • To: "Keir Fraser" <keir.xen@xxxxxxxxx>
  • From: "Gustavo Pimentel" <gustavo.pimentel@xxxxxxxxxx>
  • Date: Thu, 28 Jul 2011 18:16:26 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 28 Jul 2011 10:18:10 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcxNQVqBtABm99N7RZiRwlB4YN8SugABnZpmAABUy+A=
  • Thread-topic: Issues about domU suspending/resuming

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 log, I 
notice that suspending a the guest can oscillate between 0.299ms to 812.909ms. 
And the resuming of the same guest oscillates between 0.387ms to 1745,579ms. 
The guest it's a virtual machine with 64MB of RAM, without CPU load.

It's very strange this large range of values of the suspend/resuming of a guest.

> -----Original Message-----
> From: Keir Fraser [mailto:keir.xen@xxxxxxxxx]
> Sent: quinta-feira, 28 de Julho de 2011 18:00
> To: Gustavo Pimentel
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: Issues about domU suspending/resuming
> On 28/07/2011 17:13, "Gustavo Pimentel" <gustavo.pimentel@xxxxxxxxxx> wrote:
> > Hi, I have looked into the MAINTAINERS file on the xen source, but I didn¹t
> > find the specific maintainer for responsible for issues about domU
> > suspending/resuming procedure.
> > Can you point me to the right person?
> It crosses multiple subsystems. It could be a guest kernel bug for example,
> or a toolstack bug. Post a bug report to xen-devel and we can try to triage
> it.
>  -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.