Re: [Xen-users] Xen 3.1.0 "Error: Unable to connect to xend: No such file or directory. Is xend running?"

["Steven Wilson" <steven.e.wilson@xxxxxxxxx>]

We already have selinux disabled.  What's strange is that a fresh OS
and Xen install works (xm commands work, domU's start) until the dom0
is rebooted.  Here's the last few entries in
/var/log/xen/xend-debug.log after a reboot and then running "service
xend restart"

Xend started at Thu May 31 08:18:45 2007.^@Exception starting xend:
(28, 'No space left on device, while writing
/vm/00000000-0000-0000-0000-000000000000/shadow_memory : 0')
Xend started at Thu May 31 08:23:55 2007.
Exception starting xend: (28, 'No space left on device, while writing
/vm/00000000-0000-0000-0000-000000000000/shadow_memory : 0')
Xend started at Thu May 31 08:26:23 2007.
Exception starting xend: (5, 'Input/output error')

We don't appear to have any disk space issues:

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                     9.9G  5.5G  3.9G  59% /
/dev/sda1              99M   24M   71M  25% /boot
tmpfs                 257M     0  257M   0% /dev/shm

What else could cause xend to generate an 'Input/output error'?
No other system problems are apparent.

On 5/31/07, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > Steven Wilson
> > Sent: 31 May 2007 14:05
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] Xen 3.1.0 "Error: Unable to connect to
> > xend: No such file or directory. Is xend running?"
> >
> > Hello,
> >
> > We are running Xen 3.1.0 on CentOS 5 using the pre-build RPM's from
> > Xensource.  Upon a clean reboot the dom0 (i.e. no domU's running), we
> > see this message when attempting to run any "xm" command:
> >
> > # xm list
> > Error: Unable to connect to xend: No such file or directory.
> > Is xend running?
> >
> > We do see the various xen processes running:
> >
> > # ps -ef | grep xen | grep -v grep
> > root        13    11  0 08:48 ?        00:00:00 [xenwatch]
> > root        14    11  0 08:48 ?        00:00:00 [xenbus]
> > root     11078     1  0 08:49 ?        00:00:00 xenstored --pid-file
> > /var/run/xenstore.pid
> > root     11083     1  0 08:49 ?        00:00:00 python
> > /usr/sbin/xend start
> > root     11085     1  0 08:49 ?        00:00:00 xenconsoled
> > root     11087 11083  0 08:49 ?        00:00:00 python
> > /usr/sbin/xend start
> >
> > Not even a re-install of the Xen RPM's seems to correct issue.
> > Anyone else seeing this problem?  We have xendomains turned off.
>
> Is it possible that you are seeing a problem caused by something like
> "selinux"? If you have selinux enabled, try disabling it and see if that
> improves things... I'm not giving any promises, but certainly something
> is not quite right in this setup, and it looks like you have the right
> processes running, so that's not the issue.
> >
> > Also, even though /lib/tls was renamed to /lib/tls.disabled, we still
> > see the tls performance warning message during boot.
>
> This is normal for certain builds of Linux - it's because "nash" (or
> some other component used by the "initrd") are using statically linked
> libraries that use TLS. Since this process disappears before the system
> is up and running, I wouldn't worry about it - if you really want to
> "fix" it, then you will have to rebuild the component in question that
> is in your initrd, and then rebuild the initrd to make use of this newly
> built version. But I wouldn't worry.
>
> --
> Mats
> >
> > Any info appreciated.
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >
> >
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users