From: Konstantin <konstantin@astafjev.com>
To: Konstantin <gentoo-server@lists.gentoo.org>
Subject: Re: [gentoo-server] DomU freezes in the middle of booting
Date: Thu, 12 Apr 2012 16:49:26 +0300 [thread overview]
Message-ID: <88025804.20120412164926@astafjev.com> (raw)
In-Reply-To: <694340596.20120412155250@astafjev.com>
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
next prev parent reply other threads:[~2012-04-12 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 7:53 [gentoo-server] DomU freezes in the middle of booting Konstantin
2012-04-12 8:18 ` Matthew Thode
2012-04-12 8:27 ` Konstantin
2012-04-12 9:55 ` Konstantin
2012-04-12 10:09 ` Pandu Poluan
2012-04-12 11:21 ` Konstantin
2012-04-12 12:29 ` Pandu Poluan
2012-04-12 12:52 ` Konstantin
2012-04-12 13:49 ` Konstantin [this message]
2012-04-12 14:30 ` Pandu Poluan
2012-04-12 14:45 ` [gentoo-server] DomU freezes in the middle of booting [SOLVED] Konstantin
2012-04-12 14:53 ` Pandu Poluan
2012-04-12 10:09 ` [gentoo-server] DomU freezes in the middle of booting Andrey Korolyov
2012-04-12 10:17 ` Andrey Korolyov
2012-04-12 11:32 ` Konstantin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88025804.20120412164926@astafjev.com \
--to=konstantin@astafjev.com \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox