On Wed, Jun 13, 2012 at 12:34 PM, Cleber Rosa <cr...@redhat.com> wrote: > ----- Mensagem original ----- >> De: "steve walsh" <steve.wa...@sap.com> >> Para: "Cleber Rosa" <cr...@redhat.com> >> Cc: autotest@test.kernel.org, "Lucas Meneghel Rodrigues" <l...@redhat.com> >> Enviadas: Quarta-feira, 13 de Junho de 2012 12:20:17 >> Assunto: RE: [Autotest] kernel.boot is failing because "Unable to >> instantiate boottool" >> >> Hi Cleber, >> >> Results as follows: >> >> root@heca-autotest-b:/usr/local/autotest# ./tools/boottool >> --add-kernel=/boot/vmlinuz-autotest --initrd=/boot/initrd-autotest >> --title=autotest >> root@heca-autotest-b:/usr/local/autotest# grubby >> --info=/boot/vmlinuz-autotest >> index=0 >> kernel=/boot/vmlinuz-autotest >> args="ro crashkernel=384M-2G:64M,2G-:128M quiet panic=5" >> root=UUID=18790923-d357-4ce9-96c9-d09593dcbab8 >> initrd=/boot/initrd-autotest >> title=autotest >> > > This is actually good. Putting these messages aside for a while, do you get > to actually boot this new entry (and thus kernel)?
I was working on this, and it seems the problem is that grub-reboot doesn't do what it avertises on ubuntu. After watching a couple of failed jobs, I've looked at the boot once code, and then tried grub-reboot an index. No way, it does reboot the machine to the permanent default entry, always, hence, failing the job. I don't have a good idea of how to fix this, but now we have a better idea of what's this problem all about. _______________________________________________ Autotest mailing list Autotest@test.kernel.org http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
