FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 02-19-2009, 12:38 AM
"Oliver Schneider"
 
Default Xen on lenny fails after upgrade from etch?

Hi,

when I upgraded a test system (from etch) to lenny, one of the upgrade steps related to Xen fails. Any ideas?

I tried reinstalling the packages, but get the same error all the time:
------------------------------
Starting XEN control daemon: xendTraceback (most recent call last):
File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in <module>
from xen.xend.server import SrvDaemon
File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/server/SrvDaemon.py", line 17, in <module>
import xen.lowlevel.xc
ImportError: /usr/lib/xen-3.0.3-1/bin/../lib/python/xen/lowlevel/xc.so: undefined symbol: Py_InitModule4
Traceback (most recent call last):
File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in <module>
from xen.xend.server import SrvDaemon
File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/server/SrvDaemon.py", line 17, in <module>
import xen.lowlevel.xc
ImportError: /usr/lib/xen-3.0.3-1/bin/../lib/python/xen/lowlevel/xc.so: undefined symbol: Py_InitModule4
------------------------------


Thanks,

// Oliver


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 12:46 AM
"Oliver Schneider"
 
Default Xen on lenny fails after upgrade from etch?

I'm sorry, I should have added.

Linux test 2.6.18-6-xen-amd64 #1 SMP Fri Dec 12 07:02:03 UTC 2008 x86_64 GNU/Linux

(Note: I *had* to boot into this kernel, because the new kernel would not boot.)

Also, removing python2.4 and python2.4-minimal and then reinstalling the packages in question do not change anything.

// Oliver


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 12:54 AM
edu gargiulo
 
Default Xen on lenny fails after upgrade from etch?

On Wed, Feb 18, 2009 at 10:46 PM, Oliver Schneider <Borbarad@gmxpro.net> wrote:
> I'm sorry, I should have added.
>
> Linux test 2.6.18-6-xen-amd64 #1 SMP Fri Dec 12 07:02:03 UTC 2008 x86_64 GNU/Linux
>
> (Note: I *had* to boot into this kernel, because the new kernel would not boot.)
>
> Also, removing python2.4 and python2.4-minimal and then reinstalling the packages in question do not change anything.

I had the same problem. Looking in /usr/bin/xm I saw a reference to
/usr/bin/python2.4 and unfortunately lenny stable comes with
python2.5. The only workaround to solve this was compile xen with
python2.5.

hope that helps,

--
edu


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 01:02 AM
"Oliver Schneider"
 
Default Xen on lenny fails after upgrade from etch?

Thanks.

> I had the same problem. Looking in /usr/bin/xm I saw a reference to
> /usr/bin/python2.4 and unfortunately lenny stable comes with
> python2.5. The only workaround to solve this was compile xen with
> python2.5.

One more question then. Did you compile from the source package Debian provides or did you opt for the one from XenSource directly?


// Oliver


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 01:26 AM
edu gargiulo
 
Default Xen on lenny fails after upgrade from etch?

On Wed, Feb 18, 2009 at 11:02 PM, Oliver Schneider <Borbarad@gmxpro.net> wrote:
> Thanks.
>
>> I had the same problem. Looking in /usr/bin/xm I saw a reference to
>> /usr/bin/python2.4 and unfortunately lenny stable comes with
>> python2.5. The only workaround to solve this was compile xen with
>> python2.5.
>
> One more question then. Did you compile from the source package Debian provides or did you opt for the one from XenSource directly?

>From xen source 3.3.1 [1].

I've installed the following debian packages

aptitude install build-essential mercurial gawk zlib1g-dev libx11-dev
gettext libssl-dev libncurses5-dev python-dev texinfo

you should add bcc and bin86 if you want to use full virtualization (HVM).

$ cd /usr/include/gnu
$ ln -s stubs-64.h stubs-32.h
$ gzip -dc xen-3.3.1.tar.gz | tar xvf -
$ cd xen-3.3.1
$ make dist
$ make install

The symlink on stubs-64.h is a workaround for a bug in libc6-i386, you
have to do it if you want to complete the compilation process.
The make dist step automatically download the 2.6.18 kernel source
from mercurial and several packages so you have to be online.

hope that helps

--
edu

[1] http://www.hants.lug.org.uk/cgi-bin/wiki.pl?LinuxHints/XenOnEtch


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 02:38 AM
"Oliver Schneider"
 
Default Xen on lenny fails after upgrade from etch?

Hi again,

> hope that helps
before I did that, I noticed there were numerous xen 3.2 packages available.

Removing the xen 3.0 stuff was easy (and would have to be done anyway), but then came the issues.

Now, almost everything is fine as long as you remove xen 3.0, because the kernel that comes with Debian seems to work with xen 3.2. At least suddenly I could even boot the new kernel (after installing the xen 3.2 stuff and getting rid of the old).

However, some changes were needed after booting into the new kernel:
1.) The Xen config needed the interface name explicitly. See: <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477525#13>
2.) I had to adjust the kernel and ramdisk parameters in the domU .cfg files (for obvious reasons )

After doing those steps, I got "Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route failed; error detected." when attempting to create the domU, using "xm create domu.cfg".

That's where I am stuck now. Any ideas? ifconfig does not yet show the "vif" interfaces, but that was normal as far as I recall (i.e. those are created in the process). Or am I mistaking and they have to be created manually?


Thanks,

// Oliver


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 02:56 AM
edu gargiulo
 
Default Xen on lenny fails after upgrade from etch?

On Thu, Feb 19, 2009 at 12:38 AM, Oliver Schneider <Borbarad@gmxpro.net> wrote:
> Hi again,
>
>> hope that helps
> before I did that, I noticed there were numerous xen 3.2 packages available.
>
> Removing the xen 3.0 stuff was easy (and would have to be done anyway), but then came the issues.
>
> Now, almost everything is fine as long as you remove xen 3.0, because the kernel that comes with Debian seems to work with xen 3.2. At least suddenly I could even boot the new kernel (after installing the xen 3.2 stuff and getting rid of the old).
>
> However, some changes were needed after booting into the new kernel:
> 1.) The Xen config needed the interface name explicitly. See: <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477525#13>
> 2.) I had to adjust the kernel and ramdisk parameters in the domU .cfg files (for obvious reasons )
>
> After doing those steps, I got "Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route failed; error detected." when attempting to create the domU, using "xm create domu.cfg".
>
> That's where I am stuck now. Any ideas? ifconfig does not yet show the "vif" interfaces, but that was normal as far as I recall (i.e. those are created in the process). Or am I mistaking and they have to be created manually?

No, vif interfaces are created automagically on demand. Please, show
us the output of "dpkg -l | grep iproute" and ifconfig (just which
interfaces do you have, addresses are not necessary to view). Verify
that vif-route belongs to the package recently installed too.

regards,

--
edu


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 03:36 AM
"Oliver Schneider"
 
Default Xen on lenny fails after upgrade from etch?

> No, vif interfaces are created automagically on demand. Please, show
> us the output of "dpkg -l | grep iproute" and ifconfig (just which
> interfaces do you have, addresses are not necessary to view). Verify
> that vif-route belongs to the package recently installed too.

Here the output you asked for:

$ dpkg -l | grep iproute
ii iproute 20080725-2 ...

$ ifconfig|grep 'Link encap:'
eth0 Link encap:Ethernet HWaddr [...]
lo Link encap:Local Loopback

$ apt-file find vif-route
autopkgtest-xenlvm: /etc/xen/scripts/vif-route-adt
xen-utils-common: /etc/xen/scripts/vif-route

$ dpkg -l|grep 'xen-utils-common'
ii xen-utils-common 3.2.0-2 ...


Thanks for your help so far.

// Oliver

PS: I stripped the descriptions from the "dpkg -l" output.
--
---------------------------------------------------
DDKWizard and DDKBUILD: <http://ddkwizard.assarbad.net>

Trunk (potentially unstable) version: <http://ddkwizard.assarbad.net/trunk/ddkbuild.cmd>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-19-2009, 04:41 AM
"Oliver Schneider"
 
Default Xen on lenny fails after upgrade from etch?

Additional note: I checked the files in /etc/xen/scripts and they are identical to the one inside the .deb file mentioned in my previous mail.

The only file that was different at all was

/etc/default/xendomains
56c56
< XENDOMAINS_SAVE=/var/lib/xen/save
---
> XENDOMAINS_SAVE=/vm/save

My /etc/xen/xend-config.spx looks like this:
(xend-address localhost)
(network-script 'network-route netdev=eth0')
(vif-script vif-route)
(dom0-min-mem 96)
(dom0-cpus 0)


// Oliver


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 04:20 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org