From: Garth Dahlstrom <ironstorm@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Is there an official channel for bug reports?
Date: Mon, 2 Aug 2004 11:59:08 -0400 [thread overview]
Message-ID: <76bfb9d20408020859d37381d@mail.gmail.com> (raw)
I'm just wondering if there is an official channel for reporting
bugs... as I've got 3 that I'd like to track or offer testing towards
fixing...
Here they are (Windows QEMU 0.6):
- Guest keyboard is fsck'd up, arrow keys don't work. (this has been
reported to the list w/ a patch I think)
- Guest NIC corrupts data - this has been seen in bad crc/md5
downloads as well as "Disconnecting: Corrupted MAC on input" errors
doing an SSH reverse tunnel as described here:
http://www.northern.ca/forums/index.php?t=msg&th=124
- Guest system (only tested with guest linux 2.4.22) appears somewhat
unstable when Host system changes clock speed, i.e. when P4M or
Centrino speedstepping speeds up from 600 -> 1.4 GHz (like when you
plug into an outlet).
--
Northern.CA ===--
http://www.northern.ca/
Canada's Search Engine
next reply other threads:[~2004-08-02 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 15:59 Garth Dahlstrom [this message]
2004-08-02 16:15 ` [Qemu-devel] Is there an official channel for bug reports? Erik Karlsson
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=76bfb9d20408020859d37381d@mail.gmail.com \
--to=ironstorm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.