Hi, On Sat, Dec 20, 2008 at 2:44 PM, Todd Deshane <deshantm@gmail.com> wrote:
OK, so this looks like a file system problem. What file systems are being mount in /etc/fstab?
Arguably the same as for the boot to normal, non-xen kernel, no? cat /etc/fstab /dev/md0 /boot ext3 acl,user_xattr 1 2 /dev/System/Root / ext3 acl,user_xattr 1 1 /dev/System/Swap swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 Again, boot to non-xen kernel is OK. And no apparent filesystem/mount trouble, dmesg | egrep -i "fs|mount" Mount-cache hash table entries: 256 ACPI: Checking initramfs for custom DSDT Unpacking initramfs... done VFS: Disk quotas dquot_6.5.1 usbcore: registered new interface driver usbfs EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/System-Root 13G 2.1G 9.8G 18% / udev 4.2G 160k 4.2G 1% /dev /dev/md0 152M 52M 92M 37% /boot
Can you go through one at a time and see if you can find the problem?
fsck may be able to fix the corrupt partition, but of course use it carefully.
I'm reticent to fix 'problems' that exist only in the kernel-xen instance, but go away for normal kernel boot. THat doesn't seem like a FS error ... Am I misguided here?
May not be needed for this problem, since it is probably a file system problem, but have the debug console around is really nice for problems in general so it is a good thing to have working when needed.
Understood. I've managed to find a serial-port connector card & cable for the mobo's serial header, found a Keyspan USB-to-serial connector (I'm on a Mac ...), and built up minicom on OSX. I've verified it works connecting to a FreeBSD/Soekris box's serial port. On the Opensuse box, I've added to /boot/grub/menu.lst ... ###Don't change this comment - YaST2 identifier: Original name: xen### title Xen (x86_64) com1 and debug root (hd0,0) kernel /boot/xen-dbg.gz loglvl=all guest_loglvl=all debug_stack_lines=80 console=vga,com1 com1=115200,8n1 module /vmlinuz-xen root=/dev/System/Root resume=/dev/System/Swap splash=silent showopts vga=0x317 console=ttyS0, 115200 module /initrd-xen ... which I *think* is correct for my setup. At reboot to this grub selection, I see the "(XEN) ..." output @ VGA console, then "... Relinquishing console ...", and no more output @ the console. I gather at this point the output's been redirected to the serial port. Unfortunately, I see not a trace of connectivity in minicom :-/ Not clear as yet as to what's not working. I'll dig some more, but, as you suggest, the problem may lie elsewhere. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org