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
On Wed, Feb 18, 2009 at 10:46 PM, Oliver Schneider borba...@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,
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
On Wed, Feb 18, 2009 at 11:02 PM, Oliver Schneider borba...@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.
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
On Thu, Feb 19, 2009 at 12:38 AM, Oliver Schneider borba...@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,
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
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
8 matches
Mail list logo