Red Hat Bugzilla – Bug 483031
"init 1" does not work for xen virtual machines
Last modified: 2014-06-18 04:46:35 EDT
Description of problem:
When trying to boot to runlevel "1" (by adding 1 as kernel parameter or by running "init 1"), system is in state, where I can't do anything.
Version-Release number of selected component (if applicable):
[root@builder ~]# rpm -q upstart kernel
[root@builder ~]# uname -a
Linux builder.salstar.sk 18.104.22.168-170.2.5.fc10.x86_64 #1 SMP Wed Jan 21 01:33:24 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
Steps to Reproduce:
1. init 1
init: rc1 post-stop process (2321) terminated with status 1
running shell without other services started
After "rc1" message cursor is blinking, but I can't type commands. I only can restart my machine by xen command "xm reboot builder".
"init S" or adding "S" into kernel parameters works fine.
Not sure why this would be xen-specific at all.
If you change the last bit of /etc/event.d/rc1 to 'exec strace telinit S', does it show any obvious failure point?
(In reply to comment #1)
> Not sure why this would be xen-specific at all.
May be because console is on /dev/hvc and not on standard /dev/console.
I am not sure.
> If you change the last bit of /etc/event.d/rc1 to 'exec strace telinit S', does
> it show any obvious failure point?
Nothing changed. Tryed to change this and run "init 1" and also start kernel with parameter "1". Exactly same output as before (I have strace installed on my system).
What happens if you change it to 'clear || :'?
(In reply to comment #3)
> What happens if you change it to 'clear || :'?
echo $"Telling INIT to go to single user mode."
#exec telinit S
exec clear || :
File /etc/event.d/rc1 saved
Oops, I think I remember now what this is. Does the patch in http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=0320082b72105bb90863d43b3051623381cde73a work for you?
If so, we'll get this cherry-picked to the F10 branch for a future update.
(In reply to comment #5)
> Oops, I think I remember now what this is. Does the patch in
> work for you?
Yes. Works. Just another problem:
*** This bug has been marked as a duplicate of bug 471123 ***