public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: kvm@vger.kernel.org
Subject: Re: repeatable hang with loop mount and heavy IO in guest [SOLVED]
Date: Sat, 23 Jan 2010 01:28:30 +0700	[thread overview]
Message-ID: <4B59EE4E.6070005@nagafix.co.uk> (raw)
In-Reply-To: <4B595A7B.4010404@msgid.tls.msk.ru>

On 01/22/2010 02:57 PM, Michael Tokarev wrote:
> Antoine Martin wrote:
>    
>> I've tried various guests, including most recent Fedora12 kernels,
>> custom 2.6.32.x
>> All of them hang around the same point (~1GB written) when I do heavy IO
>> write inside the guest.
>>      
> []
>    
>> Host is running: 2.6.31.4
>> QEMU PC emulator version 0.10.50 (qemu-kvm-devel-88)
>>      
> Please update to last version and repeat.  kvm-88 is ancient and
> _lots_ of stuff fixed and changed since that time, I doubt anyone
> here will try to dig into kvm-88 problems.
>
> Current kvm is qemu-kvm-0.12.2, released yesterday.
>    
Sorry about that, I didn't realize 88 was so far behind.
Upgrading to qemu-kvm-0.12.2 did solve my IO problems.


Found these build issues if anyone is interested:
"--enable-io-thread" gave me:
   LINK  x86_64-softmmu/qemu-system-x86_64
kvm-all.o: In function `qemu_mutex_lock_iothread':
/usr/src/KVM/qemu-kvm-0.12.2/qemu-kvm.c:2526: multiple definition of 
`qemu_mutex_lock_iothread'
vl.o:/usr/src/KVM/qemu-kvm-0.12.2/vl.c:3772: first defined here
kvm-all.o: In function `qemu_mutex_unlock_iothread':
/usr/src/KVM/qemu-kvm-0.12.2/qemu-kvm.c:2520: multiple definition of 
`qemu_mutex_unlock_iothread'
vl.o:/usr/src/KVM/qemu-kvm-0.12.2/vl.c:3783: first defined here
collect2: ld returned 1 exit status

And "--enable-cap-kvm-pit" is defined if you look at "--help", but does 
not exist if you try to use it!?
# ./configure --enable-cap-kvm-pit | grep cap-kvm-pit
ERROR: unknown option --enable-cap-kvm-pit
   --disable-cap-kvm-pit    disable KVM pit support
   --enable-cap-kvm-pit     enable KVM pit support

Antoine

  reply	other threads:[~2010-01-22 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 17:26 repeatable hang with loop mount and heavy IO in guest Antoine Martin
2010-01-21 20:08 ` RW
2010-01-21 21:08   ` Thomas Beinicke
2010-01-21 21:36     ` RW
2010-01-22  7:57 ` Michael Tokarev
2010-01-22 18:28   ` Antoine Martin [this message]
2010-01-22 19:15     ` repeatable hang with loop mount and heavy IO in guest [NOT SOLVED] Antoine Martin
2010-01-24 11:23       ` Antoine Martin
2010-02-03 19:28       ` Antoine Martin
2010-02-26 17:38         ` repeatable hang with loop mount and heavy IO in guest Antoine Martin
2010-05-21  9:38           ` repeatable hang with loop mount and heavy IO in guest (now in host - not KVM then..) Antoine Martin
2010-05-22 18:10             ` Jim Paris
2010-05-22 19:33               ` Antoine Martin

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=4B59EE4E.6070005@nagafix.co.uk \
    --to=antoine@nagafix.co.uk \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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