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 "IPv6 over IP4 tunneling driver" or "EXT3 FS on hda2, internal Journal". But the domU is starting without any complications. Just to see the domU booting via "xm create host.example.tld.cfg -c doesnt work correctly. Is there any problem with serial console or something had to be build in kernel? I wonder cause i use the standard kernel configuration like described above. Holm _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I assume your xm console just uses a wrong tty. You could try a) add a line to your domU config. extra=''xencons=tty1'' or b) add a xvc0 tty _inside_ domU: cat /etc/event.d/tty1 | sed ''s,tty12,xvc0,g'' >/etc/event.d/xvc0 xvc0 should be also added to /etc/securetty cheers, Stephan Holm Kapschitzki schrieb:> 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 "IPv6 over IP4 tunneling driver" or "EXT3 FS > on hda2, internal Journal". But the domU is starting without any > complications. Just to see the domU booting via "xm create > host.example.tld.cfg -c doesnt work correctly. > > Is there any problem with serial console or something had to be build in > kernel? I wonder cause i use the standard kernel configuration like > described above. > > > Holm >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Holm Kapschitzki
2008-Sep-15 21:51 UTC
Re: [Xen-users] xen 3.3.0 etch sources console hangs
Stephan Seitz schrieb:> I assume your xm console just uses a wrong tty. > > You could try > a) add a line to your domU config. > extra=''xencons=tty1'' >works fine> or > b) add a xvc0 tty _inside_ domU: > cat /etc/event.d/tty1 | sed ''s,tty12,xvc0,g'' >/etc/event.d/xvc0 > xvc0 should be also added to /etc/securettyin debian in have to make some changes to /etc/inittab and /etc/securetty? But i am not sure about the settings to inittab. Possible to set? 0:2345:respawn:/sbin/getty 38400 tty0 original etch: # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty''s go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 #2:23:respawn:/sbin/getty 38400 tty2 #3:23:respawn:/sbin/getty 38400 tty3 #4:23:respawn:/sbin/getty 38400 tty4 #5:23:respawn:/sbin/getty 38400 tty5 #6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 Holm _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Holm Kapschitzki wrote:> Stephan Seitz schrieb: >> I assume your xm console just uses a wrong tty. >> >> You could try >> a) add a line to your domU config. >> extra=''xencons=tty1'' >> > > works fine > >> or >> b) add a xvc0 tty _inside_ domU: >> cat /etc/event.d/tty1 | sed ''s,tty12,xvc0,g'' >/etc/event.d/xvc0 >> xvc0 should be also added to /etc/securetty > > in debian in have to make some changes to /etc/inittab and > /etc/securetty? But i am not sure about the settings to inittab.... Here are my notes for Xen 3.3.0 on Debian Etch - it took a lot of googling to find all the pieces to the puzzle - including incorrect device numbers for xvc0 in many people''s posts. http://www.hants.lug.org.uk/cgi-bin/wiki.pl?LinuxHints/XenOnEtch Simon C _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users