[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-ia64-devel] why does xenU console stopat"Freeingunusedkernel memory:304KB freed"?
Hi Fujita, Akio and Alex, Could somebody give some hints and introduction about the usage of tty0 in XenU? I am always puzzled by this special setting. :) Why present setting still use "console=tty0" in XenU config and why remove "mingetty tty0" from xenU inittab? I noticed Alex send the patch about xencons several days ago. Best Regards, Yongkang (Kangkang) 永康 >-----Original Message----- >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of yo.fujita >Sent: 2006年7月7日 16:47 >To: 'Akio Takebe'; 'Alex Williamson' >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx >Subject: RE: [Xen-ia64-devel] why does xenU console >stopat"Freeingunusedkernel memory:304KB freed"? > >Hi Akio, > >Thank you for your advice. >It works successfully! >It was fixed by small changes in domU's config and inittab. >I edited lines as below. > >#domU's config >Before editing: extra = "nomca xencons=tty0 console=tty0 3" >After editing : extra = "nomca console=tty0 3" > >#/etc/inittab >Before editing: ># Run gettys in standard runlevels >1:2345:respawn:/sbin/mingetty tty0 >#1:2345:respawn:/sbin/mingetty tty1 >#2:2345:respawn:/sbin/mingetty tty2 >#3:2345:respawn:/sbin/mingetty tty3 >#4:2345:respawn:/sbin/mingetty tty4 >#5:2345:respawn:/sbin/mingetty tty5 >#6:2345:respawn:/sbin/mingetty tty6 > >After editing: ># Run gettys in standard runlevels >#1:2345:respawn:/sbin/mingetty tty0 >1:2345:respawn:/sbin/mingetty tty1 >2:2345:respawn:/sbin/mingetty tty2 >3:2345:respawn:/sbin/mingetty tty3 >4:2345:respawn:/sbin/mingetty tty4 >5:2345:respawn:/sbin/mingetty tty5 >6:2345:respawn:/sbin/mingetty tty6 > >Thanks, >Fujita >> -----Original Message----- >> From: Akio Takebe [mailto:takebe_akio@xxxxxxxxxxxxxx] >> Sent: Friday, July 07, 2006 4:44 PM >> To: yo.fujita; 'Alex Williamson' >> Cc: 'Zhang, Jingke'; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; Akio Takebe >> Subject: RE: [Xen-ia64-devel] why does xenU console stop >> at"Freeingunusedkernel memory:304KB freed"? >> >> Hi, Fujita >> >> I can use domU's console with >> http://free.linux.hp.com/~awilliam/20060706-init/. >> The below is my config file. >> >> [root@PQtest fujita]# cat /etc/xen/takebe >> kernel = "/boot/efi/efi/xen/vmlinuz-2.6.16.13-xen-takebe" >> ramdisk = "/boot/efi/efi/xen/initrd-2.6.16.13-xen.img-takebe" >> memory = 512 >> name = "rhel4-060707" >> disk = [ 'file:/root/rhel4_1.img,hda1,w' ] >> vif = [ '' ] >> root = "/dev/hda1 ro" >> extra = "nomca nosmp console=tty0 3" >> [root@PQtest fujita]# mount -o loop /root/rhel4_1.img /mnt/ >> [root@PQtest fujita]# cat /mnt/etc/inittab >> # >> # inittab This file describes how the INIT process should set up >> # the system in a certain run-level. >> # >> # Author: Miquel van Smoorenburg, ><miquels@xxxxxxxxxxxxxxxxxxxxx> >> # Modified for RHS Linux by Marc Ewing and Donnie >Barnes >> # >> >> # Default runlevel. The runlevels used by RHS are: >> # 0 - halt (Do NOT set initdefault to this) >> # 1 - Single user mode >> # 2 - Multiuser, without NFS (The same as 3, if you do not have >networking) >> # 3 - Full multiuser mode >> # 4 - unused >> # 5 - X11 >> # 6 - reboot (Do NOT set initdefault to this) >> # >> id:3:initdefault: >> >> # System initialization. >> si::sysinit:/etc/rc.d/rc.sysinit >> >> l0:0:wait:/etc/rc.d/rc 0 >> l1:1:wait:/etc/rc.d/rc 1 >> l2:2:wait:/etc/rc.d/rc 2 >> l3:3:wait:/etc/rc.d/rc 3 >> l4:4:wait:/etc/rc.d/rc 4 >> l5:5:wait:/etc/rc.d/rc 5 >> l6:6:wait:/etc/rc.d/rc 6 >> >> # Trap CTRL-ALT-DELETE >> ca::ctrlaltdel:/sbin/shutdown -t3 -r now >> >> # When our UPS tells us power has failed, assume we have a few minutes >> # of power left. Schedule a shutdown for 2 minutes from now. >> # This does, of course, assume you have powerd installed and your >> # UPS connected and working correctly. >> pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting >Down" >> >> # If power was restored before the shutdown kicked in, cancel it. >> pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown >Cancelled" >> >> >> # Run gettys in standard runlevels >> #1:2345:respawn:/sbin/mingetty tty0 >> 1:2345:respawn:/sbin/mingetty tty1 >> 2:2345:respawn:/sbin/mingetty tty2 >> 3:2345:respawn:/sbin/mingetty tty3 >> 4:2345:respawn:/sbin/mingetty tty4 >> 5:2345:respawn:/sbin/mingetty tty5 >> 6:2345:respawn:/sbin/mingetty tty6 >> >> # Run xdm in runlevel 5 >> x:5:respawn:/etc/X11/prefdm -nodaemon >> >> Best Regards, >> >> Akio Takebe >> >> >> >Hi Alex, Akio, >> > >> >Thanks for your advice. >> >> Hopefully the domU console issues are related >> >> to using older tools. >> >The domU console issues occurred on RHEL4U2 which had no compile >error. >> > >> >Thanks, >> >Fujita >> >> -----Original Message----- >> >> From: Alex Williamson [mailto:alex.williamson@xxxxxx] >> >> Sent: Friday, July 07, 2006 1:56 PM >> >> To: Akio Takebe >> >> Cc: yo.fujita; 'Zhang, Jingke'; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx >> >> Subject: RE: [Xen-ia64-devel] why does xenU console stop >> >> at"Freeingunusedkernel memory:304KB freed"? >> >> >> >> On Fri, 2006-07-07 at 13:41 +0900, Akio Takebe wrote: >> >> > Hi, Fujita >> >> > >> >> > The compile error is a bug of fedora core6. >> >> > fedoracore6 don't have linux/compile.h in glibc-kernheaders. >> >> >> >> I agree, my build system has compiler.h provided by the >> >> linux-kernel-headers package (Debian). You could try copying >> >> linux-2.6.16.13-xen/include/linux/compiler.h to /usr/include/linux to >> >> see if tools will build. Hopefully the domU console issues are related >> >> to using older tools. Thanks, >> >> >> >> Alex >> >> >> >> -- >> >> Alex Williamson HP Open Source & >Linux Org. >> > >> > >> > > > > >_______________________________________________ >Xen-ia64-devel mailing list >Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx >http://lists.xensource.com/xen-ia64-devel _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |