From: Jason Brittain <jason@brittainweb.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] enabling bus-master IDE driver
Date: Thu, 11 Nov 2004 11:02:16 -0800 [thread overview]
Message-ID: <4193B738.70106@brittainweb.org> (raw)
In-Reply-To: <20041111190649.GE11488@suse.de>
Jens Axboe wrote:
> On Thu, Nov 11 2004, Jason Brittain wrote:
>
>>I just pulled the latest source from CVS (today's), and tried
>>looking at DMA again.
>>
>>Host: Linux 2.6 (Fedora Core 2)
>>Guest: XP corp.
>>It still says the primary IDE channel is in PIO mode, and
>>doesn't seem any faster.
>>
>>Host: Linux 2.6 (Fedora Core 2)
>>Guest: Linux 2.6
>>hdparm now reports that DMA is on for /dev/hda, and I can also
>>turn it on and off. With it on, it's about twice as fast as
>>it is with it off. So, this seems to work.
>
>
> If I could install XP, I could take a look. But it will boot for me
> after install, just hangs. If I restart qemu, it complains about a bad
> boot loader.
>
> If I get time I'll look into this.
That's a known problem that aparently still isn't fixed in CVS.
To fix it, apply this patch to your ide.c:
--- hw/ide.c-bad 2004-11-11 07:54:34.000000000 -0800
+++ hw/ide.c 2004-11-11 08:56:23.000000000 -0800
@@ -1895,7 +1895,7 @@
s->heads = 16;
s->sectors = 63;
}
- bdrv_set_geometry_hint(s->bs, s->cylinders, s->heads, s->sectors);
+ /*bdrv_set_geometry_hint(s->bs, s->cylinders, s->heads, s->sectors);*/
}
if (bdrv_get_type_hint(s->bs) == BDRV_TYPE_CDROM) {
s->is_cdrom = 1;
And, then you must reinstall XP in a new hd image. Old images
are apparently corrupted, and will not work even with a patched
qemu binary. I now keep my qemu patched this way and my XP
boots fine.
--
Jason Brittain
next prev parent reply other threads:[~2004-11-11 19:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 20:35 [Qemu-devel] enabling bus-master IDE driver Simon Frew
2004-11-05 13:32 ` zitu
2004-11-05 15:02 ` zitu
2004-11-06 1:53 ` Jason Brittain
2004-11-06 14:27 ` Johannes Schindelin
2004-11-06 21:52 ` Jason Brittain
2004-11-07 9:03 ` Jens Axboe
2004-11-07 9:21 ` Jens Axboe
2004-11-07 9:38 ` Jens Axboe
2004-11-07 11:01 ` Hetz Ben Hamo
2004-11-07 11:16 ` Jens Axboe
2004-11-08 10:15 ` zitu
2004-11-08 16:51 ` Andreas Bollhalder
2004-11-09 7:38 ` Paul Jakma
2004-11-09 10:28 ` Hetz Ben Hamo
2004-11-09 13:53 ` Paul Jakma
2004-11-11 17:29 ` Jason Brittain
2004-11-11 19:06 ` Jens Axboe
2004-11-11 19:02 ` Jason Brittain [this message]
2004-11-11 19:16 ` Jens Axboe
2004-11-12 8:42 ` Jens Axboe
2004-11-07 11:02 ` James Boddington
2004-11-10 1:41 ` James Boddington
2004-11-06 21:57 ` James Boddington
2004-11-06 22:11 ` James Boddington
2004-11-06 23:46 ` zitu
2004-11-07 0:41 ` jeebs
2004-11-07 7:12 ` Jason Brittain
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 15:37 Juergen Keil
2004-11-05 15:43 ` zitu
2004-11-05 15:45 ` zitu
2004-11-05 15:52 ` Jens Axboe
2004-11-05 16:10 ` zitu
2004-11-05 17:30 ` Damien Mascord
2004-11-12 14:27 Juergen Keil
2004-11-12 18:02 ` Jason Brittain
2004-11-12 19:07 Juergen Keil
2004-11-16 19:41 ` Juergen Lock
2004-11-23 5:12 ` Norikatsu Shigemura
2004-11-25 21:12 ` Juergen Lock
2004-11-26 10:48 Juergen Keil
2004-11-28 20:09 ` Juergen Lock
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=4193B738.70106@brittainweb.org \
--to=jason@brittainweb.org \
--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).