[opensuse-virtual] xen/kernel-xen on OS 11.1 not starting; OK on 11.0
i've been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ... i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- not working, and not clear as to why not, yet. i've partitioned, as always, as RAID-1 across two disks, sda + sdb, each part1 150 MB, LinuxRaid part2 10 GB, LinuxRaid part3 *, LinuxRaid RAID-1 /dev/md0 = sda1 + sdb1, mount_pt = '/boot', ext3 /dev/md1 = sda2 + sdb2 Volume Group "System" Logical Volume "Swap", mount_pt = 'swap', 512 MB, Logical Volume "Root", mount_pt = '/', * /dev/md2 = sda3 + sdb3 with this setup, boot to non-xen kernel works perfectly, as it did on OpenSuse 11.0, uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux lsb_release -r Release: 11.1 i've installed zypper in -t pattern xen-server rpm -qa | grep -i xen kernel-xen-base-2.6.27.7-9.1 xen-libs-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 kernel-xen-2.6.27.7-9.1 kernel-xen-extra-2.6.27.7-9.1 xen-3.3.1_18494_03-1.8 on attempt to boot to xen kernel, it fails ... @ boot console I see mention of '/var' not available scroll quickly by, and something about fsck.ext3 failing ... then i'm dumped @ a console prompt. i *can* login, but ... /var exists and is populated, but nothing is written to /var/log/xen/xend.log or /var/log/messages. /boot exists, but is completely empty (?). rebooting, I can get back to non-xen kernel and all is ok again. checking, service xend start returns simply xend unused not sure if this is informative, xend ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 44, in <module> from xen.xend.server import SrvDaemon File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line 26, in <module> import relocate File "/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py", line 28, in <module> from xen.xend import XendDomain File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 35, in <module> from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module> from xen.xend import balloon, sxp, image File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 44, in <module> xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)') something's changed between 11.0 & 11.1. entirely possible i've missed some new config req'ts. what do I need to do to get xen behaving under 11.1? i'm happy to provide any info -- just need some guidance as to where to look ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Some question/comments inline. On Sat, Dec 20, 2008 at 2:05 PM, PGNet <pgnet.trash+osvm@gmail.com> wrote:
i've been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ...
i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- not working, and not clear as to why not, yet.
i've partitioned, as always, as RAID-1 across two disks,
sda + sdb, each part1 150 MB, LinuxRaid part2 10 GB, LinuxRaid part3 *, LinuxRaid
RAID-1 /dev/md0 = sda1 + sdb1, mount_pt = '/boot', ext3 /dev/md1 = sda2 + sdb2 Volume Group "System" Logical Volume "Swap", mount_pt = 'swap', 512 MB, Logical Volume "Root", mount_pt = '/', * /dev/md2 = sda3 + sdb3
with this setup, boot to non-xen kernel works perfectly, as it did on OpenSuse 11.0,
uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux lsb_release -r Release: 11.1
i've installed
zypper in -t pattern xen-server rpm -qa | grep -i xen kernel-xen-base-2.6.27.7-9.1 xen-libs-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 kernel-xen-2.6.27.7-9.1 kernel-xen-extra-2.6.27.7-9.1 xen-3.3.1_18494_03-1.8
on attempt to boot to xen kernel, it fails ...
@ boot console I see mention of '/var' not available scroll quickly by, and something about fsck.ext3 failing ... then i'm dumped @ a console prompt.
i *can* login, but ...
A normal login prompt?
/var exists and is populated, but nothing is written to /var/log/xen/xend.log or /var/log/messages.
/boot exists, but is completely empty (?).
Is it that boot is not mounted? try mount /boot Can you use these instructions to capture the serial output? http://en.opensuse.org/How_to_Capture_Xen_Hypervisor_and_Kernel_Messages_usi...
rebooting, I can get back to non-xen kernel and all is ok again.
checking,
service xend start
returns simply
xend unused
not sure if this is informative,
xend ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 44, in <module> from xen.xend.server import SrvDaemon File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line 26, in <module> import relocate File "/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py", line 28, in <module> from xen.xend import XendDomain File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 35, in <module> from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module> from xen.xend import balloon, sxp, image File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 44, in <module> xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')
xend can't start on a non-xen kernel, it doesn't have /proc/xen/* etc.
something's changed between 11.0 & 11.1. entirely possible i've missed some new config req'ts.
what do I need to do to get xen behaving under 11.1?
i'm happy to provide any info -- just need some guidance as to where to look ...
The real question is: where is it erroring out... The captured output requested above may help shed some light. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Todd, On Sat, Dec 20, 2008 at 1:37 PM, Todd Deshane <deshantm@gmail.com> wrote:
Some question/comments inline.
i *can* login, but ...
A normal login prompt?
this is what eventually is displayed at the end of console output: "fsck failed for at lease one filesystem (not /). Please repair manually and reboot. The root file system is is already mounted read-write. Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root passwod for login:" I enter the password ... "if: Expression Syntax. (none) /root # (none) /root # ls -ald /var /boot drwxr-xr-x 15 root root 4096 Dec 19 18:20 /var drwxr-xr-x 2 root root 4096 Dec 19 18:12 /boot (none) /root # ls /boot (none) /root #
Is it that boot is not mounted? try mount /boot
(none) /root # (none) /root # mount /boot "EXT3-fs: unable to read superblock mount: wrong fs type, bad option, bad superblock on /dev/md0" (none) /root # (none) /root # reboot ... which, despite the admonition above, DOES work ...
Can you use these instructions to capture the serial output? http://en.opensuse.org/How_to_Capture_Xen_Hypervisor_and_Kernel_Messages_usi...
Working on it now ... digging for cables, etc. Might take a bit ...
xend can't start on a non-xen kernel, it doesn't have /proc/xen/* etc.
Hm ... then, I've clearly misread this: http://en.opensuse.org/Installing_Xen3 "... Next you can activate the Xen daemon: /etc/init.d/xend start insserv –d xend Finally you have to reboot your system: reboot ..." which seems to me to imply that 'xend' can be started before rebooting into the xen kernel ... Fair enough.
The real question is: where is it erroring out... The captured output requested above may help shed some light.
Will follow-up here when I've figured out the serial connection etc. Thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Sat, Dec 20, 2008 at 5:34 PM, PGNet <pgnet.trash+osvm@gmail.com> wrote:
Todd,
On Sat, Dec 20, 2008 at 1:37 PM, Todd Deshane <deshantm@gmail.com> wrote:
A normal login prompt?
this is what eventually is displayed at the end of console output:
"fsck failed for at lease one filesystem (not /). Please repair manually and reboot. The root file system is is already mounted read-write.
OK, so this looks like a file system problem. What file systems are being mount in /etc/fstab? 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.
Will follow-up here when I've figured out the serial connection etc.
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. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
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
patch @ https://bugzilla.novell.com/show_bug.cgi?id=461673 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
participants (2)
-
PGNet -
Todd Deshane