public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "jmandawg" <jmandawg@hotmail.com>
To: "'Avi Kivity'" <avi@redhat.com>
Cc: "'KVM list'" <kvm@vger.kernel.org>
Subject: RE: XP guests sluggish after around 1 week of uptime
Date: Mon, 19 Jan 2009 08:00:15 -0500	[thread overview]
Message-ID: <BAY102-DAV22AD664A518A0399D9ABBD2D30@phx.gbl> (raw)
Message-ID: <000b01c97a35$df21a7f0$9d64f7d0$@com> (raw)
In-Reply-To: <49747614.4010403@redhat.com>

> -----Original Message-----
> From: Avi Kivity [mailto:avi@redhat.com]
> Sent: Monday, January 19, 2009 7:46 AM
> To: jmandawg
> Cc: KVM list
> Subject: Re: XP guests sluggish after around 1 week of uptime
> 
> (re-add kvm@vger)
> 
> 
> Software RAID or hardware RAID?
> 
> I think the root cause is the RAID here, not kvm.
> Some suggestions:
> - use the raw format directly on top of LVM.  That is, use -drive
> file=/dev/volgroup/logvol.
> - if you use the raw format, disable disk caching: -drive
> file=/dev/volgroup/logvol,cache=off
> - try non-RAID5 storage
> 
> To migrate your volumes, use
> 
>   qemu-img convert /path/to/image.qcow -O raw /dev/volgroup/logvol
> 
> Be sure to size the volume appropriately (same size as the virtual image).
> 
> This seems fine if a bit low.  You'll get better numbers sitting
> directly atop LVM.
> 
> --
> error compiling committee.c: too many arguments to function

Yes, it is software raid, I will try moving the guest images to one of my
other disks that is not RAIDed on their own LVM volume.

Does the LVM logical volume size need to be equal the guest disk size
exactly?

I will let you know the results.

Thanks again for the help,

-J  



  reply	other threads:[~2009-01-19 13:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  4:12 XP guests sluggish after around 1 week of uptime Jay Mann
2009-01-12  8:58 ` Florent
2009-01-12 12:34   ` Jay
2009-01-12 13:36 ` Avi Kivity
2009-01-12 15:24   ` Jay
2009-01-13  9:29     ` Avi Kivity
     [not found]       ` <001501c9757a$eda76400$c8f62c00$@com>
2009-01-13 12:31         ` jmandawg
     [not found]       ` <007301c97982$f704b500$e50e1f00$@com>
2009-01-18 15:39         ` jmandawg
2009-01-19 12:05           ` Avi Kivity
     [not found]             ` <BAY102-DAV67C4CDA23F6EC8D7DB94DD2D30@phx.gbl>
2009-01-19 12:46               ` Avi Kivity
     [not found]                 ` <000b01c97a35$df21a7f0$9d64f7d0$@com>
2009-01-19 13:00                   ` jmandawg [this message]
2009-01-19 13:07                     ` Avi Kivity
     [not found]       ` <000601c979ea$d67f60b0$837e2210$@com>
2009-01-19  4:03         ` jmandawg
2009-01-19 10:09           ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAY102-DAV22AD664A518A0399D9ABBD2D30@phx.gbl \
    --to=jmandawg@hotmail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox