Xen users - Nov 2008 - xend won''t start on Ubuntu Hardy server

I installed Xen 3.2 on an Ubuntu 8.04.1 server (via the ubuntu-xen-server
package).  But when I booted Xen (2.6.24-21-xen), xend wouldn''t start.

I tried "/etc/init.d/xend start" by hand, and I got several instances
of
the following:

Traceback (most recent call last):
  File "/usr/sbin/xend", line 44, in <module>
    from xen.xend.server import SrvDaemon
  File
"/usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py", line
20, in <module>
    import xen.lowlevel.xc
ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: undefined
symbol: xc_domain_setcpuweight

I wiped the box clean and reinstalled from scratch, with the same result.

Any suggestions?

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

On Mon, Nov 10, 2008 at 10:50:31PM -0800, Rich Wales wrote:
> ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: undefined
> symbol: xc_domain_setcpuweight
> 
> I wiped the box clean and reinstalled from scratch, with the same result.
> 
> Any suggestions?
ldd /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so

Rainer

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

Rainer Sokoll wrote:
> ldd /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so
and when I did the above command, I got this:

        linux-gate.so.1 =>  (0xf57fe000)
        libxenctrl.so.3.2 => /usr/lib/libxenctrl.so.3.2 (0xb7ec7000)
        libxenguest.so.3.2 => /usr/lib/libxenguest.so.3.2 (0xb7eaa000)
        libxenstore.so.3.0 => /usr/lib/libxenstore.so.3.0 (0xb7ea2000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7e8b000)
        libc.so.6 => /lib/libc.so.6 (0xb7d52000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb7d3d000)
        /lib/ld-linux.so.2 (0xb7f14000)

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Earlier, I wrote:
> I installed Xen 3.2 on an Ubuntu 8.04.1 server (via the ubuntu-xen-server
> package).  But when I booted Xen (2.6.24-21-xen), xend wouldn''t
start.
and I described getting "undefined symbol" errors from /usr/sbin/xend
for
the symbol "xc_domain_setcpuweight".

I uninstalled all traces of Xen 3.2, then installed 3.3 in its place.  The
problem appears to have gone away; Xen starts and runs OK now.

I''m still concerned about the earlier error, though.  The (apparent)
fact
that no one can explain it makes me worry that it might pop up again with
no warning.  I''d welcome any thoughts.

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Rich Wales:
> I''m still concerned about the earlier error, though.  The
(apparent)
> fact that no one can explain it makes me worry that it might pop up
> again with no warning.  I''d welcome any thoughts.
I''ve also seen the message
ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so:
undefined symbol: xc_domain_setcpuweight

AFAICT the culprit was the hardy-backports repository providing a 3.3
version of libxen3. This seems to be exceptionally brain-dead since it
is the only available Xen-related package that is on 3.3 level. All
other Hardy Xen packages (xen-utils, the hypervisor etc.) are still 3.2.
After replacing the libxen3 from backports with the 3.2-version from
main, I was able to start xend again.

Regards
  mks




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

Markus Schönhaber skrev den 29-11-2008 00:28:
> Rich Wales:
>
>   
>> I''m still concerned about the earlier error, though.  The
(apparent)
>> fact that no one can explain it makes me worry that it might pop up
>> again with no warning.  I''d welcome any thoughts.
>>     
>
> I''ve also seen the message
> ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so:
> undefined symbol: xc_domain_setcpuweight
>
> AFAICT the culprit was the hardy-backports repository providing a 3.3
> version of libxen3. This seems to be exceptionally brain-dead since it
> is the only available Xen-related package that is on 3.3 level. All
> other Hardy Xen packages (xen-utils, the hypervisor etc.) are still 3.2.
> After replacing the libxen3 from backports with the 3.2-version from
> main, I was able to start xend again.
>   
I got a running 3.3 system from Hardy backports with 3.3 packages of 
xen-utils, hypervisor and python-xen.
My problem and solution was to uninstall xen-utils 3.2 before installing 
3.3.


--
Morten Christensen

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

hi,

Am Samstag, den 29.11.2008, 11:42 +0100 schrieb Morten
Christensen:
>   
> I got a running 3.3 system from Hardy backports with 3.3 packages of 
> xen-utils, hypervisor and python-xen.
> My problem and solution was to uninstall xen-utils 3.2 before installing 
> 3.3.
i got also everything running with the hardy (multiverse) backports from
Xen 3.3. Including HVM.

cu denny


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

Denny Schierz:
> Am Samstag, den 29.11.2008, 11:42 +0100 schrieb Morten Christensen:
>> I got a running 3.3 system from Hardy backports with 3.3 packages of 
>> xen-utils, hypervisor and python-xen.
>> My problem and solution was to uninstall xen-utils 3.2 before
installing
>> 3.3.
> 
> i got also everything running with the hardy (multiverse) backports from
> Xen 3.3. Including HVM.
I don''t doubt that, and looking for Xen packages at
http://packages.ubuntu.com/hardy-backports/allpackages
verifies it (time to take "brain-dead" back).
Nevertheless, on one of my machines only libxen3 got updated leading to
the same error on xend startup as the OP saw. So, chances are that the
same mix between 3.2 and 3.3 packages I saw was the reason for the OP''s
problem too.

Regards
  mks

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

Markus Schönhaber:
> Denny Schierz:
> 
>> i got also everything running with the hardy (multiverse) backports
from
>> Xen 3.3. Including HVM.
> 
> I don''t doubt that, and looking for Xen packages at
> http://packages.ubuntu.com/hardy-backports/allpackages
> verifies it (time to take "brain-dead" back).
> Nevertheless, on one of my machines only libxen3 got updated leading to
> the same error on xend startup as the OP saw. So, chances are that the
> same mix between 3.2 and 3.3 packages I saw was the reason for the
OP''s
> problem too.
Looking at this more closely I tend to reconsider taking "brain-dead"
back: while there are *different* packages for the 3.2/3.3 Xen
hypervisor and the 3.2/3.3 Xen utils, there is only *one* libxen3
package available. So if you simply install the available updates
without actively installing the other 3.3 Xen packages, you''ll end up
with this non-working mix.

Regards
  mks

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

hi,

Am Samstag, den 29.11.2008, 13:44 +0100 schrieb Markus Schönhaber:
> Nevertheless, on one of my machines only libxen3 got updated leading to
> the same error on xend startup as the OP saw. So, chances are that the
> same mix between 3.2 and 3.3 packages I saw was the reason for the
OP''s
> problem too.
the only one that i had sometimes, are bad messages about "time went
backwards" . I used hardy 5 times in my last course and we all had no
problems. HVM and live migration works (NFS und DRBD with ISCSI) too :-)

cu denny


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

hi,

Am Samstag, den 29.11.2008, 13:57 +0100 schrieb Markus Schönhaber:
> without actively installing the other 3.3 Xen packages, you''ll end
up
> with this non-working mix.
hmm, ok. It seems so, but i started with a fresh install.  so, that
makes the difference. 

cu denny  


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

Denny Schierz:
> Am Samstag, den 29.11.2008, 13:57 +0100 schrieb Markus Schönhaber:
> 
>> without actively installing the other 3.3 Xen packages, you''ll
end up
>> with this non-working mix.
> 
> hmm, ok. It seems so, but i started with a fresh install.  so, that
> makes the difference. 
Not necessarily. If you install xen-hypervisor-3.2, xen-utils-3.2 etc.
you''ll still get a libxen3 on 3.3 level from backports. It seems that
is
what the OP did (ending up with a broken Xen install, obviously).

Regards
  mks

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

Markus Schönhaber:
> Denny Schierz:
>> hmm, ok. It seems so, but i started with a fresh install.  so, that
>> makes the difference. 
> 
> Not necessarily.
More precisely: not at all. Whether or not you start a fresh install
seems to be completely irrelevant. AFAICT what did make the difference
is that you installed Xen 3.3.
I did a fresh install using the ubuntu-xen-server meta package which
left me with a xend that wouldn''t start with the already mentioned
error
message. This isn''t too surprising if you take a look at
ubuntu-xen-server''s dependencies:
# LC_ALL=C apt-cache depends ubuntu-xen-server
ubuntu-xen-server
  Depends: bridge-utils
  Depends: libxen3
  Depends: linux-xen
  Depends: python-xen-3.2
  Depends: xen-docs-3.2
  Depends: xen-hypervisor-3.2
  Depends: xen-tools
You get mostly 3.2 Xen components - except libxen3, which will be on 3.3
level (provided the backports repositories are enabled). And this won''t
work.

Regards
  mks


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