From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Haigh Subject: Re: pv-grub and grub.conf locations Date: Fri, 07 Nov 2014 22:40:55 +1100 Message-ID: <545CAFC7.20501@crc.id.au> References: <545BFBB3.9010303@crc.id.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5809313341831803676==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============5809313341831803676== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Wjoho6aNJqOuQWEwaBaL2thTqmann8lQK" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Wjoho6aNJqOuQWEwaBaL2thTqmann8lQK Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 7/11/2014 10:19 PM, Stefano Stabellini wrote: > On Fri, 7 Nov 2014, Steven Haigh wrote: >> Hi Stefano, >> >> Sorry to hassle you directly - but I'm trying to figure out a use case= >> of pv-grub to replace most pygrub configurations. >=20 > No worries. I CC'ed xen-devel, because I think that this is an > interesting question that could be useful to other people too. >=20 >=20 >> I have two main locations where the grub config may live: >> 1) (hd0)/boot/grub/grub.conf or >> 2) (hd0,0)/boot/grub/grub.conf >> >> This depends if the DomU is created by something like the debian >> installer which refuses to install to a 'whole disk' - or say my EL6 >> kickstart which installs to /dev/xvda as ext4 (which is easier to mana= ge). >> >> From what I've been reading, there is no way to pass both of these to >> pv-grub and let it deal with whichever one exists. >> >> Interestingly, pygrub seems to search all paths to make this work - ie= >> you only need to specify: >> bootloader =3D 'pygrub' >> >> As I'm trying to generate generic config files, it makes life much >> harder to implement pv-grub as the loader (even though its preferred).= >> >> Any thoughts on this? >=20 > Unfortunately it doesn't look like there is a way to do that at the > moment. But I agree it would be useful and we might be able to make it > work for the next release (Xen 4.6). >=20 Well, from digging through the grub 0.97 documentation, it *may* be possible - however documentation on pv-grub seems to be very rare. Interestingly, from the grub documentation: 13.3.11 find =97 Command: find filename Search for the file name filename in all mountable partitions and print the list of the devices which contain the file. The file name filename should be an absolute file name like /boot/grub/stage1. Also: 13.3.6 configfile =97 Command: configfile file Load file as a configuration file. It wouldn't be too hard to imagine a grub configuration script that could be loaded (somehow) into the 'extra' section of the DomU config that basically passes the output of 'find /boot/grub/grub.conf' to configfile $result and uses that to boot. This may actually be possible already - but I haven't found any documentation that points to it or any configurations that have been published. Any further feedback from anyone who has seen this may help out... --=20 Steven Haigh Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 --Wjoho6aNJqOuQWEwaBaL2thTqmann8lQK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUXK/OAAoJEEGvNdV6fTHcSEYQAKdZMiTEdj/9He5TQaxlr1Ni 9LvctSEUYkFOJ0Wlzgh95XKhrpXidaDQ8lm481kC90KpgFrFvGU4H9WHPlvnDZ2f BTwNP+NMHHP4hBjib85yE3dcWYFUNBbXDqtea2AYlcn6FWbaQYdyqrv2VAn04ebj /NcYIb0HdnjdaYa7luasu2iDQ1YUt8mo2U/rDj8UXehIRxWvGqGbDrWbkHE6QHeY N6eoB1gUcNfEKLycjQdretYM4zfMRsYlhn9GcyoNN3TJyjS/89zZOC1UP6yvUwfs E1+GTiYQIaJ4DtoulMK21HKiFgAuQywNKKZqujSW3wqNbEptpe/5rQk7g9MVvwfM a8N9ycFs8UhDuJY9QH2r9El9qfcwwWUXb3oAhHT1LRXOlmE1dCdo6DzF40ZorPMk N69sWok+Ci2NOluZNbfs8jOv9KVqFqTLKOw4WFDsVZTshk/uhfEnVyhUah5BDnae hFe2J6KkxgWWsrWB3bKPsCMtZekHDLheLWPk4+zl172uO9Yk1oST79B1s0ihv6Hr EWRSV+ztJCWkufuwfLUL+7PfABMgzl/JQ+x4f/iFw10ILGyJelXaTjLQOvBVYfoy ZGkNWXyzVMHgV9/XqU4zpcsYsLb7MVrVoAEUy/DFBsVuw7aJDi3+v/PeaWtXkiK8 Ns0lahRsBs1zS6nYo9yI =BjMF -----END PGP SIGNATURE----- --Wjoho6aNJqOuQWEwaBaL2thTqmann8lQK-- --===============5809313341831803676== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============5809313341831803676==--