Re: [Xen-devel] pvgrub2 is merged
Hello Vladimir, sorry to resurrect an old thread and to top-post, but I noticed that in upstream grub the xenfb driver has been reverted. Is that because of this bug? If so, you should know that the bug has been fixed in QEMU. Thanks, Stefano On Fri, 20 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 19.12.2013 12:54, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 18.12.2013 20:39, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 17.12.2013 15:35, Fabio Fantoni wrote: Il 17/12/2013 15:10, Fabio Fantoni ha scritto: Il 17/12/2013 15:08, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: Thanks. Now there is another error, probably introduced by xenfb support: doesn't look like related to xenfb. Is it 64-bit or PAE guest? 64 bit I did git reset --hard to commit Remove grub_bios_interrupt on coreboot. and then I applied only grub-core/lib/x86_64/xen/relocator.S: Fix hypercall ABI violation. commit. Now the Sid domU boot correctly, therefore the regression is caused by xenfb or xen grants to v1 commit, should I find the exact commit that causes that problem or these informations are enough for you? It's because of vfb. Apparently vfb framebuffer stays mapped as rw even after vfb shutdown phcoder@debian:15:52:40:~/grub2$ sudo xenstore-ls /local/domain/54/device/vfb 0 = backend = /local/domain/0/backend/vfb/54/0 backend-id = 0 state = 1 phcoder@debian:15:52:51:~/grub2$ sudo xenstore-ls /local/domain/0/backend/vfb/54/0 frontend = /local/domain/54/device/vfb/0 frontend-id = 54 online = 1 state = 2 domain = grub vnc = 1 vnclisten = 127.0.0.1 vncdisplay = 0 vncunused = 1 sdl = 0 opengl = 0 feature-resize = 1 hotplug-status = connected When I do dry vfb: do everything except writing vfb state problem disappears. So my question would be: - how can I inspect how backend maps framebuffer pages? There is only one xenfb backend: hw/display/xenfb.c in the QEMU source tree. - Why does it map as rw and not ro? It doesn't need to write to framebuffer? Actually it is mapping it RO, see hw/display/xenfb.c:xenfb_map_fb ./tools/qemu-xen-dir-remote/hw/xenfb.c: xenfb-pixels = xc_map_foreign_pages(xen_xc, xenfb-c.xendev.dom, PROT_READ | PROT_WRITE, fbmfns, xenfb-fbpages); You are right, my bad. I did a quick test and it should be safe to modify it to PROT_READ only. - How do I force it to drop the mapping? Theoretically QEMU should drop the mapping at disconnect time: hw/display/xenfb.c:fb_disconnect /* * FIXME: qemu can't un-init gfx display (yet?). * Replacing the framebuffer with anonymous shared memory * instead. This releases the guest pages and keeps qemu happy. */ fb-pixels = mmap(fb-pixels, fb-fbpages * XC_PAGE_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0); Could this fail? Yes and we don't check for the return value (-1 in case of error). Well spotted! Do you want to submit a patch to fix both issues or should I do it? I'm fine with you doing it. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On Fri, 20 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 19.12.2013 12:54, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 18.12.2013 20:39, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 17.12.2013 15:35, Fabio Fantoni wrote: Il 17/12/2013 15:10, Fabio Fantoni ha scritto: Il 17/12/2013 15:08, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: Thanks. Now there is another error, probably introduced by xenfb support: doesn't look like related to xenfb. Is it 64-bit or PAE guest? 64 bit I did git reset --hard to commit Remove grub_bios_interrupt on coreboot. and then I applied only grub-core/lib/x86_64/xen/relocator.S: Fix hypercall ABI violation. commit. Now the Sid domU boot correctly, therefore the regression is caused by xenfb or xen grants to v1 commit, should I find the exact commit that causes that problem or these informations are enough for you? It's because of vfb. Apparently vfb framebuffer stays mapped as rw even after vfb shutdown phcoder@debian:15:52:40:~/grub2$ sudo xenstore-ls /local/domain/54/device/vfb 0 = backend = /local/domain/0/backend/vfb/54/0 backend-id = 0 state = 1 phcoder@debian:15:52:51:~/grub2$ sudo xenstore-ls /local/domain/0/backend/vfb/54/0 frontend = /local/domain/54/device/vfb/0 frontend-id = 54 online = 1 state = 2 domain = grub vnc = 1 vnclisten = 127.0.0.1 vncdisplay = 0 vncunused = 1 sdl = 0 opengl = 0 feature-resize = 1 hotplug-status = connected When I do dry vfb: do everything except writing vfb state problem disappears. So my question would be: - how can I inspect how backend maps framebuffer pages? There is only one xenfb backend: hw/display/xenfb.c in the QEMU source tree. - Why does it map as rw and not ro? It doesn't need to write to framebuffer? Actually it is mapping it RO, see hw/display/xenfb.c:xenfb_map_fb ./tools/qemu-xen-dir-remote/hw/xenfb.c: xenfb-pixels = xc_map_foreign_pages(xen_xc, xenfb-c.xendev.dom, PROT_READ | PROT_WRITE, fbmfns, xenfb-fbpages); You are right, my bad. I did a quick test and it should be safe to modify it to PROT_READ only. - How do I force it to drop the mapping? Theoretically QEMU should drop the mapping at disconnect time: hw/display/xenfb.c:fb_disconnect /* * FIXME: qemu can't un-init gfx display (yet?). * Replacing the framebuffer with anonymous shared memory * instead. This releases the guest pages and keeps qemu happy. */ fb-pixels = mmap(fb-pixels, fb-fbpages * XC_PAGE_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0); Could this fail? Yes and we don't check for the return value (-1 in case of error). Well spotted! Do you want to submit a patch to fix both issues or should I do it? I'm fine with you doing it. Done, see: http://marc.info/?l=qemu-develm=138901099512700w=2___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 11/12/2013 11:51, Ian Campbell wrote: On Wed, 2013-12-11 at 12:47 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: I can't confirm for 100% now, but I'll be 90-95% at FOSDEM and if I'll be ther I'm ok to give a talk. Is this offer still on the table? I'm afraid the deadline for submissions has passed (IIRC it was 1 December, at least for the virt devroom). There is a possibility to give an appropriate talk the day before FOSDEM at a CentOS DoJo which will be hosted at IBM in Brusseles. I will talk to the organizer later today as it is not yet clear what the format of the DoJo will be (just talks or a mixture of Hackathon and talks). Regards Lars ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 19.12.2013 12:54, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 18.12.2013 20:39, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 17.12.2013 15:35, Fabio Fantoni wrote: Il 17/12/2013 15:10, Fabio Fantoni ha scritto: Il 17/12/2013 15:08, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: Thanks. Now there is another error, probably introduced by xenfb support: doesn't look like related to xenfb. Is it 64-bit or PAE guest? 64 bit I did git reset --hard to commit Remove grub_bios_interrupt on coreboot. and then I applied only grub-core/lib/x86_64/xen/relocator.S: Fix hypercall ABI violation. commit. Now the Sid domU boot correctly, therefore the regression is caused by xenfb or xen grants to v1 commit, should I find the exact commit that causes that problem or these informations are enough for you? It's because of vfb. Apparently vfb framebuffer stays mapped as rw even after vfb shutdown phcoder@debian:15:52:40:~/grub2$ sudo xenstore-ls /local/domain/54/device/vfb 0 = backend = /local/domain/0/backend/vfb/54/0 backend-id = 0 state = 1 phcoder@debian:15:52:51:~/grub2$ sudo xenstore-ls /local/domain/0/backend/vfb/54/0 frontend = /local/domain/54/device/vfb/0 frontend-id = 54 online = 1 state = 2 domain = grub vnc = 1 vnclisten = 127.0.0.1 vncdisplay = 0 vncunused = 1 sdl = 0 opengl = 0 feature-resize = 1 hotplug-status = connected When I do dry vfb: do everything except writing vfb state problem disappears. So my question would be: - how can I inspect how backend maps framebuffer pages? There is only one xenfb backend: hw/display/xenfb.c in the QEMU source tree. - Why does it map as rw and not ro? It doesn't need to write to framebuffer? Actually it is mapping it RO, see hw/display/xenfb.c:xenfb_map_fb ./tools/qemu-xen-dir-remote/hw/xenfb.c: xenfb-pixels = xc_map_foreign_pages(xen_xc, xenfb-c.xendev.dom, PROT_READ | PROT_WRITE, fbmfns, xenfb-fbpages); You are right, my bad. I did a quick test and it should be safe to modify it to PROT_READ only. - How do I force it to drop the mapping? Theoretically QEMU should drop the mapping at disconnect time: hw/display/xenfb.c:fb_disconnect /* * FIXME: qemu can't un-init gfx display (yet?). * Replacing the framebuffer with anonymous shared memory * instead. This releases the guest pages and keeps qemu happy. */ fb-pixels = mmap(fb-pixels, fb-fbpages * XC_PAGE_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0); Could this fail? Yes and we don't check for the return value (-1 in case of error). Well spotted! Do you want to submit a patch to fix both issues or should I do it? I'm fine with you doing it. 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 Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 17.12.2013 15:35, Fabio Fantoni wrote: Il 17/12/2013 15:10, Fabio Fantoni ha scritto: Il 17/12/2013 15:08, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: Thanks. Now there is another error, probably introduced by xenfb support: doesn't look like related to xenfb. Is it 64-bit or PAE guest? 64 bit I did git reset --hard to commit Remove grub_bios_interrupt on coreboot. and then I applied only grub-core/lib/x86_64/xen/relocator.S: Fix hypercall ABI violation. commit. Now the Sid domU boot correctly, therefore the regression is caused by xenfb or xen grants to v1 commit, should I find the exact commit that causes that problem or these informations are enough for you? It's because of vfb. Apparently vfb framebuffer stays mapped as rw even after vfb shutdown phcoder@debian:15:52:40:~/grub2$ sudo xenstore-ls /local/domain/54/device/vfb 0 = backend = /local/domain/0/backend/vfb/54/0 backend-id = 0 state = 1 phcoder@debian:15:52:51:~/grub2$ sudo xenstore-ls /local/domain/0/backend/vfb/54/0 frontend = /local/domain/54/device/vfb/0 frontend-id = 54 online = 1 state = 2 domain = grub vnc = 1 vnclisten = 127.0.0.1 vncdisplay = 0 vncunused = 1 sdl = 0 opengl = 0 feature-resize = 1 hotplug-status = connected When I do dry vfb: do everything except writing vfb state problem disappears. So my question would be: - how can I inspect how backend maps framebuffer pages? There is only one xenfb backend: hw/display/xenfb.c in the QEMU source tree. - Why does it map as rw and not ro? It doesn't need to write to framebuffer? Actually it is mapping it RO, see hw/display/xenfb.c:xenfb_map_fb - How do I force it to drop the mapping? Theoretically QEMU should drop the mapping at disconnect time: hw/display/xenfb.c:fb_disconnect /* * FIXME: qemu can't un-init gfx display (yet?). * Replacing the framebuffer with anonymous shared memory * instead. This releases the guest pages and keeps qemu happy. */ fb-pixels = mmap(fb-pixels, fb-fbpages * XC_PAGE_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0);___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 18.12.2013 20:39, Stefano Stabellini wrote: On Wed, 18 Dec 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 17.12.2013 15:35, Fabio Fantoni wrote: Il 17/12/2013 15:10, Fabio Fantoni ha scritto: Il 17/12/2013 15:08, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: Thanks. Now there is another error, probably introduced by xenfb support: doesn't look like related to xenfb. Is it 64-bit or PAE guest? 64 bit I did git reset --hard to commit Remove grub_bios_interrupt on coreboot. and then I applied only grub-core/lib/x86_64/xen/relocator.S: Fix hypercall ABI violation. commit. Now the Sid domU boot correctly, therefore the regression is caused by xenfb or xen grants to v1 commit, should I find the exact commit that causes that problem or these informations are enough for you? It's because of vfb. Apparently vfb framebuffer stays mapped as rw even after vfb shutdown phcoder@debian:15:52:40:~/grub2$ sudo xenstore-ls /local/domain/54/device/vfb 0 = backend = /local/domain/0/backend/vfb/54/0 backend-id = 0 state = 1 phcoder@debian:15:52:51:~/grub2$ sudo xenstore-ls /local/domain/0/backend/vfb/54/0 frontend = /local/domain/54/device/vfb/0 frontend-id = 54 online = 1 state = 2 domain = grub vnc = 1 vnclisten = 127.0.0.1 vncdisplay = 0 vncunused = 1 sdl = 0 opengl = 0 feature-resize = 1 hotplug-status = connected When I do dry vfb: do everything except writing vfb state problem disappears. So my question would be: - how can I inspect how backend maps framebuffer pages? There is only one xenfb backend: hw/display/xenfb.c in the QEMU source tree. - Why does it map as rw and not ro? It doesn't need to write to framebuffer? Actually it is mapping it RO, see hw/display/xenfb.c:xenfb_map_fb ./tools/qemu-xen-dir-remote/hw/xenfb.c: xenfb-pixels = xc_map_foreign_pages(xen_xc, xenfb-c.xendev.dom, PROT_READ | PROT_WRITE, fbmfns, xenfb-fbpages); - How do I force it to drop the mapping? Theoretically QEMU should drop the mapping at disconnect time: hw/display/xenfb.c:fb_disconnect /* * FIXME: qemu can't un-init gfx display (yet?). * Replacing the framebuffer with anonymous shared memory * instead. This releases the guest pages and keeps qemu happy. */ fb-pixels = mmap(fb-pixels, fb-fbpages * XC_PAGE_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0); Could this fail? 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
Il 09/12/2013 11:06, Fabio Fantoni ha scritto: Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug grub boot
Re: [Xen-devel] pvgrub2 is merged
On 17.12.2013 11:44, Fabio Fantoni wrote: Il 09/12/2013 11:06, Fabio Fantoni ha scritto: Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set
Re: [Xen-devel] pvgrub2 is merged
On 17.12.2013 11:44, Fabio Fantoni wrote: Il 09/12/2013 11:06, Fabio Fantoni ha scritto: Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set
Re: [Xen-devel] pvgrub2 is merged
Il 17/12/2013 12:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 17.12.2013 11:44, Fabio Fantoni wrote: Il 09/12/2013 11:06, Fabio Fantoni ha scritto: Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub
Re: [Xen-devel] pvgrub2 is merged
On 17.12.2013 14:11, Fabio Fantoni wrote: Il 17/12/2013 12:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 17.12.2013 11:44, Fabio Fantoni wrote: Il 09/12/2013 11:06, Fabio Fantoni ha scritto: Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd.
Re: [Xen-devel] pvgrub2 is merged
Il 17/12/2013 14:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 17.12.2013 14:11, Fabio Fantoni wrote: Il 17/12/2013 12:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 17.12.2013 11:44, Fabio Fantoni wrote: Il 09/12/2013 11:06, Fabio Fantoni ha scritto: Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and
Re: [Xen-devel] pvgrub2 is merged
Thanks. Now there is another error, probably introduced by xenfb support: doesn't look like related to xenfb. Is it 64-bit or PAE guest? xl -vvv create -c /etc/xen/sid.cfg ... Welcome to GRUB! error: file `/boot/grub/x86_64-xen/gfxterm.mod' not found. error: file `/boot/grub/locale/it.gmo' not found. [0.00] PAGETABLE BUG #02! [1.298688] i8042: No controller found [1.368244] /build/linux-4VBEpo/linux-3.11.8/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 xl dmesg ... (d17) mapping kernel into physical memory (d17) about to get started... (XEN) mm.c:2352:d17 Bad type (saw 7401 != exp 1000) for mfn 2171b8 (pfn 3fbe8) (XEN) mm.c:2995:d17 Error while pinning mfn 2171b8 (XEN) mm.c:2352:d17 Bad type (saw 7401 != exp 1000) for mfn 2171b8 (pfn 3fbe8) (XEN) mm.c:906:d17 Attempt to create linear p.t. with write perms (XEN) mm.c:2352:d17 Bad type (saw 7401 != exp 1000) for mfn 2171ba (pfn 3fbe6) (XEN) mm.c:2995:d17 Error while pinning mfn 2171ba (XEN) mm.c:2352:d17 Bad type (saw 7401 != exp 1000) for mfn 2171bb (pfn 3fbe5) (XEN) mm.c:2995:d17 Error while pinning mfn 2171bb (XEN) mm.c:2352:d17 Bad type (saw 7401 != exp 2000) for mfn 2171b9 (pfn 3fbe7) (XEN) mm.c:948:d17 Attempt to create linear p.t. with write perms (XEN) mm.c:1379:d17 Failure in alloc_l3_table: entry 511 (XEN) mm.c:2099:d17 Error while validating mfn 23df00 (pfn 19a0) for type 3000: caf=8003 taf=3001 (XEN) mm.c:972:d17 Attempt to create linear p.t. with write perms (XEN) mm.c:1438:d17 Failure in alloc_l4_table: entry 511 (XEN) mm.c:2099:d17 Error while validating mfn 2b5d85 (pfn 241b) for type 4000: caf=8003 taf=4001 (XEN) mm.c:2995:d17 Error while pinning mfn 2b5d85 (XEN) mm.c:2352:d17 Bad type (saw 7401 != exp 2000) for mfn 2171b9 (pfn 3fbe7) (XEN) mm.c:948:d17 Attempt to create linear p.t. with write perms (XEN) mm.c:1379:d17 Failure in alloc_l3_table: entry 511 (XEN) mm.c:2099:d17 Error while validating mfn 23df00 (pfn 19a0) for type 3000: caf=8003 taf=3001 (XEN) mm.c:972:d17 Attempt to create linear p.t. with write perms (XEN) mm.c:1438:d17 Failure in alloc_l4_table: entry 511 (XEN) mm.c:2099:d17 Error while validating mfn 2b5d85 (pfn 241b) for type 4000: caf=8003 taf=4001 (XEN) mm.c:3122:d17 Error while installing new mfn 2b5d85 (XEN) traps.c:291:d17 Guest switching to user mode with no user page tables (XEN) traps.c:320:d17 Fatal error (XEN) domain_crash called from traps.c:321 (XEN) Domain 17 (vcpu#1) crashed on cpu#3: (XEN) [ Xen-4.4-unstable x86_64 debug=y Not tainted ] (XEN) CPU:3 (XEN) RIP:e033:[810012ed] (XEN) RFLAGS: 0286 EM: 1 CONTEXT: pv guest (XEN) rax: 0017 rbx: rcx: 810012ed (XEN) rdx: rsi: rdi: (XEN) rbp: rsp: 88003e1f9fb8 r8: (XEN) r9: r10: r11: 0286 (XEN) cr0: 8005003b cr4: 26f0 (XEN) cr3: 0002b5d86000 cr2: 7fffb46b9e19 (XEN) ds: es: fs: gs: ss: e02b cs: e033 (XEN) Guest stack trace from rsp=88003e1f9fb8: (XEN) (XEN)7f0b1f431500 0033 0200 7fffb46b9ca0 (XEN)002b 88003e004958 88003e004958 0080 (XEN)88003e1fa080 0006 d5dc82dde252 00020001 (XEN)00040003 0005 0501e668a45aed37 d3a51001f8186504 (XEN)3d41962be0a726d3 fbee8906bde13da3 9e907ea339feb0c4 270b40af55a0f4b8 (XEN)264b0560a7e2c9dc 0a3145802804d2e1 faf4b4eca4180ba6 01957dd1d4131d2e (XEN)a18b79fe805a7821 bf0afc62c71eddcb 630fca5df80eb04b 845a16e1648fdd51 (XEN)c588c03d2edcf807 9cf4717d19322687 510724530fcbf04b d8f1199bd10015fe (XEN)5272422fa11fb05c f2447667cb9fa47a 37c90f94df9206f9 43eca9d987b7240b (XEN)def99e5d7d577367 9b0d95f77cdf3672 4ef9836df37ccdf6 5a79437e62989ecf (XEN)3772f347b726713a 27fc0fe3f633e7e4 b975e7e927ca3183 a3eb9b3cea9ebb28 (XEN)76b3d73a083d2d34 3e7c801b21bd2ad3 4874b5adac7be5fe 327fb4145bc5967e (XEN)ce5fd2670ed6fe93 6671781eb982fcaf 865c0f25bbc6796d da793d360234fc4d (XEN)fe53c86f9465bf2c cf6fc89cfcb9d3e9 a05d1a75741d9703 0670c66fb870cfae (XEN)fc725a3f8a7f7448
Re: [Xen-devel] pvgrub2 is merged
On Wed, Dec 11, 2013 at 12:54:35PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 11.12.2013 12:51, Ian Campbell wrote: I can't confirm for 100% now, but I'll be 90-95% at FOSDEM and if I'll be ther I'm ok to give a talk. Is this offer still on the table? I'm afraid the deadline for submissions has passed (IIRC it was 1 December, at least for the virt devroom). Ok, np Just a thought - but the Distribution devroom call for participation is still open (until 22 Dec). It might not be entirely off-topic there. / Leif ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
I can't confirm for 100% now, but I'll be 90-95% at FOSDEM and if I'll be ther I'm ok to give a talk. Is this offer still on the table? On 14.11.2013 09:37, Ian Campbell wrote: On Wed, 2013-11-13 at 19:25 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 17:36, 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. http://git.savannah.gnu.org/cgit/grub.git I was just talking to some folks here and we thought this might make an interesting topic for a talk at fosdem e.g. in the virt and iaas room. http://lists.xen.org/archives/html/xen-devel/2013-10/msg01824.html http://www.xenproject.org/about/events/viewevent/74-fosdem-2014-virtualization-and-iaas-devroom.html I guess you have some interesting war stories from doing a pv port and all the kexec/launching stuff? Yes, I can give a talk. Even though it's not clear to me what yet what the contents will be. AFAICT you did this port with only a pretty minimal amount of input from Xen developers, xen-devel, etc which is pretty impressive. I thought you might have some interesting insights into some of the murkier corners of the Xen PV architecture, things that were easier/harder than expected, perhaps some general thoughts or advice on doing a PV OS port etc. Does giving a talk gives right to stay at student campus there? (it's the case for some conferences but not all) I can't find the reference but I seem to remember seeing somewhere that fosdem offer neither travel not accommodation subsidies. Also, this is a devroom rather than main track. When I've given a devroom talk in the past it was never suggested to me, but I also never asked. 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 Wed, 2013-12-11 at 12:47 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: I can't confirm for 100% now, but I'll be 90-95% at FOSDEM and if I'll be ther I'm ok to give a talk. Is this offer still on the table? I'm afraid the deadline for submissions has passed (IIRC it was 1 December, at least for the virt devroom). Ian. On 14.11.2013 09:37, Ian Campbell wrote: On Wed, 2013-11-13 at 19:25 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 17:36, 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. http://git.savannah.gnu.org/cgit/grub.git I was just talking to some folks here and we thought this might make an interesting topic for a talk at fosdem e.g. in the virt and iaas room. http://lists.xen.org/archives/html/xen-devel/2013-10/msg01824.html http://www.xenproject.org/about/events/viewevent/74-fosdem-2014-virtualization-and-iaas-devroom.html I guess you have some interesting war stories from doing a pv port and all the kexec/launching stuff? Yes, I can give a talk. Even though it's not clear to me what yet what the contents will be. AFAICT you did this port with only a pretty minimal amount of input from Xen developers, xen-devel, etc which is pretty impressive. I thought you might have some interesting insights into some of the murkier corners of the Xen PV architecture, things that were easier/harder than expected, perhaps some general thoughts or advice on doing a PV OS port etc. Does giving a talk gives right to stay at student campus there? (it's the case for some conferences but not all) I can't find the reference but I seem to remember seeing somewhere that fosdem offer neither travel not accommodation subsidies. Also, this is a devroom rather than main track. When I've given a devroom talk in the past it was never suggested to me, but I also never asked. 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.12.2013 12:51, Ian Campbell wrote: On Wed, 2013-12-11 at 12:47 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: I can't confirm for 100% now, but I'll be 90-95% at FOSDEM and if I'll be ther I'm ok to give a talk. Is this offer still on the table? I'm afraid the deadline for submissions has passed (IIRC it was 1 December, at least for the virt devroom). Ok, np Ian. On 14.11.2013 09:37, Ian Campbell wrote: On Wed, 2013-11-13 at 19:25 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 17:36, 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. http://git.savannah.gnu.org/cgit/grub.git I was just talking to some folks here and we thought this might make an interesting topic for a talk at fosdem e.g. in the virt and iaas room. http://lists.xen.org/archives/html/xen-devel/2013-10/msg01824.html http://www.xenproject.org/about/events/viewevent/74-fosdem-2014-virtualization-and-iaas-devroom.html I guess you have some interesting war stories from doing a pv port and all the kexec/launching stuff? Yes, I can give a talk. Even though it's not clear to me what yet what the contents will be. AFAICT you did this port with only a pretty minimal amount of input from Xen developers, xen-devel, etc which is pretty impressive. I thought you might have some interesting insights into some of the murkier corners of the Xen PV architecture, things that were easier/harder than expected, perhaps some general thoughts or advice on doing a PV OS port etc. Does giving a talk gives right to stay at student campus there? (it's the case for some conferences but not all) I can't find the reference but I seem to remember seeing somewhere that fosdem offer neither travel not accommodation subsidies. Also, this is a devroom rather than main track. When I've given a devroom talk in the past it was never suggested to me, but I also never asked. 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 mer, 2013-12-11 at 12:54 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 11.12.2013 12:51, Ian Campbell wrote: On Wed, 2013-12-11 at 12:47 +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: I can't confirm for 100% now, but I'll be 90-95% at FOSDEM and if I'll be ther I'm ok to give a talk. Is this offer still on the table? I'm afraid the deadline for submissions has passed (IIRC it was 1 December, at least for the virt devroom). Ok, np So, what about writing a blog post about this, with, if you want, specific instructions on ho to test this? Both me and George asked this before... George specifically asked whether we could have it in time for one of the Xen 4.4 test days, which would really be ideal. Still, there is no real deadline this time... Even if it's after 4.4 will be out, we really would like to have something on the project blog. Up for it? :-) Thanks and Regards, Dario -- This happens because I choose it to happen! (Raistlin Majere) - Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK) signature.asc Description: This is a digitally signed message part ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
Il 07/12/2013 11:06, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug grub boot xc: debug: hypercall buffer: total allocations:247 total releases:247
Re: [Xen-devel] pvgrub2 is merged
On 06.12.2013 16:22, Fabio Fantoni wrote: Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug grub boot xc: debug: hypercall buffer: total allocations:247 total
Re: [Xen-devel] pvgrub2 is merged
Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. 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
Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug grub boot xc: debug: hypercall buffer: total allocations:247 total releases:247 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:236 misses:4 toobig:7 ___ Grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug grub boot xc: debug: hypercall buffer: total allocations:247 total releases:247 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache
Re: [Xen-devel] pvgrub2 is merged
Il 06/12/2013 15:55, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 15:44, Fabio Fantoni wrote: Il 06/12/2013 12:32, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 06.12.2013 12:11, Fabio Fantoni wrote: Il 03/12/2013 17:16, Fabio Fantoni ha scritto: Il 03/12/2013 16:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? I tried with ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ /mnt/tmp/boot/vmlinuz-3.11-2-amd64 Probably I did something wrong or missed about this test. On xl create it arrives to grub console, so I tried to set root and include the grub.cfg of domU but gave nothing, only new console line. Can you give me more details to do a complete and correct test? Did you try root/linux/initrd/boot sequence manually? I presume you mean to do insmod, set root and all other command manually without using grub.cfg, could you confirm that or give me an exact howto? I tried manually sequence instead of do it with grub.cfg (I hope to did it correctly): ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug grub initrd /boot/initrd.img-3.11-2-amd64 grub boot xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 unfortunately the result is the same :( Hm, that is different from previous. Previously you spoke about not a xen image message. I'd remove console=tty0 and also try without initrd. Without console and initrd: ... grub insmod part_msdos grub insmod xzio grub insmod ext2 grub insmod gzio grub set root=(xen/xvda,msdos1) grub linux /boot/vmlinuz-3.11-2-amd64 root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug grub boot xc: debug: hypercall buffer: total allocations:247 total releases:247 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4
Re: [Xen-devel] pvgrub2 is merged
On 29.11.2013 12:28, Fabio Fantoni wrote: I updated git to commit 69ca97c820a623f85baf2db1627e19bef9c24e44 and the regression persist. I've just tested it here and it works perfectly. Are you sure you don't have a typo in variable name? 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
Il 29/11/2013 13:58, Fabio Fantoni ha scritto: Il 29/11/2013 12:41, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 29.11.2013 12:28, Fabio Fantoni wrote: Il 28/11/2013 15:17, Fabio Fantoni ha scritto: Il 28/11/2013 15:05, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 28.11.2013 14:07, Fabio Fantoni wrote: Il 27/11/2013 18:35, Andrey Borzenkov ha scritto: В Wed, 27 Nov 2013 17:24:53 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: Il 27/11/2013 17:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 16:59, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Yes, it was a bit naive on my side. Recursion in principle can be stopped by using global variable, but search is limited to the first match only anyway, so I guess it is not worth it. Anyone know how to exclude memdisk from the search please? Please look in grub2 sources at docs/osdetect.cfg. It implements advanced run-time detection of possible bootable files from various operating systems. It boils down to loop across all devices, and of course you can either limit device names (like looking for hd* only) or explicitly exclude known ones (like memdisk). Is it possible to specify a different default grub.cfg path (different from all other distributions) changing this command: ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg Is it hardcoded as /boot/grub/grub.cfg for grub memdisk or can be set? Not really. Currently the situation is - grub-mkstandalone hardcodes $prefix as (memdisk)/boot/grub - after launch grub unconditionally starts normal module if at all possible - normal module always tries to load and execute $prefix/grub.cfg if no explicit configuration file name is given as argument But I think that using osdetect.cfg or something based on this idea won't require changing defaults at all. Thanks for your reply. I did this script that is working about finding and include the grub.cfg of pv domUs with many cases: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt insmod btrfs insmod regexp for dev in (*); do # $device: parenthesis removed from $dev regexp -s device '\((.*)\)' $dev set root=$device for file in /boot/vmlinuz-* /boot/linux-*; do if test -f $file; then set saved_root=$root fi done done set root=$saved_root if test -f /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif test -f /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF @xen developer: Are there other modules to insert for other partitions or file systems, other grub cfg path for other distributions or other kernel type to search that support xen pv domUs? I think is good do and post complete pvgrub2 cfg that support all pv domUs. @xen and grub developer: I'm still unable to boot any entry of Sid pv domU using official kernel: xl -vvv create -c /etc/xen/sid.cfg ... Caricamento Linux 3.11-1-amd64... Caricamento ramdisk iniziale... xc: debug: hypercall buffer: total allocations:247 total releases:247 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:236 misses:4 toobig:7 Any ideas? Ah I forgot: you need to insmod xzio since debian ones are compressed. If you need more tests/informations tell me and I'll post them. Thanks for any reply. Thanks for reply, in the meantime I rebuilt updated grub2 from git (commitb67422d33de8eee83700db534a45b2ac5e5ed67a) and there is a regression from build of some days ago (I don't remember the exact commit, probably was of 24 or 25 november). Fails on script I posted on previous mail showing some errors: kern/dl.c:619: module name: test kern/dl.c:620: init function: 0x3f5abdd4 error: two arguments expected. commands/wildcard.c:164: Regexp is ^vmlinuz-.*$ commands/wildcard.c:164: Regexp is ^linux-.*$ error: two arguments expected. commands/wildcard.c:164: Regexp is ^vmlinuz-.*$ commands/wildcard.c:164: Regexp is ^linux-.*$ error: two arguments expected. commands/wildcard.c:164: Regexp is ^vmlinuz-.*$ commands/wildcard.c:164: Regexp is ^linux-.*$ Full log with debug on attachment. I updated git to commit 69ca97c820a623f85baf2db1627e19bef9c24e44 and the regression persist. About Sid boot adding insmod xzio not solve the problem. Can you give me details of your working cases? Can you send me the exact kernel? My sid kernel work fine. (Resent re-adding xen-devel and grub-devel) I have updated Sid domU today before retry with pvgrub2. Latest version of kernel
Re: [Xen-devel] pvgrub2 is merged
On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response 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
Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. Thanks for any reply. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 03.12.2013 15:00, Fabio Fantoni wrote: Il 03/12/2013 12:29, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 12:22, Fabio Fantoni wrote: Il 03/12/2013 11:33, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 03.12.2013 11:31, Fabio Fantoni wrote: If you need more tests/informations tell me and I'll post them. I've already asked you for exact kernel that I can download (and SHA512 to check it's the same one) and got only vague response Thanks for reply. The actual kernel used is from this package: http://packages.debian.org/sid/linux-image-3.11-2-amd64 I already checked kernel's files integrity with md5 (using the debian package's md5sums file and is correct). Same domU with pygrub with manual and minimal grub.cfg configuration and it boots correctly, but with pvgrub2 and grub.cfg created automatically (see attachment of previous mail) it doesn't boot. With HEAD: phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf data.tar.xz phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum boot/vmlinuz-3.11-2-amd64 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df boot/vmlinuz-3.11-2-amd64 phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$ ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d grub-core/ boot/vmlinuz-3.11-2-amd64 GNU GRUB version 2.00 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub insmod xzio grub linux /boot/vmlinuz-3.11-2-amd64 grub boot [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct I've uploaded my grub.xen to http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz Thanks for any reply. Thanks for your reply. I tried with your build and gave me: Caricamento Linux 3.11-2-amd64... errore: not xen image. Caricamento ramdisk iniziale... errore: ? necessario caricare il kernel prima. I also rebuilt pvgrub2 from clean directory, full logs of configure, make and xl create on attachment. Also in this case domU destroys on kernel and initrd loading. I not understand what are my errors and/or forgetfulness. $ sha512sum /boot/vmlinuz-3.11-2-amd64 Did you try with kernel embed in GRUB? Did you try root/linux/initrd/boot sequence manually? 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 Tue, 2013-12-03 at 17:27 +, Colin Watson wrote:
On Mon, Dec 02, 2013 at 09:48:07AM +, Ian Campbell wrote:
On Fri, 2013-11-29 at 21:44 +0400, Andrey Borzenkov wrote:
В Fri, 29 Nov 2013 13:24:22 +
Colin Watson cjwat...@ubuntu.com пишет:
Could anyone offer packaging advice for which ports should be built
here? Is it reasonable to assume that a 32-bit userspace only needs the
32-bit Xen port and a 64-bit userspace only needs the 64-bit Xen port,
or is it possible that there could be cross-architecture combinations
here? Does the architecture of the GRUB port have to match the
architecture of the Xen hypervisor?
I guess this question is better asked on xen-devel. Assuming we have 64
bit dom0 and try to boot 32 bit domU. Is it possible to start with
loading 64 bit grub that loads 32 bit kernel and jumps to it? If yes
(and in other direction too) situation becomes relatively simple.
AIUI it is not in general possible for a 32-bit PV guest to convert
itself to 64-bit or vice versa, which is essentially what would have to
happen to boot the other type of kernel. So once you have selected the
grub binary to use it cannot boot the other type of kernel. (Yes, this
is an annoying technical restriction...)
It is however possible to run 32-bit and 64-bit guests on a 32-bit dom0
with a 64-bit underlying hypervisor. It is also possible to run both
types of guest on a 64-bit kernel and 64-bit underlying hypervisor.
So, for packaging purposes it would be best to provide both 32- and
64-bit grub binaries for both 32- and 64-bit userspace.
Thanks for the feedback.
I'm inclined, then, to just ship both in the same grub-xen binary
package (actually the pattern is grub-xen{,-bin,-dbg} but never mind
that for now). It's a bit different from the usual case since you might
well want to actively use both on the same system, and I don't think we
would get much out of the two ports being in separate packages.
Yes, that makes sense to me.
Ian.
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On Fri, 2013-11-29 at 21:44 +0400, Andrey Borzenkov wrote:
В Fri, 29 Nov 2013 13:24:22 +
Colin Watson cjwat...@ubuntu.com пишет:
On Sat, Nov 09, 2013 at 09:52:20PM +0100, Vladimir 'φ-coder/phcoder'
Serbinenko wrote:
Hello, all. pvgrub2 has just became part of upstream grub as ports
i386-xen and x86_64-xen.
Could anyone offer packaging advice for which ports should be built
here? Is it reasonable to assume that a 32-bit userspace only needs the
32-bit Xen port and a 64-bit userspace only needs the 64-bit Xen port,
or is it possible that there could be cross-architecture combinations
here? Does the architecture of the GRUB port have to match the
architecture of the Xen hypervisor?
I guess this question is better asked on xen-devel. Assuming we have 64
bit dom0 and try to boot 32 bit domU. Is it possible to start with
loading 64 bit grub that loads 32 bit kernel and jumps to it? If yes
(and in other direction too) situation becomes relatively simple.
AIUI it is not in general possible for a 32-bit PV guest to convert
itself to 64-bit or vice versa, which is essentially what would have to
happen to boot the other type of kernel. So once you have selected the
grub binary to use it cannot boot the other type of kernel. (Yes, this
is an annoying technical restriction...)
It is however possible to run 32-bit and 64-bit guests on a 32-bit dom0
with a 64-bit underlying hypervisor. It is also possible to run both
types of guest on a 64-bit kernel and 64-bit underlying hypervisor.
So, for packaging purposes it would be best to provide both 32- and
64-bit grub binaries for both 32- and 64-bit userspace.
For those familiar with Debian packaging, I'm trying to work out whether
it's sufficient to just build grub-xen{,-bin,-dbg} packages which would
be i386-xen on i386 and x86_64-xen on amd64, or whether I have to have
two variants on each architecture the way I do for EFI. All other
things being equal I'd prefer to keep the package count as low as
possible, but only if that won't break real-world use cases.
Sorry!
For a long time I dream of possibility to mark grub platform packages
as noarch (speaking about RPM) - they *are* noarch from the OS PoV. I
was told that was impossible, but may be I should try once more.
That does sound like a good idea.
Ian.
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
Ian Campbell, le Mon 02 Dec 2013 09:48:07 +, a écrit : On Fri, 2013-11-29 at 21:44 +0400, Andrey Borzenkov wrote: I guess this question is better asked on xen-devel. Assuming we have 64 bit dom0 and try to boot 32 bit domU. Is it possible to start with loading 64 bit grub that loads 32 bit kernel and jumps to it? If yes (and in other direction too) situation becomes relatively simple. AIUI it is not in general possible for a 32-bit PV guest to convert itself to 64-bit or vice versa, Indeed. At the time of PV-grub1, we discussed about making it possible, but that'd be quite complex and bug-prone, so we preferred not to implement it. Samuel ___ 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-12-02 at 11:37 +0100, Samuel Thibault wrote: Ian Campbell, le Mon 02 Dec 2013 09:48:07 +, a écrit : On Fri, 2013-11-29 at 21:44 +0400, Andrey Borzenkov wrote: I guess this question is better asked on xen-devel. Assuming we have 64 bit dom0 and try to boot 32 bit domU. Is it possible to start with loading 64 bit grub that loads 32 bit kernel and jumps to it? If yes (and in other direction too) situation becomes relatively simple. AIUI it is not in general possible for a 32-bit PV guest to convert itself to 64-bit or vice versa, Indeed. At the time of PV-grub1, we discussed about making it possible, but that'd be quite complex and bug-prone, so we preferred not to implement it. I thought we'd concluded impossible, but yeah ;-) Ian. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
Il 27/11/2013 18:35, Andrey Borzenkov ha scritto: В Wed, 27 Nov 2013 17:24:53 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: Il 27/11/2013 17:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 16:59, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Yes, it was a bit naive on my side. Recursion in principle can be stopped by using global variable, but search is limited to the first match only anyway, so I guess it is not worth it. Anyone know how to exclude memdisk from the search please? Please look in grub2 sources at docs/osdetect.cfg. It implements advanced run-time detection of possible bootable files from various operating systems. It boils down to loop across all devices, and of course you can either limit device names (like looking for hd* only) or explicitly exclude known ones (like memdisk). Is it possible to specify a different default grub.cfg path (different from all other distributions) changing this command: ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg Is it hardcoded as /boot/grub/grub.cfg for grub memdisk or can be set? Not really. Currently the situation is - grub-mkstandalone hardcodes $prefix as (memdisk)/boot/grub - after launch grub unconditionally starts normal module if at all possible - normal module always tries to load and execute $prefix/grub.cfg if no explicit configuration file name is given as argument But I think that using osdetect.cfg or something based on this idea won't require changing defaults at all. Thanks for your reply. I did this script that is working about finding and include the grub.cfg of pv domUs with many cases: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt insmod btrfs insmod regexp for dev in (*); do # $device: parenthesis removed from $dev regexp -s device '\((.*)\)' $dev set root=$device for file in /boot/vmlinuz-* /boot/linux-*; do if test -f $file; then set saved_root=$root fi done done set root=$saved_root if test -f /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif test -f /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF @xen developer: Are there other modules to insert for other partitions or file systems, other grub cfg path for other distributions or other kernel type to search that support xen pv domUs? I think is good do and post complete pvgrub2 cfg that support all pv domUs. @xen and grub developer: I'm still unable to boot any entry of Sid pv domU using official kernel: xl -vvv create -c /etc/xen/sid.cfg ... Caricamento Linux 3.11-1-amd64... Caricamento ramdisk iniziale... xc: debug: hypercall buffer: total allocations:247 total releases:247 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:236 misses:4 toobig:7 Any ideas? If you need more tests/informations tell me and I'll post them. Thanks for any reply. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 28.11.2013 14:07, Fabio Fantoni wrote: Il 27/11/2013 18:35, Andrey Borzenkov ha scritto: В Wed, 27 Nov 2013 17:24:53 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: Il 27/11/2013 17:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 16:59, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Yes, it was a bit naive on my side. Recursion in principle can be stopped by using global variable, but search is limited to the first match only anyway, so I guess it is not worth it. Anyone know how to exclude memdisk from the search please? Please look in grub2 sources at docs/osdetect.cfg. It implements advanced run-time detection of possible bootable files from various operating systems. It boils down to loop across all devices, and of course you can either limit device names (like looking for hd* only) or explicitly exclude known ones (like memdisk). Is it possible to specify a different default grub.cfg path (different from all other distributions) changing this command: ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg Is it hardcoded as /boot/grub/grub.cfg for grub memdisk or can be set? Not really. Currently the situation is - grub-mkstandalone hardcodes $prefix as (memdisk)/boot/grub - after launch grub unconditionally starts normal module if at all possible - normal module always tries to load and execute $prefix/grub.cfg if no explicit configuration file name is given as argument But I think that using osdetect.cfg or something based on this idea won't require changing defaults at all. Thanks for your reply. I did this script that is working about finding and include the grub.cfg of pv domUs with many cases: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt insmod btrfs insmod regexp for dev in (*); do # $device: parenthesis removed from $dev regexp -s device '\((.*)\)' $dev set root=$device for file in /boot/vmlinuz-* /boot/linux-*; do if test -f $file; then set saved_root=$root fi done done set root=$saved_root if test -f /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif test -f /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF @xen developer: Are there other modules to insert for other partitions or file systems, other grub cfg path for other distributions or other kernel type to search that support xen pv domUs? I think is good do and post complete pvgrub2 cfg that support all pv domUs. @xen and grub developer: I'm still unable to boot any entry of Sid pv domU using official kernel: xl -vvv create -c /etc/xen/sid.cfg ... Caricamento Linux 3.11-1-amd64... Caricamento ramdisk iniziale... xc: debug: hypercall buffer: total allocations:247 total releases:247 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:236 misses:4 toobig:7 Any ideas? Ah I forgot: you need to insmod xzio since debian ones are compressed. If you need more tests/informations tell me and I'll post them. Thanks for any reply. 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
Il 26/11/2013 19:12, Andrey Borzenkov ha scritto: В Tue, 26 Nov 2013 18:58:47 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? You can do something like if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg elif ... ... fi I tried with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF But it's not working and it prints this line indefinitely in loop: error: no such device: /boot/grub2/grub.cfg. I also tried with only these lines instead of conditions: search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg But all I get is the line Welcome to GRUB! followed by a white screen on xl console. I don't know what else to try :( Thanks for any reply. If xen provides way to pass arguments to kernel, it sure could be implemented as arguments to grub. Actually someone asked for a way to pass arguments to grub on EFI, so this could share implementation. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 27.11.2013 12:32, Fabio Fantoni wrote: Il 26/11/2013 19:12, Andrey Borzenkov ha scritto: В Tue, 26 Nov 2013 18:58:47 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? You can do something like if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg elif ... ... fi I tried with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF But it's not working and it prints this line indefinitely in loop: error: no such device: /boot/grub2/grub.cfg. That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. I also tried with only these lines instead of conditions: search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg But all I get is the line Welcome to GRUB! followed by a white screen on xl console. I don't know what else to try :( Thanks for any reply. If xen provides way to pass arguments to kernel, it sure could be implemented as arguments to grub. Actually someone asked for a way to pass arguments to grub on EFI, so this could share implementation. 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
Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 12:32, Fabio Fantoni wrote: Il 26/11/2013 19:12, Andrey Borzenkov ha scritto: В Tue, 26 Nov 2013 18:58:47 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? You can do something like if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg elif ... ... fi I tried with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF But it's not working and it prints this line indefinitely in loop: error: no such device: /boot/grub2/grub.cfg. That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Ok, now I understand with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF that has the debian grub.cfg path equal to memdisk's grub, and then it loads the memdisk ones indefinitely. Anyone know how to exclude memdisk from the search please? With this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt root='(xen/xvda,msdos1)' configfile /boot/grub/grub.cfg EOF it loads correctly the Sid grub.cfg but grub fails to load with any entry I select, that domU stop. xl -vvv create -c /etc/xen/sid.cfg ... Caricamento Linux 3.11-1-amd64... error: not xen image. Caricamento ramdisk iniziale... xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 Maybe that grub is waiting for a dom0 configuration type (with also xen.gz) but find only kernel and ramdisk? (which is right for a domU) If you need more tests/informations tell me and I'll post them. Thanks for any reply. I also tried with only these lines instead of conditions: search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg But all I get is the line Welcome to GRUB! followed by a white screen on xl console. I don't know what else to try :( Thanks for any reply. If xen provides way to pass arguments to kernel, it sure could be implemented as arguments to grub. Actually someone asked for a way to pass arguments to grub on EFI, so this could share implementation. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 27.11.2013 16:59, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 12:32, Fabio Fantoni wrote: Il 26/11/2013 19:12, Andrey Borzenkov ha scritto: В Tue, 26 Nov 2013 18:58:47 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? You can do something like if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg elif ... ... fi I tried with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF But it's not working and it prints this line indefinitely in loop: error: no such device: /boot/grub2/grub.cfg. That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Ok, now I understand with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF that has the debian grub.cfg path equal to memdisk's grub, and then it loads the memdisk ones indefinitely. Anyone know how to exclude memdisk from the search please? With this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt root='(xen/xvda,msdos1)' configfile /boot/grub/grub.cfg EOF it loads correctly the Sid grub.cfg but grub fails to load with any entry I select, that domU stop. xl -vvv create -c /etc/xen/sid.cfg ... Caricamento Linux 3.11-1-amd64... error: not xen image. Caricamento ramdisk iniziale... xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 Maybe that grub is waiting for a dom0 configuration type (with also xen.gz) but find only kernel and ramdisk? (which is right for a domU) No, this message indicates problem parsing domU image. Can you give the link to exact image you use? If you need more tests/informations tell me and I'll post them. Thanks for any reply. I also tried with only these lines instead of conditions: search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg But all I get is the line Welcome to GRUB! followed by a white screen on xl console. I don't know what else to try :( Thanks for any reply. If xen provides way to pass arguments to kernel, it sure could be implemented as arguments to grub. Actually someone asked for a way to pass arguments to grub on EFI, so this could share implementation. 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 Wed, 27 Nov 2013, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Ok, now I understand with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF that has the debian grub.cfg path equal to memdisk's grub, and then it loads the memdisk ones indefinitely. Anyone know how to exclude memdisk from the search please? Probably the simplest way is to rename the grub.cfg file on the memdisk so that search doesn't find it, eg. to grub-memdisk.cfg or grub-internal.cfg and then adjust the ./grub-mkstandalone line appropriately. Michael Young___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
Il 27/11/2013 17:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 16:59, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 12:32, Fabio Fantoni wrote: Il 26/11/2013 19:12, Andrey Borzenkov ha scritto: В Tue, 26 Nov 2013 18:58:47 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? You can do something like if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg elif ... ... fi I tried with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg fi EOF But it's not working and it prints this line indefinitely in loop: error: no such device: /boot/grub2/grub.cfg. That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Ok, now I understand with this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF that has the debian grub.cfg path equal to memdisk's grub, and then it loads the memdisk ones indefinitely. Anyone know how to exclude memdisk from the search please? Is it possible to specify a different default grub.cfg path (different from all other distributions) changing this command: ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg Is it hardcoded as /boot/grub/grub.cfg for grub memdisk or can be set? With this: cat boot/grub/grub.cfg EOF insmod lvm insmod ext2 insmod part_msdos insmod part_gpt root='(xen/xvda,msdos1)' configfile /boot/grub/grub.cfg EOF it loads correctly the Sid grub.cfg but grub fails to load with any entry I select, that domU stop. xl -vvv create -c /etc/xen/sid.cfg ... Caricamento Linux 3.11-1-amd64... error: not xen image. Caricamento ramdisk iniziale... xc: debug: hypercall buffer: total allocations:237 total releases:237 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7 Maybe that grub is waiting for a dom0 configuration type (with also xen.gz) but find only kernel and ramdisk? (which is right for a domU) No, this message indicates problem parsing domU image. Can you give the link to exact image you use? The standard kernel image installed by debian installer, the package is this: http://packages.debian.org/sid/linux-image-3.11-2-amd64 On domU a previous version is installed but it was working and xen dom0/domU modules are included in this kernel image. If you need more tests/informations tell me and I'll post them. Thanks for any reply. I also tried with only these lines instead of conditions: search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg But all I get is the line Welcome to GRUB! followed by a white screen on xl console. I don't know what else to try :( Thanks for any reply. If xen provides way to pass arguments to kernel, it sure could be implemented as arguments to grub. Actually someone asked for a way to pass arguments to grub on EFI, so this could share implementation. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
В Wed, 27 Nov 2013 17:24:53 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: Il 27/11/2013 17:03, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 27.11.2013 16:59, Fabio Fantoni wrote: Il 27/11/2013 12:50, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: That pretty much explains what happened: you don't have any /boot/grub2/grub.cfg and when looking for /boot/grub/grub.cfg GRUB found its own memdisk and fell into recursion. I'm not sure what should be the proper way to solve this recursion. Yes, it was a bit naive on my side. Recursion in principle can be stopped by using global variable, but search is limited to the first match only anyway, so I guess it is not worth it. Anyone know how to exclude memdisk from the search please? Please look in grub2 sources at docs/osdetect.cfg. It implements advanced run-time detection of possible bootable files from various operating systems. It boils down to loop across all devices, and of course you can either limit device names (like looking for hd* only) or explicitly exclude known ones (like memdisk). Is it possible to specify a different default grub.cfg path (different from all other distributions) changing this command: ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg Is it hardcoded as /boot/grub/grub.cfg for grub memdisk or can be set? Not really. Currently the situation is - grub-mkstandalone hardcodes $prefix as (memdisk)/boot/grub - after launch grub unconditionally starts normal module if at all possible - normal module always tries to load and execute $prefix/grub.cfg if no explicit configuration file name is given as argument But I think that using osdetect.cfg or something based on this idea won't require changing defaults at all. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
Il 25/11/2013 20:35, M A Young ha scritto: On Mon, 25 Nov 2013, Fabio Fantoni wrote: I did a test following informations on one of post before: git clone git://git.sv.gnu.org/grub.git # commit 61e1b9a49d48035bde52784abb54c3212b647fc8 ./autogen.sh ./configure --target=x86_64 --with-platform=xen mkdir -p boot/grub/ cat boot/grub/grub.cfg EOF search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF You may want to adapt this script to your circumstances. I ended up with cat boot/grub/grub.cfg EOF insmod part_msdos insmod part_gpt search -s root -f /grub2/grub.cfg configfile /grub2/grub.cfg EOF for a Fedora domU. ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg I also suggest export pkgdatadir=. before this so it looks in the grub source rather than the installed version. Thanks for reply. Seems not working: export pkgdatadir=. ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg ./grub-mkstandalone: warning: cannot open directory `/usr/local/share/locale': File o directory non esistente. I also added the partition mods but Sid domU still unable to boot :( I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? Thanks for any reply and sorry for my bad english. Of course this may not help your current problem, though I can boot a domU guest with grub configured as above via the hvc0 interface with vnc enabled. Michael Young ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 26/11/13 18:12, Andrey Borzenkov wrote: В Tue, 26 Nov 2013 18:58:47 +0100 Fabio Fantoni fabio.fant...@m2r.biz пишет: I have also another question: Is possible specify multiple path where search the grub.cfg for support all mainly distributions and add a custom cfg path support taking it from arguments? You can do something like if search --set root --file /boot/grub2/grub.cfg ; then configfile /boot/grub2/grub.cfg elif search --set root --file /boot/grub/grub.cfg ; then configfile /boot/grub/grub.cfg elif ... ... fi If xen provides way to pass arguments to kernel, it sure could be implemented as arguments to grub. Actually someone asked for a way to pass arguments to grub on EFI, so this could share implementation. The way PV guests get a command line from the toolstack is via the start_info.cmd_line, which is up to 1024 bytes. This will be available to anything which gets its hand on the start info page. ~Andrew ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On Mon, 25 Nov 2013, Fabio Fantoni wrote: I did a test following informations on one of post before: git clone git://git.sv.gnu.org/grub.git # commit 61e1b9a49d48035bde52784abb54c3212b647fc8 ./autogen.sh ./configure --target=x86_64 --with-platform=xen mkdir -p boot/grub/ cat boot/grub/grub.cfg EOF search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg EOF You may want to adapt this script to your circumstances. I ended up with cat boot/grub/grub.cfg EOF insmod part_msdos insmod part_gpt search -s root -f /grub2/grub.cfg configfile /grub2/grub.cfg EOF for a Fedora domU. ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg I also suggest export pkgdatadir=. before this so it looks in the grub source rather than the installed version. Of course this may not help your current problem, though I can boot a domU guest with grub configured as above via the hvc0 interface with vnc enabled. Michael Young ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
Il 14/11/2013 22:43, Vladimir 'φ-coder/phcoder' Serbinenko ha scritto: On 14.11.2013 22:11, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:57, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:48, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) The section is tidied up, ie. backend = /local/domain/0/backend/vbd/4/51712 backend-id = 0 state = 6 virtual-device = 51712 device-type = disk ring-ref = event-channel = protocol = x86_64-abi but unfortunately it doesn't help as the boot process sticks at the same point. I notice this section is in state 6 which apparently is closed. I wonder if the kernel expecting something else. Possible. I'd try this (on top of previous patch): Sorry, too tired. I meant: diff --git a/grub-core/disk/xen/xendisk.c b/grub-core/disk/xen/xendisk.c index c449848..9b71d3a 100644 --- a/grub-core/disk/xen/xendisk.c +++ b/grub-core/disk/xen/xendisk.c @@ -449,5 +449,10 @@ grub_xendisk_fini (void) grub_xen_free_shared_page (virtdisks[i].shared_page); grub_xen_event_channel_op (EVTCHNOP_close, close_op); + + /* Prepare for handoff. */ + grub_snprintf (fdir, sizeof (fdir), %s/state, +virtdisks[i].frontend_dir); + grub_xenstore_write_file (fdir, 0, 1); } } That doesn't work. However, according to the documentation state 0 is unknown, and the vif interface (while grub is running) is in state 1 (initializing) so I thought I would try it, and if you replace 0 with 1 in the above patch then the kernel does boot. Thanks. http://git.savannah.gnu.org/cgit/grub.git/commit/?id=c7995256e410c5272e2be2f94faf62d3c9d57b61 and http://git.savannah.gnu.org/cgit/grub.git/commit/?id=e1aa5b662088cea329fc968af7c819784b6da068 Michael Young Thanks for all that have worked for xen support on upstream grub2. I did a test following informations on one of post before: git clone git://git.sv.gnu.org/grub.git # commit 61e1b9a49d48035bde52784abb54c3212b647fc8 ./autogen.sh ./configure --target=x86_64 --with-platform=xen 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 pvgrub2.xen -O x86_64-xen -d grub-core/ boot/grub/grub.cfg Latest command give me this warning: ./grub-mkstandalone: warning: cannot open directory `/usr/local/share/locale': File o directory non esistente. I tried to use it on Sid domU adding this line on domU's xl cfg: kernel = /mnt/vm/pvgrub2/grub/pvgrub2.xen But vnc show black screen and xl console white screen with only this line on start before refresh: Welcome to GRUB! I also tried to add this line: extra = (hd0,msdos1)/grub/grub.cfg but the result on vnc and xl console is the same. I did something wrong? Output of xl -vvv create on attachment. If you need more tests and/or details tell me and I'll post them. Thanks for any reply and sorry for my bad english. ___ Xen-devel mailing list xen-de...@lists.xen.org http://lists.xen.org/xen-devel xl -vvv create /etc/xen/sid.cfg Parsing config from
Re: [Xen-devel] pvgrub2 is merged
On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Michael Young___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Michael Young___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) Michael Young 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 Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) The section is tidied up, ie. backend = /local/domain/0/backend/vbd/4/51712 backend-id = 0 state = 6 virtual-device = 51712 device-type = disk ring-ref = event-channel = protocol = x86_64-abi but unfortunately it doesn't help as the boot process sticks at the same point. I notice this section is in state 6 which apparently is closed. I wonder if the kernel expecting something else. Michael Young___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 14.11.2013 19:48, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) The section is tidied up, ie. backend = /local/domain/0/backend/vbd/4/51712 backend-id = 0 state = 6 virtual-device = 51712 device-type = disk ring-ref = event-channel = protocol = x86_64-abi but unfortunately it doesn't help as the boot process sticks at the same point. I notice this section is in state 6 which apparently is closed. I wonder if the kernel expecting something else. Possible. I'd try this (on top of previous patch): diff --git a/grub-core/disk/xen/xendisk.c b/grub-core/disk/xen/xendisk.c index c449848..829da3d 100644 --- a/grub-core/disk/xen/xendisk.c +++ b/grub-core/disk/xen/xendisk.c @@ -449,5 +449,8 @@ grub_xendisk_fini (void) grub_xen_free_shared_page (virtdisks[i].shared_page); grub_xen_event_channel_op (EVTCHNOP_close, close_op); + + /* Prepare for handoff. */ + grub_xenstore_write_file (fdir, 0, 1); } } Michael Young 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 14.11.2013 19:57, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:48, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) The section is tidied up, ie. backend = /local/domain/0/backend/vbd/4/51712 backend-id = 0 state = 6 virtual-device = 51712 device-type = disk ring-ref = event-channel = protocol = x86_64-abi but unfortunately it doesn't help as the boot process sticks at the same point. I notice this section is in state 6 which apparently is closed. I wonder if the kernel expecting something else. Possible. I'd try this (on top of previous patch): Sorry, too tired. I meant: diff --git a/grub-core/disk/xen/xendisk.c b/grub-core/disk/xen/xendisk.c index c449848..9b71d3a 100644 --- a/grub-core/disk/xen/xendisk.c +++ b/grub-core/disk/xen/xendisk.c @@ -449,5 +449,10 @@ grub_xendisk_fini (void) grub_xen_free_shared_page (virtdisks[i].shared_page); grub_xen_event_channel_op (EVTCHNOP_close, close_op); + + /* Prepare for handoff. */ + grub_snprintf (fdir, sizeof (fdir), %s/state, +virtdisks[i].frontend_dir); + grub_xenstore_write_file (fdir, 0, 1); } } 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 Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:57, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:48, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) The section is tidied up, ie. backend = /local/domain/0/backend/vbd/4/51712 backend-id = 0 state = 6 virtual-device = 51712 device-type = disk ring-ref = event-channel = protocol = x86_64-abi but unfortunately it doesn't help as the boot process sticks at the same point. I notice this section is in state 6 which apparently is closed. I wonder if the kernel expecting something else. Possible. I'd try this (on top of previous patch): Sorry, too tired. I meant: diff --git a/grub-core/disk/xen/xendisk.c b/grub-core/disk/xen/xendisk.c index c449848..9b71d3a 100644 --- a/grub-core/disk/xen/xendisk.c +++ b/grub-core/disk/xen/xendisk.c @@ -449,5 +449,10 @@ grub_xendisk_fini (void) grub_xen_free_shared_page (virtdisks[i].shared_page); grub_xen_event_channel_op (EVTCHNOP_close, close_op); + + /* Prepare for handoff. */ + grub_snprintf (fdir, sizeof (fdir), %s/state, +virtdisks[i].frontend_dir); + grub_xenstore_write_file (fdir, 0, 1); } } That doesn't work. However, according to the documentation state 0 is unknown, and the vif interface (while grub is running) is in state 1 (initializing) so I thought I would try it, and if you replace 0 with 1 in the above patch then the kernel does boot. Michael Young___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 14.11.2013 22:11, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:57, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 19:48, M A Young wrote: On Thu, 14 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 14.11.2013 18:03, M A Young wrote: On Thu, 14 Nov 2013, M A Young wrote: On Wed, 13 Nov 2013, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 13.11.2013 20:06, M A Young wrote: It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Right, if I add those to the embedded grub.cfg file I get to the standard grub menu and the boot starts. However the boot doesn't get very far - it loads the kernel and the initrd file and starts the kernel but the kernel doesn't see the virtual disks so it doesn't get very far. Using xenstore-ls from the dom0 on the guest when the boot stops the local/domain/2/device/vbd/51712 section looks like backend = /local/domain/0/backend/vbd/2/51712 backend-id = 0 state = 6\000 virtual-device = 51712 device-type = disk ring-ref = \000 event-channel = \000 protocol = x86_64-abi\000 As nothing else has null character endings I suspend that is wrong. Good catch. Could you test following: diff --git a/grub-core/kern/xen/init.c b/grub-core/kern/xen/init.c index 3bfd99f..ab74543 100644 --- a/grub-core/kern/xen/init.c +++ b/grub-core/kern/xen/init.c @@ -256,11 +256,10 @@ grub_xenstore_write_file (const char *dir, const void *buf, grub_size_t len) grub_memset (msg, 0, sizeof (msg)); msg.type = XS_WRITE; - msg.len = dirlen + len + 1; + msg.len = dirlen + len; grub_xen_store_send (msg, sizeof (msg)); grub_xen_store_send (dir, dirlen); grub_xen_store_send (buf, len); - grub_xen_store_send (, 1); grub_xen_store_recv (msg, sizeof (msg)); resp = grub_malloc (msg.len + 1); if (!resp) The section is tidied up, ie. backend = /local/domain/0/backend/vbd/4/51712 backend-id = 0 state = 6 virtual-device = 51712 device-type = disk ring-ref = event-channel = protocol = x86_64-abi but unfortunately it doesn't help as the boot process sticks at the same point. I notice this section is in state 6 which apparently is closed. I wonder if the kernel expecting something else. Possible. I'd try this (on top of previous patch): Sorry, too tired. I meant: diff --git a/grub-core/disk/xen/xendisk.c b/grub-core/disk/xen/xendisk.c index c449848..9b71d3a 100644 --- a/grub-core/disk/xen/xendisk.c +++ b/grub-core/disk/xen/xendisk.c @@ -449,5 +449,10 @@ grub_xendisk_fini (void) grub_xen_free_shared_page (virtdisks[i].shared_page); grub_xen_event_channel_op (EVTCHNOP_close, close_op); + + /* Prepare for handoff. */ + grub_snprintf (fdir, sizeof (fdir), %s/state, +virtdisks[i].frontend_dir); + grub_xenstore_write_file (fdir, 0, 1); } } That doesn't work. However, according to the documentation state 0 is unknown, and the vif interface (while grub is running) is in state 1 (initializing) so I thought I would try it, and if you replace 0 with 1 in the above patch then the kernel does boot. Thanks. http://git.savannah.gnu.org/cgit/grub.git/commit/?id=c7995256e410c5272e2be2f94faf62d3c9d57b61 and http://git.savannah.gnu.org/cgit/grub.git/commit/?id=e1aa5b662088cea329fc968af7c819784b6da068 Michael Young 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 lun, 2013-11-11 at 10: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! Indeed! Actually, it would be great to have an entry about this in the Xen-Project blog: http://blog.xen.org/ Vladimir, would you be interested? If yes, would you be up to writing the blog post? I'm thinking about something like: - what is this? - what is this good for? - how to enable/use it? - how [hard] was it to do it? (if you like) And, of course, whatever else you think could be interesting to have there. If not Vladimir, anyone else? If not, I can try to collect the info from this thread and put something together, but it'll take longer (since I'm not at all into this). Anyway, if anyone is interested, please, contact me. I'll provide all the necessary information either privately or on the @xen-publicity mailing list (so that we also will stop bothering people in @xen-devel :-)). Thanks and Regards, Dario -- This happens because I choose it to happen! (Raistlin Majere) - Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK) signature.asc Description: This is a digitally signed message part ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
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. http://git.savannah.gnu.org/cgit/grub.git I was just talking to some folks here and we thought this might make an interesting topic for a talk at fosdem e.g. in the virt and iaas room. http://lists.xen.org/archives/html/xen-devel/2013-10/msg01824.html http://www.xenproject.org/about/events/viewevent/74-fosdem-2014-virtualization-and-iaas-devroom.html I guess you have some interesting war stories from doing a pv port and all the kexec/launching stuff? Ian. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 13.11.2013 17:36, 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. http://git.savannah.gnu.org/cgit/grub.git I was just talking to some folks here and we thought this might make an interesting topic for a talk at fosdem e.g. in the virt and iaas room. http://lists.xen.org/archives/html/xen-devel/2013-10/msg01824.html http://www.xenproject.org/about/events/viewevent/74-fosdem-2014-virtualization-and-iaas-devroom.html I guess you have some interesting war stories from doing a pv port and all the kexec/launching stuff? Yes, I can give a talk. Even though it's not clear to me what yet what the contents will be. Does giving a talk gives right to stay at student campus there? (it's the case for some conferences but not all) 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 Sun, 10 Nov 2013, 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? I have found the following problems in doing this; The instructions are missing a step. You I found I had to do export pkgdatadir=. before running ./grub-mkstandalone as otherwise it looks for some files in the installed version of grub2 rather than the build location. Your script search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg only checks one location, and the grub.cfg file can be in other places such as /grub/grub.cfg if there is a separate boot partition, or /boot/grub2/grub.cfg for Fedora. For testing it can be set correctly by hand but more locations would need to be searched for general use. It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . Michael Young___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: [Xen-devel] pvgrub2 is merged
On 13.11.2013 20:06, M A Young wrote: On Sun, 10 Nov 2013, 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? I have found the following problems in doing this; The instructions are missing a step. You I found I had to do export pkgdatadir=. before running ./grub-mkstandalone as otherwise it looks for some files in the installed version of grub2 rather than the build location. Your script search -s root -f /boot/grub/grub.cfg configfile /boot/grub/grub.cfg only checks one location, and the grub.cfg file can be in other places such as /grub/grub.cfg if there is a separate boot partition, or /boot/grub2/grub.cfg for Fedora. For testing it can be set correctly by hand but more locations would need to be searched for general use. ok It doesn't seem to understand sub-partitions. I can get it to work if the boot files are in /dev/xvda but not in /dev/xvda1 . insmod part_msdos insmod part_gpt Michael Young 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 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: [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: [Xen-devel] pvgrub2 is merged
Vladimir 'φ-coder/phcoder' Serbinenko, le Sat 09 Nov 2013 21:52:20 +0100, a écrit : pvgrub2 has just became part of upstream grub as ports i386-xen and x86_64-xen. \o/ Samuel ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
