qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] whats up with QEMU and virtual disks?
Date: Tue, 16 Nov 2004 00:02:16 +0100	[thread overview]
Message-ID: <41993578.5030804@bellard.org> (raw)
In-Reply-To: <41e41e7a041115140120b83bf8@mail.gmail.com>

Hetz Ben Hamo wrote:
>>>in both cases, the only way to bypass this problem is by using the
>>>-hdachs parameter..
>>>Why? what has changed that broke the normal behavior? how can it be fixed?
>>
>>My quick and dirty fix of commenting out the call to bdrv_set_geometry_hint in
>>line 1898 of hw/ide.c doesn't appear to work anymore with the disk image newly
>>created with the 0.6.1 version.
>>However my older disk images, created with previous versions of Qemu, don't
>>work with 0.6.1 (it says that NTLDR is missing) but, if I comment out the line
>>as per above, everything goes back to normal behavior.
> 
> 
> I see...
> 
> Fabrice, since this change breaks compatibility, is there a way to either:
> 
> * Add a parameter to load "old" images with the old bdrv_set_geometry_hint 

No one gave precise enough information to fix the problem. The problem 
is related to the default Bochs BIOS tranlation mode, and I would like 
to understand first before doing a fix.

> * Provide a simple script to convert from the old to new format?

If it is the only solution, I can do it, but there may be a better one.

> One more thing Fabrice, regarding the message about the RTC. Could you
> detect if the user is running 2.6.x kernel and if so, avoid showing
> the RTC message please?

I'll try.

Fabrice.

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 21:14 [Qemu-devel] whats up with QEMU and virtual disks? Hetz Ben Hamo
2004-11-15 21:40 ` ML
2004-11-15 22:01   ` Hetz Ben Hamo
2004-11-15 23:02     ` Fabrice Bellard [this message]
2004-11-16  0:12       ` Fabrice Bellard
2004-11-16  0:18         ` 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=41993578.5030804@bellard.org \
    --to=fabrice@bellard.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).