From: "Lorenzo Fernando Bivens de la Fuente" <lorenzobivens@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] I/O load crashes Qemu
Date: Thu, 12 Jun 2008 22:38:55 -0500 [thread overview]
Message-ID: <fb4c8d190806122038k5c8e67b0odba6e0252bce175c@mail.gmail.com> (raw)
In-Reply-To: <fb4c8d190806122038l5abe3427r5ca28d0b3085de1a@mail.gmail.com>
Also... Renice if you can.
On 6/12/08, Lorenzo Fernando Bivens de la Fuente
<lorenzobivens@gmail.com> wrote:
> Thoughts:
> + Running Plan 9 on qemu is slow (when doing disk access) (the
> ethernal DMA wiwi bla bla bla)
> + qcow2 is quality challenged, but I think that the standard plan9.img
> ain't qcow2
> +kqemu has worked for me very well... but I have not benchmarked it.
> + Unpacking 100 MiB sounds like a lot of I/O... Ergo a lot of "disk"
> ergo a lot of no-dma bottleneck
>
> Good luck
>
>
> On 6/12/08, Pietro Gagliardi <pietro10@mac.com> wrote:
> > On Jun 12, 2008, at 9:54 PM, Venkatesh Srinivas wrote:
> >
> >
> > > Hi,
> > >
> > > I currently use Plan 9 in qemu 0.9.1; whenever I try to do anything I/O
> > > demanding such as unpacking a ~100MB tarball, qemu locks up and refuses
> > > further connections (via vnc, or gdb for example). I am using fossil
> > > alone. This behavior occurs whether kqemu is enabled or not, though it
> > > happens a lot faster w/o kqemu.
> > >
> > > Has anyone else noticed anything like this? Any thoughts about running
> > > Plan 9 in qemu?
> > >
> > > Thanks,
> > > --vs
> > >
> > >
> >
> > Compressed disc image (qcow2)? That's what screwed up my fossil+venti.
> >
> >
> >
>
next prev parent reply other threads:[~2008-06-13 3:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 1:54 Venkatesh Srinivas
2008-06-13 2:01 ` Pietro Gagliardi
2008-06-13 3:38 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 3:38 ` Lorenzo Fernando Bivens de la Fuente [this message]
2008-06-13 4:00 ` Venkatesh Srinivas
2008-06-13 8:08 ` sqweek
2008-06-13 10:41 ` Bruce Ellis
2008-06-13 11:47 ` Rodolfo kix García
2008-06-13 19:05 ` Bakul Shah
2008-06-13 20:03 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 20:33 ` Charles Forsyth
2008-06-13 20:30 ` erik quanstrom
2008-06-13 20:58 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 23:52 ` erik quanstrom
2008-06-14 0:40 ` Bakul Shah
2008-06-13 20:35 ` Charles Forsyth
2008-06-13 23:01 ` Bakul Shah
2008-06-13 23:26 ` Pietro Gagliardi
2008-06-13 23:36 ` Bakul Shah
2008-06-13 23:42 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 23:52 ` Uriel
2008-06-17 10:51 ` matt
2008-06-13 12:57 ` stefanha
2008-06-13 12:22 ` Fazlul Shahriar
2008-06-14 0:39 erik quanstrom
2008-06-14 1:24 ` Bakul Shah
2008-06-14 4:58 ` Bruce Ellis
2008-06-14 5:30 ` Iruata Souza
2008-06-14 12:53 ` erik quanstrom
2008-06-14 15:14 ` Iruata Souza
2008-06-14 14:15 ` erik quanstrom
2008-06-15 0:01 ` Bakul Shah
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=fb4c8d190806122038k5c8e67b0odba6e0252bce175c@mail.gmail.com \
--to=lorenzobivens@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).