Hello I''m currently trying to get a Debian image running under Xen. I''ve followed the directions that are available in the user guide but when I go to boot the system it doesn''t finish booting. Immediatly after the cron daemon starts it appears to hang and shortly after that errors are printed to the console that init is respawning to fast. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "3" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id "5" respawning too fast: disabled for 5 minutes INIT: Id "6" respawning too fast: disabled for 5 minutes INIT: no more processes left in this runlevel The only error before that is this. hwclock is unable to get I/O port access: the iopl(3) call failed. Does anyone have any ideas on how to resolve this issue? Thanks Mike ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Michael McCabe wrote:> Hello > I''m currently trying to get a Debian image running under Xen. I''ve > followed the directions that are available in the user guide but when I > go to boot the system it doesn''t finish booting. Immediatly after the > cron daemon starts it appears to hang and shortly after that errors are > printed to the console that init is respawning to fast. INIT: Id "1" > respawning too fast: disabled for 5 minutes > INIT: Id "2" respawning too fast: disabled for 5 minutes > INIT: Id "3" respawning too fast: disabled for 5 minutes > INIT: Id "4" respawning too fast: disabled for 5 minutes > INIT: Id "5" respawning too fast: disabled for 5 minutes > INIT: Id "6" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > > The only error before that is this. hwclock is unable to get I/O port > access: the iopl(3) call failed.This error means that the processes defined in /etc/inittab are dying to fast, and as init is trying to respawn them, some limit is reached. I''m not using Debian, bu tgoogle search returned something about X stuff - are you sure you aren''t trying to start X from the default runlevel? Or some other application which has problems running under Xen? -jkt -- cd /local/pub && more beer > /dev/mouth ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I''m not running X. This is a base debian install after running debootstrap and editing the necessary config files as described in the user manual. Mike Jan Kundrát wrote:> Michael McCabe wrote: > >> Hello >> I''m currently trying to get a Debian image running under Xen. I''ve >> followed the directions that are available in the user guide but when >> I go to boot the system it doesn''t finish booting. Immediatly after >> the cron daemon starts it appears to hang and shortly after that >> errors are printed to the console that init is respawning to fast. >> INIT: Id "1" respawning too fast: disabled for 5 minutes >> INIT: Id "2" respawning too fast: disabled for 5 minutes >> INIT: Id "3" respawning too fast: disabled for 5 minutes >> INIT: Id "4" respawning too fast: disabled for 5 minutes >> INIT: Id "5" respawning too fast: disabled for 5 minutes >> INIT: Id "6" respawning too fast: disabled for 5 minutes >> INIT: no more processes left in this runlevel >> >> The only error before that is this. hwclock is unable to get I/O port >> access: the iopl(3) call failed. > > > This error means that the processes defined in /etc/inittab are dying > to fast, and as init is trying to respawn them, some limit is reached. > I''m not using Debian, bu tgoogle search returned something about X > stuff - are you sure you aren''t trying to start X from the default > runlevel? Or some other application which has problems running under Xen? > > -jkt >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, 9 Mar 2005, Michael McCabe wrote:> Hello > I''m currently trying to get a Debian image running under Xen. I''ve > followed the directions that are available in the user guide but when I > go to boot the system it doesn''t finish booting. Immediatly after the > cron daemon starts it appears to hang and shortly after that errors are > printed to the console that init is respawning to fast. > INIT: Id "1" respawning too fast: disabled for 5 minutes > INIT: Id "2" respawning too fast: disabled for 5 minutes > INIT: Id "3" respawning too fast: disabled for 5 minutes > INIT: Id "4" respawning too fast: disabled for 5 minutes > INIT: Id "5" respawning too fast: disabled for 5 minutes > INIT: Id "6" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevelThat''s not init spawning too fast, but the processes defined with those ids in /etc/inittab. In this case, they are gettys. Disabling them(using # to comment them out) will solve this non-problem. I also don''t think cron is hanging.> The only error before that is this. hwclock is unable to get I/O port > access: the iopl(3) call failed.This implies you are booting domU, which doesn''t have access to the raw io ports. You can actually remove hwclock from the bootscripts of domU instances, as they all just inherit the time from dom0.> Does anyone have any ideas on how to resolve this issue?ps: you didn''t mention if this was a dom0 or domU boot. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > I''m currently trying to get a Debian image running under Xen. I''ve > > followed the directions that are available in the user guide but when I > > go to boot the system it doesn''t finish booting. Immediatly after the > > cron daemon starts it appears to hang and shortly after that errors are > > printed to the console that init is respawning to fast. > > INIT: Id "1" respawning too fast: disabled for 5 minutes > > INIT: Id "2" respawning too fast: disabled for 5 minutes > > INIT: Id "3" respawning too fast: disabled for 5 minutes > > INIT: Id "4" respawning too fast: disabled for 5 minutes > > INIT: Id "5" respawning too fast: disabled for 5 minutes > > INIT: Id "6" respawning too fast: disabled for 5 minutes > > INIT: no more processes left in this runlevel > > That''s not init spawning too fast, but the processes defined with those ids in > /etc/inittab. In this case, they are gettys. Disabling them(using # to > comment them out) will solve this non-problem. > > I also don''t think cron is hanging.I''d expect that it just happens that cron is the last thing in the boot sequence, and that it''s simply not printing any additional messages after that point. This sounds like init is trying to spawn the gettys and they''re failing to open the tty devices -> are you using devfs in the Debian image? Ensure that the lines in inittab which look like this: 1:12345:respawn:/sbin/getty 38400 tty1 ..for the console gettys, are pointing at a tty device (in this case /dev/tty1) which exists. Hope this helps, Dave
On Fri, Mar 11, 2005 at 09:21:19PM +0000, Dave wrote:> > > I''m currently trying to get a Debian image running under Xen. I''ve > > > followed the directions that are available in the user guide but when I > > > go to boot the system it doesn''t finish booting. Immediatly after the > > > cron daemon starts it appears to hang and shortly after that errors are > > > printed to the console that init is respawning to fast. > > > INIT: Id "1" respawning too fast: disabled for 5 minutes > > > INIT: Id "2" respawning too fast: disabled for 5 minutes > > > INIT: Id "3" respawning too fast: disabled for 5 minutes > > > INIT: Id "4" respawning too fast: disabled for 5 minutes > > > INIT: Id "5" respawning too fast: disabled for 5 minutes > > > INIT: Id "6" respawning too fast: disabled for 5 minutes > > > INIT: no more processes left in this runlevelIn UML this can be a symptom of the NTPL libs. Try ''mv /lib/ /lib/tls.disabled/''. See also: http://uml.harlowhill.com/index.php/Troubleshooting#distrosetup Another thing to try is changing to this line in inittab. 0:2345:respawn:/sbin/getty 38400 ttys/0 Otherwise, maybe tty dev permissions problem. Try udev or devfs. Nicholas ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > > > printed to the console that init is respawning to fast. > > > > INIT: Id "1" respawning too fast: disabled for 5 minutes > > > > INIT: Id "2" respawning too fast: disabled for 5 minutes > > > > INIT: Id "3" respawning too fast: disabled for 5 minutes > > > > INIT: Id "4" respawning too fast: disabled for 5 minutes > > > > INIT: Id "5" respawning too fast: disabled for 5 minutes > > > > INIT: Id "6" respawning too fast: disabled for 5 minutes > > > > INIT: no more processes left in this runlevelXen currently only starts one console for each guest, tty0. To avoid these error messages, comment out the other lines that start getty''s on other terminals in /etc/inittab. In any event, these messages are harmless. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Xen currently only starts one console for each guest, tty0. > To avoid these error messages, comment out the other lines that start > getty''s on other terminals in /etc/inittab.Didn''t we used to fake out the other terminals so that Linux distros wouldn''t complain so much? Just curious... Cheers, Mark> In any event, these messages are harmless. > > Ian > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id396&op=Click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> This sounds like init is trying to spawn the gettys and they''re failing to > open the tty devices -> are you using devfs in the Debian image? > Ensure that the lines in inittab which look like this:Ah right, good point, I hadn''t thought of this - are you in fact using udev? (I''m guessing not DevFS because it doesn''t work in domUs). I''m guess the support in there for keeping the gettys quiet doesn''t help if the device nodes don''t exist!!! In any case, it''s totally harmless and you can comment out the inittab entries, as other people have mentioned, in order to make it go away. Cheers, Mark> > 1:12345:respawn:/sbin/getty 38400 tty1 > > ..for the console gettys, are pointing at a tty device (in this case > /dev/tty1) which exists. > > > > Hope this helps, > > Dave------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt wrote:> >>>>> printed to the console that init is respawning to fast. >>>>> INIT: Id "1" respawning too fast: disabled for 5 minutes >>>>> INIT: Id "2" respawning too fast: disabled for 5 minutes >>>>> INIT: Id "3" respawning too fast: disabled for 5 minutes >>>>> INIT: Id "4" respawning too fast: disabled for 5 minutes >>>>> INIT: Id "5" respawning too fast: disabled for 5 minutes >>>>> INIT: Id "6" respawning too fast: disabled for 5 minutes >>>>> INIT: no more processes left in this runlevel > > Xen currently only starts one console for each guest, tty0. To > avoid these error messages, comment out the other lines that start > getty''s on other terminals in /etc/inittab. > > In any event, these messages are harmless.Um, I hate to disagree with an actual Xen developer who has implemented this whole thing, but I believe you are wrong :-) Those messages are not harmless. Firstly, if Xen really did provide *only* tty0 - no standard Debian installation could ever get a console up, since it only starts consoles on tty1-tty6, not tty0. However, I have booted vanilla Debian installations under Xen, and there are no error messages of this sort - so I believe the first console (tty1) is the Xen console, and others are faked or just don''t give an error message. What these messages really mean (especially the last line, no more processes left) is that init fails to start any of the gettys. This usually happens in two different circumstances: a) INIT is unable to fork *any* processes. This happens with UML when you have /lib/tls around - forks fail. This should not really happen with Xen, but if libc is borked, it might. But if this is the case, then there should be no normal daemon bootup messages either. b) INIT is unable to open the tty devices. This can ofcourse be caused by a number of things - having the wrong root partition, having an empty dev, having devfs mounted without devfsd, having a broken udev mount or simply by having wrong paths in inittab. We had one problem where a Debian image downloaded from the net did not have ''tty1'' etc. as the device paths, but ''vc/1'' instead. (Remember that devfs is not a good idea with Xen guests.) So, I guess the original poster needs to check his filesystem image and that''s all - no Xen bug involved in any case. However, in the case I am actually wrong about this, I already apologize profusely in advance. -- Naked ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> >>>>> printed to the console that init is respawning to fast. > >>>>> INIT: Id "1" respawning too fast: disabled for 5 minutes > >>>>> INIT: Id "2" respawning too fast: disabled for 5 minutes > >>>>> INIT: Id "3" respawning too fast: disabled for 5 minutes > >>>>> INIT: Id "4" respawning too fast: disabled for 5 minutes > >>>>> INIT: Id "5" respawning too fast: disabled for 5 minutes > >>>>> INIT: Id "6" respawning too fast: disabled for 5 minutes > >>>>> INIT: no more processes left in this runlevel> Firstly, if Xen really did provide *only* tty0 - no standard Debian > installation could ever get a console up, since it only starts > consoles on tty1-tty6, not tty0. However, I have booted vanilla Debian > installations under Xen, and there are no error messages of this sort > - so I believe the first console (tty1) is the Xen console, and others > are faked or just don''t give an error message.Yep, we now register dummy devices, so I was totally wrong.> b) INIT is unable to open the tty devices. This can ofcourse be > caused by a number of things - having the wrong root partition, > having an empty dev, having devfs mounted without devfsd, having a > broken udev mount or simply by having wrong paths in inittab. We had > one problem where a Debian image downloaded from the net did not have > ''tty1'' etc. as the device paths, but ''vc/1'' instead. (Remember that > devfs is not a good idea with Xen guests.)That''s the most probable cause. Thanks for correcting me :-) Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel