Re: About kexec issues in AWS nitro instances (RH bz 1758323)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2020-03-05 at 19:14 -0300, Guilherme G. Piccoli wrote:
> Hi Bhupesh, I re-tested again using 5.6-rc4 with "retain_initrd" and
> "swiotlb=noforce" and got a quite interesting discrepancy. First run got
> me 99 kexecs with no issue (the public IP of my AWS instance was
> 3.215.x.y). After this, I powered the instance off and some minutes
> later, restarted it (and the new IP was 34.239.x.y) - guess what? It
> failed after 6th kexec iteration with an oops, which I was able to
> collect [0] using pstore.
> 
> So, I'm inclined to think when I restarted the instance (and it got a
> different IP, on a different range), likely it got deployed in a
> different host, which explain some differences we are observing across
> tests. I collected DMI data on both but it didn't show me any difference
> - it is though feasible to hide host details from guest (almost?)
> completely, so this should be a question to AWS.

Can you give me the instance ID and specific times, please?

<<attachment: smime.p7s>>

_______________________________________________
kexec mailing list
kexec@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/kexec

[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux