All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Brittain <jason@brittainweb.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img documentation
Date: Tue, 16 Nov 2004 07:17:23 -0800	[thread overview]
Message-ID: <419A1A03.9010707@brittainweb.org> (raw)
In-Reply-To: <4199B04F.8020307@railnet.it>

ML wrote:
> ---
> Fabrice Bellard said the following on 11/16/2004 02:46 AM:
> 
>> Try my last fix. The important fix is in 
>> hw/ide.c:ide_guess_geometry(). I think the problem is that after 
>> reboot when installing ide_guess_geometry() returns an invalid 
>> geometry because the BIOS translated geometry is stored in the MBR 
>> instead of the real hard disk geometry.
>>
>> For the desperate user, I added an option to manually specify the BIOS 
>> translation mode.
> 
> With this fix now I can boot XP images newly created with 0.6.1 but I 
> can't boot any longer my older images created with versions < 0.6.1 
> unless I specify hda geometry on the command line.

This is going to cause lots of people to not be able to figure out
how to use qemu anymore after an upgrade.  For example, even if I
knew that I needed to use the -hdachs option (pronounced "headaches"),
how would I know what geometry numbers to give it?  I'm not real
good with this sort of thing, and I haven't found any docs yet that
try to explain it from the perspective of a VM user.  I know, I know,
you can't have everything.  But, I do think this will cause users
repeated hdachs.  :)

-- 
Jason Brittain

  reply	other threads:[~2004-11-16 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 22:58 [Qemu-devel] qemu-img documentation Fabrice Bellard
2004-11-15 23:04 ` Hetz Ben Hamo
2004-11-16  1:46   ` Fabrice Bellard
2004-11-16  7:46     ` ML
2004-11-16 15:17       ` Jason Brittain [this message]
2004-11-16 15:42         ` Panagiotis Issaris
2004-11-16 15:53           ` Johannes Schindelin
2004-11-17  8:09           ` ML
2004-11-17 21:56             ` Jim C. Brown
2004-11-16 21:45         ` Fabrice Bellard

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=419A1A03.9010707@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 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.