From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: pvgrub boot problems Date: Sun, 28 Mar 2010 11:12:15 +0200 Message-ID: <20100328091215.GD7497@const.famille.thibault.fr> References: <20100327105311.GU1878@reaktio.net> <20100327112400.GW1878@reaktio.net> <4BAE856E.5090902@goop.org> <4BAE8FD1.1000700@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: M A Young Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org M A Young, le Sat 27 Mar 2010 23:34:58 +0000, a =E9crit : > 3) it doesn't work well with the > disk =3D [ 'phy:mapper/VolGroup00-austen1,xvda1,w' ] > option. pygrub sees this as (hd0,0) as I think does the booted OS (thou= gh=20 > I can't say I have actually tested this), but pygrub sees this as (hd0)= .=20 Yes, I had added documentation about this issue that will be far from easy to fix within pvgrub itself. Samuel