Re: [Xen-devel] pvgrub2 is merged
On Sat, 2013-11-09 at 21:52 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: Hello, all. pvgrub2 has just became part of upstream grub as ports i386-xen and x86_64-xen. This is super cool, thanks! http://git.savannah.gnu.org/cgit/grub.git Documentation on its usage is missing for now but in short: ARCH=x86_64 ./autogen.sh ./configure --target=$ARCH --with-platform=xen Does this enable Xen statically for the resulting binaries or is it a dynamic/boot time selection between Xen and native? Also, does this require any code from Xen (libxc, minios etc) at build time or is it completely standalone? (I'm asking because I'm thinking how to enable this in distro packaging...) Ian. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: pvgrub2 is merged
On 10.11.2013 05:47, Andrey Borzenkov wrote: В Sat, 09 Nov 2013 21:52:20 +0100 Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com пишет: Hello, all. pvgrub2 has just became part of upstream grub as ports i386-xen and x86_64-xen. http://git.savannah.gnu.org/cgit/grub.git Documentation on its usage is missing for now but in short: ARCH=x86_64 ./autogen.sh ./configure --target=$ARCH --with-platform=xen make mkdir -p boot/grub/ cat boot/grub/grub.cfg EOF search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O $ARCH-xen -d grub-core/ boot/grub/grub.cfg Do I understand it correctly that to use grub.xen it is enough to add kernel = /path/to/grub.xen to guest configuration? Yes signature.asc Description: OpenPGP digital signature ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 11.11.2013 11:10, Ian Campbell wrote: On Sat, 2013-11-09 at 21:52 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: Hello, all. pvgrub2 has just became part of upstream grub as ports i386-xen and x86_64-xen. This is super cool, thanks! You're welcome http://git.savannah.gnu.org/cgit/grub.git Documentation on its usage is missing for now but in short: ARCH=x86_64 ./autogen.sh ./configure --target=$ARCH --with-platform=xen Does this enable Xen statically for the resulting binaries or is it a dynamic/boot time selection between Xen and native? The result binaries are xen only. Dynamic selection makes very little sense for bootloader. Also, does this require any code from Xen (libxc, minios etc) at build time or is it completely standalone? It needs xen headers (/ur/include/xen). On debian those are in libxen-devel (I'm asking because I'm thinking how to enable this in distro packaging...) Ian. signature.asc Description: OpenPGP digital signature ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On Mon, 2013-11-11 at 12:54 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 11.11.2013 11:10, Ian Campbell wrote: On Sat, 2013-11-09 at 21:52 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: Hello, all. pvgrub2 has just became part of upstream grub as ports i386-xen and x86_64-xen. This is super cool, thanks! You're welcome http://git.savannah.gnu.org/cgit/grub.git Documentation on its usage is missing for now but in short: ARCH=x86_64 ./autogen.sh ./configure --target=$ARCH --with-platform=xen Does this enable Xen statically for the resulting binaries or is it a dynamic/boot time selection between Xen and native? The result binaries are xen only. Dynamic selection makes very little sense for bootloader. Right this is what I expected. Can it coexist alright with a native grub? e.g. will grub-makestandalone pick the right inputs based on -O $arch-xen instead of -O $arch? Also, does this require any code from Xen (libxc, minios etc) at build time or is it completely standalone? It needs xen headers (/ur/include/xen). On debian those are in libxen-devel So no requirement for e.g. a Xen source tree. That should make things much easier for the distros... Thanks. Ian. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 11.11.2013 13:06, Ian Campbell wrote:
On Mon, 2013-11-11 at 12:54 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
On 11.11.2013 11:10, Ian Campbell wrote:
On Sat, 2013-11-09 at 21:52 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
Hello, all. pvgrub2 has just became part of upstream grub as ports
i386-xen and x86_64-xen.
This is super cool, thanks!
You're welcome
http://git.savannah.gnu.org/cgit/grub.git
Documentation on its usage is missing for now but in short:
ARCH=x86_64
./autogen.sh
./configure --target=$ARCH --with-platform=xen
Does this enable Xen statically for the resulting binaries or is it a
dynamic/boot time selection between Xen and native?
The result binaries are xen only. Dynamic selection makes very little
sense for bootloader.
Right this is what I expected.
Can it coexist alright with a native grub? e.g. will grub-makestandalone
pick the right inputs based on -O $arch-xen instead of -O $arch?
Coexistance of ports is no problem. All files between ports which share
the name also share the contents. Files which differ have different
names ( E.g.
/usr/lib/grub/{i386-pc,i386-efi,i386-xen,x86_64-xen,x86_64-efi}/*.mod)
Also, does this require any code from Xen (libxc, minios etc) at build
time or is it completely standalone?
It needs xen headers (/ur/include/xen). On debian those are in libxen-devel
So no requirement for e.g. a Xen source tree. That should make things
much easier for the distros...
Thanks.
Ian.
signature.asc
Description: OpenPGP digital signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [PATCH] remove dependency on /boot/config-* in grub.d/20_linux_xen
On Sun, Nov 10, 2013 at 09:40:29PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 15.07.2013 20:00, Konrad Rzeszutek Wilk wrote: Hey, There is a discussion on the linux-kernel mailing list in which the Linus states that if you depend on any config file, you're broken by definition (https://lkml.org/lkml/2013/7/15/368). Please try my grub_file branch: http://git.savannah.gnu.org/cgit/grub.git/log/?h=phcoder/grub_file It should do what you want. Will do this week! Thank you! ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: Install_c merge intention
В Sun, 10 Nov 2013 16:38:09 +0100 Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com пишет: On 10.11.2013 15:52, Andrey Borzenkov wrote: В Sat, 09 Nov 2013 13:51:09 +0100 Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com пишет: Hello, all. install_c is feature complete and I intent to make it upstream unless issues are raised until 16 Nov. It's available under http://git.savannah.gnu.org/cgit/grub.git/log/?h=phcoder/install_c As was discussed before - shell grub-istall provides relatively easy way to track what is done (which modules are selected etc). Binary grub-install does not. It was suggested to enable easy access to this information (like echoing invocations of grub-mkimage and grub-setup). This is missing currently. I added it. Is the one I added enough? Yes, thank you. May be having basic verbose level that just prints them would be better, but that's something that can be implemented later. - looks like shell backticks in /etc/default/grub are not evaluated or I missed it. Only normal shell quoting is interpreted. There are 2 routines for loading config: Use sh helper or read directly. We use sh helper when on unix-like OS and sh is available. Yes, I missed it. - I guess before merging obsolete shell commands should be removed? They are still present. Yes, it's to avoid messing with conflicts in deleted files. They'll be removed in merge ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel signature.asc Description: PGP signature ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
