From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Fri, 13 Jun 2008 15:03:13 -0500 From: "Lorenzo Fernando Bivens de la Fuente" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <20080613190551.3C0265B46@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <775b8d190806130341s1b93d240x2c82e444dd3937f1@mail.gmail.com> <20080613190551.3C0265B46@mail.bitblocks.com> Subject: Re: [9fans] I/O load crashes Qemu Topicbox-Message-UUID: bf269260-ead3-11e9-9d60-3106f5b1d025 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 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. > >