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",
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash+F@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c1 Summary: xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0 Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: pgnet.trash+F@gmail.com QAContact: qa@suse.de Found By: Customer 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 -- Xen Dom0 on 11.1 w/ RAID-1 is not working; not clear as to why not. drop back to same setup on v11.0 -- all's ok. i've now reproduced this on another box, so posting it as a bug (?). i'm happy to provide any info -- just need some guidance as to where to look .. here are the 'gory details': 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 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 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 next, 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: "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 ... checking, nothing is written to /var/log/xen/xend.log or /var/log/messages. rebooting to non-xen kernel, all is ok again. at the non-xen kernel system's prompt, checking, service xend start returns simply xend unused and, 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)') It was pointed out to me elsewhere that, > xend can't start on a non-xen kernel, it doesn't have /proc/xen/* etc. If true, 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 ... for debugging, I'm in the process of trying to communicate with the box via serial port to capture the Xen startup process output. no luck with serial comms -- yet ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.