From: Kevin O'Connor <kevin@koconnor.net>
To: CurtisNelson <586175@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 586175] Re: Windows XP/2003 doesn't boot
Date: Fri, 30 Jul 2010 11:19:06 -0400 [thread overview]
Message-ID: <20100730151906.GA28029@morn.localdomain> (raw)
In-Reply-To: <20100725201524.18685.89912.malone@potassium.ubuntu.com>
On Sun, Jul 25, 2010 at 08:15:24PM -0000, CurtisNelson wrote:
> My next step at this point was to install hexedit and compare the two
> resulting images. Specifically, the mbr at the beginning of the disk
> and the ntfs partition starting at sector 63. On the net there is some
> talk about changing 0x7E1A to 'FF' -- which is supposed to indicate disk
> geometry of the ntfs partition. There were three values that were
> different at this point in the ntfs file region -- 0x8E18, 0x7E1A, and
> 0x7E1C. The first two did not seem to have any effect. But changing
> 0x7E1C to the value of '3F' would result in the image booting properly.
> Evidently this is the part of the NTFS file system that records the
> starting sector of the partition. This change successfully booted all
> my test cases restores with a single partition.
This looks like some hd geometry confusion. You could try playing
with the qemu "-hdachs" option to force a different geometry
translation.
You might also want to capture the seabios log to see what it thinks
the drive geometry is. On qemu you can add the following to the
command-line to see the seabios log:
qemu -chardev stdio,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios
look for lines like:
"drive %p: PCHS=%u/%d/%d translation=%s LCHS=%d/%d/%d s=%d\n"
-Kevin
next prev parent reply other threads:[~2010-07-30 15:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 2:37 [Qemu-devel] [Bug 586175] [NEW] Windows XP/2003 doesn't boot tekditt
2010-05-27 14:11 ` [Qemu-devel] [Bug 586175] " Cole Robinson
2010-05-27 14:21 ` Anthony Liguori
2010-05-27 14:24 ` Natalia Portillo
2010-05-27 15:11 ` tekditt
2010-06-02 16:32 ` Joel Schopp
2010-06-02 22:10 ` Ryan Harper
2010-06-09 17:33 ` tekditt
2010-06-09 20:33 ` Ryan Harper
2010-06-20 12:50 ` Olivier Berger
2010-06-20 13:16 ` Bug Watch Updater
2010-06-20 13:40 ` Gleb Natapov
2010-06-25 15:55 ` Cole Robinson
2010-06-26 5:27 ` Markus Armbruster
2010-07-02 22:41 ` tekditt
2010-07-07 18:05 ` Jona
2010-07-22 1:51 ` tekditt
2010-07-22 1:53 ` tekditt
2010-07-22 6:53 ` Olivier Berger
2010-07-22 22:42 ` tekditt
2010-07-25 20:15 ` CurtisNelson
2010-07-30 15:19 ` Kevin O'Connor [this message]
2010-07-25 23:57 ` CurtisNelson
2010-07-27 20:41 ` flashydave
2010-07-28 1:55 ` Mathias Gug
2010-07-30 18:56 ` James Pulver
2010-08-01 17:46 ` Andreas Jacob
2010-08-02 14:31 ` Andy Lee Robinson
2010-08-02 15:00 ` Andreas Jacob
2010-08-02 16:53 ` Jt Loni
2010-08-02 18:43 ` Andy Lee Robinson
2010-08-04 15:54 ` Bug Watch Updater
2010-08-10 11:14 ` Michael Tokarev
2010-08-10 11:16 ` Michael Tokarev
2010-08-19 21:58 ` Michael Tokarev
2010-08-29 18:45 ` tekditt
2010-08-29 18:52 ` tekditt
2010-08-29 21:13 ` Michael Tokarev
2010-09-16 1:00 ` Launchpad Bug Tracker
2010-09-16 1:15 ` Launchpad Bug Tracker
2010-10-17 22:58 ` tekditt
2010-10-18 6:55 ` Michael Tokarev
2011-02-20 17:16 ` Aurelien Jarno
2017-10-27 7:07 ` Bug Watch Updater
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=20100730151906.GA28029@morn.localdomain \
--to=kevin@koconnor.net \
--cc=586175@bugs.launchpad.net \
--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).