On 03/02/20 at 12:20am, Bhupesh Sharma wrote: > Hi Guilherme, > > On Sat, Feb 29, 2020 at 10:37 PM Guilherme G. Piccoli > <gpiccoli@xxxxxxxxxxxxx> wrote: > > > > Hi Bhupesh and Dave (and everybody CC'ed here), I'm Guilherme Piccoli > > and I'm working in the same issue observed in RH bugzilla 1758323 [0] - > > or at least, it seems to be the the same heh > > Ok. > > > The reported issue in my case was that the 2nd kexec fails on Nitro > > instanced, and indeed it's reproducible. More than this, it shows as an > > initrd corruption. I've found 2 workarounds, using the "new" kexec > > syscall (by doing kexec -s -l) and keep the initrd memory "un-freed", > > using the kernel parameter "retain_initrd". > > I have a couple of questions: > - How do you conclude that you see an initrd corruption across kexec? > Do you print the initial hex contents of initrd across kexec? I'm also interested if any of you can dump the initrd memory in kernel printk log, and then save to somewhere to compare with the original initrd content. Thanks Dave _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
