[Starlingx-discuss] Compute boot-loop
von Hoesslin, Volker
Volker.Hoesslin at swsn.de
Mon Nov 5 16:05:38 UTC 2018
Ok, shame on me!
I have to read all the hints from you and realy check all the details... I have an AMD EPYC 7601 (32 cores), and I didn’t realized that the point "IOMMU" in my BIOS the generic term for VT-d is, so it is all the time leave disabled -.-
After enabled this option, my VM seems to run, currently booted but still in "In-Test" mode... we will see...
Thx for help! Volker...
-----Ursprüngliche Nachricht-----
Von: Michel Thebeau [mailto:michel.thebeau at windriver.com]
Gesendet: Montag, 5. November 2018 16:34
An: Hu, Yong; Alonso, Juan Carlos; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io'
Betreff: Re: [Starlingx-discuss] Compute boot-loop
Ack Yong.
I received this initial internal response: "The usual cause of this
error is when they don't enable VT-d (Intel Virtualization Technology
for Directed I/O) in the BIOS for the compute hosts."
Volker, please let us know when you've confirmed that.
M
On 2018-11-01 9:19 p.m., Hu, Yong wrote:
> Another head-up is that we need to assure VT is turned on in BIOS for the compute node.
>
>
> On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com> wrote:
>
> Hi,
>
> I think you set up a Duplex system (two controllers), right?
>
> I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso
> I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso.
>
> Please set up again a Duplex system with today's ISO to see if issue is still presented.
>
> Regards.
> Juan Carlos Alonso
>
> -----Original Message-----
> From: Michel Thebeau [mailto:michel.thebeau at windriver.com]
> Sent: Thursday, November 1, 2018 10:29 AM
> To: von Hoesslin, Volker <Volker.Hoesslin at swsn.de>; 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
> Subject: Re: [Starlingx-discuss] Compute boot-loop
>
> Hi Volker,
>
> Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes?
>
> How many cpus do your computes have?
>
> Which build are you using? Did you build your own?
>
> When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/
>
> M
>
>
> On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote:
> > Hello, there,
> > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop.
> > Error messages are not really noticeable, except:
> > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress
> >
> > any suggestions? Greez & thx, volker...
> >
> >
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>
>
More information about the Starlingx-discuss
mailing list