From: Avi Kivity <avi@qumranet.com>
To: David Mair <dmair@mair-family.org>
Cc: KVM list <kvm@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 63 sectors
Date: Wed, 03 Sep 2008 12:32:11 +0300 [thread overview]
Message-ID: <48BE599B.9020709@qumranet.com> (raw)
In-Reply-To: <48BE4C43.1010401@mair-family.org>
David Mair wrote:
> A solution used on another platform I'm familiar with is for the
> platform's storage drivers to report disk geometry as having have 32
> sectors per track. The native partitioning tool will then always
> create partitions with 32 sector alignment. It's possible a BIOS
> change could be made to achieve that.
>
I tried 60 sectors per track, but Windows saw the disk as an 8GB disk
and refused to format. Linux had similar problems.
>> Does anybody know if scsi will have the same problems? Can anyone
>> suggest other workarounds?
>
> If you are using a guest platform like linux and don't need multiple
> file systems on the same [virtual] disk then just format the whole
> disk rather than partition it:
>
> # mkfs -t ext3 /dev/sdb
>
> (instead of /dev/sdb1, 2, 3, etc)
That won't work with the installers (at least not simply), and doesn't
allow for a swap partition.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-09-03 9:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 8:12 63 sectors Avi Kivity
2008-09-03 8:35 ` David Mair
2008-09-03 9:32 ` Avi Kivity [this message]
2008-09-03 11:26 ` Gerd Hoffmann
2008-09-04 8:49 ` Gerd Hoffmann
2008-09-03 16:15 ` H. Peter Anvin
2008-09-04 3:20 ` Liu Yu-B13201
2008-09-04 3:33 ` H. Peter Anvin
2008-09-04 3:39 ` Liu Yu-B13201
2008-09-04 3:56 ` H. Peter Anvin
2008-09-04 7:47 ` Itamar Heim
2008-09-07 8:20 ` Avi Kivity
2008-09-04 8:58 ` Ian Kirk
2008-09-04 11:15 ` Laurent Vivier
2008-09-04 12:18 ` H. Peter Anvin
2008-09-04 13:56 ` H. Peter Anvin
2008-09-04 17:56 ` Charles Duffy
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=48BE599B.9020709@qumranet.com \
--to=avi@qumranet.com \
--cc=dmair@mair-family.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.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