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: Fri, 13 Jun 2008 15:03:13 -0500 [thread overview]
Message-ID: <fb4c8d190806131303n6d6e262cma13e88bb58ecfc49@mail.gmail.com> (raw)
In-Reply-To: <20080613190551.3C0265B46@mail.bitblocks.com>
In fact it is definetly not a plan9 issue...
If qemu fails hosting plan 9, it affects plan 9 but there is little to
be done unless we communicate with the qemu dev team.
Plan 9 is not the only os having problems with DMA access through
qemu. I am myself a moron... All I know is that the issue exists, I
don't know why... (But it would be very appreciated if an explanation
is given)
One thing I've thought several times is that perhaps qemu-ide specific
drivers need to be done. Many hosted OSs need custom made drivers to
be used with a virtualizer.
I am sure a lot has been discused about this on the list.
I'll try to do a quick scan about it later.
On 6/13/08, Bakul Shah <bakul+plan9@bitblocks.com> wrote:
> > Everything, in my experience, crashes QEMU. Nice try.
>
> > Just the opinion of me and my dog (who barks loudly when I shout
> > f**king QEMU - piece of f**king sh*t!).
>
>
> I have used qemu/freebsd for the past 4 years or so. On the
> whole it has worked quite well. I often use plan9, Windows
> 2000 and freebsd under qemu for hours on end. Juergen Lock
> has done an excellent job on making sure qemu+kqemu continue
> to work on freebsd but he has needed feedback from
> qemu/freebsd users.
>
> If you plan on continuing with qemu it might be worth asking
> on the qemu-devel mailing list or #qemu on freenode as I
> don't think any qemu dveloper follows 9fans. But they will
> need details like the host OS and version, qemu version,
> command line used, exact symptoms, steps to repeat the
> problem etc.
>
>
next prev parent reply other threads:[~2008-06-13 20:03 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
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 [this message]
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=fb4c8d190806131303n6d6e262cma13e88bb58ecfc49@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).