This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0
From: PGNet <pgnet.trash+xen@xxxxxxxxx>
Date: Sat, 20 Dec 2008 15:35:18 -0800
Delivery-date: Sat, 20 Dec 2008 15:36:07 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=IbDC9WMy8i1NOR9uaPch7CNBirbI5E7L2F952k1jxbw=; b=MMLmKlqNCTVUOeTDiU93wrLuX5j9d18tV1PhMLfgNvwVBBd0ytKZ8Qd/tQUCQbCSsV nqGZsbNFp3QZuYcsNMXNEiJackHUeW6G1pqc+yKXlkWKjZDfDeJgFlTfGFlWmZEmMcm5 sNE/P8lZnh7zYkSLO9sUtwOtTC11h3/6Fn8vY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=xCkBrUDebY4cNCLqUpKiw8MPO9vBzdAIHjbuUGWIRPe8Glxp+J7GLcyStXack81Kli k29V7GWYf6iMGeNQRb2IAUoaxHGGfG4qTadRpaV14o702I9uJb85EqU90riMItXcnpPE LYDdRk+ePi9DsL+2RyjdcyJ7KOtajv6/RliZI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

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 .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 ...

(ps -- already posted this to 'opensuse-virtual' list; was suggested
to post here as well ...)

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

       /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 #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

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


> 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", 
28, in <module>
                   from xen.xend import XendDomain
         File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 
in <module>
                   from xen.xend import XendOptions, XendCheckpoint, 
         File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", 
20, in <module>
                   from xen.xend import balloon, sxp, image
         File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 44, 
                   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 @


   Next you can activate the Xen daemon:

   /etc/init.d/xend start
   insserv –d xend

   Finally you have to reboot your system:


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 tocapture the Xen startup process output.

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 ...


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>