From: Ryan Harper <ryanh@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ryan Harper <ryanh@us.ibm.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [PATCH] add virtio disk geometry feature
Date: Thu, 17 Apr 2008 09:37:38 -0500 [thread overview]
Message-ID: <20080417143738.GE17938@us.ibm.com> (raw)
In-Reply-To: <4806706E.10701@us.ibm.com>
* Anthony Liguori <aliguori@us.ibm.com> [2008-04-16 16:33]:
> Rusty Russell wrote:
> >On Thursday 17 April 2008 04:56:37 Ryan Harper wrote:
> >
> >>From: Ryan Harper <ryanh@us.ibm.com>
> >>
> >>Rather than faking up some geometry, allow the backend to push the disk
> >>geometry via virtio pci config option. Keep the old geo code around for
> >>compatibility.
> >>
> >
> >Hi Ryan,
> >
> > Looks good! Some brief review below. Mainly just "how I would have done
> >things" stuff. BTW, does this help in real life? I assume something in
> >userspace wants it?
> >
>
> Boot loaders (like grub) query the geometry from the kernel to figure
> out how to setup the stage1/stage2. We've seen strange issues with grub
> thinking it has crazy geometries when installed on a virtio disk (as
> opposed to booting from virtio with an existing disk).
>
> Ryan: have you tested a hardy install with your patches? Does it help
> when installing to virtio? I could pretty reliably reproduce the
> strangeness with a 20GB disk image FWIW.
I had tested out hardy with a 10G disk and saw nothing out of the
ordinary. Disk size was the expected value and grub had no issues with
it.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2008-04-17 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 18:56 [PATCH] add virtio disk geometry feature Ryan Harper
2008-04-16 18:56 ` Ryan Harper
2008-04-16 21:15 ` Rusty Russell
2008-04-16 21:15 ` Rusty Russell
2008-04-16 21:32 ` Anthony Liguori
2008-04-16 21:32 ` Anthony Liguori
2008-04-16 21:32 ` Anthony Liguori
2008-04-16 21:57 ` Hollis Blanchard
2008-04-16 21:57 ` Hollis Blanchard
2008-04-16 21:57 ` Hollis Blanchard
2008-04-17 14:37 ` Ryan Harper [this message]
2008-04-17 14:37 ` Ryan Harper
2008-04-16 21:15 ` Rusty Russell
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=20080417143738.GE17938@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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.