From: Marcelo Tosatti <mtosatti@redhat.com>
To: Gerd von Egidy <lists@egidy.de>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: disappointing speed with virtio_blk
Date: Fri, 18 Apr 2008 18:49:10 -0300 [thread overview]
Message-ID: <20080418214910.GA24619@dmt> (raw)
In-Reply-To: <200804182327.58902.lists@egidy.de>
Hi Gerd,
On Fri, Apr 18, 2008 at 11:27:58PM +0200, Gerd von Egidy wrote:
> Hi Marcelo,
>
> > > >
> http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg14732.html
> > >
> > > I tried it this evening with kvm 66 - which should include your patch,
> > > right?
> >
> > No its not included. The issue is being worked on.
>
> my bad, sorry.
>
> Now I know I really have that patch: qemu-kvm hangs :(
>
> I was trying kvm 66 with only the patch listed above applied on an otherwise
> perfectly working vm with virtio_blk root partition:
>
> Last line of the booting kernel in my vnc window:
>
> Serial: 8250/16550 driver $Revision 1.90... (you know the rest)
When the hang happens, can you run kvm-stat --once (script can be found
kvm-66 directory) and paste the result?
Can you confirm that reverting the patch fixes it?
> an strace of the qemu-kvm gave the following in rapid succession:
>
> clock_gettime(CLOCK_MONOTONIC, {2565, 306799672}) = 0
> clock_gettime(CLOCK_MONOTONIC, {2565, 307065342}) = 0
> clock_gettime(CLOCK_MONOTONIC, {2565, 307354930}) = 0
> clock_gettime(CLOCK_MONOTONIC, {2565, 307618803}) = 0
> clock_gettime(CLOCK_MONOTONIC, {2565, 307886312}) = 0
> timer_gettime(0, {it_interval={0, 0}, it_value={0, 0}}) = 0
> timer_settime(0, 0, {it_interval={0, 0}, it_value={0, 33000000}}, NULL) = 0
> rt_sigtimedwait([USR1 USR2 ALRM IO], {si_signo=SIGALRM, si_code=SI_TIMER,
> si_pid=0, si_uid=0, si_value={int=0, ptr=0}}, 0xbfe5af88, 8) = 14
> rt_sigaction(SIGALRM, NULL, {0x804d8f8, ~[KILL STOP RTMIN RT_1], 0}, 8) = 0
This won't help much.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-18 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 21:04 disappointing speed with virtio_blk Gerd von Egidy
2008-04-13 21:22 ` Charles Duffy
2008-04-13 21:55 ` Gerd von Egidy
2008-04-14 0:29 ` Marcelo Tosatti
2008-04-16 23:05 ` Gerd von Egidy
2008-04-16 23:40 ` Marcelo Tosatti
2008-04-18 21:27 ` Gerd von Egidy
2008-04-18 21:49 ` Marcelo Tosatti [this message]
2008-04-18 22:32 ` Gerd von Egidy
2008-04-14 1:41 ` Anthony Liguori
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=20080418214910.GA24619@dmt \
--to=mtosatti@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=lists@egidy.de \
/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