Re: DomU freezes in the middle of booting

Pandu Poluan <[email protected]> Thu, 12 Apr 2012 21:30:08 +0700
Newsgroups gmane.linux.gentoo.server
Message-ID <CAA2qdGVc8n=LQJG5u8vWcWitWOK-MNz-BtRPchZahz39LG9o9Q@mail.gmail.com>
--f46d042fdaec5cd4b504bd7c318b
Content-Type: text/plain; charset=UTF-8

On Apr 12, 2012 8:51 PM, "Konstantin" <[email protected]> wrote:
>
> Hello,
>
> Thursday, April 12, 2012, 15:52:50, Konstantin wrote:
> > Thursday, April 12, 2012, 15:29:42, Pandu Poluan wrote:
> >>> Thursday, April 12, 2012, 13:09:15, Pandu Poluan wrote:
> >>> > Have you tried:
> >>> > root   = '/dev/xvda1'
> >>> > That is, without 'ro'?
> >>> > Rgds,
> >>>
> >>> Thank you. Already tried without any difference.
> >>>
> >> It's a DomU, right? Why do you have Dom0 option enabled?
>
> > You mean this part of .config file:
> > CONFIG_XEN_DOM0=y
> > CONFIG_XEN_PRIVILEGED_GUEST=y
> > CONFIG_XEN_PVHVM=y
> > CONFIG_XEN_MAX_DOMAIN_MEMORY=128
> > CONFIG_XEN_SAVE_RESTORE=y
>
> > I just could not find how to disable this code in menuconfig. :)
>
> If I'm trying to turn it off, but then other frontend options
> disappear.
>
> Latest update: When I saw
> ---------------------
>  * Starting local
>  [ ok ]
> ---------------------
>
> I've noticed that domU actually working. I've tried to change inittab
> remotely via ssh to something like
>
> # TERMINALS
> x1:12345:respawn:/sbin/agetty 38400 console linux
> #c1:12345:respawn:/sbin/agetty 38400 tty1 linux
> #c2:2345:respawn:/sbin/agetty 38400 tty2 linux
> #c3:2345:respawn:/sbin/agetty 38400 tty3 linux
> #c4:2345:respawn:/sbin/agetty 38400 tty4 linux
> #c5:2345:respawn:/sbin/agetty 38400 tty5 linux
> #c6:2345:respawn:/sbin/agetty 38400 tty6 linux
>
> Then reinitialized init by
> localhost ~ # init q
>
> and console in Dom0 become interactive again. So that freezing after
> "Starting local" was the console problem anyway.
>
> Right now only one left with that random start. DomU starts
> successfully about one time per three unsuccessful.
>
> I've noticed that it gets stuck when kernel outputs this text:
>
> -------------------------------------------------------------
> Switching to clocksource xen
> pnp: PnP ACPI: disabled
> CE: xen increased min_delta_ns to 150000 nsec
> CE: xen increased min_delta_ns to 225000 nsec
> CE: xen increased min_delta_ns to 337500 nsec
> CE: xen increased min_delta_ns to 506250 nsec
> CE: xen increased min_delta_ns to 759375 nsec
> CE: xen increased min_delta_ns to 1139062 nsec
> CE: xen increased min_delta_ns to 1708593 nsec
> CE: xen increased min_delta_ns to 2562889 nsec
> CE: xen increased min_delta_ns to 3844333 nsec
> CE: xen increased min_delta_ns to 5766499 nsec
> CE: xen increased min_delta_ns to 8649748 nsec
> CE: xen increased min_delta_ns to 10000000 nsec
> CE: Reprogramming failure. Giving up
> CE: Reprogramming failure. Giving up
> hrtimer: interrupt took 5171 ns
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> UDP hash table entries: 512 (order: 2, 16384 bytes)
> UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
> CE: xen increased min_delta_ns to 150000 nsec
> CE: xen increased min_delta_ns to 225000 nsec
> CE: xen increased min_delta_ns to 337500 nsec
> CE: xen increased min_delta_ns to 506250 nsec
> CE: xen increased min_delta_ns to 759375 nsec
> CE: xen increased min_delta_ns to 1139062 nsec
> CE: xen increased min_delta_ns to 1708593 nsec
> CE: xen increased min_delta_ns to 2562889 nsec
> CE: xen increased min_delta_ns to 3844333 nsec
> CE: xen increased min_delta_ns to 5766499 nsec
> CE: xen increased min_delta_ns to 8649748 nsec
> CE: xen increased min_delta_ns to 10000000 nsec
> CE: Reprogramming failure. Giving up
> CE: Reprogramming failure. Giving up
> platform rtc_cmos: registered platform RTC device (no PNP device found)
> -------------------------------------------------------------
>
> And when kernel not writing any "CE: " messages domU boots
> successfully:
>
> --------------------------------
> PCI: System does not support PCI
> PCI: System does not support PCI
> Switching to clocksource xen
> pnp: PnP ACPI: disabled
> --------------------------------
>
> Trying to figure out what to do next.
>
> --
> Konstantin
>
>

Try using "tickless". I forgot where exactly, but IIRC on the same page
where you set the CPU type.

Rgds,

--f46d042fdaec5cd4b504bd7c318b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p><br>
On Apr 12, 2012 8:51 PM, &quot;Konstantin&quot; &lt;<a href=3D"mailto:konst=
[email protected]">[email protected]</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello,<br>
&gt;<br>
&gt; Thursday, April 12, 2012, 15:52:50, Konstantin wrote:<br>
&gt; &gt; Thursday, April 12, 2012, 15:29:42, Pandu Poluan wrote:<br>
&gt; &gt;&gt;&gt; Thursday, April 12, 2012, 13:09:15, Pandu Poluan wrote:<b=
r>
&gt; &gt;&gt;&gt; &gt; Have you tried:<br>
&gt; &gt;&gt;&gt; &gt; root =C2=A0 =3D &#39;/dev/xvda1&#39;<br>
&gt; &gt;&gt;&gt; &gt; That is, without &#39;ro&#39;?<br>
&gt; &gt;&gt;&gt; &gt; Rgds,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Thank you. Already tried without any difference.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt; It&#39;s a DomU, right? Why do you have Dom0 option enabled?<=
br>
&gt;<br>
&gt; &gt; You mean this part of .config file:<br>
&gt; &gt; CONFIG_XEN_DOM0=3Dy<br>
&gt; &gt; CONFIG_XEN_PRIVILEGED_GUEST=3Dy<br>
&gt; &gt; CONFIG_XEN_PVHVM=3Dy<br>
&gt; &gt; CONFIG_XEN_MAX_DOMAIN_MEMORY=3D128<br>
&gt; &gt; CONFIG_XEN_SAVE_RESTORE=3Dy<br>
&gt;<br>
&gt; &gt; I just could not find how to disable this code in menuconfig. :)<=
br>
&gt;<br>
&gt; If I&#39;m trying to turn it off, but then other frontend options<br>
&gt; disappear.<br>
&gt;<br>
&gt; Latest update: When I saw<br>
&gt; ---------------------<br>
&gt; =C2=A0* Starting local<br>
&gt; =C2=A0[ ok ]<br>
&gt; ---------------------<br>
&gt;<br>
&gt; I&#39;ve noticed that domU actually working. I&#39;ve tried to change =
inittab<br>
&gt; remotely via ssh to something like<br>
&gt;<br>
&gt; # TERMINALS<br>
&gt; x1:12345:respawn:/sbin/agetty 38400 console linux<br>
&gt; #c1:12345:respawn:/sbin/agetty 38400 tty1 linux<br>
&gt; #c2:2345:respawn:/sbin/agetty 38400 tty2 linux<br>
&gt; #c3:2345:respawn:/sbin/agetty 38400 tty3 linux<br>
&gt; #c4:2345:respawn:/sbin/agetty 38400 tty4 linux<br>
&gt; #c5:2345:respawn:/sbin/agetty 38400 tty5 linux<br>
&gt; #c6:2345:respawn:/sbin/agetty 38400 tty6 linux<br>
&gt;<br>
&gt; Then reinitialized init by<br>
&gt; localhost ~ # init q<br>
&gt;<br>
&gt; and console in Dom0 become interactive again. So that freezing after<b=
r>
&gt; &quot;Starting local&quot; was the console problem anyway.<br>
&gt;<br>
&gt; Right now only one left with that random start. DomU starts<br>
&gt; successfully about one time per three unsuccessful.<br>
&gt;<br>
&gt; I&#39;ve noticed that it gets stuck when kernel outputs this text:<br>
&gt;<br>
&gt; -------------------------------------------------------------<br>
&gt; Switching to clocksource xen<br>
&gt; pnp: PnP ACPI: disabled<br>
&gt; CE: xen increased min_delta_ns to 150000 nsec<br>
&gt; CE: xen increased min_delta_ns to 225000 nsec<br>
&gt; CE: xen increased min_delta_ns to 337500 nsec<br>
&gt; CE: xen increased min_delta_ns to 506250 nsec<br>
&gt; CE: xen increased min_delta_ns to 759375 nsec<br>
&gt; CE: xen increased min_delta_ns to 1139062 nsec<br>
&gt; CE: xen increased min_delta_ns to 1708593 nsec<br>
&gt; CE: xen increased min_delta_ns to 2562889 nsec<br>
&gt; CE: xen increased min_delta_ns to 3844333 nsec<br>
&gt; CE: xen increased min_delta_ns to 5766499 nsec<br>
&gt; CE: xen increased min_delta_ns to 8649748 nsec<br>
&gt; CE: xen increased min_delta_ns to 10000000 nsec<br>
&gt; CE: Reprogramming failure. Giving up<br>
&gt; CE: Reprogramming failure. Giving up<br>
&gt; hrtimer: interrupt took 5171 ns<br>
&gt; TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)<br>
&gt; TCP: Hash tables configured (established 131072 bind 65536)<br>
&gt; TCP reno registered<br>
&gt; UDP hash table entries: 512 (order: 2, 16384 bytes)<br>
&gt; UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)<br>
&gt; CE: xen increased min_delta_ns to 150000 nsec<br>
&gt; CE: xen increased min_delta_ns to 225000 nsec<br>
&gt; CE: xen increased min_delta_ns to 337500 nsec<br>
&gt; CE: xen increased min_delta_ns to 506250 nsec<br>
&gt; CE: xen increased min_delta_ns to 759375 nsec<br>
&gt; CE: xen increased min_delta_ns to 1139062 nsec<br>
&gt; CE: xen increased min_delta_ns to 1708593 nsec<br>
&gt; CE: xen increased min_delta_ns to 2562889 nsec<br>
&gt; CE: xen increased min_delta_ns to 3844333 nsec<br>
&gt; CE: xen increased min_delta_ns to 5766499 nsec<br>
&gt; CE: xen increased min_delta_ns to 8649748 nsec<br>
&gt; CE: xen increased min_delta_ns to 10000000 nsec<br>
&gt; CE: Reprogramming failure. Giving up<br>
&gt; CE: Reprogramming failure. Giving up<br>
&gt; platform rtc_cmos: registered platform RTC device (no PNP device found=
)<br>
&gt; -------------------------------------------------------------<br>
&gt;<br>
&gt; And when kernel not writing any &quot;CE: &quot; messages domU boots<b=
r>
&gt; successfully:<br>
&gt;<br>
&gt; --------------------------------<br>
&gt; PCI: System does not support PCI<br>
&gt; PCI: System does not support PCI<br>
&gt; Switching to clocksource xen<br>
&gt; pnp: PnP ACPI: disabled<br>
&gt; --------------------------------<br>
&gt;<br>
&gt; Trying to figure out what to do next.<br>
&gt;<br>
&gt; --<br>
&gt; Konstantin<br>
&gt;<br>
&gt;</p>
<p>Try using &quot;tickless&quot;. I forgot where exactly, but IIRC on the =
same page where you set the CPU type. </p>
<p>Rgds, <br>
</p>

--f46d042fdaec5cd4b504bd7c318b--