similar to: Init checking for processes that are configured to "respawn"

Hi Pasi, if I don''t change the tty to hvc it will stopped on Kernel 2.6.31.13 on i686 (console) localhost login: root Kernel 2.6.31.13 on i686 (console) localhost login: root Kernel 2.6.31.13 on i686 (console) localhost login: root After I change it to hvc0 followed the twiki page the log is Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK

Hi list, I am running a virtualized server. Dom0 uses Xen 3.2.1 with Debian Etch and a custom kernel 2.6.21 created by my webhosting company. I install my domU using debootstrap for a Debian Etch with 2.6.18-6-xen-amd64 kernel. Everything works well except the fact that once the VM is started I cannot "xm console" into it. It only works while it is booting and while it is shutting

Also unify .index-fragment files --- builder/templates/debian-7.index-fragment | 7 ------- builder/templates/debian-8.index-fragment | 7 ------- builder/templates/debian-9.index-fragment | 18 ++++++------------ builder/templates/debian.preseed | 1 + builder/templates/make-template.ml | 6 ------ 5 files changed, 7 insertions(+), 32 deletions(-) diff --git

Thread stealing is not nice, even if the subject is generic. > Related question - what physical device does /dev/xvc0 refer to? What can > I > connect to get to the agetty running on this device? > xvc0 is a xen virtual console and does not correspond directly to a physical device that I am aware of. Yves-Gaël Chény seemed to have answered the second part of the question: >

Guys (and Gals), FYI I also have the *same* message here. Wonder is it is related to my Compaq D500 Space Saver PIV 1.7 or the fact that I don't yet have a modem card in the * box. (Please don't shoot me, did try Google first) Many thanks, Wagner Gimenes -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf

Hello All, After a few months of hiatus, we have resumed working on mips port of Xen. We are at the point of booting dom0 userland (init process and its children). The init process gets spawned and in turn forks off processes to run commands in /etc/rc.d/init.d/rcS. However, the getty process does not seem to run subsequently and hence the login prompt is not displayed. Dom 0 does not use the

Hi, I''m running Xen 4 on Slack64. I haven''t console login prompt to domU until I changed xvc0 to hvc0 on /etc/inittab file. No I have access to login but whenever I try to login I get this error from /var/adm/secure file root@darkstar:/var/adm# cat secure Apr 28 22:49:22 darkstar login[1286]: ILLEGAL ROOT LOGIN on `hvc0'' Apr 28 22:49:45 darkstar last message repeated

I just installed xen-linux-system-2.6.26-1-xen-amd64 2.6.26-7 on a freshly installed Debian Lenny AMD64 system, and when I create a Debian Lenny DomU with xen-tools I cannot attach to a console nor log in with SSH. When running # xm create -c test.cfg the system starts booting, but it seems to "freeze" after the kernel has booted. Googling a bit, shows that I seem to have the problem

Hello, I''ve got a problem to get a serial output on grub, xen, linux-xen0 and getty. The serial works fine with grub, xen and linux-xen0, but I''m unable to start a console, where I''m able to login. I dont''t get any output. If I change only the getty from ttyS0 to ttyS1 than I''m able to login.. At the attachment you can see what I see through a serial,

Hello, sorry, for 1 more question on CentOS 5 -> CentOS 6 migration. On my old CentOS 5.7 machine I have the following line: pref:3:respawn:/bin/su -c '/usr/local/pref/pref.pl >/tmp/pref-`date +%a`.txt 2>&1' afarber and this has served me well, I don't want to install anything else like daemontools etc. - to keep my web-server easily reinstallable (or movable to

Hello all, I recently started seeing these messages on the consoles of three production Centos 5.2 servers. They have been occurring nonstop for the past few days and show up routinely every five minutes. INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast:

I''m running Xen 3.2 on Debian 5.0 (Lenny) and am having trouble booting up a Debian Etch DomU. It hangs at the end when it says "Starting periodic command scheduler: cron." It''s just completely frozen. At one point I set it sit for a few hours and got back into the console and it said something about "time went backwards" but I used the

I installed xen 3.3.0 on a etch box from sources. I just modified the standard kernel cause of some hardware drivers. I installed xen-tools from backports (3.9-3~bpo40+1). To create a domU ist not the problem. I can connect via ssh and everything works fine. But when i start a domU with "xm create host.example.tld.cfg -c" to login to console from domU it hangs after the message

I am trying to get a CentOS 6.3 serial console to work with IPMI SOL. I think I have everything working but maybe the wrong baud rate on the getty: $ ipmitool -I lanplus -U root -H 10.0.0.14 sol activate Password: [SOL Session operational. Use ~? for help] ?????????? 10.0.0.14 is the DRAC IP address of the CentOS 6.3 box. It accepts the password and connects me to the console but then when I

Hello xen-users ! I am coming for help concerning the just released 4.0 version. Install has worked rather well on my Debian Lenny. I have just had a few bugs for which I have found the answer looking around on this list. I have created a Debian Lenny domU which boots up just fine. The only problem is that I am unable to get a console prompt when using "xm console nameofdomU". I do see

We run a CentOS-5 based hylafax server with external serial modems. We are transitioning to an Asterisk system using IAXmodem running on CentOS-6. On the CentOS-5 system to start the fax modems we added these lines to inittab: # Add fax lines and always ALWAYS run "telinit q" after making a change. fax1:2345:respawn:/usr/sbin/faxgetty ttyS0 fax2:2345:respawn:/usr/sbin/faxgetty ttyS1

Hi all, I have a question on /etc/inittab for DomU booted with xencons parameter. I saw the following error messages when I appended xencons=ttyS to DomU boot option. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id

Hi, This is my setting: I have a Logical Volume /dev/VG/suse with Suse installed. I have added it to the grub and I can boot it and works perfectly fine. Now I am running /dev/VG/root which is running Xen0. I have created a Xen config file to boot a VM with disk: /dev/VG/suse. In other words I want to boot /dev/VG/suse as a virtual machine. Below is what I am getting at boot time :

I decided to upgrade from openSuse 10.2 to openSuse 10.3. I installed xen things, but when I boot using xen option the system is blocked. It appears the green window, with little suse logo in the middle, and mouse cursor, but the system crashes. My computer is a Pentium 4 1,5 GHz, 512 MB of RAM. I attached "diff boot.msg boot.omsg" (as diff opensuse-normal-kernel opensuse-xen-kernel)

Hello, I have installed Ubuntu Interpid in pv domU. It boots fine, but I cannot get any console running. The boot hangs on: * Setting up console font and keymap... [ OK ] * Starting system log daemon... [ OK ] * Starting kernel log daemon... [ OK ] And then nothing happens. My config file looks like that: bootloader = ''/usr/bin/pygrub'' memory = 2048 name =