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.000000] Initializing cgroup subsys cpuset >>>>> [ 0.000000] Initializing cgroup subsys cpu >>>>> [ 0.000000] 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