Hello, I have Xen running on an Ubuntu 8.04 LTS machine. This machine has been in production for a few months now. Up until recently, all the DomU machines have also been Ubuntu 8.04 machines. Recently, I tried creating a Debian Lenny machine. I use xen tools to create the DomU machines. Upon completion of creating the DomU with xen tools, I start the DomU using the [sanitized] command "xm create -c /etc/xen/<<hostname>>.cfg. The DomU console appears and the normal boot messages begin populating as normal. However, at some point, the boot messages appear to hang in this console. I never get to a login prompt on the console when using this method. I can however, open another instance of Putty and SSH into the DomU machine and use it as normal. So despite the console appearing to hang, the machine appears to be in fine working order. Can anyone point me in the right direction to troubleshoot this? Below is the output from dmesg in the DomU. Output from dmesg: [ 0.030737] console [xvc0] enabled [ 0.030791] Console: colour dummy device 80x25 [ 0.031237] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.031481] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) [ 0.031543] Software IO TLB disabled [ 0.034139] Memory: 228596k/270336k available (2533k kernel code, 33212k reserved, 1331k data, 220k init) [ 0.098742] Calibrating delay using timer specific routine.. 5995.27 BogoMIPS (lpj=11990555) [ 0.098797] Security Framework initialized [ 0.098812] SELinux: Disabled at boot. [ 0.098832] AppArmor: AppArmor initialized [ 0.098844] Failure registering capabilities with primary security module. [ 0.098879] Mount-cache hash table entries: 256 [ 0.099141] CPU: Trace cache: 12K uops, L1 D cache: 16K [ 0.099156] CPU: L2 cache: 2048K [ 0.099172] CPU: Physical Processor ID: 3 [ 0.099176] CPU: Processor Core ID: 0 [ 0.099183] SMP alternatives: switching to UP code [ 0.100570] Freeing SMP alternatives: 23k freed [ 0.100782] Early unpacking initramfs... done [ 0.130064] Brought up 1 CPUs [ 0.130081] CPU0 attaching NULL sched-domain. [ 0.130847] net_namespace: 120 bytes [ 0.130863] failed to set up cpufreq notifier [ 0.150790] Time: 165:165:165 Date: 165/165/65 [ 0.150835] NET: Registered protocol family 16 [ 0.152539] Brought up 1 CPUs [ 0.152556] PCI: Fatal: No config space access function found [ 0.152561] PCI: setting up Xen PCI frontend stub [ 0.153457] ACPI: Interpreter disabled. [ 0.153470] Linux Plug and Play Support v0.97 (c) Adam Belay [ 0.153509] pnp: PnP ACPI: disabled [ 0.153831] xen_mem: Initialising balloon driver. [ 0.155562] Setting mem allocation to 262144 kiB [ 0.155907] PCI: System does not support PCI [ 0.155918] PCI: System does not support PCI [ 0.166387] NET: Registered protocol family 8 [ 0.166392] NET: Registered protocol family 20 [ 0.166480] AppArmor: AppArmor Filesystem Enabled [ 0.167012] NET: Registered protocol family 2 [ 0.170340] Time: xen clocksource has been installed. [ 0.202407] IP route cache hash table entries: 4096 (order: 3, 32768 bytes) [ 0.202608] TCP established hash table entries: 16384 (order: 6, 262144 bytes) [ 0.202707] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [ 0.202799] TCP: Hash tables configured (established 16384 bind 16384) [ 0.202804] TCP reno registered [ 0.214466] checking if image is initramfs... it is [ 0.244498] Freeing initrd memory: 22560k freed [ 0.259728] audit: initializing netlink socket (disabled) [ 0.259760] audit(1238258349.016:1): initialized [ 0.259989] VFS: Disk quotas dquot_6.5.1 [ 0.260021] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.260115] io scheduler noop registered [ 0.260121] io scheduler anticipatory registered [ 0.260124] io scheduler deadline registered [ 0.260133] io scheduler cfq registered (default) [ 0.260440] Xen virtual console successfully installed as xvc0 [ 0.260524] Event-channel device installed. [ 0.268794] Successfully initialized TPM backend driver. [ 0.280006] netfront: Initialising virtual ethernet driver. [ 0.288122] xen-vbd: registered block device major 202 [ 0.288164] blkfront: xvda1: barriers enabled [ 0.297120] blkfront: xvda2: barriers enabled [ 0.321966] rtc: IRQ 8 is not free. [ 0.322107] Linux agpgart interface v0.102 [ 0.323249] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize [ 0.323354] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [ 0.323601] PNP: No PS/2 controller found. Probing ports directly. [ 0.324483] i8042.c: No controller found. [ 0.337947] mice: PS/2 mouse device common for all mice [ 0.338006] cpuidle: using governor ladder [ 0.338090] NET: Registered protocol family 1 [ 0.338167] registered taskstats version 1 [ 0.338180] XENBUS: Device with no driver: device/console/0 [ 0.338194] Magic number: 1:252:3141 [ 0.338327] /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 0.338338] Freeing unused kernel memory: 220k freed [ 0.637544] fuse init (API version 7.9) [ 0.678357] thermal: Unknown symbol acpi_processor_set_thermal_limit [ 0.696756] device-mapper: uevent: version 1.0.3 [ 0.696833] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com [ 0.719650] md: linear personality registered for level -1 [ 0.726626] md: multipath personality registered for level -4 [ 0.733354] md: raid0 personality registered for level 0 [ 0.740722] md: raid1 personality registered for level 1 [ 0.747314] xor: automatically using best checksumming function: generic_sse [ 0.765850] generic_sse: 3034.000 MB/sec [ 0.765855] xor: using function: generic_sse (3034.000 MB/sec) [ 0.766563] async_tx: api initialized (async) [ 0.833914] raid6: int64x1 1456 MB/s [ 0.901926] raid6: int64x2 2047 MB/s [ 0.969941] raid6: int64x4 2176 MB/s [ 1.037972] raid6: int64x8 1912 MB/s [ 1.105987] raid6: sse2x1 2151 MB/s [ 1.174003] raid6: sse2x2 3157 MB/s [ 1.242040] raid6: sse2x4 3031 MB/s [ 1.242045] raid6: using algorithm sse2x2 (3157 MB/s) [ 1.242053] md: raid6 personality registered for level 6 [ 1.242061] md: raid5 personality registered for level 5 [ 1.242066] md: raid4 personality registered for level 4 [ 1.271599] md: raid10 personality registered for level 10 [ 7.770540] kjournald starting. Commit interval 5 seconds [ 7.770562] EXT3-fs: mounted filesystem with ordered data mode. [ 8.846702] udevd version 125 started [ 10.491278] Adding 524280k swap on /dev/xvda1. Priority:-1 extents:1 across:524280k [ 10.848880] EXT3 FS on xvda2, internal journal [ 91.706139] NET: Registered protocol family 10 [ 91.706653] lo: Disabled Privacy Extensions [ 102.045625] eth0: no IPv6 routers present [ 116.206746] ip_tables: (C) 2000-2006 Netfilter Core Team Tom Jensen | President Digital Toolbox _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Luke S Crawford
2009-Mar-31 04:11 UTC
Re: [Xen-users] DomU console appears to hang when starting
"Tom Jensen" <tom.jensen@digitaltoolbox-inc.com> writes:> The DomU console appears and the normal boot messages begin populating as normal. However, at some point, the boot messages appear to hang in this console.you saw the line [ 0.260440] Xen virtual console successfully installed as xvc0 in dmesg? that means you need to run a getty on xvc0. On CentOS/RHEL, you''d do this in /etc/inittab. I''m not sure about debian. (it''s a tricky problem ''cause there are several different things that different kernels call the xen virtual console; so when I get this problem, the first thing I do is grep for ''Xen virtual console'' in the DomU dmesg so I know what to run a getty on.) -- Luke S. Crawford http://prgmr.com/xen/ - Hosting for the technically adept We don''t assume you are stupid. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tom Jensen
2009-Apr-06 02:46 UTC
Re: [Xen-users] DomU console appears to hang when starting
I checked the file /etc/inittab. I did a search and did not see any instance of the xvc0 so I assume I need to add it. As I mentioned in my original thread, this is my first time building a non-Ubuntu DomU. I have never had to modify the /etc/inittab file before. Do you have any references on what I need to add to the inittab file to make it work for Xen? Tom Jensen | President Digital Toolbox -------------------------------------------------- From: "Luke S Crawford" <lsc@prgmr.com> Sent: Monday, March 30, 2009 11:11 PM To: "Tom Jensen" <tom.jensen@digitaltoolbox-inc.com> Cc: <xen-users@lists.xensource.com> Subject: Re: [Xen-users] DomU console appears to hang when starting> "Tom Jensen" <tom.jensen@digitaltoolbox-inc.com> writes: > >> The DomU console appears and the normal boot messages begin populating as >> normal. However, at some point, the boot messages appear to hang in this >> console. > > you saw the line > > [ 0.260440] Xen virtual console successfully installed as xvc0 > > in dmesg? > > that means you need to run a getty on xvc0. On CentOS/RHEL, you''d do > this in /etc/inittab. I''m not sure about debian. > > (it''s a tricky problem ''cause there are several different things that > different > kernels call the xen virtual console; so when I get this problem, the > first thing I do is grep for ''Xen virtual console'' in the DomU dmesg so > I know what to run a getty on.) > > -- > Luke S. Crawford > http://prgmr.com/xen/ - Hosting for the technically adept > We don''t assume you are stupid. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users