From: "Christian MICHON" <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bugs found
Date: Fri, 30 Mar 2007 14:44:54 +0200 [thread overview]
Message-ID: <46d6db660703300544t27a6a97cs509ee3ceb916e47@mail.gmail.com> (raw)
In-Reply-To: <000901c772bd$56bd9940$b7b1683a@domain.invalid>
On 3/30/07, James Jacobs <jrj76@optusnet.com.au> wrote:
> 3 more bugs that need attention...
>
> a) serious: Image files, even those created by the version of qemu-img.exe
> that comes with QEMU 0.90, are unreadable by QEMU 0.90, QEMU 0.82 works fine
> with them.
>
> b) less serious: "Out of environment space" error when starting.
>
> c) serious: "audio: Failed to create voice 'es1370.adc" error when starting.
>
> 3 more bugs that need attention...
some info missing here...
host type, guest type, command lines, and most important type of
images you're creating.
from your email, you're using released versions, not cvs snapshot,
right ?
personally: I do not see (a) on windows host, I do not know which
guest gives you (b) and I do not use audio, so I cannot confirm (c)...
--
Christian
prev parent reply other threads:[~2007-03-30 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 11:19 [Qemu-devel] Bugs found James Jacobs
2007-03-30 12:44 ` Christian MICHON [this message]
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=46d6db660703300544t27a6a97cs509ee3ceb916e47@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).