[Xen-users] Xen disabled with Debian & Xen-Kernel 2.6.18

[Gerhard Wendebourg <gw@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

after I was successful with inserting the kernel 2.6.18-k7 at one
Xen-machine I failed by using it at another and don't understand why:

when starting xend it returns ".. could not connect / error 111"

when starting xend:

 File
"/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xstransact.py",
line 351, in complete
    t = xstransact(path)
  File
"/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xstransact.py",
line 20, in __init__
    self.transaction = xshandle().transaction_start()
  File
"/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xsutil.py",
line 18, in xshandle
    xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

After downgrading to 2.6.17-xen-k7 things worked again.

CPU ist Athlon with 1,833 GHZ.

The difference between installing the systems was:
at the successful with 2.6.18 running one I uninstalled the Debian-Xen
and tried the Xen-binary-installation (with 2.6.29), which didn't work.
After that step I reinstalled the Debian-Xen with 2.6.18, and then Xen
was running.

Some answer on this behaviour - or maybe solution?

GW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFT8B8WgcH1Ne3oGIRAr3aAJ4odVX4dw+VBgggcf8DYdA/b5fcwQCeJEi3
TGiFYLxFDwYNj6SF1yDoaxQ=
=PL/r
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users