Xen users - Jul 2008 - Xen installation : Python C API mismatch

Hello,

I am trying to install Xen 3.1.0 on a Debian Sid. I have been able to do
this type of installation correctly with it working perfectly before but I
have to admit I can''t get this one to work.

Here are the error messages that I get at Xen startup :

orangene1-hyp:~# /etc/init.d/xend start
/usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning: Python C
API version mismatch for module xen.lowlevel.xc: This Python has API version
1013, module xen.lowlevel.xc has version 1012.
  import xen.lowlevel.xc
/usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
version mismatch for module acm: This Python has API version 1013, module
acm has version 1012.
  from xen.lowlevel import acm
/usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python C API
version mismatch for module xen.lowlevel.xs: This Python has API version
1013, module xen.lowlevel.xs has version 1012.
  import xen.lowlevel.xs
/usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python C API
version mismatch for module ptsname: This Python has API version 1013,
module ptsname has version 1012.
  from xen.lowlevel import ptsname
/usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning: Python C
API version mismatch for module xen.lowlevel.xc: This Python has API version
1013, module xen.lowlevel.xc has version 1012.
  import xen.lowlevel.xc
/usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
version mismatch for module acm: This Python has API version 1013, module
acm has version 1012.
  from xen.lowlevel import acm
/usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python C API
version mismatch for module xen.lowlevel.xs: This Python has API version
1013, module xen.lowlevel.xs has version 1012.
  import xen.lowlevel.xs
/usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python C API
version mismatch for module ptsname: This Python has API version 1013,
module ptsname has version 1012.
  from xen.lowlevel import ptsname

I have tried to install python from Sid and Lenny versions but none seem to
change any of this... I have no Python knowledge at all so I would like to
know if anybody would happen to have an idea concerning this problem.

I will be happy to give you more info if there is something missing in this
post.

Thank you in advance for your help,

Antoine Benkemoun

-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

These errors typically happen when the Xen code was built against a different 
version of Python to the one that''s available at runtime. 
I''ve actually
found these are often harmless but that''s probably not an appropriate
risk to
take for a production machine.

Where exactly did you get your install source for Xen from?  Could you just 
build Xen yourself rather than using a pre-compiled version?

Cheers,
Mark

On Thursday 17 July 2008, Antoine Benkemoun wrote:
> Hello,
>
> I am trying to install Xen 3.1.0 on a Debian Sid. I have been able to do
> this type of installation correctly with it working perfectly before but I
> have to admit I can''t get this one to work.
>
> Here are the error messages that I get at Xen startup :
>
> orangene1-hyp:~# /etc/init.d/xend start
> /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning: Python C
> API version mismatch for module xen.lowlevel.xc: This Python has API
> version 1013, module xen.lowlevel.xc has version 1012.
>   import xen.lowlevel.xc
> /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
> version mismatch for module acm: This Python has API version 1013, module
> acm has version 1012.
>   from xen.lowlevel import acm
> /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python C API
> version mismatch for module xen.lowlevel.xs: This Python has API version
> 1013, module xen.lowlevel.xs has version 1012.
>   import xen.lowlevel.xs
> /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python C API
> version mismatch for module ptsname: This Python has API version 1013,
> module ptsname has version 1012.
>   from xen.lowlevel import ptsname
> /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning: Python C
> API version mismatch for module xen.lowlevel.xc: This Python has API
> version 1013, module xen.lowlevel.xc has version 1012.
>   import xen.lowlevel.xc
> /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
> version mismatch for module acm: This Python has API version 1013, module
> acm has version 1012.
>   from xen.lowlevel import acm
> /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python C API
> version mismatch for module xen.lowlevel.xs: This Python has API version
> 1013, module xen.lowlevel.xs has version 1012.
>   import xen.lowlevel.xs
> /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python C API
> version mismatch for module ptsname: This Python has API version 1013,
> module ptsname has version 1012.
>   from xen.lowlevel import ptsname
>
> I have tried to install python from Sid and Lenny versions but none seem to
> change any of this... I have no Python knowledge at all so I would like to
> know if anybody would happen to have an idea concerning this problem.
>
> I will be happy to give you more info if there is something missing in this
> post.
>
> Thank you in advance for your help,
>
> Antoine Benkemoun


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

Thank you for your quick answer.

I installed the 3.1.0 binaries on a Lenny Sid installed. I followed the
"Perfect Xen 3.0 install" tutorial to the letter.

I have the possibility to install from sources but I am somewhat afraid to
do so... Can it crash the machine if installed ontop a previous install ?
Basically, the machine not rebooting correctly wins me a trip to the
datacentre and that''s not fun :P

Is it possible to uninstall a previous Xen install so it doesn''t mess
up
everything ?

Antoine

On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> These errors typically happen when the Xen code was built against a
> different
> version of Python to the one that''s available at runtime. 
I''ve actually
> found these are often harmless but that''s probably not an
appropriate risk
> to
> take for a production machine.
>
> Where exactly did you get your install source for Xen from?  Could you just
> build Xen yourself rather than using a pre-compiled version?
>
> Cheers,
> Mark
>
> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > Hello,
> >
> > I am trying to install Xen 3.1.0 on a Debian Sid. I have been able to
do
> > this type of installation correctly with it working perfectly before
but
> I
> > have to admit I can''t get this one to work.
> >
> > Here are the error messages that I get at Xen startup :
> >
> > orangene1-hyp:~# /etc/init.d/xend start
> > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
Python C
> > API version mismatch for module xen.lowlevel.xc: This Python has API
> > version 1013, module xen.lowlevel.xc has version 1012.
> >   import xen.lowlevel.xc
> > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
> > version mismatch for module acm: This Python has API version 1013,
module
> > acm has version 1012.
> >   from xen.lowlevel import acm
> > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python
C
> API
> > version mismatch for module xen.lowlevel.xs: This Python has API
version
> > 1013, module xen.lowlevel.xs has version 1012.
> >   import xen.lowlevel.xs
> > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python
C
> API
> > version mismatch for module ptsname: This Python has API version 1013,
> > module ptsname has version 1012.
> >   from xen.lowlevel import ptsname
> > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
Python C
> > API version mismatch for module xen.lowlevel.xc: This Python has API
> > version 1013, module xen.lowlevel.xc has version 1012.
> >   import xen.lowlevel.xc
> > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
> > version mismatch for module acm: This Python has API version 1013,
module
> > acm has version 1012.
> >   from xen.lowlevel import acm
> > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python
C
> API
> > version mismatch for module xen.lowlevel.xs: This Python has API
version
> > 1013, module xen.lowlevel.xs has version 1012.
> >   import xen.lowlevel.xs
> > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python
C
> API
> > version mismatch for module ptsname: This Python has API version 1013,
> > module ptsname has version 1012.
> >   from xen.lowlevel import ptsname
> >
> > I have tried to install python from Sid and Lenny versions but none
seem
> to
> > change any of this... I have no Python knowledge at all so I would
like
> to
> > know if anybody would happen to have an idea concerning this problem.
> >
> > I will be happy to give you more info if there is something missing in
> this
> > post.
> >
> > Thank you in advance for your help,
> >
> > Antoine Benkemoun
>
>
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

Thank you for your quick answer.

I installed the 3.1.0 binaries on a Lenny Sid installed. I followed the
"Perfect Xen 3.0 install" tutorial to the letter.

I have the possibility to install from sources but I am somewhat afraid to
do so... Can it crash the machine if installed ontop a previous install ?
Basically, the machine not rebooting correctly wins me a trip to the
datacentre and that''s not fun :P

Is it possible to uninstall a previous Xen install so it doesn''t mess
up
everything ?

On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> These errors typically happen when the Xen code was built against a
> different
> version of Python to the one that''s available at runtime. 
I''ve actually
> found these are often harmless but that''s probably not an
appropriate risk
> to
> take for a production machine.
>
> Where exactly did you get your install source for Xen from?  Could you just
> build Xen yourself rather than using a pre-compiled version?
>
> Cheers,
> Mark
>
> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > Hello,
> >
> > I am trying to install Xen 3.1.0 on a Debian Sid. I have been able to
do
> > this type of installation correctly with it working perfectly before
but
> I
> > have to admit I can''t get this one to work.
> >
> > Here are the error messages that I get at Xen startup :
> >
> > orangene1-hyp:~# /etc/init.d/xend start
> > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
Python C
> > API version mismatch for module xen.lowlevel.xc: This Python has API
> > version 1013, module xen.lowlevel.xc has version 1012.
> >   import xen.lowlevel.xc
> > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
> > version mismatch for module acm: This Python has API version 1013,
module
> > acm has version 1012.
> >   from xen.lowlevel import acm
> > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python
C
> API
> > version mismatch for module xen.lowlevel.xs: This Python has API
version
> > 1013, module xen.lowlevel.xs has version 1012.
> >   import xen.lowlevel.xs
> > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python
C
> API
> > version mismatch for module ptsname: This Python has API version 1013,
> > module ptsname has version 1012.
> >   from xen.lowlevel import ptsname
> > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
Python C
> > API version mismatch for module xen.lowlevel.xc: This Python has API
> > version 1013, module xen.lowlevel.xc has version 1012.
> >   import xen.lowlevel.xc
> > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C API
> > version mismatch for module acm: This Python has API version 1013,
module
> > acm has version 1012.
> >   from xen.lowlevel import acm
> > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning: Python
C
> API
> > version mismatch for module xen.lowlevel.xs: This Python has API
version
> > 1013, module xen.lowlevel.xs has version 1012.
> >   import xen.lowlevel.xs
> > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning: Python
C
> API
> > version mismatch for module ptsname: This Python has API version 1013,
> > module ptsname has version 1012.
> >   from xen.lowlevel import ptsname
> >
> > I have tried to install python from Sid and Lenny versions but none
seem
> to
> > change any of this... I have no Python knowledge at all so I would
like
> to
> > know if anybody would happen to have an idea concerning this problem.
> >
> > I will be happy to give you more info if there is something missing in
> this
> > post.
> >
> > Thank you in advance for your help,
> >
> > Antoine Benkemoun
>
>
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

> Thank you for your quick answer.
>
> I installed the 3.1.0 binaries on a Lenny Sid installed. I followed the
> "Perfect Xen 3.0 install" tutorial to the letter.
>
> I have the possibility to install from sources but I am somewhat afraid to
> do so... Can it crash the machine if installed ontop a previous install ?
> Basically, the machine not rebooting correctly wins me a trip to the
> datacentre and that''s not fun :P
Xen doesn''t play very well with conflicting installs.  I guess if
you''re
installing the same version from source that you''ve just installed in 
binaries it''s not so likely to screw things up.  That said, most of the
conflicts are typically in userspace stuff, which shouldn''t stop the
machine
actually booting.  I''d also not expect such conflicts to result in a
crash at
runtime, it just usually means Xend doesn''t work properly.
> Is it possible to uninstall a previous Xen install so it doesn''t
mess up
> everything ?
Yes, if you can figure out which bits to remove.  I think there''s a
"make
uninstall" target in the source distribution that should do this reasonably
thoroughly for you; it''s not included in the binary distribution you 
currently have :-(

*however* in your case, you have successfully installed Xen and XenLinux by 
the sound of it and they''re already booting - am I reading you right?

If you get the source distribution for the same version of Xen and then just 
compile / install the userspace tools, that should do.  You probably
don''t
really need to build Xen / XenLinux lot again, or even reboot for that 
matter.

You might still need to remove the old userspace libraries to make Xend work 
right.  make uninstall should take them away but it might remove your Xen / 
XenLinux too...  I''d suggest you manually look at what the Makefile
does to
see which libraries / binaries to remove, then do it yourself.  Does that 
sound reasonably doable to you?  Don''t use make uninstall, just use it
for
inspiration when uninstalling the userspace tools.  Then run make 
tools-install to build and install a new version of the tools.

You may need to install a few -dev packages to build successfully.

Cheers,
Mark
> On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
>
> mark.williamson@cl.cam.ac.uk> wrote:
> > These errors typically happen when the Xen code was built against a
> > different
> > version of Python to the one that''s available at runtime. 
I''ve actually
> > found these are often harmless but that''s probably not an
appropriate
> > risk to
> > take for a production machine.
> >
> > Where exactly did you get your install source for Xen from?  Could you
> > just build Xen yourself rather than using a pre-compiled version?
> >
> > Cheers,
> > Mark
> >
> > On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > Hello,
> > >
> > > I am trying to install Xen 3.1.0 on a Debian Sid. I have been
able to
> > > do this type of installation correctly with it working perfectly
before
> > > but
> >
> > I
> >
> > > have to admit I can''t get this one to work.
> > >
> > > Here are the error messages that I get at Xen startup :
> > >
> > > orangene1-hyp:~# /etc/init.d/xend start
> > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
Python
> > > C API version mismatch for module xen.lowlevel.xc: This Python
has API
> > > version 1013, module xen.lowlevel.xc has version 1012.
> > >   import xen.lowlevel.xc
> > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C
API
> > > version mismatch for module acm: This Python has API version
1013,
> > > module acm has version 1012.
> > >   from xen.lowlevel import acm
> > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning:
Python C
> >
> > API
> >
> > > version mismatch for module xen.lowlevel.xs: This Python has API
> > > version 1013, module xen.lowlevel.xs has version 1012.
> > >   import xen.lowlevel.xs
> > > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning:
Python C
> >
> > API
> >
> > > version mismatch for module ptsname: This Python has API version
1013,
> > > module ptsname has version 1012.
> > >   from xen.lowlevel import ptsname
> > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
Python
> > > C API version mismatch for module xen.lowlevel.xc: This Python
has API
> > > version 1013, module xen.lowlevel.xc has version 1012.
> > >   import xen.lowlevel.xc
> > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C
API
> > > version mismatch for module acm: This Python has API version
1013,
> > > module acm has version 1012.
> > >   from xen.lowlevel import acm
> > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning:
Python C
> >
> > API
> >
> > > version mismatch for module xen.lowlevel.xs: This Python has API
> > > version 1013, module xen.lowlevel.xs has version 1012.
> > >   import xen.lowlevel.xs
> > > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning:
Python C
> >
> > API
> >
> > > version mismatch for module ptsname: This Python has API version
1013,
> > > module ptsname has version 1012.
> > >   from xen.lowlevel import ptsname
> > >
> > > I have tried to install python from Sid and Lenny versions but
none
> > > seem
> >
> > to
> >
> > > change any of this... I have no Python knowledge at all so I
would like
> >
> > to
> >
> > > know if anybody would happen to have an idea concerning this
problem.
> > >
> > > I will be happy to give you more info if there is something
missing in
> >
> > this
> >
> > > post.
> > >
> > > Thank you in advance for your help,
> > >
> > > Antoine Benkemoun
> >
> > --
> > Push Me Pull You - Distributed SCM tool (
> >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >u/> )


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

Thank you for your thorough answer !

Indeed I am booting Debian with the Xen kernel perfectly. I don''t know
what
you mean by XenLinux but I''m guessing it''s what I am booting
or something
similar enough.

I agree that since it is the same version it shouldn''t mess things up
too
much. I am compiling at the moment using the same tutorial (it had a
compiling source page included). It''s taking for ever even with a Quad
Core
Xen machine with 4GB of RAM...

I''ll keep you updated if this works or if I get a free trip to the
datacentre :P

Antoine

On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> > Thank you for your quick answer.
> >
> > I installed the 3.1.0 binaries on a Lenny Sid installed. I followed
the
> > "Perfect Xen 3.0 install" tutorial to the letter.
> >
> > I have the possibility to install from sources but I am somewhat
afraid
> to
> > do so... Can it crash the machine if installed ontop a previous
install ?
> > Basically, the machine not rebooting correctly wins me a trip to the
> > datacentre and that''s not fun :P
>
> Xen doesn''t play very well with conflicting installs.  I guess if
you''re
> installing the same version from source that you''ve just installed
in
> binaries it''s not so likely to screw things up.  That said, most
of the
> conflicts are typically in userspace stuff, which shouldn''t stop
the
> machine
> actually booting.  I''d also not expect such conflicts to result in
a crash
> at
> runtime, it just usually means Xend doesn''t work properly.
>
> > Is it possible to uninstall a previous Xen install so it
doesn''t mess up
> > everything ?
>
> Yes, if you can figure out which bits to remove.  I think there''s
a "make
> uninstall" target in the source distribution that should do this
reasonably
> thoroughly for you; it''s not included in the binary distribution
you
> currently have :-(
>
> *however* in your case, you have successfully installed Xen and XenLinux by
> the sound of it and they''re already booting - am I reading you
right?
>
> If you get the source distribution for the same version of Xen and then
> just
> compile / install the userspace tools, that should do.  You probably
don''t
> really need to build Xen / XenLinux lot again, or even reboot for that
> matter.
>
> You might still need to remove the old userspace libraries to make Xend
> work
> right.  make uninstall should take them away but it might remove your Xen /
> XenLinux too...  I''d suggest you manually look at what the
Makefile does to
> see which libraries / binaries to remove, then do it yourself.  Does that
> sound reasonably doable to you?  Don''t use make uninstall, just
use it for
> inspiration when uninstalling the userspace tools.  Then run make
> tools-install to build and install a new version of the tools.
>
> You may need to install a few -dev packages to build successfully.
>
> Cheers,
> Mark
>
> > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
> >
> > mark.williamson@cl.cam.ac.uk> wrote:
> > > These errors typically happen when the Xen code was built against
a
> > > different
> > > version of Python to the one that''s available at
runtime.  I''ve
> actually
> > > found these are often harmless but that''s probably not
an appropriate
> > > risk to
> > > take for a production machine.
> > >
> > > Where exactly did you get your install source for Xen from? 
Could you
> > > just build Xen yourself rather than using a pre-compiled version?
> > >
> > > Cheers,
> > > Mark
> > >
> > > On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > > Hello,
> > > >
> > > > I am trying to install Xen 3.1.0 on a Debian Sid. I have
been able to
> > > > do this type of installation correctly with it working
perfectly
> before
> > > > but
> > >
> > > I
> > >
> > > > have to admit I can''t get this one to work.
> > > >
> > > > Here are the error messages that I get at Xen startup :
> > > >
> > > > orangene1-hyp:~# /etc/init.d/xend start
> > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
RuntimeWarning:
> Python
> > > > C API version mismatch for module xen.lowlevel.xc: This
Python has
> API
> > > > version 1013, module xen.lowlevel.xc has version 1012.
> > > >   import xen.lowlevel.xc
> > > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning:
Python C API
> > > > version mismatch for module acm: This Python has API version
1013,
> > > > module acm has version 1012.
> > > >   from xen.lowlevel import acm
> > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning: Python
> C
> > >
> > > API
> > >
> > > > version mismatch for module xen.lowlevel.xs: This Python has
API
> > > > version 1013, module xen.lowlevel.xs has version 1012.
> > > >   import xen.lowlevel.xs
> > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning: Python
> C
> > >
> > > API
> > >
> > > > version mismatch for module ptsname: This Python has API
version
> 1013,
> > > > module ptsname has version 1012.
> > > >   from xen.lowlevel import ptsname
> > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
RuntimeWarning:
> Python
> > > > C API version mismatch for module xen.lowlevel.xc: This
Python has
> API
> > > > version 1013, module xen.lowlevel.xc has version 1012.
> > > >   import xen.lowlevel.xc
> > > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning:
Python C API
> > > > version mismatch for module acm: This Python has API version
1013,
> > > > module acm has version 1012.
> > > >   from xen.lowlevel import acm
> > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning: Python
> C
> > >
> > > API
> > >
> > > > version mismatch for module xen.lowlevel.xs: This Python has
API
> > > > version 1013, module xen.lowlevel.xs has version 1012.
> > > >   import xen.lowlevel.xs
> > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning: Python
> C
> > >
> > > API
> > >
> > > > version mismatch for module ptsname: This Python has API
version
> 1013,
> > > > module ptsname has version 1012.
> > > >   from xen.lowlevel import ptsname
> > > >
> > > > I have tried to install python from Sid and Lenny versions
but none
> > > > seem
> > >
> > > to
> > >
> > > > change any of this... I have no Python knowledge at all so I
would
> like
> > >
> > > to
> > >
> > > > know if anybody would happen to have an idea concerning this
problem.
> > > >
> > > > I will be happy to give you more info if there is something
missing
> in
> > >
> > > this
> > >
> > > > post.
> > > >
> > > > Thank you in advance for your help,
> > > >
> > > > Antoine Benkemoun
> > >
> > > --
> > > Push Me Pull You - Distributed SCM tool (
> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > >u/> )
>
>
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

On Thursday 17 July 2008, Antoine Benkemoun wrote:
> Thank you for your thorough answer !
>
> Indeed I am booting Debian with the Xen kernel perfectly. I don''t
know what
> you mean by XenLinux but I''m guessing it''s what I am
booting or something
> similar enough.
Sorry.

By XenLinux I mean the Xen-aware Linux you''re booting on top of Xen.
> I agree that since it is the same version it shouldn''t mess things
up too
> much. I am compiling at the moment using the same tutorial (it had a
> compiling source page included). It''s taking for ever even with a
Quad Core
> Xen machine with 4GB of RAM...
If you''re only installing the tools, as I suggested, you only actually
need to
do make tools; make install-tools, which should be much faster.  If you just 
do "make world" it''ll build Xen and the XenLinux, which will
take ages and
you already have those.
> I''ll keep you updated if this works or if I get a free trip to the
> datacentre :P
I hope you don''t win that prize :-)

Cheers,
Mark
> Antoine
>
> On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
>
> mark.williamson@cl.cam.ac.uk> wrote:
> > > Thank you for your quick answer.
> > >
> > > I installed the 3.1.0 binaries on a Lenny Sid installed. I
followed the
> > > "Perfect Xen 3.0 install" tutorial to the letter.
> > >
> > > I have the possibility to install from sources but I am somewhat
afraid
> >
> > to
> >
> > > do so... Can it crash the machine if installed ontop a previous
install
> > > ? Basically, the machine not rebooting correctly wins me a trip
to the
> > > datacentre and that''s not fun :P
> >
> > Xen doesn''t play very well with conflicting installs.  I
guess if you''re
> > installing the same version from source that you''ve just
installed in
> > binaries it''s not so likely to screw things up.  That said,
most of the
> > conflicts are typically in userspace stuff, which shouldn''t
stop the
> > machine
> > actually booting.  I''d also not expect such conflicts to
result in a
> > crash at
> > runtime, it just usually means Xend doesn''t work properly.
> >
> > > Is it possible to uninstall a previous Xen install so it
doesn''t mess
> > > up everything ?
> >
> > Yes, if you can figure out which bits to remove.  I think
there''s a "make
> > uninstall" target in the source distribution that should do this
> > reasonably thoroughly for you; it''s not included in the
binary
> > distribution you currently have :-(
> >
> > *however* in your case, you have successfully installed Xen and
XenLinux
> > by the sound of it and they''re already booting - am I reading
you right?
> >
> > If you get the source distribution for the same version of Xen and
then
> > just
> > compile / install the userspace tools, that should do.  You probably
> > don''t really need to build Xen / XenLinux lot again, or even
reboot for
> > that matter.
> >
> > You might still need to remove the old userspace libraries to make
Xend
> > work
> > right.  make uninstall should take them away but it might remove your
Xen
> > / XenLinux too...  I''d suggest you manually look at what the
Makefile
> > does to see which libraries / binaries to remove, then do it yourself.
> > Does that sound reasonably doable to you?  Don''t use make
uninstall, just
> > use it for inspiration when uninstalling the userspace tools.  Then
run
> > make tools-install to build and install a new version of the tools.
> >
> > You may need to install a few -dev packages to build successfully.
> >
> > Cheers,
> > Mark
> >
> > > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
> > >
> > > mark.williamson@cl.cam.ac.uk> wrote:
> > > > These errors typically happen when the Xen code was built
against a
> > > > different
> > > > version of Python to the one that''s available at
runtime.  I''ve
> >
> > actually
> >
> > > > found these are often harmless but that''s probably
not an appropriate
> > > > risk to
> > > > take for a production machine.
> > > >
> > > > Where exactly did you get your install source for Xen from? 
Could
> > > > you just build Xen yourself rather than using a pre-compiled
version?
> > > >
> > > > Cheers,
> > > > Mark
> > > >
> > > > On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > > > Hello,
> > > > >
> > > > > I am trying to install Xen 3.1.0 on a Debian Sid. I
have been able
> > > > > to do this type of installation correctly with it
working perfectly
> >
> > before
> >
> > > > > but
> > > >
> > > > I
> > > >
> > > > > have to admit I can''t get this one to work.
> > > > >
> > > > > Here are the error messages that I get at Xen startup :
> > > > >
> > > > > orangene1-hyp:~# /etc/init.d/xend start
> > > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
RuntimeWarning:
> >
> > Python
> >
> > > > > C API version mismatch for module xen.lowlevel.xc: This
Python has
> >
> > API
> >
> > > > > version 1013, module xen.lowlevel.xc has version 1012.
> > > > >   import xen.lowlevel.xc
> > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python C
> > > > > API version mismatch for module acm: This Python has
API version
> > > > > 1013, module acm has version 1012.
> > > > >   from xen.lowlevel import acm
> > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module xen.lowlevel.xs: This
Python has API
> > > > > version 1013, module xen.lowlevel.xs has version 1012.
> > > > >   import xen.lowlevel.xs
> > > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module ptsname: This Python has
API version
> >
> > 1013,
> >
> > > > > module ptsname has version 1012.
> > > > >   from xen.lowlevel import ptsname
> > > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
RuntimeWarning:
> >
> > Python
> >
> > > > > C API version mismatch for module xen.lowlevel.xc: This
Python has
> >
> > API
> >
> > > > > version 1013, module xen.lowlevel.xc has version 1012.
> > > > >   import xen.lowlevel.xc
> > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python C
> > > > > API version mismatch for module acm: This Python has
API version
> > > > > 1013, module acm has version 1012.
> > > > >   from xen.lowlevel import acm
> > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module xen.lowlevel.xs: This
Python has API
> > > > > version 1013, module xen.lowlevel.xs has version 1012.
> > > > >   import xen.lowlevel.xs
> > > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module ptsname: This Python has
API version
> >
> > 1013,
> >
> > > > > module ptsname has version 1012.
> > > > >   from xen.lowlevel import ptsname
> > > > >
> > > > > I have tried to install python from Sid and Lenny
versions but none
> > > > > seem
> > > >
> > > > to
> > > >
> > > > > change any of this... I have no Python knowledge at all
so I would
> >
> > like
> >
> > > > to
> > > >
> > > > > know if anybody would happen to have an idea concerning
this
> > > > > problem.
> > > > >
> > > > > I will be happy to give you more info if there is
something missing
> >
> > in
> >
> > > > this
> > > >
> > > > > post.
> > > > >
> > > > > Thank you in advance for your help,
> > > > >
> > > > > Antoine Benkemoun
> > > >
> > > > --
> > > > Push Me Pull You - Distributed SCM tool (
> > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48
> > > >/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >
> > > >u/> )
> >
> > --
> > Push Me Pull You - Distributed SCM tool (
> >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >u/> )


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

Antoine Benkemoun schrieb:
> Thank you for your thorough answer !
>
> Indeed I am booting Debian with the Xen kernel perfectly. I don''t
know
> what you mean by XenLinux but I''m guessing it''s what I am
booting or
> something similar enough.
>
> I agree that since it is the same version it shouldn''t mess things
up
> too much. I am compiling at the moment using the same tutorial (it had 
> a compiling source page included). It''s taking for ever even with
a
> Quad Core Xen machine with 4GB of RAM...
>
> I''ll keep you updated if this works or if I get a free trip to the
> datacentre :P
>
> Antoine
Hi,

You should not forget to create an initrd with the new kernel modules, 
if you need one.
That would fail your machine to boot ;-)

Cheers,
Alex

>
> On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson 
> <mark.williamson@cl.cam.ac.uk
<mailto:mark.williamson@cl.cam.ac.uk>>
> wrote:
>
>     > Thank you for your quick answer.
>     >
>     > I installed the 3.1.0 binaries on a Lenny Sid installed. I
>     followed the
>     > "Perfect Xen 3.0 install" tutorial to the letter.
>     >
>     > I have the possibility to install from sources but I am somewhat
>     afraid to
>     > do so... Can it crash the machine if installed ontop a previous
>     install ?
>     > Basically, the machine not rebooting correctly wins me a trip to
the
>     > datacentre and that''s not fun :P
>
>     Xen doesn''t play very well with conflicting installs.  I guess
if
>     you''re
>     installing the same version from source that you''ve just
installed in
>     binaries it''s not so likely to screw things up.  That said,
most
>     of the
>     conflicts are typically in userspace stuff, which shouldn''t
stop
>     the machine
>     actually booting.  I''d also not expect such conflicts to
result in
>     a crash at
>     runtime, it just usually means Xend doesn''t work properly.
>
>     > Is it possible to uninstall a previous Xen install so it
doesn''t
>     mess up
>     > everything ?
>
>     Yes, if you can figure out which bits to remove.  I think
there''s
>     a "make
>     uninstall" target in the source distribution that should do this
>     reasonably
>     thoroughly for you; it''s not included in the binary
distribution you
>     currently have :-(
>
>     *however* in your case, you have successfully installed Xen and
>     XenLinux by
>     the sound of it and they''re already booting - am I reading you
right?
>
>     If you get the source distribution for the same version of Xen and
>     then just
>     compile / install the userspace tools, that should do.  You
>     probably don''t
>     really need to build Xen / XenLinux lot again, or even reboot for that
>     matter.
>
>     You might still need to remove the old userspace libraries to make
>     Xend work
>     right.  make uninstall should take them away but it might remove
>     your Xen /
>     XenLinux too...  I''d suggest you manually look at what the
>     Makefile does to
>     see which libraries / binaries to remove, then do it yourself.
>      Does that
>     sound reasonably doable to you?  Don''t use make uninstall,
just
>     use it for
>     inspiration when uninstalling the userspace tools.  Then run make
>     tools-install to build and install a new version of the tools.
>
>     You may need to install a few -dev packages to build successfully.
>
>     Cheers,
>     Mark
>
>     > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
>     >
>     > mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > > These errors typically happen when the Xen code was built
>     against a
>     > > different
>     > > version of Python to the one that''s available at
runtime.
>      I''ve actually
>     > > found these are often harmless but that''s probably
not an
>     appropriate
>     > > risk to
>     > > take for a production machine.
>     > >
>     > > Where exactly did you get your install source for Xen from?
>      Could you
>     > > just build Xen yourself rather than using a pre-compiled
version?
>     > >
>     > > Cheers,
>     > > Mark
>     > >
>     > > On Thursday 17 July 2008, Antoine Benkemoun wrote:
>     > > > Hello,
>     > > >
>     > > > I am trying to install Xen 3.1.0 on a Debian Sid. I have
>     been able to
>     > > > do this type of installation correctly with it working
>     perfectly before
>     > > > but
>     > >
>     > > I
>     > >
>     > > > have to admit I can''t get this one to work.
>     > > >
>     > > > Here are the error messages that I get at Xen startup :
>     > > >
>     > > > orangene1-hyp:~# /etc/init.d/xend start
>     > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>     RuntimeWarning: Python
>     > > > C API version mismatch for module xen.lowlevel.xc: This
>     Python has API
>     > > > version 1013, module xen.lowlevel.xc has version 1012.
>     > > >   import xen.lowlevel.xc
>     > > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning:
>     Python C API
>     > > > version mismatch for module acm: This Python has API
version
>     1013,
>     > > > module acm has version 1012.
>     > > >   from xen.lowlevel import acm
>     > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>     RuntimeWarning: Python C
>     > >
>     > > API
>     > >
>     > > > version mismatch for module xen.lowlevel.xs: This Python
has API
>     > > > version 1013, module xen.lowlevel.xs has version 1012.
>     > > >   import xen.lowlevel.xs
>     > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
>     RuntimeWarning: Python C
>     > >
>     > > API
>     > >
>     > > > version mismatch for module ptsname: This Python has API
>     version 1013,
>     > > > module ptsname has version 1012.
>     > > >   from xen.lowlevel import ptsname
>     > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>     RuntimeWarning: Python
>     > > > C API version mismatch for module xen.lowlevel.xc: This
>     Python has API
>     > > > version 1013, module xen.lowlevel.xc has version 1012.
>     > > >   import xen.lowlevel.xc
>     > > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning:
>     Python C API
>     > > > version mismatch for module acm: This Python has API
version
>     1013,
>     > > > module acm has version 1012.
>     > > >   from xen.lowlevel import acm
>     > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>     RuntimeWarning: Python C
>     > >
>     > > API
>     > >
>     > > > version mismatch for module xen.lowlevel.xs: This Python
has API
>     > > > version 1013, module xen.lowlevel.xs has version 1012.
>     > > >   import xen.lowlevel.xs
>     > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
>     RuntimeWarning: Python C
>     > >
>     > > API
>     > >
>     > > > version mismatch for module ptsname: This Python has API
>     version 1013,
>     > > > module ptsname has version 1012.
>     > > >   from xen.lowlevel import ptsname
>     > > >
>     > > > I have tried to install python from Sid and Lenny
versions
>     but none
>     > > > seem
>     > >
>     > > to
>     > >
>     > > > change any of this... I have no Python knowledge at all
so I
>     would like
>     > >
>     > > to
>     > >
>     > > > know if anybody would happen to have an idea concerning
this
>     problem.
>     > > >
>     > > > I will be happy to give you more info if there is
something
>     missing in
>     > >
>     > > this
>     > >
>     > > > post.
>     > > >
>     > > > Thank you in advance for your help,
>     > > >
>     > > > Antoine Benkemoun
>     > >
>     > > --
>     > > Push Me Pull You - Distributed SCM tool (
>     > > http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7Emaw48/pmp
>     > >u/> )
>
>
>
>     --
>     Push Me Pull You - Distributed SCM tool
>     (http://www.cl.cam.ac.uk/~maw48/pmpu/
>     <http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>)
>
>
>
>
> -- 
> Antoine Benkemoun
> Tel : 03.51.53.57.00
> Port : 06.32.88.59.35
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3276
(20080717) __________
>
> E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>
> http://www.eset.com
>   

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

Ah sorry I didn''t read your email correctly.

I will do that afterwards might just as well finish since it''s been
running
for quite a while...

Won''t be forgetting to do the initrd, thank you for reminder. Already
got
trapped previously but the PC was right next to me so it wasn''t so bad.

Thanks !

Antoine

On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > Thank you for your thorough answer !
> >
> > Indeed I am booting Debian with the Xen kernel perfectly. I
don''t know
> what
> > you mean by XenLinux but I''m guessing it''s what I am
booting or something
> > similar enough.
>
> Sorry.
>
> By XenLinux I mean the Xen-aware Linux you''re booting on top of
Xen.
>
> > I agree that since it is the same version it shouldn''t mess
things up too
> > much. I am compiling at the moment using the same tutorial (it had a
> > compiling source page included). It''s taking for ever even
with a Quad
> Core
> > Xen machine with 4GB of RAM...
>
> If you''re only installing the tools, as I suggested, you only
actually need
> to
> do make tools; make install-tools, which should be much faster.  If you
> just
> do "make world" it''ll build Xen and the XenLinux, which
will take ages and
> you already have those.
>
> > I''ll keep you updated if this works or if I get a free trip
to the
> > datacentre :P
>
> I hope you don''t win that prize :-)
>
> Cheers,
> Mark
>
> > Antoine
> >
> > On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
> >
> > mark.williamson@cl.cam.ac.uk> wrote:
> > > > Thank you for your quick answer.
> > > >
> > > > I installed the 3.1.0 binaries on a Lenny Sid installed. I
followed
> the
> > > > "Perfect Xen 3.0 install" tutorial to the letter.
> > > >
> > > > I have the possibility to install from sources but I am
somewhat
> afraid
> > >
> > > to
> > >
> > > > do so... Can it crash the machine if installed ontop a
previous
> install
> > > > ? Basically, the machine not rebooting correctly wins me a
trip to
> the
> > > > datacentre and that''s not fun :P
> > >
> > > Xen doesn''t play very well with conflicting installs.  I
guess if
> you''re
> > > installing the same version from source that you''ve just
installed in
> > > binaries it''s not so likely to screw things up.  That
said, most of the
> > > conflicts are typically in userspace stuff, which
shouldn''t stop the
> > > machine
> > > actually booting.  I''d also not expect such conflicts to
result in a
> > > crash at
> > > runtime, it just usually means Xend doesn''t work
properly.
> > >
> > > > Is it possible to uninstall a previous Xen install so it
doesn''t mess
> > > > up everything ?
> > >
> > > Yes, if you can figure out which bits to remove.  I think
there''s a
> "make
> > > uninstall" target in the source distribution that should do
this
> > > reasonably thoroughly for you; it''s not included in the
binary
> > > distribution you currently have :-(
> > >
> > > *however* in your case, you have successfully installed Xen and
> XenLinux
> > > by the sound of it and they''re already booting - am I
reading you
> right?
> > >
> > > If you get the source distribution for the same version of Xen
and then
> > > just
> > > compile / install the userspace tools, that should do.  You
probably
> > > don''t really need to build Xen / XenLinux lot again, or
even reboot for
> > > that matter.
> > >
> > > You might still need to remove the old userspace libraries to
make Xend
> > > work
> > > right.  make uninstall should take them away but it might remove
your
> Xen
> > > / XenLinux too...  I''d suggest you manually look at what
the Makefile
> > > does to see which libraries / binaries to remove, then do it
yourself.
> > > Does that sound reasonably doable to you?  Don''t use
make uninstall,
> just
> > > use it for inspiration when uninstalling the userspace tools. 
Then run
> > > make tools-install to build and install a new version of the
tools.
> > >
> > > You may need to install a few -dev packages to build
successfully.
> > >
> > > Cheers,
> > > Mark
> > >
> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
> > > >
> > > > mark.williamson@cl.cam.ac.uk> wrote:
> > > > > These errors typically happen when the Xen code was
built against a
> > > > > different
> > > > > version of Python to the one that''s available
at runtime.  I''ve
> > >
> > > actually
> > >
> > > > > found these are often harmless but that''s
probably not an
> appropriate
> > > > > risk to
> > > > > take for a production machine.
> > > > >
> > > > > Where exactly did you get your install source for Xen
from?  Could
> > > > > you just build Xen yourself rather than using a
pre-compiled
> version?
> > > > >
> > > > > Cheers,
> > > > > Mark
> > > > >
> > > > > On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > > > > Hello,
> > > > > >
> > > > > > I am trying to install Xen 3.1.0 on a Debian Sid.
I have been
> able
> > > > > > to do this type of installation correctly with it
working
> perfectly
> > >
> > > before
> > >
> > > > > > but
> > > > >
> > > > > I
> > > > >
> > > > > > have to admit I can''t get this one to
work.
> > > > > >
> > > > > > Here are the error messages that I get at Xen
startup :
> > > > > >
> > > > > > orangene1-hyp:~# /etc/init.d/xend start
> > > > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
RuntimeWarning:
> > >
> > > Python
> > >
> > > > > > C API version mismatch for module xen.lowlevel.xc:
This Python
> has
> > >
> > > API
> > >
> > > > > > version 1013, module xen.lowlevel.xc has version
1012.
> > > > > >   import xen.lowlevel.xc
> > > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python C
> > > > > > API version mismatch for module acm: This Python
has API version
> > > > > > 1013, module acm has version 1012.
> > > > > >   from xen.lowlevel import acm
> > > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning:
> > > > > > Python
> > >
> > > C
> > >
> > > > > API
> > > > >
> > > > > > version mismatch for module xen.lowlevel.xs: This
Python has API
> > > > > > version 1013, module xen.lowlevel.xs has version
1012.
> > > > > >   import xen.lowlevel.xs
> > > > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning:
> > > > > > Python
> > >
> > > C
> > >
> > > > > API
> > > > >
> > > > > > version mismatch for module ptsname: This Python
has API version
> > >
> > > 1013,
> > >
> > > > > > module ptsname has version 1012.
> > > > > >   from xen.lowlevel import ptsname
> > > > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20:
RuntimeWarning:
> > >
> > > Python
> > >
> > > > > > C API version mismatch for module xen.lowlevel.xc:
This Python
> has
> > >
> > > API
> > >
> > > > > > version 1013, module xen.lowlevel.xc has version
1012.
> > > > > >   import xen.lowlevel.xc
> > > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python C
> > > > > > API version mismatch for module acm: This Python
has API version
> > > > > > 1013, module acm has version 1012.
> > > > > >   from xen.lowlevel import acm
> > > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning:
> > > > > > Python
> > >
> > > C
> > >
> > > > > API
> > > > >
> > > > > > version mismatch for module xen.lowlevel.xs: This
Python has API
> > > > > > version 1013, module xen.lowlevel.xs has version
1012.
> > > > > >   import xen.lowlevel.xs
> > > > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning:
> > > > > > Python
> > >
> > > C
> > >
> > > > > API
> > > > >
> > > > > > version mismatch for module ptsname: This Python
has API version
> > >
> > > 1013,
> > >
> > > > > > module ptsname has version 1012.
> > > > > >   from xen.lowlevel import ptsname
> > > > > >
> > > > > > I have tried to install python from Sid and Lenny
versions but
> none
> > > > > > seem
> > > > >
> > > > > to
> > > > >
> > > > > > change any of this... I have no Python knowledge
at all so I
> would
> > >
> > > like
> > >
> > > > > to
> > > > >
> > > > > > know if anybody would happen to have an idea
concerning this
> > > > > > problem.
> > > > > >
> > > > > > I will be happy to give you more info if there is
something
> missing
> > >
> > > in
> > >
> > > > > this
> > > > >
> > > > > > post.
> > > > > >
> > > > > > Thank you in advance for your help,
> > > > > >
> > > > > > Antoine Benkemoun
> > > > >
> > > > > --
> > > > > Push Me Pull You - Distributed SCM tool (
> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw48
> > > > >/pmpu/>
> > >
> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > >
> > > > >u/> )
> > >
> > > --
> > > Push Me Pull You - Distributed SCM tool (
> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > >u/> )
>
>
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

Critical failure... machine doesn''t boot anymore. I win the free trip !

I am trying to do just make install-tools on the second machine just to see
if it will change something.

Antoine

On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
antoine.benkemoun@gmail.com> wrote:
> Ah sorry I didn''t read your email correctly.
>
> I will do that afterwards might just as well finish since it''s
been running
> for quite a while...
>
> Won''t be forgetting to do the initrd, thank you for reminder.
Already got
> trapped previously but the PC was right next to me so it wasn''t so
bad.
>
> Thanks !
>
> Antoine
>
>
> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
> mark.williamson@cl.cam.ac.uk> wrote:
>
>> On Thursday 17 July 2008, Antoine Benkemoun wrote:
>> > Thank you for your thorough answer !
>> >
>> > Indeed I am booting Debian with the Xen kernel perfectly. I
don''t know
>> what
>> > you mean by XenLinux but I''m guessing it''s what
I am booting or
>> something
>> > similar enough.
>>
>> Sorry.
>>
>> By XenLinux I mean the Xen-aware Linux you''re booting on top
of Xen.
>>
>> > I agree that since it is the same version it shouldn''t
mess things up
>> too
>> > much. I am compiling at the moment using the same tutorial (it had
a
>> > compiling source page included). It''s taking for ever
even with a Quad
>> Core
>> > Xen machine with 4GB of RAM...
>>
>> If you''re only installing the tools, as I suggested, you only
actually
>> need to
>> do make tools; make install-tools, which should be much faster.  If you
>> just
>> do "make world" it''ll build Xen and the XenLinux,
which will take ages and
>> you already have those.
>>
>> > I''ll keep you updated if this works or if I get a free
trip to the
>> > datacentre :P
>>
>> I hope you don''t win that prize :-)
>>
>> Cheers,
>> Mark
>>
>> > Antoine
>> >
>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
>> >
>> > mark.williamson@cl.cam.ac.uk> wrote:
>> > > > Thank you for your quick answer.
>> > > >
>> > > > I installed the 3.1.0 binaries on a Lenny Sid installed.
I followed
>> the
>> > > > "Perfect Xen 3.0 install" tutorial to the
letter.
>> > > >
>> > > > I have the possibility to install from sources but I am
somewhat
>> afraid
>> > >
>> > > to
>> > >
>> > > > do so... Can it crash the machine if installed ontop a
previous
>> install
>> > > > ? Basically, the machine not rebooting correctly wins me
a trip to
>> the
>> > > > datacentre and that''s not fun :P
>> > >
>> > > Xen doesn''t play very well with conflicting
installs.  I guess if
>> you''re
>> > > installing the same version from source that you''ve
just installed in
>> > > binaries it''s not so likely to screw things up. 
That said, most of
>> the
>> > > conflicts are typically in userspace stuff, which
shouldn''t stop the
>> > > machine
>> > > actually booting.  I''d also not expect such
conflicts to result in a
>> > > crash at
>> > > runtime, it just usually means Xend doesn''t work
properly.
>> > >
>> > > > Is it possible to uninstall a previous Xen install so it
doesn''t
>> mess
>> > > > up everything ?
>> > >
>> > > Yes, if you can figure out which bits to remove.  I think
there''s a
>> "make
>> > > uninstall" target in the source distribution that should
do this
>> > > reasonably thoroughly for you; it''s not included in
the binary
>> > > distribution you currently have :-(
>> > >
>> > > *however* in your case, you have successfully installed Xen
and
>> XenLinux
>> > > by the sound of it and they''re already booting - am
I reading you
>> right?
>> > >
>> > > If you get the source distribution for the same version of
Xen and
>> then
>> > > just
>> > > compile / install the userspace tools, that should do.  You
probably
>> > > don''t really need to build Xen / XenLinux lot again,
or even reboot
>> for
>> > > that matter.
>> > >
>> > > You might still need to remove the old userspace libraries to
make
>> Xend
>> > > work
>> > > right.  make uninstall should take them away but it might
remove your
>> Xen
>> > > / XenLinux too...  I''d suggest you manually look at
what the Makefile
>> > > does to see which libraries / binaries to remove, then do it
yourself.
>> > > Does that sound reasonably doable to you?  Don''t use
make uninstall,
>> just
>> > > use it for inspiration when uninstalling the userspace tools.
Then
>> run
>> > > make tools-install to build and install a new version of the
tools.
>> > >
>> > > You may need to install a few -dev packages to build
successfully.
>> > >
>> > > Cheers,
>> > > Mark
>> > >
>> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
>> > > >
>> > > > mark.williamson@cl.cam.ac.uk> wrote:
>> > > > > These errors typically happen when the Xen code was
built against
>> a
>> > > > > different
>> > > > > version of Python to the one that''s
available at runtime.  I''ve
>> > >
>> > > actually
>> > >
>> > > > > found these are often harmless but that''s
probably not an
>> appropriate
>> > > > > risk to
>> > > > > take for a production machine.
>> > > > >
>> > > > > Where exactly did you get your install source for
Xen from?  Could
>> > > > > you just build Xen yourself rather than using a
pre-compiled
>> version?
>> > > > >
>> > > > > Cheers,
>> > > > > Mark
>> > > > >
>> > > > > On Thursday 17 July 2008, Antoine Benkemoun wrote:
>> > > > > > Hello,
>> > > > > >
>> > > > > > I am trying to install Xen 3.1.0 on a Debian
Sid. I have been
>> able
>> > > > > > to do this type of installation correctly with
it working
>> perfectly
>> > >
>> > > before
>> > >
>> > > > > > but
>> > > > >
>> > > > > I
>> > > > >
>> > > > > > have to admit I can''t get this one to
work.
>> > > > > >
>> > > > > > Here are the error messages that I get at Xen
startup :
>> > > > > >
>> > > > > > orangene1-hyp:~# /etc/init.d/xend start
>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
>> > >
>> > > Python
>> > >
>> > > > > > C API version mismatch for module
xen.lowlevel.xc: This Python
>> has
>> > >
>> > > API
>> > >
>> > > > > > version 1013, module xen.lowlevel.xc has
version 1012.
>> > > > > >   import xen.lowlevel.xc
>> > > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python
>> C
>> > > > > > API version mismatch for module acm: This
Python has API version
>> > > > > > 1013, module acm has version 1012.
>> > > > > >   from xen.lowlevel import acm
>> > > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning:
>> > > > > > Python
>> > >
>> > > C
>> > >
>> > > > > API
>> > > > >
>> > > > > > version mismatch for module xen.lowlevel.xs:
This Python has API
>> > > > > > version 1013, module xen.lowlevel.xs has
version 1012.
>> > > > > >   import xen.lowlevel.xs
>> > > > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning:
>> > > > > > Python
>> > >
>> > > C
>> > >
>> > > > > API
>> > > > >
>> > > > > > version mismatch for module ptsname: This
Python has API version
>> > >
>> > > 1013,
>> > >
>> > > > > > module ptsname has version 1012.
>> > > > > >   from xen.lowlevel import ptsname
>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
>> > >
>> > > Python
>> > >
>> > > > > > C API version mismatch for module
xen.lowlevel.xc: This Python
>> has
>> > >
>> > > API
>> > >
>> > > > > > version 1013, module xen.lowlevel.xc has
version 1012.
>> > > > > >   import xen.lowlevel.xc
>> > > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python
>> C
>> > > > > > API version mismatch for module acm: This
Python has API version
>> > > > > > 1013, module acm has version 1012.
>> > > > > >   from xen.lowlevel import acm
>> > > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8:
RuntimeWarning:
>> > > > > > Python
>> > >
>> > > C
>> > >
>> > > > > API
>> > > > >
>> > > > > > version mismatch for module xen.lowlevel.xs:
This Python has API
>> > > > > > version 1013, module xen.lowlevel.xs has
version 1012.
>> > > > > >   import xen.lowlevel.xs
>> > > > > > /usr/lib/python/xen/xend/XendBootloader.py:25:
RuntimeWarning:
>> > > > > > Python
>> > >
>> > > C
>> > >
>> > > > > API
>> > > > >
>> > > > > > version mismatch for module ptsname: This
Python has API version
>> > >
>> > > 1013,
>> > >
>> > > > > > module ptsname has version 1012.
>> > > > > >   from xen.lowlevel import ptsname
>> > > > > >
>> > > > > > I have tried to install python from Sid and
Lenny versions but
>> none
>> > > > > > seem
>> > > > >
>> > > > > to
>> > > > >
>> > > > > > change any of this... I have no Python
knowledge at all so I
>> would
>> > >
>> > > like
>> > >
>> > > > > to
>> > > > >
>> > > > > > know if anybody would happen to have an idea
concerning this
>> > > > > > problem.
>> > > > > >
>> > > > > > I will be happy to give you more info if there
is something
>> missing
>> > >
>> > > in
>> > >
>> > > > > this
>> > > > >
>> > > > > > post.
>> > > > > >
>> > > > > > Thank you in advance for your help,
>> > > > > >
>> > > > > > Antoine Benkemoun
>> > > > >
>> > > > > --
>> > > > > Push Me Pull You - Distributed SCM tool (
>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>> <http://www.cl.cam.ac.uk/%7Emaw48
>> > > > >/pmpu/>
>> > >
>> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>> > >
>> > > > >u/> )
>> > >
>> > > --
>> > > Push Me Pull You - Distributed SCM tool (
>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>> > >u/> )
>>
>>
>>
>> --
>> Push Me Pull You - Distributed SCM tool (
>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>> )
>>
>
>
>
> --
> Antoine Benkemoun
> Tel : 03.51.53.57.00
> Port : 06.32.88.59.35
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

I just did make install-tools and it didn''t change anything. I
don''t know if
I was supposed to do something else for it to take action.

Antoine

On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
antoine.benkemoun@gmail.com> wrote:
> Critical failure... machine doesn''t boot anymore. I win the free
trip !
>
> I am trying to do just make install-tools on the second machine just to see
> if it will change something.
>
> Antoine
>
>
> On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
> antoine.benkemoun@gmail.com> wrote:
>
>> Ah sorry I didn''t read your email correctly.
>>
>> I will do that afterwards might just as well finish since it''s
been
>> running for quite a while...
>>
>> Won''t be forgetting to do the initrd, thank you for reminder.
Already got
>> trapped previously but the PC was right next to me so it
wasn''t so bad.
>>
>> Thanks !
>>
>> Antoine
>>
>>
>> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
>> mark.williamson@cl.cam.ac.uk> wrote:
>>
>>> On Thursday 17 July 2008, Antoine Benkemoun wrote:
>>> > Thank you for your thorough answer !
>>> >
>>> > Indeed I am booting Debian with the Xen kernel perfectly. I
don''t know
>>> what
>>> > you mean by XenLinux but I''m guessing it''s
what I am booting or
>>> something
>>> > similar enough.
>>>
>>> Sorry.
>>>
>>> By XenLinux I mean the Xen-aware Linux you''re booting on
top of Xen.
>>>
>>> > I agree that since it is the same version it
shouldn''t mess things up
>>> too
>>> > much. I am compiling at the moment using the same tutorial (it
had a
>>> > compiling source page included). It''s taking for ever
even with a Quad
>>> Core
>>> > Xen machine with 4GB of RAM...
>>>
>>> If you''re only installing the tools, as I suggested, you
only actually
>>> need to
>>> do make tools; make install-tools, which should be much faster.  If
you
>>> just
>>> do "make world" it''ll build Xen and the
XenLinux, which will take ages
>>> and
>>> you already have those.
>>>
>>> > I''ll keep you updated if this works or if I get a
free trip to the
>>> > datacentre :P
>>>
>>> I hope you don''t win that prize :-)
>>>
>>> Cheers,
>>> Mark
>>>
>>> > Antoine
>>> >
>>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
>>> >
>>> > mark.williamson@cl.cam.ac.uk> wrote:
>>> > > > Thank you for your quick answer.
>>> > > >
>>> > > > I installed the 3.1.0 binaries on a Lenny Sid
installed. I followed
>>> the
>>> > > > "Perfect Xen 3.0 install" tutorial to the
letter.
>>> > > >
>>> > > > I have the possibility to install from sources but I
am somewhat
>>> afraid
>>> > >
>>> > > to
>>> > >
>>> > > > do so... Can it crash the machine if installed ontop
a previous
>>> install
>>> > > > ? Basically, the machine not rebooting correctly
wins me a trip to
>>> the
>>> > > > datacentre and that''s not fun :P
>>> > >
>>> > > Xen doesn''t play very well with conflicting
installs.  I guess if
>>> you''re
>>> > > installing the same version from source that
you''ve just installed in
>>> > > binaries it''s not so likely to screw things up. 
That said, most of
>>> the
>>> > > conflicts are typically in userspace stuff, which
shouldn''t stop the
>>> > > machine
>>> > > actually booting.  I''d also not expect such
conflicts to result in a
>>> > > crash at
>>> > > runtime, it just usually means Xend doesn''t work
properly.
>>> > >
>>> > > > Is it possible to uninstall a previous Xen install
so it doesn''t
>>> mess
>>> > > > up everything ?
>>> > >
>>> > > Yes, if you can figure out which bits to remove.  I think
there''s a
>>> "make
>>> > > uninstall" target in the source distribution that
should do this
>>> > > reasonably thoroughly for you; it''s not included
in the binary
>>> > > distribution you currently have :-(
>>> > >
>>> > > *however* in your case, you have successfully installed
Xen and
>>> XenLinux
>>> > > by the sound of it and they''re already booting -
am I reading you
>>> right?
>>> > >
>>> > > If you get the source distribution for the same version
of Xen and
>>> then
>>> > > just
>>> > > compile / install the userspace tools, that should do. 
You probably
>>> > > don''t really need to build Xen / XenLinux lot
again, or even reboot
>>> for
>>> > > that matter.
>>> > >
>>> > > You might still need to remove the old userspace
libraries to make
>>> Xend
>>> > > work
>>> > > right.  make uninstall should take them away but it might
remove your
>>> Xen
>>> > > / XenLinux too...  I''d suggest you manually look
at what the Makefile
>>> > > does to see which libraries / binaries to remove, then do
it
>>> yourself.
>>> > > Does that sound reasonably doable to you?  Don''t
use make uninstall,
>>> just
>>> > > use it for inspiration when uninstalling the userspace
tools.  Then
>>> run
>>> > > make tools-install to build and install a new version of
the tools.
>>> > >
>>> > > You may need to install a few -dev packages to build
successfully.
>>> > >
>>> > > Cheers,
>>> > > Mark
>>> > >
>>> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson
<
>>> > > >
>>> > > > mark.williamson@cl.cam.ac.uk> wrote:
>>> > > > > These errors typically happen when the Xen code
was built against
>>> a
>>> > > > > different
>>> > > > > version of Python to the one that''s
available at runtime.  I''ve
>>> > >
>>> > > actually
>>> > >
>>> > > > > found these are often harmless but
that''s probably not an
>>> appropriate
>>> > > > > risk to
>>> > > > > take for a production machine.
>>> > > > >
>>> > > > > Where exactly did you get your install source
for Xen from?
>>>  Could
>>> > > > > you just build Xen yourself rather than using a
pre-compiled
>>> version?
>>> > > > >
>>> > > > > Cheers,
>>> > > > > Mark
>>> > > > >
>>> > > > > On Thursday 17 July 2008, Antoine Benkemoun
wrote:
>>> > > > > > Hello,
>>> > > > > >
>>> > > > > > I am trying to install Xen 3.1.0 on a
Debian Sid. I have been
>>> able
>>> > > > > > to do this type of installation correctly
with it working
>>> perfectly
>>> > >
>>> > > before
>>> > >
>>> > > > > > but
>>> > > > >
>>> > > > > I
>>> > > > >
>>> > > > > > have to admit I can''t get this
one to work.
>>> > > > > >
>>> > > > > > Here are the error messages that I get at
Xen startup :
>>> > > > > >
>>> > > > > > orangene1-hyp:~# /etc/init.d/xend start
>>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>>> RuntimeWarning:
>>> > >
>>> > > Python
>>> > >
>>> > > > > > C API version mismatch for module
xen.lowlevel.xc: This Python
>>> has
>>> > >
>>> > > API
>>> > >
>>> > > > > > version 1013, module xen.lowlevel.xc has
version 1012.
>>> > > > > >   import xen.lowlevel.xc
>>> > > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python
>>> C
>>> > > > > > API version mismatch for module acm: This
Python has API
>>> version
>>> > > > > > 1013, module acm has version 1012.
>>> > > > > >   from xen.lowlevel import acm
>>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning:
>>> > > > > > Python
>>> > >
>>> > > C
>>> > >
>>> > > > > API
>>> > > > >
>>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python has
>>> API
>>> > > > > > version 1013, module xen.lowlevel.xs has
version 1012.
>>> > > > > >   import xen.lowlevel.xs
>>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning:
>>> > > > > > Python
>>> > >
>>> > > C
>>> > >
>>> > > > > API
>>> > > > >
>>> > > > > > version mismatch for module ptsname: This
Python has API
>>> version
>>> > >
>>> > > 1013,
>>> > >
>>> > > > > > module ptsname has version 1012.
>>> > > > > >   from xen.lowlevel import ptsname
>>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>>> RuntimeWarning:
>>> > >
>>> > > Python
>>> > >
>>> > > > > > C API version mismatch for module
xen.lowlevel.xc: This Python
>>> has
>>> > >
>>> > > API
>>> > >
>>> > > > > > version 1013, module xen.lowlevel.xc has
version 1012.
>>> > > > > >   import xen.lowlevel.xc
>>> > > > > > /usr/lib/python/xen/util/security.py:25:
RuntimeWarning: Python
>>> C
>>> > > > > > API version mismatch for module acm: This
Python has API
>>> version
>>> > > > > > 1013, module acm has version 1012.
>>> > > > > >   from xen.lowlevel import acm
>>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning:
>>> > > > > > Python
>>> > >
>>> > > C
>>> > >
>>> > > > > API
>>> > > > >
>>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python has
>>> API
>>> > > > > > version 1013, module xen.lowlevel.xs has
version 1012.
>>> > > > > >   import xen.lowlevel.xs
>>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning:
>>> > > > > > Python
>>> > >
>>> > > C
>>> > >
>>> > > > > API
>>> > > > >
>>> > > > > > version mismatch for module ptsname: This
Python has API
>>> version
>>> > >
>>> > > 1013,
>>> > >
>>> > > > > > module ptsname has version 1012.
>>> > > > > >   from xen.lowlevel import ptsname
>>> > > > > >
>>> > > > > > I have tried to install python from Sid
and Lenny versions but
>>> none
>>> > > > > > seem
>>> > > > >
>>> > > > > to
>>> > > > >
>>> > > > > > change any of this... I have no Python
knowledge at all so I
>>> would
>>> > >
>>> > > like
>>> > >
>>> > > > > to
>>> > > > >
>>> > > > > > know if anybody would happen to have an
idea concerning this
>>> > > > > > problem.
>>> > > > > >
>>> > > > > > I will be happy to give you more info if
there is something
>>> missing
>>> > >
>>> > > in
>>> > >
>>> > > > > this
>>> > > > >
>>> > > > > > post.
>>> > > > > >
>>> > > > > > Thank you in advance for your help,
>>> > > > > >
>>> > > > > > Antoine Benkemoun
>>> > > > >
>>> > > > > --
>>> > > > > Push Me Pull You - Distributed SCM tool (
>>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>> <http://www.cl.cam.ac.uk/%7Emaw48
>>> > > > >/pmpu/>
>>> > >
>>> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>>> > >
>>> > > > >u/> )
>>> > >
>>> > > --
>>> > > Push Me Pull You - Distributed SCM tool (
>>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>>> > >u/> )
>>>
>>>
>>>
>>> --
>>> Push Me Pull You - Distributed SCM tool (
>>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>> )
>>>
>>
>>
>>
>> --
>> Antoine Benkemoun
>> Tel : 03.51.53.57.00
>> Port : 06.32.88.59.35
>>
>
>
>
> --
> Antoine Benkemoun
> Tel : 03.51.53.57.00
> Port : 06.32.88.59.35
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

On Thursday 17 July 2008, you wrote:
> I just did make install-tools and it didn''t change anything. I
don''t know
> if I was supposed to do something else for it to take action.
Bad luck with getting the free trip, I was hoping to avoid that for you. :-(

make install-tools should work, it''s only a userspace problem you have.
Did
you try to uninstall the existing userspace tools first as I suggested?  
Reinstalling Xen / XenLinux will *definitely* not help with Python <-> C
API
problems.

I went and poked in the Makefile for you and found that "make
uninstall" runs
the following (I''ve removed the lines that delete the hypervisor and
the
XenLinux kernel stuff, since you want to keep those).

You should substitute appropriate values for the environment variables.  $(D) 
should be set to the empty string, LIBDIR is probably /usr/lib.  Please 
double check the following commands for sanity as you always should before 
rm -rf.  Don''t trust me too much :-)

        rm -rf $(D)/etc/init.d/xend*
        rm -rf $(D)/etc/hotplug/xen-backend.agent
        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
        rm -f  $(D)/etc/udev/xen-backend.rules
        rm -f  $(D)/etc/sysconfig/xendomains
        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
        rm -rf $(D)/usr/bin/cpuperf-perfcntr $(D)/usr/bin/cpuperf-xen
        rm -rf $(D)/usr/bin/xc_shadow
        rm -rf $(D)/usr/bin/pygrub
        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
        rm -rf $(D)/usr/bin/xsls
        rm -rf $(D)/usr/include/xenctrl.h $(D)/usr/include/xenguest.h
        rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
        rm -rf $(D)/usr/include/xen
        rm -rf $(D)$(LIBDIR)/libxenctrl* $(D)$(LIBDIR)/libxenguest*
        rm -rf $(D)$(LIBDIR)/libxenstore*
        rm -rf $(D)$(LIBDIR)/python/xen $(D)$(LIBDIR)/python/grub
        rm -rf $(D)$(LIBDIR)/xen/
        rm -rf $(D)/usr/lib/xen/
        rm -rf $(D)/usr/local/sbin/setmask $(D)/usr/local/sbin/xen*
        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix $(D)/usr/sbin/xm
        rm -rf $(D)/usr/share/doc/xen
        rm -rf $(D)/usr/share/xen
        rm -rf $(D)/usr/share/man/man1/xen*
        rm -rf $(D)/usr/share/man/man8/xen*

Cheers,
Mark
> Antoine
>
> On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
>
> antoine.benkemoun@gmail.com> wrote:
> > Critical failure... machine doesn''t boot anymore. I win the
free trip !
> >
> > I am trying to do just make install-tools on the second machine just
to
> > see if it will change something.
> >
> > Antoine
> >
> >
> > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
> >
> > antoine.benkemoun@gmail.com> wrote:
> >> Ah sorry I didn''t read your email correctly.
> >>
> >> I will do that afterwards might just as well finish since
it''s been
> >> running for quite a while...
> >>
> >> Won''t be forgetting to do the initrd, thank you for
reminder. Already
> >> got trapped previously but the PC was right next to me so it
wasn''t so
> >> bad.
> >>
> >> Thanks !
> >>
> >> Antoine
> >>
> >>
> >> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
> >>
> >> mark.williamson@cl.cam.ac.uk> wrote:
> >>> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> >>> > Thank you for your thorough answer !
> >>> >
> >>> > Indeed I am booting Debian with the Xen kernel perfectly.
I don''t
> >>> > know
> >>>
> >>> what
> >>>
> >>> > you mean by XenLinux but I''m guessing
it''s what I am booting or
> >>>
> >>> something
> >>>
> >>> > similar enough.
> >>>
> >>> Sorry.
> >>>
> >>> By XenLinux I mean the Xen-aware Linux you''re booting
on top of Xen.
> >>>
> >>> > I agree that since it is the same version it
shouldn''t mess things up
> >>>
> >>> too
> >>>
> >>> > much. I am compiling at the moment using the same
tutorial (it had a
> >>> > compiling source page included). It''s taking for
ever even with a
> >>> > Quad
> >>>
> >>> Core
> >>>
> >>> > Xen machine with 4GB of RAM...
> >>>
> >>> If you''re only installing the tools, as I suggested,
you only actually
> >>> need to
> >>> do make tools; make install-tools, which should be much
faster.  If you
> >>> just
> >>> do "make world" it''ll build Xen and the
XenLinux, which will take ages
> >>> and
> >>> you already have those.
> >>>
> >>> > I''ll keep you updated if this works or if I get
a free trip to the
> >>> > datacentre :P
> >>>
> >>> I hope you don''t win that prize :-)
> >>>
> >>> Cheers,
> >>> Mark
> >>>
> >>> > Antoine
> >>> >
> >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
> >>> >
> >>> > mark.williamson@cl.cam.ac.uk> wrote:
> >>> > > > Thank you for your quick answer.
> >>> > > >
> >>> > > > I installed the 3.1.0 binaries on a Lenny Sid
installed. I
> >>> > > > followed
> >>>
> >>> the
> >>>
> >>> > > > "Perfect Xen 3.0 install" tutorial to
the letter.
> >>> > > >
> >>> > > > I have the possibility to install from sources
but I am somewhat
> >>>
> >>> afraid
> >>>
> >>> > > to
> >>> > >
> >>> > > > do so... Can it crash the machine if installed
ontop a previous
> >>>
> >>> install
> >>>
> >>> > > > ? Basically, the machine not rebooting
correctly wins me a trip
> >>> > > > to
> >>>
> >>> the
> >>>
> >>> > > > datacentre and that''s not fun :P
> >>> > >
> >>> > > Xen doesn''t play very well with conflicting
installs.  I guess if
> >>>
> >>> you''re
> >>>
> >>> > > installing the same version from source that
you''ve just installed
> >>> > > in binaries it''s not so likely to screw
things up.  That said, most
> >>> > > of
> >>>
> >>> the
> >>>
> >>> > > conflicts are typically in userspace stuff, which
shouldn''t stop
> >>> > > the machine
> >>> > > actually booting.  I''d also not expect such
conflicts to result in
> >>> > > a crash at
> >>> > > runtime, it just usually means Xend doesn''t
work properly.
> >>> > >
> >>> > > > Is it possible to uninstall a previous Xen
install so it doesn''t
> >>>
> >>> mess
> >>>
> >>> > > > up everything ?
> >>> > >
> >>> > > Yes, if you can figure out which bits to remove.  I
think there''s a
> >>>
> >>> "make
> >>>
> >>> > > uninstall" target in the source distribution
that should do this
> >>> > > reasonably thoroughly for you; it''s not
included in the binary
> >>> > > distribution you currently have :-(
> >>> > >
> >>> > > *however* in your case, you have successfully
installed Xen and
> >>>
> >>> XenLinux
> >>>
> >>> > > by the sound of it and they''re already
booting - am I reading you
> >>>
> >>> right?
> >>>
> >>> > > If you get the source distribution for the same
version of Xen and
> >>>
> >>> then
> >>>
> >>> > > just
> >>> > > compile / install the userspace tools, that should
do.  You
> >>> > > probably don''t really need to build Xen /
XenLinux lot again, or
> >>> > > even reboot
> >>>
> >>> for
> >>>
> >>> > > that matter.
> >>> > >
> >>> > > You might still need to remove the old userspace
libraries to make
> >>>
> >>> Xend
> >>>
> >>> > > work
> >>> > > right.  make uninstall should take them away but it
might remove
> >>> > > your
> >>>
> >>> Xen
> >>>
> >>> > > / XenLinux too...  I''d suggest you manually
look at what the
> >>> > > Makefile does to see which libraries / binaries to
remove, then do
> >>> > > it
> >>>
> >>> yourself.
> >>>
> >>> > > Does that sound reasonably doable to you? 
Don''t use make
> >>> > > uninstall,
> >>>
> >>> just
> >>>
> >>> > > use it for inspiration when uninstalling the
userspace tools.  Then
> >>>
> >>> run
> >>>
> >>> > > make tools-install to build and install a new
version of the tools.
> >>> > >
> >>> > > You may need to install a few -dev packages to build
successfully.
> >>> > >
> >>> > > Cheers,
> >>> > > Mark
> >>> > >
> >>> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark
Williamson <
> >>> > > >
> >>> > > > mark.williamson@cl.cam.ac.uk> wrote:
> >>> > > > > These errors typically happen when the Xen
code was built
> >>> > > > > against
> >>>
> >>> a
> >>>
> >>> > > > > different
> >>> > > > > version of Python to the one
that''s available at runtime.  I''ve
> >>> > >
> >>> > > actually
> >>> > >
> >>> > > > > found these are often harmless but
that''s probably not an
> >>>
> >>> appropriate
> >>>
> >>> > > > > risk to
> >>> > > > > take for a production machine.
> >>> > > > >
> >>> > > > > Where exactly did you get your install
source for Xen from?
> >>>
> >>>  Could
> >>>
> >>> > > > > you just build Xen yourself rather than
using a pre-compiled
> >>>
> >>> version?
> >>>
> >>> > > > > Cheers,
> >>> > > > > Mark
> >>> > > > >
> >>> > > > > On Thursday 17 July 2008, Antoine
Benkemoun wrote:
> >>> > > > > > Hello,
> >>> > > > > >
> >>> > > > > > I am trying to install Xen 3.1.0 on a
Debian Sid. I have been
> >>>
> >>> able
> >>>
> >>> > > > > > to do this type of installation
correctly with it working
> >>>
> >>> perfectly
> >>>
> >>> > > before
> >>> > >
> >>> > > > > > but
> >>> > > > >
> >>> > > > > I
> >>> > > > >
> >>> > > > > > have to admit I can''t get
this one to work.
> >>> > > > > >
> >>> > > > > > Here are the error messages that I
get at Xen startup :
> >>> > > > > >
> >>> > > > > > orangene1-hyp:~# /etc/init.d/xend
start
> >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> >>>
> >>> RuntimeWarning:
> >>> > > Python
> >>> > >
> >>> > > > > > C API version mismatch for module
xen.lowlevel.xc: This
> >>> > > > > > Python
> >>>
> >>> has
> >>>
> >>> > > API
> >>> > >
> >>> > > > > > version 1013, module xen.lowlevel.xc
has version 1012.
> >>> > > > > >   import xen.lowlevel.xc
> >>> > > > > >
/usr/lib/python/xen/util/security.py:25: RuntimeWarning:
> >>> > > > > > Python
> >>>
> >>> C
> >>>
> >>> > > > > > API version mismatch for module acm:
This Python has API
> >>>
> >>> version
> >>>
> >>> > > > > > 1013, module acm has version 1012.
> >>> > > > > >   from xen.lowlevel import acm
> >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> >>> > > > > > RuntimeWarning: Python
> >>> > >
> >>> > > C
> >>> > >
> >>> > > > > API
> >>> > > > >
> >>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python has
> >>>
> >>> API
> >>>
> >>> > > > > > version 1013, module xen.lowlevel.xs
has version 1012.
> >>> > > > > >   import xen.lowlevel.xs
> >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> >>> > > > > > RuntimeWarning: Python
> >>> > >
> >>> > > C
> >>> > >
> >>> > > > > API
> >>> > > > >
> >>> > > > > > version mismatch for module ptsname:
This Python has API
> >>>
> >>> version
> >>>
> >>> > > 1013,
> >>> > >
> >>> > > > > > module ptsname has version 1012.
> >>> > > > > >   from xen.lowlevel import ptsname
> >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> >>>
> >>> RuntimeWarning:
> >>> > > Python
> >>> > >
> >>> > > > > > C API version mismatch for module
xen.lowlevel.xc: This
> >>> > > > > > Python
> >>>
> >>> has
> >>>
> >>> > > API
> >>> > >
> >>> > > > > > version 1013, module xen.lowlevel.xc
has version 1012.
> >>> > > > > >   import xen.lowlevel.xc
> >>> > > > > >
/usr/lib/python/xen/util/security.py:25: RuntimeWarning:
> >>> > > > > > Python
> >>>
> >>> C
> >>>
> >>> > > > > > API version mismatch for module acm:
This Python has API
> >>>
> >>> version
> >>>
> >>> > > > > > 1013, module acm has version 1012.
> >>> > > > > >   from xen.lowlevel import acm
> >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> >>> > > > > > RuntimeWarning: Python
> >>> > >
> >>> > > C
> >>> > >
> >>> > > > > API
> >>> > > > >
> >>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python has
> >>>
> >>> API
> >>>
> >>> > > > > > version 1013, module xen.lowlevel.xs
has version 1012.
> >>> > > > > >   import xen.lowlevel.xs
> >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> >>> > > > > > RuntimeWarning: Python
> >>> > >
> >>> > > C
> >>> > >
> >>> > > > > API
> >>> > > > >
> >>> > > > > > version mismatch for module ptsname:
This Python has API
> >>>
> >>> version
> >>>
> >>> > > 1013,
> >>> > >
> >>> > > > > > module ptsname has version 1012.
> >>> > > > > >   from xen.lowlevel import ptsname
> >>> > > > > >
> >>> > > > > > I have tried to install python from
Sid and Lenny versions
> >>> > > > > > but
> >>>
> >>> none
> >>>
> >>> > > > > > seem
> >>> > > > >
> >>> > > > > to
> >>> > > > >
> >>> > > > > > change any of this... I have no
Python knowledge at all so I
> >>>
> >>> would
> >>>
> >>> > > like
> >>> > >
> >>> > > > > to
> >>> > > > >
> >>> > > > > > know if anybody would happen to have
an idea concerning this
> >>> > > > > > problem.
> >>> > > > > >
> >>> > > > > > I will be happy to give you more info
if there is something
> >>>
> >>> missing
> >>>
> >>> > > in
> >>> > >
> >>> > > > > this
> >>> > > > >
> >>> > > > > > post.
> >>> > > > > >
> >>> > > > > > Thank you in advance for your help,
> >>> > > > > >
> >>> > > > > > Antoine Benkemoun
> >>> > > > >
> >>> > > > > --
> >>> > > > > Push Me Pull You - Distributed SCM tool (
> >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7
> >>> > > > >Emaw48/pmpu/>
> >>>
> >>> <http://www.cl.cam.ac.uk/%7Emaw48
> >>>
> >>> > > > >/pmpu/>
> >>> > >
> >>> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >>> > >
> >>> > > > >u/> )
> >>> > >
> >>> > > --
> >>> > > Push Me Pull You - Distributed SCM tool (
> >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw
> >>> > >48/pmpu/>
> >>>
> >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >>>
> >>> > >u/> )
> >>>
> >>> --
> >>> Push Me Pull You - Distributed SCM tool (
> >>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/p
> >>>mpu/> )
> >>
> >> --
> >> Antoine Benkemoun
> >> Tel : 03.51.53.57.00
> >> Port : 06.32.88.59.35
> >
> > --
> > Antoine Benkemoun
> > Tel : 03.51.53.57.00
> > Port : 06.32.88.59.35


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

I have to admit I am a bit lost here. Concerning userspace tools, I
don''t
really know what you are talking about.

Also, the command lines you have given me will remove Xen. After that''s
done, do I just reinstall using the binaries or do I do something else ?

I am starting to think that this is going to be too complex to fix. I think
the big error that I made is trying to install it on a Lenny Sid. I
don''t
remember that ever working for me... I think just installing it on a Stable
Etch should do the trick without having to bother to spend hours patching
this to achieve mediocre stability.

Does anyone happen to have any feedback on install Xen on a Debian Sid Lenny
or Sid Etch ? I don''t recall that ever working on previous occasions.

Antoine

On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> On Thursday 17 July 2008, you wrote:
> > I just did make install-tools and it didn''t change anything.
I don''t know
> > if I was supposed to do something else for it to take action.
>
> Bad luck with getting the free trip, I was hoping to avoid that for you.
> :-(
>
> make install-tools should work, it''s only a userspace problem you
have.
>  Did
> you try to uninstall the existing userspace tools first as I suggested?
> Reinstalling Xen / XenLinux will *definitely* not help with Python
<-> C
> API
> problems.
>
> I went and poked in the Makefile for you and found that "make
uninstall"
> runs
> the following (I''ve removed the lines that delete the hypervisor
and the
> XenLinux kernel stuff, since you want to keep those).
>
> You should substitute appropriate values for the environment variables.
>  $(D)
> should be set to the empty string, LIBDIR is probably /usr/lib.  Please
> double check the following commands for sanity as you always should before
> rm -rf.  Don''t trust me too much :-)
>
>        rm -rf $(D)/etc/init.d/xend*
>        rm -rf $(D)/etc/hotplug/xen-backend.agent
>        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
>        rm -f  $(D)/etc/udev/xen-backend.rules
>        rm -f  $(D)/etc/sysconfig/xendomains
>        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
>        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
>        rm -rf $(D)/usr/bin/cpuperf-perfcntr $(D)/usr/bin/cpuperf-xen
>        rm -rf $(D)/usr/bin/xc_shadow
>        rm -rf $(D)/usr/bin/pygrub
>        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
>        rm -rf $(D)/usr/bin/xsls
>        rm -rf $(D)/usr/include/xenctrl.h $(D)/usr/include/xenguest.h
>        rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
>        rm -rf $(D)/usr/include/xen
>        rm -rf $(D)$(LIBDIR)/libxenctrl* $(D)$(LIBDIR)/libxenguest*
>        rm -rf $(D)$(LIBDIR)/libxenstore*
>        rm -rf $(D)$(LIBDIR)/python/xen $(D)$(LIBDIR)/python/grub
>        rm -rf $(D)$(LIBDIR)/xen/
>        rm -rf $(D)/usr/lib/xen/
>        rm -rf $(D)/usr/local/sbin/setmask $(D)/usr/local/sbin/xen*
>        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix $(D)/usr/sbin/xm
>        rm -rf $(D)/usr/share/doc/xen
>        rm -rf $(D)/usr/share/xen
>        rm -rf $(D)/usr/share/man/man1/xen*
>        rm -rf $(D)/usr/share/man/man8/xen*
>
> Cheers,
> Mark
>
> > Antoine
> >
> > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
> >
> > antoine.benkemoun@gmail.com> wrote:
> > > Critical failure... machine doesn''t boot anymore. I win
the free trip !
> > >
> > > I am trying to do just make install-tools on the second machine
just to
> > > see if it will change something.
> > >
> > > Antoine
> > >
> > >
> > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
> > >
> > > antoine.benkemoun@gmail.com> wrote:
> > >> Ah sorry I didn''t read your email correctly.
> > >>
> > >> I will do that afterwards might just as well finish since
it''s been
> > >> running for quite a while...
> > >>
> > >> Won''t be forgetting to do the initrd, thank you for
reminder. Already
> > >> got trapped previously but the PC was right next to me so it
wasn''t so
> > >> bad.
> > >>
> > >> Thanks !
> > >>
> > >> Antoine
> > >>
> > >>
> > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
> > >>
> > >> mark.williamson@cl.cam.ac.uk> wrote:
> > >>> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > >>> > Thank you for your thorough answer !
> > >>> >
> > >>> > Indeed I am booting Debian with the Xen kernel
perfectly. I don''t
> > >>> > know
> > >>>
> > >>> what
> > >>>
> > >>> > you mean by XenLinux but I''m guessing
it''s what I am booting or
> > >>>
> > >>> something
> > >>>
> > >>> > similar enough.
> > >>>
> > >>> Sorry.
> > >>>
> > >>> By XenLinux I mean the Xen-aware Linux you''re
booting on top of Xen.
> > >>>
> > >>> > I agree that since it is the same version it
shouldn''t mess things
> up
> > >>>
> > >>> too
> > >>>
> > >>> > much. I am compiling at the moment using the same
tutorial (it had
> a
> > >>> > compiling source page included). It''s
taking for ever even with a
> > >>> > Quad
> > >>>
> > >>> Core
> > >>>
> > >>> > Xen machine with 4GB of RAM...
> > >>>
> > >>> If you''re only installing the tools, as I
suggested, you only
> actually
> > >>> need to
> > >>> do make tools; make install-tools, which should be much
faster.  If
> you
> > >>> just
> > >>> do "make world" it''ll build Xen and
the XenLinux, which will take
> ages
> > >>> and
> > >>> you already have those.
> > >>>
> > >>> > I''ll keep you updated if this works or if I
get a free trip to the
> > >>> > datacentre :P
> > >>>
> > >>> I hope you don''t win that prize :-)
> > >>>
> > >>> Cheers,
> > >>> Mark
> > >>>
> > >>> > Antoine
> > >>> >
> > >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson
<
> > >>> >
> > >>> > mark.williamson@cl.cam.ac.uk> wrote:
> > >>> > > > Thank you for your quick answer.
> > >>> > > >
> > >>> > > > I installed the 3.1.0 binaries on a Lenny
Sid installed. I
> > >>> > > > followed
> > >>>
> > >>> the
> > >>>
> > >>> > > > "Perfect Xen 3.0 install"
tutorial to the letter.
> > >>> > > >
> > >>> > > > I have the possibility to install from
sources but I am
> somewhat
> > >>>
> > >>> afraid
> > >>>
> > >>> > > to
> > >>> > >
> > >>> > > > do so... Can it crash the machine if
installed ontop a previous
> > >>>
> > >>> install
> > >>>
> > >>> > > > ? Basically, the machine not rebooting
correctly wins me a trip
> > >>> > > > to
> > >>>
> > >>> the
> > >>>
> > >>> > > > datacentre and that''s not fun :P
> > >>> > >
> > >>> > > Xen doesn''t play very well with
conflicting installs.  I guess if
> > >>>
> > >>> you''re
> > >>>
> > >>> > > installing the same version from source that
you''ve just
> installed
> > >>> > > in binaries it''s not so likely to
screw things up.  That said,
> most
> > >>> > > of
> > >>>
> > >>> the
> > >>>
> > >>> > > conflicts are typically in userspace stuff,
which shouldn''t stop
> > >>> > > the machine
> > >>> > > actually booting.  I''d also not expect
such conflicts to result
> in
> > >>> > > a crash at
> > >>> > > runtime, it just usually means Xend
doesn''t work properly.
> > >>> > >
> > >>> > > > Is it possible to uninstall a previous Xen
install so it
> doesn''t
> > >>>
> > >>> mess
> > >>>
> > >>> > > > up everything ?
> > >>> > >
> > >>> > > Yes, if you can figure out which bits to
remove.  I think there''s
> a
> > >>>
> > >>> "make
> > >>>
> > >>> > > uninstall" target in the source
distribution that should do this
> > >>> > > reasonably thoroughly for you; it''s
not included in the binary
> > >>> > > distribution you currently have :-(
> > >>> > >
> > >>> > > *however* in your case, you have successfully
installed Xen and
> > >>>
> > >>> XenLinux
> > >>>
> > >>> > > by the sound of it and they''re already
booting - am I reading you
> > >>>
> > >>> right?
> > >>>
> > >>> > > If you get the source distribution for the same
version of Xen
> and
> > >>>
> > >>> then
> > >>>
> > >>> > > just
> > >>> > > compile / install the userspace tools, that
should do.  You
> > >>> > > probably don''t really need to build
Xen / XenLinux lot again, or
> > >>> > > even reboot
> > >>>
> > >>> for
> > >>>
> > >>> > > that matter.
> > >>> > >
> > >>> > > You might still need to remove the old
userspace libraries to
> make
> > >>>
> > >>> Xend
> > >>>
> > >>> > > work
> > >>> > > right.  make uninstall should take them away
but it might remove
> > >>> > > your
> > >>>
> > >>> Xen
> > >>>
> > >>> > > / XenLinux too...  I''d suggest you
manually look at what the
> > >>> > > Makefile does to see which libraries / binaries
to remove, then
> do
> > >>> > > it
> > >>>
> > >>> yourself.
> > >>>
> > >>> > > Does that sound reasonably doable to you? 
Don''t use make
> > >>> > > uninstall,
> > >>>
> > >>> just
> > >>>
> > >>> > > use it for inspiration when uninstalling the
userspace tools.
>  Then
> > >>>
> > >>> run
> > >>>
> > >>> > > make tools-install to build and install a new
version of the
> tools.
> > >>> > >
> > >>> > > You may need to install a few -dev packages to
build
> successfully.
> > >>> > >
> > >>> > > Cheers,
> > >>> > > Mark
> > >>> > >
> > >>> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark
Williamson <
> > >>> > > >
> > >>> > > > mark.williamson@cl.cam.ac.uk> wrote:
> > >>> > > > > These errors typically happen when
the Xen code was built
> > >>> > > > > against
> > >>>
> > >>> a
> > >>>
> > >>> > > > > different
> > >>> > > > > version of Python to the one
that''s available at runtime.
>  I''ve
> > >>> > >
> > >>> > > actually
> > >>> > >
> > >>> > > > > found these are often harmless but
that''s probably not an
> > >>>
> > >>> appropriate
> > >>>
> > >>> > > > > risk to
> > >>> > > > > take for a production machine.
> > >>> > > > >
> > >>> > > > > Where exactly did you get your
install source for Xen from?
> > >>>
> > >>>  Could
> > >>>
> > >>> > > > > you just build Xen yourself rather
than using a pre-compiled
> > >>>
> > >>> version?
> > >>>
> > >>> > > > > Cheers,
> > >>> > > > > Mark
> > >>> > > > >
> > >>> > > > > On Thursday 17 July 2008, Antoine
Benkemoun wrote:
> > >>> > > > > > Hello,
> > >>> > > > > >
> > >>> > > > > > I am trying to install Xen 3.1.0
on a Debian Sid. I have
> been
> > >>>
> > >>> able
> > >>>
> > >>> > > > > > to do this type of installation
correctly with it working
> > >>>
> > >>> perfectly
> > >>>
> > >>> > > before
> > >>> > >
> > >>> > > > > > but
> > >>> > > > >
> > >>> > > > > I
> > >>> > > > >
> > >>> > > > > > have to admit I can''t
get this one to work.
> > >>> > > > > >
> > >>> > > > > > Here are the error messages that
I get at Xen startup :
> > >>> > > > > >
> > >>> > > > > > orangene1-hyp:~#
/etc/init.d/xend start
> > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > >>>
> > >>> RuntimeWarning:
> > >>> > > Python
> > >>> > >
> > >>> > > > > > C API version mismatch for
module xen.lowlevel.xc: This
> > >>> > > > > > Python
> > >>>
> > >>> has
> > >>>
> > >>> > > API
> > >>> > >
> > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
> > >>> > > > > >   import xen.lowlevel.xc
> > >>> > > > > >
/usr/lib/python/xen/util/security.py:25: RuntimeWarning:
> > >>> > > > > > Python
> > >>>
> > >>> C
> > >>>
> > >>> > > > > > API version mismatch for module
acm: This Python has API
> > >>>
> > >>> version
> > >>>
> > >>> > > > > > 1013, module acm has version
1012.
> > >>> > > > > >   from xen.lowlevel import acm
> > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > >>> > > > > > RuntimeWarning: Python
> > >>> > >
> > >>> > > C
> > >>> > >
> > >>> > > > > API
> > >>> > > > >
> > >>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python
> has
> > >>>
> > >>> API
> > >>>
> > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
> > >>> > > > > >   import xen.lowlevel.xs
> > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > >>> > > > > > RuntimeWarning: Python
> > >>> > >
> > >>> > > C
> > >>> > >
> > >>> > > > > API
> > >>> > > > >
> > >>> > > > > > version mismatch for module
ptsname: This Python has API
> > >>>
> > >>> version
> > >>>
> > >>> > > 1013,
> > >>> > >
> > >>> > > > > > module ptsname has version 1012.
> > >>> > > > > >   from xen.lowlevel import
ptsname
> > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > >>>
> > >>> RuntimeWarning:
> > >>> > > Python
> > >>> > >
> > >>> > > > > > C API version mismatch for
module xen.lowlevel.xc: This
> > >>> > > > > > Python
> > >>>
> > >>> has
> > >>>
> > >>> > > API
> > >>> > >
> > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
> > >>> > > > > >   import xen.lowlevel.xc
> > >>> > > > > >
/usr/lib/python/xen/util/security.py:25: RuntimeWarning:
> > >>> > > > > > Python
> > >>>
> > >>> C
> > >>>
> > >>> > > > > > API version mismatch for module
acm: This Python has API
> > >>>
> > >>> version
> > >>>
> > >>> > > > > > 1013, module acm has version
1012.
> > >>> > > > > >   from xen.lowlevel import acm
> > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > >>> > > > > > RuntimeWarning: Python
> > >>> > >
> > >>> > > C
> > >>> > >
> > >>> > > > > API
> > >>> > > > >
> > >>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python
> has
> > >>>
> > >>> API
> > >>>
> > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
> > >>> > > > > >   import xen.lowlevel.xs
> > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > >>> > > > > > RuntimeWarning: Python
> > >>> > >
> > >>> > > C
> > >>> > >
> > >>> > > > > API
> > >>> > > > >
> > >>> > > > > > version mismatch for module
ptsname: This Python has API
> > >>>
> > >>> version
> > >>>
> > >>> > > 1013,
> > >>> > >
> > >>> > > > > > module ptsname has version 1012.
> > >>> > > > > >   from xen.lowlevel import
ptsname
> > >>> > > > > >
> > >>> > > > > > I have tried to install python
from Sid and Lenny versions
> > >>> > > > > > but
> > >>>
> > >>> none
> > >>>
> > >>> > > > > > seem
> > >>> > > > >
> > >>> > > > > to
> > >>> > > > >
> > >>> > > > > > change any of this... I have no
Python knowledge at all so
> I
> > >>>
> > >>> would
> > >>>
> > >>> > > like
> > >>> > >
> > >>> > > > > to
> > >>> > > > >
> > >>> > > > > > know if anybody would happen to
have an idea concerning
> this
> > >>> > > > > > problem.
> > >>> > > > > >
> > >>> > > > > > I will be happy to give you more
info if there is something
> > >>>
> > >>> missing
> > >>>
> > >>> > > in
> > >>> > >
> > >>> > > > > this
> > >>> > > > >
> > >>> > > > > > post.
> > >>> > > > > >
> > >>> > > > > > Thank you in advance for your
help,
> > >>> > > > > >
> > >>> > > > > > Antoine Benkemoun
> > >>> > > > >
> > >>> > > > > --
> > >>> > > > > Push Me Pull You - Distributed SCM
tool (
> > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7
> > >>> > > > >Emaw48/pmpu/>
> > >>>
> > >>> <http://www.cl.cam.ac.uk/%7Emaw48
> > >>>
> > >>> > > > >/pmpu/>
> > >>> > >
> > >>> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > >>> > >
> > >>> > > > >u/> )
> > >>> > >
> > >>> > > --
> > >>> > > Push Me Pull You - Distributed SCM tool (
> > >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw
> > >>> > >48/pmpu/>
> > >>>
> > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > >>>
> > >>> > >u/> )
> > >>>
> > >>> --
> > >>> Push Me Pull You - Distributed SCM tool (
> > >>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw48/p
> > >>>mpu/> )
> > >>
> > >> --
> > >> Antoine Benkemoun
> > >> Tel : 03.51.53.57.00
> > >> Port : 06.32.88.59.35
> > >
> > > --
> > > Antoine Benkemoun
> > > Tel : 03.51.53.57.00
> > > Port : 06.32.88.59.35
>
>
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

On Thursday 17 July 2008, Antoine Benkemoun wrote:
> I have to admit I am a bit lost here. Concerning userspace tools, I
don''t
> really know what you are talking about.
OK, sorry, lets step back a bit.

If you want your host to *boot* you need the Xen hypervisor (xen.gz) and 
XenLinux (vmlinuz-xen or somesuch) and an initrd.

I understood from your previous e-mails that you''ve installed these,
set up
menu.lst to boot them and successfully booted into them.  Is that right?  
This means you''ve got a running dom0.

From this system, you''re then trying to run xend and it''s
giving loads of
errors about Python C API mismatches.  I''m I correct so far?
> Also, the command lines you have given me will remove Xen. After
that''s
> done, do I just reinstall using the binaries or do I do something else ?
A Xen-based system has three main components: the Xen hypervisor, the dom0 
Linux kernel and the userspace tools.  You seem to have the first two working 
OK, I think?

The problem you''re seeing when starting Xend is strictly a userspace
tools
issue.  xend is just a daemon that''s written in Python and C which
issues
control hypercalls to Xen to tell it what to do.  To fix this issue you only 
need to fix these tools.

The command lines I gave you will remove all the *userspace* parts of Xen but 
should (if I''ve editted them right) leave the Xen hypervisor and the
XenLinux
kernel you''re using in place.  This should leave the machine still
bootable
(assuming I''m correct in thinking you''ve successfully booted
Xen/XenLinux
already).

Using a source tree of the same version of Xen, "make install-tools"
should
replace the stuff we just removed with a custom-built copy, allowing you to 
start Xend without errors.  That''s the plan.  You shouldn''t
even need to
reboot.  You should still be able to do this on the box you didn''t
reboot...
> I am starting to think that this is going to be too complex to fix. I think
> the big error that I made is trying to install it on a Lenny Sid. I
don''t
> remember that ever working for me... I think just installing it on a Stable
> Etch should do the trick without having to bother to spend hours patching
> this to achieve mediocre stability.
>
> Does anyone happen to have any feedback on install Xen on a Debian Sid
> Lenny or Sid Etch ? I don''t recall that ever working on previous
occasions.
I think that Etch, at least, has reasonably recent Xen packages.  How about 
just using the Debian-provided packages, at least to start with?  XenSource 
don''t guarantee to keep updating their kernels with security / bug
fixes so
you might find that the Debian kernels are more up-to-date.

Cheers,
Mark
> Antoine
>
> On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
>
> mark.williamson@cl.cam.ac.uk> wrote:
> > On Thursday 17 July 2008, you wrote:
> > > I just did make install-tools and it didn''t change
anything. I don''t
> > > know if I was supposed to do something else for it to take
action.
> >
> > Bad luck with getting the free trip, I was hoping to avoid that for
you.
> >
> > :-(
> >
> > make install-tools should work, it''s only a userspace problem
you have.
> >  Did
> > you try to uninstall the existing userspace tools first as I
suggested?
> > Reinstalling Xen / XenLinux will *definitely* not help with Python
<-> C
> > API
> > problems.
> >
> > I went and poked in the Makefile for you and found that "make
uninstall"
> > runs
> > the following (I''ve removed the lines that delete the
hypervisor and the
> > XenLinux kernel stuff, since you want to keep those).
> >
> > You should substitute appropriate values for the environment
variables.
> >  $(D)
> > should be set to the empty string, LIBDIR is probably /usr/lib. 
Please
> > double check the following commands for sanity as you always should
> > before rm -rf.  Don''t trust me too much :-)
> >
> >        rm -rf $(D)/etc/init.d/xend*
> >        rm -rf $(D)/etc/hotplug/xen-backend.agent
> >        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
> >        rm -f  $(D)/etc/udev/xen-backend.rules
> >        rm -f  $(D)/etc/sysconfig/xendomains
> >        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
> >        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
> >        rm -rf $(D)/usr/bin/cpuperf-perfcntr $(D)/usr/bin/cpuperf-xen
> >        rm -rf $(D)/usr/bin/xc_shadow
> >        rm -rf $(D)/usr/bin/pygrub
> >        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
> >        rm -rf $(D)/usr/bin/xsls
> >        rm -rf $(D)/usr/include/xenctrl.h $(D)/usr/include/xenguest.h
> >        rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
> >        rm -rf $(D)/usr/include/xen
> >        rm -rf $(D)$(LIBDIR)/libxenctrl* $(D)$(LIBDIR)/libxenguest*
> >        rm -rf $(D)$(LIBDIR)/libxenstore*
> >        rm -rf $(D)$(LIBDIR)/python/xen $(D)$(LIBDIR)/python/grub
> >        rm -rf $(D)$(LIBDIR)/xen/
> >        rm -rf $(D)/usr/lib/xen/
> >        rm -rf $(D)/usr/local/sbin/setmask $(D)/usr/local/sbin/xen*
> >        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix $(D)/usr/sbin/xm
> >        rm -rf $(D)/usr/share/doc/xen
> >        rm -rf $(D)/usr/share/xen
> >        rm -rf $(D)/usr/share/man/man1/xen*
> >        rm -rf $(D)/usr/share/man/man8/xen*
> >
> > Cheers,
> > Mark
> >
> > > Antoine
> > >
> > > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
> > >
> > > antoine.benkemoun@gmail.com> wrote:
> > > > Critical failure... machine doesn''t boot anymore. I
win the free trip
> > > > !
> > > >
> > > > I am trying to do just make install-tools on the second
machine just
> > > > to see if it will change something.
> > > >
> > > > Antoine
> > > >
> > > >
> > > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
> > > >
> > > > antoine.benkemoun@gmail.com> wrote:
> > > >> Ah sorry I didn''t read your email correctly.
> > > >>
> > > >> I will do that afterwards might just as well finish
since it''s been
> > > >> running for quite a while...
> > > >>
> > > >> Won''t be forgetting to do the initrd, thank you
for reminder.
> > > >> Already got trapped previously but the PC was right next
to me so it
> > > >> wasn''t so bad.
> > > >>
> > > >> Thanks !
> > > >>
> > > >> Antoine
> > > >>
> > > >>
> > > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
> > > >>
> > > >> mark.williamson@cl.cam.ac.uk> wrote:
> > > >>> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > >>> > Thank you for your thorough answer !
> > > >>> >
> > > >>> > Indeed I am booting Debian with the Xen kernel
perfectly. I don''t
> > > >>> > know
> > > >>>
> > > >>> what
> > > >>>
> > > >>> > you mean by XenLinux but I''m guessing
it''s what I am booting or
> > > >>>
> > > >>> something
> > > >>>
> > > >>> > similar enough.
> > > >>>
> > > >>> Sorry.
> > > >>>
> > > >>> By XenLinux I mean the Xen-aware Linux
you''re booting on top of
> > > >>> Xen.
> > > >>>
> > > >>> > I agree that since it is the same version it
shouldn''t mess
> > > >>> > things
> >
> > up
> >
> > > >>> too
> > > >>>
> > > >>> > much. I am compiling at the moment using the
same tutorial (it
> > > >>> > had
> >
> > a
> >
> > > >>> > compiling source page included). It''s
taking for ever even with a
> > > >>> > Quad
> > > >>>
> > > >>> Core
> > > >>>
> > > >>> > Xen machine with 4GB of RAM...
> > > >>>
> > > >>> If you''re only installing the tools, as I
suggested, you only
> >
> > actually
> >
> > > >>> need to
> > > >>> do make tools; make install-tools, which should be
much faster.  If
> >
> > you
> >
> > > >>> just
> > > >>> do "make world" it''ll build Xen
and the XenLinux, which will take
> >
> > ages
> >
> > > >>> and
> > > >>> you already have those.
> > > >>>
> > > >>> > I''ll keep you updated if this works or
if I get a free trip to
> > > >>> > the datacentre :P
> > > >>>
> > > >>> I hope you don''t win that prize :-)
> > > >>>
> > > >>> Cheers,
> > > >>> Mark
> > > >>>
> > > >>> > Antoine
> > > >>> >
> > > >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark
Williamson <
> > > >>> >
> > > >>> > mark.williamson@cl.cam.ac.uk> wrote:
> > > >>> > > > Thank you for your quick answer.
> > > >>> > > >
> > > >>> > > > I installed the 3.1.0 binaries on a
Lenny Sid installed. I
> > > >>> > > > followed
> > > >>>
> > > >>> the
> > > >>>
> > > >>> > > > "Perfect Xen 3.0 install"
tutorial to the letter.
> > > >>> > > >
> > > >>> > > > I have the possibility to install
from sources but I am
> >
> > somewhat
> >
> > > >>> afraid
> > > >>>
> > > >>> > > to
> > > >>> > >
> > > >>> > > > do so... Can it crash the machine if
installed ontop a
> > > >>> > > > previous
> > > >>>
> > > >>> install
> > > >>>
> > > >>> > > > ? Basically, the machine not
rebooting correctly wins me a
> > > >>> > > > trip to
> > > >>>
> > > >>> the
> > > >>>
> > > >>> > > > datacentre and that''s not
fun :P
> > > >>> > >
> > > >>> > > Xen doesn''t play very well with
conflicting installs.  I guess
> > > >>> > > if
> > > >>>
> > > >>> you''re
> > > >>>
> > > >>> > > installing the same version from source
that you''ve just
> >
> > installed
> >
> > > >>> > > in binaries it''s not so likely to
screw things up.  That said,
> >
> > most
> >
> > > >>> > > of
> > > >>>
> > > >>> the
> > > >>>
> > > >>> > > conflicts are typically in userspace
stuff, which shouldn''t
> > > >>> > > stop the machine
> > > >>> > > actually booting.  I''d also not
expect such conflicts to result
> >
> > in
> >
> > > >>> > > a crash at
> > > >>> > > runtime, it just usually means Xend
doesn''t work properly.
> > > >>> > >
> > > >>> > > > Is it possible to uninstall a
previous Xen install so it
> >
> > doesn''t
> >
> > > >>> mess
> > > >>>
> > > >>> > > > up everything ?
> > > >>> > >
> > > >>> > > Yes, if you can figure out which bits to
remove.  I think
> > > >>> > > there''s
> >
> > a
> >
> > > >>> "make
> > > >>>
> > > >>> > > uninstall" target in the source
distribution that should do
> > > >>> > > this reasonably thoroughly for you;
it''s not included in the
> > > >>> > > binary distribution you currently have :-(
> > > >>> > >
> > > >>> > > *however* in your case, you have
successfully installed Xen and
> > > >>>
> > > >>> XenLinux
> > > >>>
> > > >>> > > by the sound of it and they''re
already booting - am I reading
> > > >>> > > you
> > > >>>
> > > >>> right?
> > > >>>
> > > >>> > > If you get the source distribution for the
same version of Xen
> >
> > and
> >
> > > >>> then
> > > >>>
> > > >>> > > just
> > > >>> > > compile / install the userspace tools,
that should do.  You
> > > >>> > > probably don''t really need to
build Xen / XenLinux lot again,
> > > >>> > > or even reboot
> > > >>>
> > > >>> for
> > > >>>
> > > >>> > > that matter.
> > > >>> > >
> > > >>> > > You might still need to remove the old
userspace libraries to
> >
> > make
> >
> > > >>> Xend
> > > >>>
> > > >>> > > work
> > > >>> > > right.  make uninstall should take them
away but it might
> > > >>> > > remove your
> > > >>>
> > > >>> Xen
> > > >>>
> > > >>> > > / XenLinux too...  I''d suggest
you manually look at what the
> > > >>> > > Makefile does to see which libraries /
binaries to remove, then
> >
> > do
> >
> > > >>> > > it
> > > >>>
> > > >>> yourself.
> > > >>>
> > > >>> > > Does that sound reasonably doable to you? 
Don''t use make
> > > >>> > > uninstall,
> > > >>>
> > > >>> just
> > > >>>
> > > >>> > > use it for inspiration when uninstalling
the userspace tools.
> >
> >  Then
> >
> > > >>> run
> > > >>>
> > > >>> > > make tools-install to build and install a
new version of the
> >
> > tools.
> >
> > > >>> > > You may need to install a few -dev
packages to build
> >
> > successfully.
> >
> > > >>> > > Cheers,
> > > >>> > > Mark
> > > >>> > >
> > > >>> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark
Williamson <
> > > >>> > > >
> > > >>> > > > mark.williamson@cl.cam.ac.uk>
wrote:
> > > >>> > > > > These errors typically happen
when the Xen code was built
> > > >>> > > > > against
> > > >>>
> > > >>> a
> > > >>>
> > > >>> > > > > different
> > > >>> > > > > version of Python to the one
that''s available at runtime.
> >
> >  I''ve
> >
> > > >>> > > actually
> > > >>> > >
> > > >>> > > > > found these are often harmless
but that''s probably not an
> > > >>>
> > > >>> appropriate
> > > >>>
> > > >>> > > > > risk to
> > > >>> > > > > take for a production machine.
> > > >>> > > > >
> > > >>> > > > > Where exactly did you get your
install source for Xen from?
> > > >>>
> > > >>>  Could
> > > >>>
> > > >>> > > > > you just build Xen yourself
rather than using a
> > > >>> > > > > pre-compiled
> > > >>>
> > > >>> version?
> > > >>>
> > > >>> > > > > Cheers,
> > > >>> > > > > Mark
> > > >>> > > > >
> > > >>> > > > > On Thursday 17 July 2008,
Antoine Benkemoun wrote:
> > > >>> > > > > > Hello,
> > > >>> > > > > >
> > > >>> > > > > > I am trying to install Xen
3.1.0 on a Debian Sid. I have
> >
> > been
> >
> > > >>> able
> > > >>>
> > > >>> > > > > > to do this type of
installation correctly with it working
> > > >>>
> > > >>> perfectly
> > > >>>
> > > >>> > > before
> > > >>> > >
> > > >>> > > > > > but
> > > >>> > > > >
> > > >>> > > > > I
> > > >>> > > > >
> > > >>> > > > > > have to admit I
can''t get this one to work.
> > > >>> > > > > >
> > > >>> > > > > > Here are the error messages
that I get at Xen startup :
> > > >>> > > > > >
> > > >>> > > > > > orangene1-hyp:~#
/etc/init.d/xend start
> > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > > >>>
> > > >>> RuntimeWarning:
> > > >>> > > Python
> > > >>> > >
> > > >>> > > > > > C API version mismatch for
module xen.lowlevel.xc: This
> > > >>> > > > > > Python
> > > >>>
> > > >>> has
> > > >>>
> > > >>> > > API
> > > >>> > >
> > > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
> > > >>> > > > > >   import xen.lowlevel.xc
> > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25: RuntimeWarning:
> > > >>> > > > > > Python
> > > >>>
> > > >>> C
> > > >>>
> > > >>> > > > > > API version mismatch for
module acm: This Python has API
> > > >>>
> > > >>> version
> > > >>>
> > > >>> > > > > > 1013, module acm has
version 1012.
> > > >>> > > > > >   from xen.lowlevel import
acm
> > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > > >>> > > > > > RuntimeWarning: Python
> > > >>> > >
> > > >>> > > C
> > > >>> > >
> > > >>> > > > > API
> > > >>> > > > >
> > > >>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python
> >
> > has
> >
> > > >>> API
> > > >>>
> > > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
> > > >>> > > > > >   import xen.lowlevel.xs
> > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > > >>> > > > > > RuntimeWarning: Python
> > > >>> > >
> > > >>> > > C
> > > >>> > >
> > > >>> > > > > API
> > > >>> > > > >
> > > >>> > > > > > version mismatch for module
ptsname: This Python has API
> > > >>>
> > > >>> version
> > > >>>
> > > >>> > > 1013,
> > > >>> > >
> > > >>> > > > > > module ptsname has version
1012.
> > > >>> > > > > >   from xen.lowlevel import
ptsname
> > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > > >>>
> > > >>> RuntimeWarning:
> > > >>> > > Python
> > > >>> > >
> > > >>> > > > > > C API version mismatch for
module xen.lowlevel.xc: This
> > > >>> > > > > > Python
> > > >>>
> > > >>> has
> > > >>>
> > > >>> > > API
> > > >>> > >
> > > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
> > > >>> > > > > >   import xen.lowlevel.xc
> > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25: RuntimeWarning:
> > > >>> > > > > > Python
> > > >>>
> > > >>> C
> > > >>>
> > > >>> > > > > > API version mismatch for
module acm: This Python has API
> > > >>>
> > > >>> version
> > > >>>
> > > >>> > > > > > 1013, module acm has
version 1012.
> > > >>> > > > > >   from xen.lowlevel import
acm
> > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > > >>> > > > > > RuntimeWarning: Python
> > > >>> > >
> > > >>> > > C
> > > >>> > >
> > > >>> > > > > API
> > > >>> > > > >
> > > >>> > > > > > version mismatch for module
xen.lowlevel.xs: This Python
> >
> > has
> >
> > > >>> API
> > > >>>
> > > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
> > > >>> > > > > >   import xen.lowlevel.xs
> > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > > >>> > > > > > RuntimeWarning: Python
> > > >>> > >
> > > >>> > > C
> > > >>> > >
> > > >>> > > > > API
> > > >>> > > > >
> > > >>> > > > > > version mismatch for module
ptsname: This Python has API
> > > >>>
> > > >>> version
> > > >>>
> > > >>> > > 1013,
> > > >>> > >
> > > >>> > > > > > module ptsname has version
1012.
> > > >>> > > > > >   from xen.lowlevel import
ptsname
> > > >>> > > > > >
> > > >>> > > > > > I have tried to install
python from Sid and Lenny
> > > >>> > > > > > versions but
> > > >>>
> > > >>> none
> > > >>>
> > > >>> > > > > > seem
> > > >>> > > > >
> > > >>> > > > > to
> > > >>> > > > >
> > > >>> > > > > > change any of this... I
have no Python knowledge at all
> > > >>> > > > > > so
> >
> > I
> >
> > > >>> would
> > > >>>
> > > >>> > > like
> > > >>> > >
> > > >>> > > > > to
> > > >>> > > > >
> > > >>> > > > > > know if anybody would
happen to have an idea concerning
> >
> > this
> >
> > > >>> > > > > > problem.
> > > >>> > > > > >
> > > >>> > > > > > I will be happy to give you
more info if there is
> > > >>> > > > > > something
> > > >>>
> > > >>> missing
> > > >>>
> > > >>> > > in
> > > >>> > >
> > > >>> > > > > this
> > > >>> > > > >
> > > >>> > > > > > post.
> > > >>> > > > > >
> > > >>> > > > > > Thank you in advance for
your help,
> > > >>> > > > > >
> > > >>> > > > > > Antoine Benkemoun
> > > >>> > > > >
> > > >>> > > > > --
> > > >>> > > > > Push Me Pull You - Distributed
SCM tool (
> > > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.u
> > > >>> > > > >k/%7Emaw48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7
> >
> > > >>> > > > >Emaw48/pmpu/>
> > > >>>
> > > >>> <http://www.cl.cam.ac.uk/%7Emaw48
> > > >>>
> > > >>> > > > >/pmpu/>
> > > >>> > >
> > > >>> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > > >>> > >
> > > >>> > > > >u/> )
> > > >>> > >
> > > >>> > > --
> > > >>> > > Push Me Pull You - Distributed SCM tool (
> > > >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7
> > > >>> > >Emaw48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw
> >
> > > >>> > >48/pmpu/>
> > > >>>
> > > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > > >>>
> > > >>> > >u/> )
> > > >>>
> > > >>> --
> > > >>> Push Me Pull You - Distributed SCM tool (
> > > >>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw
> > > >>>48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw48/p
> >
> > > >>>mpu/> )
> > > >>
> > > >> --
> > > >> Antoine Benkemoun
> > > >> Tel : 03.51.53.57.00
> > > >> Port : 06.32.88.59.35
> > > >
> > > > --
> > > > Antoine Benkemoun
> > > > Tel : 03.51.53.57.00
> > > > Port : 06.32.88.59.35
> >
> > --
> > Push Me Pull You - Distributed SCM tool (
> >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >u/> )


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

Antoine Benkemoun schrieb:
> I have to admit I am a bit lost here. Concerning userspace tools, I 
> don''t really know what you are talking about.
>
> Also, the command lines you have given me will remove Xen. After 
> that''s done, do I just reinstall using the binaries or do I do 
> something else ?
>
> I am starting to think that this is going to be too complex to fix. I 
> think the big error that I made is trying to install it on a Lenny 
> Sid. I don''t remember that ever working for me... I think just 
> installing it on a Stable Etch should do the trick without having to 
> bother to spend hours patching this to achieve mediocre stability.
>
> Does anyone happen to have any feedback on install Xen on a Debian Sid 
> Lenny or Sid Etch ? I don''t recall that ever working on previous 
> occasions.
>
I''ve run xen 3.1 from source pretty stable on debian etch.
Just make a clean debian etch install and follow the perfect xen 3.1 howto.
http://www.howtoforge.com/debian_etch_xen_3.1_p5
You should also do apt-get install g++ for correct compiling.
If you want to do so and have any questions, don''t hesitate to ask me.

Cheers,
Alex

> Antoine
>
> On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson 
> <mark.williamson@cl.cam.ac.uk
<mailto:mark.williamson@cl.cam.ac.uk>>
> wrote:
>
>     On Thursday 17 July 2008, you wrote:
>     > I just did make install-tools and it didn''t change
anything. I
>     don''t know
>     > if I was supposed to do something else for it to take action.
>
>     Bad luck with getting the free trip, I was hoping to avoid that
>     for you. :-(
>
>     make install-tools should work, it''s only a userspace problem
you
>     have.  Did
>     you try to uninstall the existing userspace tools first as I
>     suggested?
>     Reinstalling Xen / XenLinux will *definitely* not help with Python
>     <-> C API
>     problems.
>
>     I went and poked in the Makefile for you and found that "make
>     uninstall" runs
>     the following (I''ve removed the lines that delete the
hypervisor
>     and the
>     XenLinux kernel stuff, since you want to keep those).
>
>     You should substitute appropriate values for the environment
>     variables.  $(D)
>     should be set to the empty string, LIBDIR is probably /usr/lib.
>      Please
>     double check the following commands for sanity as you always
>     should before
>     rm -rf.  Don''t trust me too much :-)
>
>            rm -rf $(D)/etc/init.d/xend*
>            rm -rf $(D)/etc/hotplug/xen-backend.agent
>            rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
>            rm -f  $(D)/etc/udev/xen-backend.rules
>            rm -f  $(D)/etc/sysconfig/xendomains
>            rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
>            rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
>            rm -rf $(D)/usr/bin/cpuperf-perfcntr $(D)/usr/bin/cpuperf-xen
>            rm -rf $(D)/usr/bin/xc_shadow
>            rm -rf $(D)/usr/bin/pygrub
>            rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
>            rm -rf $(D)/usr/bin/xsls
>            rm -rf $(D)/usr/include/xenctrl.h $(D)/usr/include/xenguest.h
>            rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
>            rm -rf $(D)/usr/include/xen
>            rm -rf $(D)$(LIBDIR)/libxenctrl* $(D)$(LIBDIR)/libxenguest*
>            rm -rf $(D)$(LIBDIR)/libxenstore*
>            rm -rf $(D)$(LIBDIR)/python/xen $(D)$(LIBDIR)/python/grub
>            rm -rf $(D)$(LIBDIR)/xen/
>            rm -rf $(D)/usr/lib/xen/
>            rm -rf $(D)/usr/local/sbin/setmask $(D)/usr/local/sbin/xen*
>            rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix $(D)/usr/sbin/xm
>            rm -rf $(D)/usr/share/doc/xen
>            rm -rf $(D)/usr/share/xen
>            rm -rf $(D)/usr/share/man/man1/xen*
>            rm -rf $(D)/usr/share/man/man8/xen*
>
>     Cheers,
>     Mark
>
>     > Antoine
>     >
>     > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
>     >
>     > antoine.benkemoun@gmail.com
>     <mailto:antoine.benkemoun@gmail.com>> wrote:
>     > > Critical failure... machine doesn''t boot anymore. I
win the
>     free trip !
>     > >
>     > > I am trying to do just make install-tools on the second
>     machine just to
>     > > see if it will change something.
>     > >
>     > > Antoine
>     > >
>     > >
>     > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
>     > >
>     > > antoine.benkemoun@gmail.com
>     <mailto:antoine.benkemoun@gmail.com>> wrote:
>     > >> Ah sorry I didn''t read your email correctly.
>     > >>
>     > >> I will do that afterwards might just as well finish since
>     it''s been
>     > >> running for quite a while...
>     > >>
>     > >> Won''t be forgetting to do the initrd, thank you
for reminder.
>     Already
>     > >> got trapped previously but the PC was right next to me so
it
>     wasn''t so
>     > >> bad.
>     > >>
>     > >> Thanks !
>     > >>
>     > >> Antoine
>     > >>
>     > >>
>     > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
>     > >>
>     > >> mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > >>> On Thursday 17 July 2008, Antoine Benkemoun wrote:
>     > >>> > Thank you for your thorough answer !
>     > >>> >
>     > >>> > Indeed I am booting Debian with the Xen kernel
perfectly.
>     I don''t
>     > >>> > know
>     > >>>
>     > >>> what
>     > >>>
>     > >>> > you mean by XenLinux but I''m guessing
it''s what I am
>     booting or
>     > >>>
>     > >>> something
>     > >>>
>     > >>> > similar enough.
>     > >>>
>     > >>> Sorry.
>     > >>>
>     > >>> By XenLinux I mean the Xen-aware Linux
you''re booting on top
>     of Xen.
>     > >>>
>     > >>> > I agree that since it is the same version it
shouldn''t
>     mess things up
>     > >>>
>     > >>> too
>     > >>>
>     > >>> > much. I am compiling at the moment using the
same tutorial
>     (it had a
>     > >>> > compiling source page included). It''s
taking for ever even
>     with a
>     > >>> > Quad
>     > >>>
>     > >>> Core
>     > >>>
>     > >>> > Xen machine with 4GB of RAM...
>     > >>>
>     > >>> If you''re only installing the tools, as I
suggested, you
>     only actually
>     > >>> need to
>     > >>> do make tools; make install-tools, which should be
much
>     faster.  If you
>     > >>> just
>     > >>> do "make world" it''ll build Xen
and the XenLinux, which will
>     take ages
>     > >>> and
>     > >>> you already have those.
>     > >>>
>     > >>> > I''ll keep you updated if this works or
if I get a free
>     trip to the
>     > >>> > datacentre :P
>     > >>>
>     > >>> I hope you don''t win that prize :-)
>     > >>>
>     > >>> Cheers,
>     > >>> Mark
>     > >>>
>     > >>> > Antoine
>     > >>> >
>     > >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson
<
>     > >>> >
>     > >>> > mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > >>> > > > Thank you for your quick answer.
>     > >>> > > >
>     > >>> > > > I installed the 3.1.0 binaries on a
Lenny Sid installed. I
>     > >>> > > > followed
>     > >>>
>     > >>> the
>     > >>>
>     > >>> > > > "Perfect Xen 3.0 install"
tutorial to the letter.
>     > >>> > > >
>     > >>> > > > I have the possibility to install from
sources but I
>     am somewhat
>     > >>>
>     > >>> afraid
>     > >>>
>     > >>> > > to
>     > >>> > >
>     > >>> > > > do so... Can it crash the machine if
installed ontop a
>     previous
>     > >>>
>     > >>> install
>     > >>>
>     > >>> > > > ? Basically, the machine not rebooting
correctly wins
>     me a trip
>     > >>> > > > to
>     > >>>
>     > >>> the
>     > >>>
>     > >>> > > > datacentre and that''s not fun
:P
>     > >>> > >
>     > >>> > > Xen doesn''t play very well with
conflicting installs.  I
>     guess if
>     > >>>
>     > >>> you''re
>     > >>>
>     > >>> > > installing the same version from source
that you''ve just
>     installed
>     > >>> > > in binaries it''s not so likely to
screw things up.  That
>     said, most
>     > >>> > > of
>     > >>>
>     > >>> the
>     > >>>
>     > >>> > > conflicts are typically in userspace stuff,
which
>     shouldn''t stop
>     > >>> > > the machine
>     > >>> > > actually booting.  I''d also not
expect such conflicts to
>     result in
>     > >>> > > a crash at
>     > >>> > > runtime, it just usually means Xend
doesn''t work properly.
>     > >>> > >
>     > >>> > > > Is it possible to uninstall a previous
Xen install so
>     it doesn''t
>     > >>>
>     > >>> mess
>     > >>>
>     > >>> > > > up everything ?
>     > >>> > >
>     > >>> > > Yes, if you can figure out which bits to
remove.  I
>     think there''s a
>     > >>>
>     > >>> "make
>     > >>>
>     > >>> > > uninstall" target in the source
distribution that should
>     do this
>     > >>> > > reasonably thoroughly for you;
it''s not included in the
>     binary
>     > >>> > > distribution you currently have :-(
>     > >>> > >
>     > >>> > > *however* in your case, you have
successfully installed
>     Xen and
>     > >>>
>     > >>> XenLinux
>     > >>>
>     > >>> > > by the sound of it and they''re
already booting - am I
>     reading you
>     > >>>
>     > >>> right?
>     > >>>
>     > >>> > > If you get the source distribution for the
same version
>     of Xen and
>     > >>>
>     > >>> then
>     > >>>
>     > >>> > > just
>     > >>> > > compile / install the userspace tools, that
should do.  You
>     > >>> > > probably don''t really need to
build Xen / XenLinux lot
>     again, or
>     > >>> > > even reboot
>     > >>>
>     > >>> for
>     > >>>
>     > >>> > > that matter.
>     > >>> > >
>     > >>> > > You might still need to remove the old
userspace
>     libraries to make
>     > >>>
>     > >>> Xend
>     > >>>
>     > >>> > > work
>     > >>> > > right.  make uninstall should take them
away but it
>     might remove
>     > >>> > > your
>     > >>>
>     > >>> Xen
>     > >>>
>     > >>> > > / XenLinux too...  I''d suggest you
manually look at what the
>     > >>> > > Makefile does to see which libraries /
binaries to
>     remove, then do
>     > >>> > > it
>     > >>>
>     > >>> yourself.
>     > >>>
>     > >>> > > Does that sound reasonably doable to you? 
Don''t use make
>     > >>> > > uninstall,
>     > >>>
>     > >>> just
>     > >>>
>     > >>> > > use it for inspiration when uninstalling
the userspace
>     tools.  Then
>     > >>>
>     > >>> run
>     > >>>
>     > >>> > > make tools-install to build and install a
new version of
>     the tools.
>     > >>> > >
>     > >>> > > You may need to install a few -dev packages
to build
>     successfully.
>     > >>> > >
>     > >>> > > Cheers,
>     > >>> > > Mark
>     > >>> > >
>     > >>> > > > On Thu, Jul 17, 2008 at 9:02 PM, Mark
Williamson <
>     > >>> > > >
>     > >>> > > > mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > >>> > > > > These errors typically happen
when the Xen code was
>     built
>     > >>> > > > > against
>     > >>>
>     > >>> a
>     > >>>
>     > >>> > > > > different
>     > >>> > > > > version of Python to the one
that''s available at
>     runtime.  I''ve
>     > >>> > >
>     > >>> > > actually
>     > >>> > >
>     > >>> > > > > found these are often harmless
but that''s probably
>     not an
>     > >>>
>     > >>> appropriate
>     > >>>
>     > >>> > > > > risk to
>     > >>> > > > > take for a production machine.
>     > >>> > > > >
>     > >>> > > > > Where exactly did you get your
install source for
>     Xen from?
>     > >>>
>     > >>>  Could
>     > >>>
>     > >>> > > > > you just build Xen yourself
rather than using a
>     pre-compiled
>     > >>>
>     > >>> version?
>     > >>>
>     > >>> > > > > Cheers,
>     > >>> > > > > Mark
>     > >>> > > > >
>     > >>> > > > > On Thursday 17 July 2008, Antoine
Benkemoun wrote:
>     > >>> > > > > > Hello,
>     > >>> > > > > >
>     > >>> > > > > > I am trying to install Xen
3.1.0 on a Debian Sid.
>     I have been
>     > >>>
>     > >>> able
>     > >>>
>     > >>> > > > > > to do this type of
installation correctly with it
>     working
>     > >>>
>     > >>> perfectly
>     > >>>
>     > >>> > > before
>     > >>> > >
>     > >>> > > > > > but
>     > >>> > > > >
>     > >>> > > > > I
>     > >>> > > > >
>     > >>> > > > > > have to admit I
can''t get this one to work.
>     > >>> > > > > >
>     > >>> > > > > > Here are the error messages
that I get at Xen
>     startup :
>     > >>> > > > > >
>     > >>> > > > > > orangene1-hyp:~#
/etc/init.d/xend start
>     > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>     > >>>
>     > >>> RuntimeWarning:
>     > >>> > > Python
>     > >>> > >
>     > >>> > > > > > C API version mismatch for
module xen.lowlevel.xc:
>     This
>     > >>> > > > > > Python
>     > >>>
>     > >>> has
>     > >>>
>     > >>> > > API
>     > >>> > >
>     > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
>     > >>> > > > > >   import xen.lowlevel.xc
>     > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
>     RuntimeWarning:
>     > >>> > > > > > Python
>     > >>>
>     > >>> C
>     > >>>
>     > >>> > > > > > API version mismatch for
module acm: This Python
>     has API
>     > >>>
>     > >>> version
>     > >>>
>     > >>> > > > > > 1013, module acm has version
1012.
>     > >>> > > > > >   from xen.lowlevel import
acm
>     > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>     > >>> > > > > > RuntimeWarning: Python
>     > >>> > >
>     > >>> > > C
>     > >>> > >
>     > >>> > > > > API
>     > >>> > > > >
>     > >>> > > > > > version mismatch for module
xen.lowlevel.xs: This
>     Python has
>     > >>>
>     > >>> API
>     > >>>
>     > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
>     > >>> > > > > >   import xen.lowlevel.xs
>     > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
>     > >>> > > > > > RuntimeWarning: Python
>     > >>> > >
>     > >>> > > C
>     > >>> > >
>     > >>> > > > > API
>     > >>> > > > >
>     > >>> > > > > > version mismatch for module
ptsname: This Python
>     has API
>     > >>>
>     > >>> version
>     > >>>
>     > >>> > > 1013,
>     > >>> > >
>     > >>> > > > > > module ptsname has version
1012.
>     > >>> > > > > >   from xen.lowlevel import
ptsname
>     > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>     > >>>
>     > >>> RuntimeWarning:
>     > >>> > > Python
>     > >>> > >
>     > >>> > > > > > C API version mismatch for
module xen.lowlevel.xc:
>     This
>     > >>> > > > > > Python
>     > >>>
>     > >>> has
>     > >>>
>     > >>> > > API
>     > >>> > >
>     > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
>     > >>> > > > > >   import xen.lowlevel.xc
>     > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
>     RuntimeWarning:
>     > >>> > > > > > Python
>     > >>>
>     > >>> C
>     > >>>
>     > >>> > > > > > API version mismatch for
module acm: This Python
>     has API
>     > >>>
>     > >>> version
>     > >>>
>     > >>> > > > > > 1013, module acm has version
1012.
>     > >>> > > > > >   from xen.lowlevel import
acm
>     > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>     > >>> > > > > > RuntimeWarning: Python
>     > >>> > >
>     > >>> > > C
>     > >>> > >
>     > >>> > > > > API
>     > >>> > > > >
>     > >>> > > > > > version mismatch for module
xen.lowlevel.xs: This
>     Python has
>     > >>>
>     > >>> API
>     > >>>
>     > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
>     > >>> > > > > >   import xen.lowlevel.xs
>     > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
>     > >>> > > > > > RuntimeWarning: Python
>     > >>> > >
>     > >>> > > C
>     > >>> > >
>     > >>> > > > > API
>     > >>> > > > >
>     > >>> > > > > > version mismatch for module
ptsname: This Python
>     has API
>     > >>>
>     > >>> version
>     > >>>
>     > >>> > > 1013,
>     > >>> > >
>     > >>> > > > > > module ptsname has version
1012.
>     > >>> > > > > >   from xen.lowlevel import
ptsname
>     > >>> > > > > >
>     > >>> > > > > > I have tried to install
python from Sid and Lenny
>     versions
>     > >>> > > > > > but
>     > >>>
>     > >>> none
>     > >>>
>     > >>> > > > > > seem
>     > >>> > > > >
>     > >>> > > > > to
>     > >>> > > > >
>     > >>> > > > > > change any of this... I have
no Python knowledge
>     at all so I
>     > >>>
>     > >>> would
>     > >>>
>     > >>> > > like
>     > >>> > >
>     > >>> > > > > to
>     > >>> > > > >
>     > >>> > > > > > know if anybody would happen
to have an idea
>     concerning this
>     > >>> > > > > > problem.
>     > >>> > > > > >
>     > >>> > > > > > I will be happy to give you
more info if there is
>     something
>     > >>>
>     > >>> missing
>     > >>>
>     > >>> > > in
>     > >>> > >
>     > >>> > > > > this
>     > >>> > > > >
>     > >>> > > > > > post.
>     > >>> > > > > >
>     > >>> > > > > > Thank you in advance for
your help,
>     > >>> > > > > >
>     > >>> > > > > > Antoine Benkemoun
>     > >>> > > > >
>     > >>> > > > > --
>     > >>> > > > > Push Me Pull You - Distributed
SCM tool (
>     > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7
>     > >>> > > > >Emaw48/pmpu/>
>     > >>>
>     > >>> <http://www.cl.cam.ac.uk/%7Emaw48
>     > >>>
>     > >>> > > > >/pmpu/>
>     > >>> > >
>     > >>> > > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>     > >>> > >
>     > >>> > > > >u/> )
>     > >>> > >
>     > >>> > > --
>     > >>> > > Push Me Pull You - Distributed SCM tool (
>     > >>> > > http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7Emaw
>     > >>> > >48/pmpu/>
>     > >>>
>     > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>     > >>>
>     > >>> > >u/> )
>     > >>>
>     > >>> --
>     > >>> Push Me Pull You - Distributed SCM tool (
>     > >>> http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7Emaw48/p
>     > >>>mpu/> )
>     > >>
>     > >> --
>     > >> Antoine Benkemoun
>     > >> Tel : 03.51.53.57.00
>     > >> Port : 06.32.88.59.35
>     > >
>     > > --
>     > > Antoine Benkemoun
>     > > Tel : 03.51.53.57.00
>     > > Port : 06.32.88.59.35
>
>
>
>     --
>     Push Me Pull You - Distributed SCM tool
>     (http://www.cl.cam.ac.uk/~maw48/pmpu/
>     <http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>)
>
>
>
>
> -- 
> Antoine Benkemoun
> Tel : 03.51.53.57.00
> Port : 06.32.88.59.35
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3276
(20080717) __________
>
> E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>
> http://www.eset.com
>   

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

Thank you for taking the time to re-explain everything.

You have understood my situation right.

I have applied your script. Gotten the sources. But make install-tools seems
to start correctly but fails since /etc/init.d/xend doesn''t appear and
errors appear.

Here is the detail :

orangene2-hyp:~/xen-3.1.0-src# make install-tools
make -C tools install
make[1]: Entering directory `/root/xen-3.1.0-src/tools''
make -C check
make[2]: Entering directory `/root/xen-3.1.0-src/tools/check''
XENFB_TOOLS=n ./chk build
Xen CHECK-BUILD  Fri Jul 18 09:07:51 CEST 2008
Checking check_crypto_lib: OK
Checking check_libvncserver: unused, OK
Checking check_openssl_devel: OK
Checking check_python: OK
Checking check_python_devel: OK
Checking check_sdl: unused, OK
Checking check_x11_devel: OK
Checking check_xgettext: OK
Checking check_zlib_devel: OK
Checking check_zlib_lib: OK
make[2]: Leaving directory `/root/xen-3.1.0-src/tools/check''
make[2]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
mkdir -p xen
( cd xen && ln -sf ../../../xen/include/public/*.h . )
mkdir -p xen/hvm
( cd xen/hvm && ln -sf ../../../../xen/include/public/hvm/*.h . )
mkdir -p xen/io
( cd xen/io && ln -sf ../../../../xen/include/public/io/*.h . )
mkdir -p xen/arch-x86
( cd xen/arch-x86 && ln -sf ../../../../xen/include/public/arch-x86/*.h
. )
mkdir -p xen/foreign
( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/Makefile .
)
( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/reference.size . )
( cd xen/foreign && ln -sf ../../../../xen/include/public/foreign/*.py .
)
make -C xen/foreign
make[3]: Entering directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
./checker > x86_32.size
diff -u reference.size x86_32.size
make[3]: Leaving directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
mkdir -p xen/linux
( cd xen/linux && \
          ln -sf ../../../../linux-2.6-xen-sparse/include/xen/public/*.h . )
( cd xen && rm -f sys && ln -sf linux sys )
make libxenctrl.a libxenctrl.so libxenctrl.so.3.0 libxenctrl.so.3.0.0
libxenguest.a libxenguest.so libxenguest.so.3.0 libxenguest.so.3.0.0
make[3]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
gcc  -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
-D_GNU_SOURCE -Werror -Wmissing-prototypes -fno-strict-aliasing  -I.
-I../xenstore -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c
cc1: warnings being treated as errors
xc_core.c: In function ''xc_core_shdr_get'':
xc_core.c:195: error: assuming signed overflow does not occur when assuming
that (X + c) < X is always false
make[3]: *** [xc_core.o] Error 1
make[3]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
make[2]: *** [build] Error 2
make[2]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
make[1]: *** [install] Error 2
make[1]: Leaving directory `/root/xen-3.1.0-src/tools''
make: *** [install-tools] Error 2

Antoine

On Thu, Jul 17, 2008 at 10:53 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > I have to admit I am a bit lost here. Concerning userspace tools, I
don''t
> > really know what you are talking about.
>
> OK, sorry, lets step back a bit.
>
> If you want your host to *boot* you need the Xen hypervisor (xen.gz) and
> XenLinux (vmlinuz-xen or somesuch) and an initrd.
>
> I understood from your previous e-mails that you''ve installed
these, set up
> menu.lst to boot them and successfully booted into them.  Is that right?
> This means you''ve got a running dom0.
>
> From this system, you''re then trying to run xend and it''s
giving loads of
> errors about Python C API mismatches.  I''m I correct so far?
>
> > Also, the command lines you have given me will remove Xen. After
that''s
> > done, do I just reinstall using the binaries or do I do something else
?
>
> A Xen-based system has three main components: the Xen hypervisor, the dom0
> Linux kernel and the userspace tools.  You seem to have the first two
> working
> OK, I think?
>
> The problem you''re seeing when starting Xend is strictly a
userspace tools
> issue.  xend is just a daemon that''s written in Python and C which
issues
> control hypercalls to Xen to tell it what to do.  To fix this issue you
> only
> need to fix these tools.
>
> The command lines I gave you will remove all the *userspace* parts of Xen
> but
> should (if I''ve editted them right) leave the Xen hypervisor and
the
> XenLinux
> kernel you''re using in place.  This should leave the machine still
bootable
> (assuming I''m correct in thinking you''ve successfully
booted Xen/XenLinux
> already).
>
> Using a source tree of the same version of Xen, "make
install-tools" should
> replace the stuff we just removed with a custom-built copy, allowing you to
> start Xend without errors.  That''s the plan.  You
shouldn''t even need to
> reboot.  You should still be able to do this on the box you didn''t
> reboot...
>
> > I am starting to think that this is going to be too complex to fix. I
> think
> > the big error that I made is trying to install it on a Lenny Sid. I
don''t
> > remember that ever working for me... I think just installing it on a
> Stable
> > Etch should do the trick without having to bother to spend hours
patching
> > this to achieve mediocre stability.
> >
> > Does anyone happen to have any feedback on install Xen on a Debian Sid
> > Lenny or Sid Etch ? I don''t recall that ever working on
previous
> occasions.
>
> I think that Etch, at least, has reasonably recent Xen packages.  How about
> just using the Debian-provided packages, at least to start with?  XenSource
> don''t guarantee to keep updating their kernels with security / bug
fixes so
> you might find that the Debian kernels are more up-to-date.
>
> Cheers,
> Mark
>
> > Antoine
> >
> > On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
> >
> > mark.williamson@cl.cam.ac.uk> wrote:
> > > On Thursday 17 July 2008, you wrote:
> > > > I just did make install-tools and it didn''t change
anything. I don''t
> > > > know if I was supposed to do something else for it to take
action.
> > >
> > > Bad luck with getting the free trip, I was hoping to avoid that
for
> you.
> > >
> > > :-(
> > >
> > > make install-tools should work, it''s only a userspace
problem you have.
> > >  Did
> > > you try to uninstall the existing userspace tools first as I
suggested?
> > > Reinstalling Xen / XenLinux will *definitely* not help with
Python <->
> C
> > > API
> > > problems.
> > >
> > > I went and poked in the Makefile for you and found that
"make
> uninstall"
> > > runs
> > > the following (I''ve removed the lines that delete the
hypervisor and
> the
> > > XenLinux kernel stuff, since you want to keep those).
> > >
> > > You should substitute appropriate values for the environment
variables.
> > >  $(D)
> > > should be set to the empty string, LIBDIR is probably /usr/lib. 
Please
> > > double check the following commands for sanity as you always
should
> > > before rm -rf.  Don''t trust me too much :-)
> > >
> > >        rm -rf $(D)/etc/init.d/xend*
> > >        rm -rf $(D)/etc/hotplug/xen-backend.agent
> > >        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
> > >        rm -f  $(D)/etc/udev/xen-backend.rules
> > >        rm -f  $(D)/etc/sysconfig/xendomains
> > >        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
> > >        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
> > >        rm -rf $(D)/usr/bin/cpuperf-perfcntr
$(D)/usr/bin/cpuperf-xen
> > >        rm -rf $(D)/usr/bin/xc_shadow
> > >        rm -rf $(D)/usr/bin/pygrub
> > >        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
> > >        rm -rf $(D)/usr/bin/xsls
> > >        rm -rf $(D)/usr/include/xenctrl.h
$(D)/usr/include/xenguest.h
> > >        rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
> > >        rm -rf $(D)/usr/include/xen
> > >        rm -rf $(D)$(LIBDIR)/libxenctrl*
$(D)$(LIBDIR)/libxenguest*
> > >        rm -rf $(D)$(LIBDIR)/libxenstore*
> > >        rm -rf $(D)$(LIBDIR)/python/xen $(D)$(LIBDIR)/python/grub
> > >        rm -rf $(D)$(LIBDIR)/xen/
> > >        rm -rf $(D)/usr/lib/xen/
> > >        rm -rf $(D)/usr/local/sbin/setmask
$(D)/usr/local/sbin/xen*
> > >        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix
$(D)/usr/sbin/xm
> > >        rm -rf $(D)/usr/share/doc/xen
> > >        rm -rf $(D)/usr/share/xen
> > >        rm -rf $(D)/usr/share/man/man1/xen*
> > >        rm -rf $(D)/usr/share/man/man8/xen*
> > >
> > > Cheers,
> > > Mark
> > >
> > > > Antoine
> > > >
> > > > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
> > > >
> > > > antoine.benkemoun@gmail.com> wrote:
> > > > > Critical failure... machine doesn''t boot
anymore. I win the free
> trip
> > > > > !
> > > > >
> > > > > I am trying to do just make install-tools on the second
machine
> just
> > > > > to see if it will change something.
> > > > >
> > > > > Antoine
> > > > >
> > > > >
> > > > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun
<
> > > > >
> > > > > antoine.benkemoun@gmail.com> wrote:
> > > > >> Ah sorry I didn''t read your email
correctly.
> > > > >>
> > > > >> I will do that afterwards might just as well finish
since it''s
> been
> > > > >> running for quite a while...
> > > > >>
> > > > >> Won''t be forgetting to do the initrd,
thank you for reminder.
> > > > >> Already got trapped previously but the PC was right
next to me so
> it
> > > > >> wasn''t so bad.
> > > > >>
> > > > >> Thanks !
> > > > >>
> > > > >> Antoine
> > > > >>
> > > > >>
> > > > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson
<
> > > > >>
> > > > >> mark.williamson@cl.cam.ac.uk> wrote:
> > > > >>> On Thursday 17 July 2008, Antoine Benkemoun
wrote:
> > > > >>> > Thank you for your thorough answer !
> > > > >>> >
> > > > >>> > Indeed I am booting Debian with the Xen
kernel perfectly. I
> don''t
> > > > >>> > know
> > > > >>>
> > > > >>> what
> > > > >>>
> > > > >>> > you mean by XenLinux but I''m
guessing it''s what I am booting or
> > > > >>>
> > > > >>> something
> > > > >>>
> > > > >>> > similar enough.
> > > > >>>
> > > > >>> Sorry.
> > > > >>>
> > > > >>> By XenLinux I mean the Xen-aware Linux
you''re booting on top of
> > > > >>> Xen.
> > > > >>>
> > > > >>> > I agree that since it is the same version
it shouldn''t mess
> > > > >>> > things
> > >
> > > up
> > >
> > > > >>> too
> > > > >>>
> > > > >>> > much. I am compiling at the moment using
the same tutorial (it
> > > > >>> > had
> > >
> > > a
> > >
> > > > >>> > compiling source page included).
It''s taking for ever even with
> a
> > > > >>> > Quad
> > > > >>>
> > > > >>> Core
> > > > >>>
> > > > >>> > Xen machine with 4GB of RAM...
> > > > >>>
> > > > >>> If you''re only installing the tools,
as I suggested, you only
> > >
> > > actually
> > >
> > > > >>> need to
> > > > >>> do make tools; make install-tools, which should
be much faster.
>  If
> > >
> > > you
> > >
> > > > >>> just
> > > > >>> do "make world" it''ll build
Xen and the XenLinux, which will take
> > >
> > > ages
> > >
> > > > >>> and
> > > > >>> you already have those.
> > > > >>>
> > > > >>> > I''ll keep you updated if this
works or if I get a free trip to
> > > > >>> > the datacentre :P
> > > > >>>
> > > > >>> I hope you don''t win that prize :-)
> > > > >>>
> > > > >>> Cheers,
> > > > >>> Mark
> > > > >>>
> > > > >>> > Antoine
> > > > >>> >
> > > > >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark
Williamson <
> > > > >>> >
> > > > >>> > mark.williamson@cl.cam.ac.uk> wrote:
> > > > >>> > > > Thank you for your quick answer.
> > > > >>> > > >
> > > > >>> > > > I installed the 3.1.0 binaries
on a Lenny Sid installed. I
> > > > >>> > > > followed
> > > > >>>
> > > > >>> the
> > > > >>>
> > > > >>> > > > "Perfect Xen 3.0
install" tutorial to the letter.
> > > > >>> > > >
> > > > >>> > > > I have the possibility to
install from sources but I am
> > >
> > > somewhat
> > >
> > > > >>> afraid
> > > > >>>
> > > > >>> > > to
> > > > >>> > >
> > > > >>> > > > do so... Can it crash the
machine if installed ontop a
> > > > >>> > > > previous
> > > > >>>
> > > > >>> install
> > > > >>>
> > > > >>> > > > ? Basically, the machine not
rebooting correctly wins me a
> > > > >>> > > > trip to
> > > > >>>
> > > > >>> the
> > > > >>>
> > > > >>> > > > datacentre and that''s
not fun :P
> > > > >>> > >
> > > > >>> > > Xen doesn''t play very well
with conflicting installs.  I
> guess
> > > > >>> > > if
> > > > >>>
> > > > >>> you''re
> > > > >>>
> > > > >>> > > installing the same version from
source that you''ve just
> > >
> > > installed
> > >
> > > > >>> > > in binaries it''s not so
likely to screw things up.  That
> said,
> > >
> > > most
> > >
> > > > >>> > > of
> > > > >>>
> > > > >>> the
> > > > >>>
> > > > >>> > > conflicts are typically in userspace
stuff, which shouldn''t
> > > > >>> > > stop the machine
> > > > >>> > > actually booting.  I''d also
not expect such conflicts to
> result
> > >
> > > in
> > >
> > > > >>> > > a crash at
> > > > >>> > > runtime, it just usually means Xend
doesn''t work properly.
> > > > >>> > >
> > > > >>> > > > Is it possible to uninstall a
previous Xen install so it
> > >
> > > doesn''t
> > >
> > > > >>> mess
> > > > >>>
> > > > >>> > > > up everything ?
> > > > >>> > >
> > > > >>> > > Yes, if you can figure out which bits
to remove.  I think
> > > > >>> > > there''s
> > >
> > > a
> > >
> > > > >>> "make
> > > > >>>
> > > > >>> > > uninstall" target in the source
distribution that should do
> > > > >>> > > this reasonably thoroughly for you;
it''s not included in the
> > > > >>> > > binary distribution you currently
have :-(
> > > > >>> > >
> > > > >>> > > *however* in your case, you have
successfully installed Xen
> and
> > > > >>>
> > > > >>> XenLinux
> > > > >>>
> > > > >>> > > by the sound of it and
they''re already booting - am I reading
> > > > >>> > > you
> > > > >>>
> > > > >>> right?
> > > > >>>
> > > > >>> > > If you get the source distribution
for the same version of
> Xen
> > >
> > > and
> > >
> > > > >>> then
> > > > >>>
> > > > >>> > > just
> > > > >>> > > compile / install the userspace
tools, that should do.  You
> > > > >>> > > probably don''t really need
to build Xen / XenLinux lot again,
> > > > >>> > > or even reboot
> > > > >>>
> > > > >>> for
> > > > >>>
> > > > >>> > > that matter.
> > > > >>> > >
> > > > >>> > > You might still need to remove the
old userspace libraries to
> > >
> > > make
> > >
> > > > >>> Xend
> > > > >>>
> > > > >>> > > work
> > > > >>> > > right.  make uninstall should take
them away but it might
> > > > >>> > > remove your
> > > > >>>
> > > > >>> Xen
> > > > >>>
> > > > >>> > > / XenLinux too...  I''d
suggest you manually look at what the
> > > > >>> > > Makefile does to see which libraries
/ binaries to remove,
> then
> > >
> > > do
> > >
> > > > >>> > > it
> > > > >>>
> > > > >>> yourself.
> > > > >>>
> > > > >>> > > Does that sound reasonably doable to
you?  Don''t use make
> > > > >>> > > uninstall,
> > > > >>>
> > > > >>> just
> > > > >>>
> > > > >>> > > use it for inspiration when
uninstalling the userspace tools.
> > >
> > >  Then
> > >
> > > > >>> run
> > > > >>>
> > > > >>> > > make tools-install to build and
install a new version of the
> > >
> > > tools.
> > >
> > > > >>> > > You may need to install a few -dev
packages to build
> > >
> > > successfully.
> > >
> > > > >>> > > Cheers,
> > > > >>> > > Mark
> > > > >>> > >
> > > > >>> > > > On Thu, Jul 17, 2008 at 9:02 PM,
Mark Williamson <
> > > > >>> > > >
> > > > >>> > > > mark.williamson@cl.cam.ac.uk>
wrote:
> > > > >>> > > > > These errors typically
happen when the Xen code was built
> > > > >>> > > > > against
> > > > >>>
> > > > >>> a
> > > > >>>
> > > > >>> > > > > different
> > > > >>> > > > > version of Python to the
one that''s available at runtime.
> > >
> > >  I''ve
> > >
> > > > >>> > > actually
> > > > >>> > >
> > > > >>> > > > > found these are often
harmless but that''s probably not an
> > > > >>>
> > > > >>> appropriate
> > > > >>>
> > > > >>> > > > > risk to
> > > > >>> > > > > take for a production
machine.
> > > > >>> > > > >
> > > > >>> > > > > Where exactly did you get
your install source for Xen
> from?
> > > > >>>
> > > > >>>  Could
> > > > >>>
> > > > >>> > > > > you just build Xen yourself
rather than using a
> > > > >>> > > > > pre-compiled
> > > > >>>
> > > > >>> version?
> > > > >>>
> > > > >>> > > > > Cheers,
> > > > >>> > > > > Mark
> > > > >>> > > > >
> > > > >>> > > > > On Thursday 17 July 2008,
Antoine Benkemoun wrote:
> > > > >>> > > > > > Hello,
> > > > >>> > > > > >
> > > > >>> > > > > > I am trying to install
Xen 3.1.0 on a Debian Sid. I
> have
> > >
> > > been
> > >
> > > > >>> able
> > > > >>>
> > > > >>> > > > > > to do this type of
installation correctly with it
> working
> > > > >>>
> > > > >>> perfectly
> > > > >>>
> > > > >>> > > before
> > > > >>> > >
> > > > >>> > > > > > but
> > > > >>> > > > >
> > > > >>> > > > > I
> > > > >>> > > > >
> > > > >>> > > > > > have to admit I
can''t get this one to work.
> > > > >>> > > > > >
> > > > >>> > > > > > Here are the error
messages that I get at Xen startup :
> > > > >>> > > > > >
> > > > >>> > > > > > orangene1-hyp:~#
/etc/init.d/xend start
> > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > > > >>>
> > > > >>> RuntimeWarning:
> > > > >>> > > Python
> > > > >>> > >
> > > > >>> > > > > > C API version mismatch
for module xen.lowlevel.xc: This
> > > > >>> > > > > > Python
> > > > >>>
> > > > >>> has
> > > > >>>
> > > > >>> > > API
> > > > >>> > >
> > > > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
> > > > >>> > > > > >   import
xen.lowlevel.xc
> > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
> RuntimeWarning:
> > > > >>> > > > > > Python
> > > > >>>
> > > > >>> C
> > > > >>>
> > > > >>> > > > > > API version mismatch
for module acm: This Python has
> API
> > > > >>>
> > > > >>> version
> > > > >>>
> > > > >>> > > > > > 1013, module acm has
version 1012.
> > > > >>> > > > > >   from xen.lowlevel
import acm
> > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > > > >>> > > > > > RuntimeWarning: Python
> > > > >>> > >
> > > > >>> > > C
> > > > >>> > >
> > > > >>> > > > > API
> > > > >>> > > > >
> > > > >>> > > > > > version mismatch for
module xen.lowlevel.xs: This
> Python
> > >
> > > has
> > >
> > > > >>> API
> > > > >>>
> > > > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
> > > > >>> > > > > >   import
xen.lowlevel.xs
> > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > > > >>> > > > > > RuntimeWarning: Python
> > > > >>> > >
> > > > >>> > > C
> > > > >>> > >
> > > > >>> > > > > API
> > > > >>> > > > >
> > > > >>> > > > > > version mismatch for
module ptsname: This Python has
> API
> > > > >>>
> > > > >>> version
> > > > >>>
> > > > >>> > > 1013,
> > > > >>> > >
> > > > >>> > > > > > module ptsname has
version 1012.
> > > > >>> > > > > >   from xen.lowlevel
import ptsname
> > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > > > >>>
> > > > >>> RuntimeWarning:
> > > > >>> > > Python
> > > > >>> > >
> > > > >>> > > > > > C API version mismatch
for module xen.lowlevel.xc: This
> > > > >>> > > > > > Python
> > > > >>>
> > > > >>> has
> > > > >>>
> > > > >>> > > API
> > > > >>> > >
> > > > >>> > > > > > version 1013, module
xen.lowlevel.xc has version 1012.
> > > > >>> > > > > >   import
xen.lowlevel.xc
> > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
> RuntimeWarning:
> > > > >>> > > > > > Python
> > > > >>>
> > > > >>> C
> > > > >>>
> > > > >>> > > > > > API version mismatch
for module acm: This Python has
> API
> > > > >>>
> > > > >>> version
> > > > >>>
> > > > >>> > > > > > 1013, module acm has
version 1012.
> > > > >>> > > > > >   from xen.lowlevel
import acm
> > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > > > >>> > > > > > RuntimeWarning: Python
> > > > >>> > >
> > > > >>> > > C
> > > > >>> > >
> > > > >>> > > > > API
> > > > >>> > > > >
> > > > >>> > > > > > version mismatch for
module xen.lowlevel.xs: This
> Python
> > >
> > > has
> > >
> > > > >>> API
> > > > >>>
> > > > >>> > > > > > version 1013, module
xen.lowlevel.xs has version 1012.
> > > > >>> > > > > >   import
xen.lowlevel.xs
> > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > > > >>> > > > > > RuntimeWarning: Python
> > > > >>> > >
> > > > >>> > > C
> > > > >>> > >
> > > > >>> > > > > API
> > > > >>> > > > >
> > > > >>> > > > > > version mismatch for
module ptsname: This Python has
> API
> > > > >>>
> > > > >>> version
> > > > >>>
> > > > >>> > > 1013,
> > > > >>> > >
> > > > >>> > > > > > module ptsname has
version 1012.
> > > > >>> > > > > >   from xen.lowlevel
import ptsname
> > > > >>> > > > > >
> > > > >>> > > > > > I have tried to
install python from Sid and Lenny
> > > > >>> > > > > > versions but
> > > > >>>
> > > > >>> none
> > > > >>>
> > > > >>> > > > > > seem
> > > > >>> > > > >
> > > > >>> > > > > to
> > > > >>> > > > >
> > > > >>> > > > > > change any of this...
I have no Python knowledge at all
> > > > >>> > > > > > so
> > >
> > > I
> > >
> > > > >>> would
> > > > >>>
> > > > >>> > > like
> > > > >>> > >
> > > > >>> > > > > to
> > > > >>> > > > >
> > > > >>> > > > > > know if anybody would
happen to have an idea concerning
> > >
> > > this
> > >
> > > > >>> > > > > > problem.
> > > > >>> > > > > >
> > > > >>> > > > > > I will be happy to
give you more info if there is
> > > > >>> > > > > > something
> > > > >>>
> > > > >>> missing
> > > > >>>
> > > > >>> > > in
> > > > >>> > >
> > > > >>> > > > > this
> > > > >>> > > > >
> > > > >>> > > > > > post.
> > > > >>> > > > > >
> > > > >>> > > > > > Thank you in advance
for your help,
> > > > >>> > > > > >
> > > > >>> > > > > > Antoine Benkemoun
> > > > >>> > > > >
> > > > >>> > > > > --
> > > > >>> > > > > Push Me Pull You -
Distributed SCM tool (
> > > > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.u
> > > > >>> > > > >k/%7Emaw48/pmpu/>
> > >
> > > <http://www.cl.cam.ac.uk/%7
> > >
> > > > >>> > > > >Emaw48/pmpu/>
> > > > >>>
> > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48
> > > > >>>
> > > > >>> > > > >/pmpu/>
> > > > >>> > >
> > > > >>> > >
<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > > > >>> > >
> > > > >>> > > > >u/> )
> > > > >>> > >
> > > > >>> > > --
> > > > >>> > > Push Me Pull You - Distributed SCM
tool (
> > > > >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7
> > > > >>> > >Emaw48/pmpu/>
> > >
> > > <http://www.cl.cam.ac.uk/%7Emaw
> > >
> > > > >>> > >48/pmpu/>
> > > > >>>
> > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > > > >>>
> > > > >>> > >u/> )
> > > > >>>
> > > > >>> --
> > > > >>> Push Me Pull You - Distributed SCM tool (
> > > > >>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw
> > > > >>>48/pmpu/>
> > >
> > > <http://www.cl.cam.ac.uk/%7Emaw48/p
> > >
> > > > >>>mpu/> )
> > > > >>
> > > > >> --
> > > > >> Antoine Benkemoun
> > > > >> Tel : 03.51.53.57.00
> > > > >> Port : 06.32.88.59.35
> > > > >
> > > > > --
> > > > > Antoine Benkemoun
> > > > > Tel : 03.51.53.57.00
> > > > > Port : 06.32.88.59.35
> > >
> > > --
> > > Push Me Pull You - Distributed SCM tool (
> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > >u/> )
>
>
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>


-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

may this perhaps be a bug?
I found this:
http://markmail.org/message/mujwmt5tstg34mh6

I''m not familiar with overflow checks.
But you might try this out, I think you''ve nothing to lose ;-)
Backup your xc_core.c before editing.

Hope this helps...

Cheers,
Alex


Antoine Benkemoun schrieb:
> Thank you for taking the time to re-explain everything.
>
> You have understood my situation right.
>
> I have applied your script. Gotten the sources. But make install-tools 
> seems to start correctly but fails since /etc/init.d/xend doesn''t 
> appear and errors appear.
>
> Here is the detail :
>
> orangene2-hyp:~/xen-3.1.0-src# make install-tools
> make -C tools install
> make[1]: Entering directory `/root/xen-3.1.0-src/tools''
> make -C check
> make[2]: Entering directory `/root/xen-3.1.0-src/tools/check''
> XENFB_TOOLS=n ./chk build
> Xen CHECK-BUILD  Fri Jul 18 09:07:51 CEST 2008
> Checking check_crypto_lib: OK
> Checking check_libvncserver: unused, OK
> Checking check_openssl_devel: OK
> Checking check_python: OK
> Checking check_python_devel: OK
> Checking check_sdl: unused, OK
> Checking check_x11_devel: OK
> Checking check_xgettext: OK
> Checking check_zlib_devel: OK
> Checking check_zlib_lib: OK
> make[2]: Leaving directory `/root/xen-3.1.0-src/tools/check''
> make[2]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
> mkdir -p xen
> ( cd xen && ln -sf ../../../xen/include/public/*.h . )
> mkdir -p xen/hvm
> ( cd xen/hvm && ln -sf ../../../../xen/include/public/hvm/*.h . )
> mkdir -p xen/io
> ( cd xen/io && ln -sf ../../../../xen/include/public/io/*.h . )
> mkdir -p xen/arch-x86
> ( cd xen/arch-x86 && ln -sf 
> ../../../../xen/include/public/arch-x86/*.h . )
> mkdir -p xen/foreign
> ( cd xen/foreign && ln -sf 
> ../../../../xen/include/public/foreign/Makefile . )
> ( cd xen/foreign && ln -sf 
> ../../../../xen/include/public/foreign/reference.size . )
> ( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/*.py . )
> make -C xen/foreign
> make[3]: Entering directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
> ./checker > x86_32.size
> diff -u reference.size x86_32.size
> make[3]: Leaving directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
> mkdir -p xen/linux
> ( cd xen/linux && \
>           ln -sf 
> ../../../../linux-2.6-xen-sparse/include/xen/public/*.h . )
> ( cd xen && rm -f sys && ln -sf linux sys )
> make libxenctrl.a libxenctrl.so libxenctrl.so.3.0 libxenctrl.so.3.0.0 
> libxenguest.a libxenguest.so libxenguest.so.3.0 libxenguest.so.3.0.0
> make[3]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
> gcc  -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99 
> -Wall -Wstrict-prototypes -Wno-unused-value 
> -Wdeclaration-after-statement  -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
> -mno-tls-direct-seg-refs -D_GNU_SOURCE -Werror -Wmissing-prototypes 
> -fno-strict-aliasing  -I. -I../xenstore -Wp,-MD,.xc_core.o.d -c -o 
> xc_core.o xc_core.c
> cc1: warnings being treated as errors
> xc_core.c: In function ''xc_core_shdr_get'':
> xc_core.c:195: error: assuming signed overflow does not occur when 
> assuming that (X + c) < X is always false
> make[3]: *** [xc_core.o] Error 1
> make[3]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
> make[2]: *** [build] Error 2
> make[2]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
> make[1]: *** [install] Error 2
> make[1]: Leaving directory `/root/xen-3.1.0-src/tools''
> make: *** [install-tools] Error 2
>
> Antoine
>
> On Thu, Jul 17, 2008 at 10:53 PM, Mark Williamson 
> <mark.williamson@cl.cam.ac.uk
<mailto:mark.williamson@cl.cam.ac.uk>>
> wrote:
>
>     On Thursday 17 July 2008, Antoine Benkemoun wrote:
>     > I have to admit I am a bit lost here. Concerning userspace
>     tools, I don''t
>     > really know what you are talking about.
>
>     OK, sorry, lets step back a bit.
>
>     If you want your host to *boot* you need the Xen hypervisor
>     (xen.gz) and
>     XenLinux (vmlinuz-xen or somesuch) and an initrd.
>
>     I understood from your previous e-mails that you''ve installed
>     these, set up
>     menu.lst to boot them and successfully booted into them.  Is that
>     right?
>     This means you''ve got a running dom0.
>
>     >From this system, you''re then trying to run xend and
it''s giving
>     loads of
>     errors about Python C API mismatches.  I''m I correct so far?
>
>     > Also, the command lines you have given me will remove Xen. After
>     that''s
>     > done, do I just reinstall using the binaries or do I do
>     something else ?
>
>     A Xen-based system has three main components: the Xen hypervisor,
>     the dom0
>     Linux kernel and the userspace tools.  You seem to have the first
>     two working
>     OK, I think?
>
>     The problem you''re seeing when starting Xend is strictly a
>     userspace tools
>     issue.  xend is just a daemon that''s written in Python and C
which
>     issues
>     control hypercalls to Xen to tell it what to do.  To fix this
>     issue you only
>     need to fix these tools.
>
>     The command lines I gave you will remove all the *userspace* parts
>     of Xen but
>     should (if I''ve editted them right) leave the Xen hypervisor
and
>     the XenLinux
>     kernel you''re using in place.  This should leave the machine
still
>     bootable
>     (assuming I''m correct in thinking you''ve successfully
booted
>     Xen/XenLinux
>     already).
>
>     Using a source tree of the same version of Xen, "make
>     install-tools" should
>     replace the stuff we just removed with a custom-built copy,
>     allowing you to
>     start Xend without errors.  That''s the plan.  You
shouldn''t even
>     need to
>     reboot.  You should still be able to do this on the box you
didn''t
>     reboot...
>
>     > I am starting to think that this is going to be too complex to
>     fix. I think
>     > the big error that I made is trying to install it on a Lenny
>     Sid. I don''t
>     > remember that ever working for me... I think just installing it
>     on a Stable
>     > Etch should do the trick without having to bother to spend hours
>     patching
>     > this to achieve mediocre stability.
>     >
>     > Does anyone happen to have any feedback on install Xen on a
>     Debian Sid
>     > Lenny or Sid Etch ? I don''t recall that ever working on
previous
>     occasions.
>
>     I think that Etch, at least, has reasonably recent Xen packages.
>      How about
>     just using the Debian-provided packages, at least to start with?
>      XenSource
>     don''t guarantee to keep updating their kernels with security /
bug
>     fixes so
>     you might find that the Debian kernels are more up-to-date.
>
>     Cheers,
>     Mark
>
>     > Antoine
>     >
>     > On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
>     >
>     > mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > > On Thursday 17 July 2008, you wrote:
>     > > > I just did make install-tools and it didn''t
change anything.
>     I don''t
>     > > > know if I was supposed to do something else for it to
take
>     action.
>     > >
>     > > Bad luck with getting the free trip, I was hoping to avoid
>     that for you.
>     > >
>     > > :-(
>     > >
>     > > make install-tools should work, it''s only a
userspace problem
>     you have.
>     > >  Did
>     > > you try to uninstall the existing userspace tools first as I
>     suggested?
>     > > Reinstalling Xen / XenLinux will *definitely* not help with
>     Python <-> C
>     > > API
>     > > problems.
>     > >
>     > > I went and poked in the Makefile for you and found that
"make
>     uninstall"
>     > > runs
>     > > the following (I''ve removed the lines that delete
the
>     hypervisor and the
>     > > XenLinux kernel stuff, since you want to keep those).
>     > >
>     > > You should substitute appropriate values for the environment
>     variables.
>     > >  $(D)
>     > > should be set to the empty string, LIBDIR is probably
>     /usr/lib.  Please
>     > > double check the following commands for sanity as you always
>     should
>     > > before rm -rf.  Don''t trust me too much :-)
>     > >
>     > >        rm -rf $(D)/etc/init.d/xend*
>     > >        rm -rf $(D)/etc/hotplug/xen-backend.agent
>     > >        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
>     > >        rm -f  $(D)/etc/udev/xen-backend.rules
>     > >        rm -f  $(D)/etc/sysconfig/xendomains
>     > >        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
>     > >        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
>     > >        rm -rf $(D)/usr/bin/cpuperf-perfcntr
>     $(D)/usr/bin/cpuperf-xen
>     > >        rm -rf $(D)/usr/bin/xc_shadow
>     > >        rm -rf $(D)/usr/bin/pygrub
>     > >        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
>     > >        rm -rf $(D)/usr/bin/xsls
>     > >        rm -rf $(D)/usr/include/xenctrl.h
>     $(D)/usr/include/xenguest.h
>     > >        rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
>     > >        rm -rf $(D)/usr/include/xen
>     > >        rm -rf $(D)$(LIBDIR)/libxenctrl*
$(D)$(LIBDIR)/libxenguest*
>     > >        rm -rf $(D)$(LIBDIR)/libxenstore*
>     > >        rm -rf $(D)$(LIBDIR)/python/xen
$(D)$(LIBDIR)/python/grub
>     > >        rm -rf $(D)$(LIBDIR)/xen/
>     > >        rm -rf $(D)/usr/lib/xen/
>     > >        rm -rf $(D)/usr/local/sbin/setmask
$(D)/usr/local/sbin/xen*
>     > >        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix
>     $(D)/usr/sbin/xm
>     > >        rm -rf $(D)/usr/share/doc/xen
>     > >        rm -rf $(D)/usr/share/xen
>     > >        rm -rf $(D)/usr/share/man/man1/xen*
>     > >        rm -rf $(D)/usr/share/man/man8/xen*
>     > >
>     > > Cheers,
>     > > Mark
>     > >
>     > > > Antoine
>     > > >
>     > > > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
>     > > >
>     > > > antoine.benkemoun@gmail.com
>     <mailto:antoine.benkemoun@gmail.com>> wrote:
>     > > > > Critical failure... machine doesn''t boot
anymore. I win
>     the free trip
>     > > > > !
>     > > > >
>     > > > > I am trying to do just make install-tools on the
second
>     machine just
>     > > > > to see if it will change something.
>     > > > >
>     > > > > Antoine
>     > > > >
>     > > > >
>     > > > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun
<
>     > > > >
>     > > > > antoine.benkemoun@gmail.com
>     <mailto:antoine.benkemoun@gmail.com>> wrote:
>     > > > >> Ah sorry I didn''t read your email
correctly.
>     > > > >>
>     > > > >> I will do that afterwards might just as well
finish since
>     it''s been
>     > > > >> running for quite a while...
>     > > > >>
>     > > > >> Won''t be forgetting to do the initrd,
thank you for reminder.
>     > > > >> Already got trapped previously but the PC was
right next
>     to me so it
>     > > > >> wasn''t so bad.
>     > > > >>
>     > > > >> Thanks !
>     > > > >>
>     > > > >> Antoine
>     > > > >>
>     > > > >>
>     > > > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark
Williamson <
>     > > > >>
>     > > > >> mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > > > >>> On Thursday 17 July 2008, Antoine Benkemoun
wrote:
>     > > > >>> > Thank you for your thorough answer !
>     > > > >>> >
>     > > > >>> > Indeed I am booting Debian with the
Xen kernel
>     perfectly. I don''t
>     > > > >>> > know
>     > > > >>>
>     > > > >>> what
>     > > > >>>
>     > > > >>> > you mean by XenLinux but I''m
guessing it''s what I am
>     booting or
>     > > > >>>
>     > > > >>> something
>     > > > >>>
>     > > > >>> > similar enough.
>     > > > >>>
>     > > > >>> Sorry.
>     > > > >>>
>     > > > >>> By XenLinux I mean the Xen-aware Linux
you''re booting on
>     top of
>     > > > >>> Xen.
>     > > > >>>
>     > > > >>> > I agree that since it is the same
version it shouldn''t
>     mess
>     > > > >>> > things
>     > >
>     > > up
>     > >
>     > > > >>> too
>     > > > >>>
>     > > > >>> > much. I am compiling at the moment
using the same
>     tutorial (it
>     > > > >>> > had
>     > >
>     > > a
>     > >
>     > > > >>> > compiling source page included).
It''s taking for ever
>     even with a
>     > > > >>> > Quad
>     > > > >>>
>     > > > >>> Core
>     > > > >>>
>     > > > >>> > Xen machine with 4GB of RAM...
>     > > > >>>
>     > > > >>> If you''re only installing the
tools, as I suggested, you
>     only
>     > >
>     > > actually
>     > >
>     > > > >>> need to
>     > > > >>> do make tools; make install-tools, which
should be much
>     faster.  If
>     > >
>     > > you
>     > >
>     > > > >>> just
>     > > > >>> do "make world" it''ll
build Xen and the XenLinux, which
>     will take
>     > >
>     > > ages
>     > >
>     > > > >>> and
>     > > > >>> you already have those.
>     > > > >>>
>     > > > >>> > I''ll keep you updated if this
works or if I get a free
>     trip to
>     > > > >>> > the datacentre :P
>     > > > >>>
>     > > > >>> I hope you don''t win that prize
:-)
>     > > > >>>
>     > > > >>> Cheers,
>     > > > >>> Mark
>     > > > >>>
>     > > > >>> > Antoine
>     > > > >>> >
>     > > > >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark
Williamson <
>     > > > >>> >
>     > > > >>> > mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > > > >>> > > > Thank you for your quick
answer.
>     > > > >>> > > >
>     > > > >>> > > > I installed the 3.1.0
binaries on a Lenny Sid
>     installed. I
>     > > > >>> > > > followed
>     > > > >>>
>     > > > >>> the
>     > > > >>>
>     > > > >>> > > > "Perfect Xen 3.0
install" tutorial to the letter.
>     > > > >>> > > >
>     > > > >>> > > > I have the possibility to
install from sources but
>     I am
>     > >
>     > > somewhat
>     > >
>     > > > >>> afraid
>     > > > >>>
>     > > > >>> > > to
>     > > > >>> > >
>     > > > >>> > > > do so... Can it crash the
machine if installed ontop a
>     > > > >>> > > > previous
>     > > > >>>
>     > > > >>> install
>     > > > >>>
>     > > > >>> > > > ? Basically, the machine not
rebooting correctly
>     wins me a
>     > > > >>> > > > trip to
>     > > > >>>
>     > > > >>> the
>     > > > >>>
>     > > > >>> > > > datacentre and
that''s not fun :P
>     > > > >>> > >
>     > > > >>> > > Xen doesn''t play very
well with conflicting
>     installs.  I guess
>     > > > >>> > > if
>     > > > >>>
>     > > > >>> you''re
>     > > > >>>
>     > > > >>> > > installing the same version from
source that you''ve just
>     > >
>     > > installed
>     > >
>     > > > >>> > > in binaries it''s not so
likely to screw things up.
>      That said,
>     > >
>     > > most
>     > >
>     > > > >>> > > of
>     > > > >>>
>     > > > >>> the
>     > > > >>>
>     > > > >>> > > conflicts are typically in
userspace stuff, which
>     shouldn''t
>     > > > >>> > > stop the machine
>     > > > >>> > > actually booting.  I''d
also not expect such
>     conflicts to result
>     > >
>     > > in
>     > >
>     > > > >>> > > a crash at
>     > > > >>> > > runtime, it just usually means
Xend doesn''t work
>     properly.
>     > > > >>> > >
>     > > > >>> > > > Is it possible to uninstall
a previous Xen install
>     so it
>     > >
>     > > doesn''t
>     > >
>     > > > >>> mess
>     > > > >>>
>     > > > >>> > > > up everything ?
>     > > > >>> > >
>     > > > >>> > > Yes, if you can figure out which
bits to remove.  I
>     think
>     > > > >>> > > there''s
>     > >
>     > > a
>     > >
>     > > > >>> "make
>     > > > >>>
>     > > > >>> > > uninstall" target in the
source distribution that
>     should do
>     > > > >>> > > this reasonably thoroughly for
you; it''s not
>     included in the
>     > > > >>> > > binary distribution you currently
have :-(
>     > > > >>> > >
>     > > > >>> > > *however* in your case, you have
successfully
>     installed Xen and
>     > > > >>>
>     > > > >>> XenLinux
>     > > > >>>
>     > > > >>> > > by the sound of it and
they''re already booting - am
>     I reading
>     > > > >>> > > you
>     > > > >>>
>     > > > >>> right?
>     > > > >>>
>     > > > >>> > > If you get the source
distribution for the same
>     version of Xen
>     > >
>     > > and
>     > >
>     > > > >>> then
>     > > > >>>
>     > > > >>> > > just
>     > > > >>> > > compile / install the userspace
tools, that should
>     do.  You
>     > > > >>> > > probably don''t really
need to build Xen / XenLinux
>     lot again,
>     > > > >>> > > or even reboot
>     > > > >>>
>     > > > >>> for
>     > > > >>>
>     > > > >>> > > that matter.
>     > > > >>> > >
>     > > > >>> > > You might still need to remove
the old userspace
>     libraries to
>     > >
>     > > make
>     > >
>     > > > >>> Xend
>     > > > >>>
>     > > > >>> > > work
>     > > > >>> > > right.  make uninstall should
take them away but it
>     might
>     > > > >>> > > remove your
>     > > > >>>
>     > > > >>> Xen
>     > > > >>>
>     > > > >>> > > / XenLinux too...  I''d
suggest you manually look at
>     what the
>     > > > >>> > > Makefile does to see which
libraries / binaries to
>     remove, then
>     > >
>     > > do
>     > >
>     > > > >>> > > it
>     > > > >>>
>     > > > >>> yourself.
>     > > > >>>
>     > > > >>> > > Does that sound reasonably doable
to you?  Don''t use
>     make
>     > > > >>> > > uninstall,
>     > > > >>>
>     > > > >>> just
>     > > > >>>
>     > > > >>> > > use it for inspiration when
uninstalling the
>     userspace tools.
>     > >
>     > >  Then
>     > >
>     > > > >>> run
>     > > > >>>
>     > > > >>> > > make tools-install to build and
install a new
>     version of the
>     > >
>     > > tools.
>     > >
>     > > > >>> > > You may need to install a few
-dev packages to build
>     > >
>     > > successfully.
>     > >
>     > > > >>> > > Cheers,
>     > > > >>> > > Mark
>     > > > >>> > >
>     > > > >>> > > > On Thu, Jul 17, 2008 at 9:02
PM, Mark Williamson <
>     > > > >>> > > >
>     > > > >>> > > > mark.williamson@cl.cam.ac.uk
>     <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>     > > > >>> > > > > These errors typically
happen when the Xen code
>     was built
>     > > > >>> > > > > against
>     > > > >>>
>     > > > >>> a
>     > > > >>>
>     > > > >>> > > > > different
>     > > > >>> > > > > version of Python to
the one that''s available at
>     runtime.
>     > >
>     > >  I''ve
>     > >
>     > > > >>> > > actually
>     > > > >>> > >
>     > > > >>> > > > > found these are often
harmless but that''s
>     probably not an
>     > > > >>>
>     > > > >>> appropriate
>     > > > >>>
>     > > > >>> > > > > risk to
>     > > > >>> > > > > take for a production
machine.
>     > > > >>> > > > >
>     > > > >>> > > > > Where exactly did you
get your install source
>     for Xen from?
>     > > > >>>
>     > > > >>>  Could
>     > > > >>>
>     > > > >>> > > > > you just build Xen
yourself rather than using a
>     > > > >>> > > > > pre-compiled
>     > > > >>>
>     > > > >>> version?
>     > > > >>>
>     > > > >>> > > > > Cheers,
>     > > > >>> > > > > Mark
>     > > > >>> > > > >
>     > > > >>> > > > > On Thursday 17 July
2008, Antoine Benkemoun wrote:
>     > > > >>> > > > > > Hello,
>     > > > >>> > > > > >
>     > > > >>> > > > > > I am trying to
install Xen 3.1.0 on a Debian
>     Sid. I have
>     > >
>     > > been
>     > >
>     > > > >>> able
>     > > > >>>
>     > > > >>> > > > > > to do this type of
installation correctly with
>     it working
>     > > > >>>
>     > > > >>> perfectly
>     > > > >>>
>     > > > >>> > > before
>     > > > >>> > >
>     > > > >>> > > > > > but
>     > > > >>> > > > >
>     > > > >>> > > > > I
>     > > > >>> > > > >
>     > > > >>> > > > > > have to admit I
can''t get this one to work.
>     > > > >>> > > > > >
>     > > > >>> > > > > > Here are the error
messages that I get at Xen
>     startup :
>     > > > >>> > > > > >
>     > > > >>> > > > > > orangene1-hyp:~#
/etc/init.d/xend start
>     > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>     > > > >>>
>     > > > >>> RuntimeWarning:
>     > > > >>> > > Python
>     > > > >>> > >
>     > > > >>> > > > > > C API version
mismatch for module
>     xen.lowlevel.xc: This
>     > > > >>> > > > > > Python
>     > > > >>>
>     > > > >>> has
>     > > > >>>
>     > > > >>> > > API
>     > > > >>> > >
>     > > > >>> > > > > > version 1013,
module xen.lowlevel.xc has
>     version 1012.
>     > > > >>> > > > > >   import
xen.lowlevel.xc
>     > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
>     RuntimeWarning:
>     > > > >>> > > > > > Python
>     > > > >>>
>     > > > >>> C
>     > > > >>>
>     > > > >>> > > > > > API version
mismatch for module acm: This
>     Python has API
>     > > > >>>
>     > > > >>> version
>     > > > >>>
>     > > > >>> > > > > > 1013, module acm
has version 1012.
>     > > > >>> > > > > >   from
xen.lowlevel import acm
>     > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>     > > > >>> > > > > > RuntimeWarning:
Python
>     > > > >>> > >
>     > > > >>> > > C
>     > > > >>> > >
>     > > > >>> > > > > API
>     > > > >>> > > > >
>     > > > >>> > > > > > version mismatch
for module xen.lowlevel.xs:
>     This Python
>     > >
>     > > has
>     > >
>     > > > >>> API
>     > > > >>>
>     > > > >>> > > > > > version 1013,
module xen.lowlevel.xs has
>     version 1012.
>     > > > >>> > > > > >   import
xen.lowlevel.xs
>     > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
>     > > > >>> > > > > > RuntimeWarning:
Python
>     > > > >>> > >
>     > > > >>> > > C
>     > > > >>> > >
>     > > > >>> > > > > API
>     > > > >>> > > > >
>     > > > >>> > > > > > version mismatch
for module ptsname: This
>     Python has API
>     > > > >>>
>     > > > >>> version
>     > > > >>>
>     > > > >>> > > 1013,
>     > > > >>> > >
>     > > > >>> > > > > > module ptsname has
version 1012.
>     > > > >>> > > > > >   from
xen.lowlevel import ptsname
>     > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>     > > > >>>
>     > > > >>> RuntimeWarning:
>     > > > >>> > > Python
>     > > > >>> > >
>     > > > >>> > > > > > C API version
mismatch for module
>     xen.lowlevel.xc: This
>     > > > >>> > > > > > Python
>     > > > >>>
>     > > > >>> has
>     > > > >>>
>     > > > >>> > > API
>     > > > >>> > >
>     > > > >>> > > > > > version 1013,
module xen.lowlevel.xc has
>     version 1012.
>     > > > >>> > > > > >   import
xen.lowlevel.xc
>     > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
>     RuntimeWarning:
>     > > > >>> > > > > > Python
>     > > > >>>
>     > > > >>> C
>     > > > >>>
>     > > > >>> > > > > > API version
mismatch for module acm: This
>     Python has API
>     > > > >>>
>     > > > >>> version
>     > > > >>>
>     > > > >>> > > > > > 1013, module acm
has version 1012.
>     > > > >>> > > > > >   from
xen.lowlevel import acm
>     > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>     > > > >>> > > > > > RuntimeWarning:
Python
>     > > > >>> > >
>     > > > >>> > > C
>     > > > >>> > >
>     > > > >>> > > > > API
>     > > > >>> > > > >
>     > > > >>> > > > > > version mismatch
for module xen.lowlevel.xs:
>     This Python
>     > >
>     > > has
>     > >
>     > > > >>> API
>     > > > >>>
>     > > > >>> > > > > > version 1013,
module xen.lowlevel.xs has
>     version 1012.
>     > > > >>> > > > > >   import
xen.lowlevel.xs
>     > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
>     > > > >>> > > > > > RuntimeWarning:
Python
>     > > > >>> > >
>     > > > >>> > > C
>     > > > >>> > >
>     > > > >>> > > > > API
>     > > > >>> > > > >
>     > > > >>> > > > > > version mismatch
for module ptsname: This
>     Python has API
>     > > > >>>
>     > > > >>> version
>     > > > >>>
>     > > > >>> > > 1013,
>     > > > >>> > >
>     > > > >>> > > > > > module ptsname has
version 1012.
>     > > > >>> > > > > >   from
xen.lowlevel import ptsname
>     > > > >>> > > > > >
>     > > > >>> > > > > > I have tried to
install python from Sid and Lenny
>     > > > >>> > > > > > versions but
>     > > > >>>
>     > > > >>> none
>     > > > >>>
>     > > > >>> > > > > > seem
>     > > > >>> > > > >
>     > > > >>> > > > > to
>     > > > >>> > > > >
>     > > > >>> > > > > > change any of
this... I have no Python
>     knowledge at all
>     > > > >>> > > > > > so
>     > >
>     > > I
>     > >
>     > > > >>> would
>     > > > >>>
>     > > > >>> > > like
>     > > > >>> > >
>     > > > >>> > > > > to
>     > > > >>> > > > >
>     > > > >>> > > > > > know if anybody
would happen to have an idea
>     concerning
>     > >
>     > > this
>     > >
>     > > > >>> > > > > > problem.
>     > > > >>> > > > > >
>     > > > >>> > > > > > I will be happy to
give you more info if there is
>     > > > >>> > > > > > something
>     > > > >>>
>     > > > >>> missing
>     > > > >>>
>     > > > >>> > > in
>     > > > >>> > >
>     > > > >>> > > > > this
>     > > > >>> > > > >
>     > > > >>> > > > > > post.
>     > > > >>> > > > > >
>     > > > >>> > > > > > Thank you in
advance for your help,
>     > > > >>> > > > > >
>     > > > >>> > > > > > Antoine Benkemoun
>     > > > >>> > > > >
>     > > > >>> > > > > --
>     > > > >>> > > > > Push Me Pull You -
Distributed SCM tool (
>     > > > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.u
>     > > > >>> > > > >k/%7Emaw48/pmpu/>
>     > >
>     > > <http://www.cl.cam.ac.uk/%7
>     > >
>     > > > >>> > > > >Emaw48/pmpu/>
>     > > > >>>
>     > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48
>     > > > >>>
>     > > > >>> > > > >/pmpu/>
>     > > > >>> > >
>     > > > >>> > >
<http://www.cl.cam.ac.uk/%7Emaw48/pmp
>     > > > >>> > >
>     > > > >>> > > > >u/> )
>     > > > >>> > >
>     > > > >>> > > --
>     > > > >>> > > Push Me Pull You - Distributed
SCM tool (
>     > > > >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7
>     > > > >>> > >Emaw48/pmpu/>
>     > >
>     > > <http://www.cl.cam.ac.uk/%7Emaw
>     > >
>     > > > >>> > >48/pmpu/>
>     > > > >>>
>     > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>     > > > >>>
>     > > > >>> > >u/> )
>     > > > >>>
>     > > > >>> --
>     > > > >>> Push Me Pull You - Distributed SCM tool (
>     > > > >>> http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7Emaw
>     > > > >>>48/pmpu/>
>     > >
>     > > <http://www.cl.cam.ac.uk/%7Emaw48/p
>     > >
>     > > > >>>mpu/> )
>     > > > >>
>     > > > >> --
>     > > > >> Antoine Benkemoun
>     > > > >> Tel : 03.51.53.57.00
>     > > > >> Port : 06.32.88.59.35
>     > > > >
>     > > > > --
>     > > > > Antoine Benkemoun
>     > > > > Tel : 03.51.53.57.00
>     > > > > Port : 06.32.88.59.35
>     > >
>     > > --
>     > > Push Me Pull You - Distributed SCM tool (
>     > > http://www.cl.cam.ac.uk/~maw48/pmpu/
>    
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7Emaw48/pmp
>     > >u/> )
>
>
>
>     --
>     Push Me Pull You - Distributed SCM tool
>     (http://www.cl.cam.ac.uk/~maw48/pmpu/
>     <http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>)
>
>
>
>
> -- 
> Antoine Benkemoun
> Tel : 03.51.53.57.00
> Port : 06.32.88.59.35
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

Thank you very much for your help guys !

I ended just reinstalling ontop of a clean Debian Etch Stable. Worked
perfectly fine using the binary and seems to be running stable.

Antoine

On Fri, Jul 18, 2008 at 3:09 PM, Alexander Hoßdorf <xen-users@hossdorf.eu>
wrote:
> may this perhaps be a bug?
> I found this:
> http://markmail.org/message/mujwmt5tstg34mh6
>
> I''m not familiar with overflow checks.
> But you might try this out, I think you''ve nothing to lose ;-)
> Backup your xc_core.c before editing.
>
> Hope this helps...
>
> Cheers,
> Alex
>
>
> Antoine Benkemoun schrieb:
>
>> Thank you for taking the time to re-explain everything.
>>
>> You have understood my situation right.
>>
>> I have applied your script. Gotten the sources. But make install-tools
>> seems to start correctly but fails since /etc/init.d/xend
doesn''t appear and
>> errors appear.
>>
>> Here is the detail :
>>
>> orangene2-hyp:~/xen-3.1.0-src# make install-tools
>> make -C tools install
>> make[1]: Entering directory `/root/xen-3.1.0-src/tools''
>> make -C check
>> make[2]: Entering directory `/root/xen-3.1.0-src/tools/check''
>> XENFB_TOOLS=n ./chk build
>> Xen CHECK-BUILD  Fri Jul 18 09:07:51 CEST 2008
>> Checking check_crypto_lib: OK
>> Checking check_libvncserver: unused, OK
>> Checking check_openssl_devel: OK
>> Checking check_python: OK
>> Checking check_python_devel: OK
>> Checking check_sdl: unused, OK
>> Checking check_x11_devel: OK
>> Checking check_xgettext: OK
>> Checking check_zlib_devel: OK
>> Checking check_zlib_lib: OK
>> make[2]: Leaving directory `/root/xen-3.1.0-src/tools/check''
>> make[2]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
>> mkdir -p xen
>> ( cd xen && ln -sf ../../../xen/include/public/*.h . )
>> mkdir -p xen/hvm
>> ( cd xen/hvm && ln -sf ../../../../xen/include/public/hvm/*.h .
)
>> mkdir -p xen/io
>> ( cd xen/io && ln -sf ../../../../xen/include/public/io/*.h . )
>> mkdir -p xen/arch-x86
>> ( cd xen/arch-x86 && ln -sf
../../../../xen/include/public/arch-x86/*.h .
>> )
>> mkdir -p xen/foreign
>> ( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/Makefile
>> . )
>> ( cd xen/foreign && ln -sf
>> ../../../../xen/include/public/foreign/reference.size . )
>> ( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/*.py . )
>> make -C xen/foreign
>> make[3]: Entering directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
>> ./checker > x86_32.size
>> diff -u reference.size x86_32.size
>> make[3]: Leaving directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
>> mkdir -p xen/linux
>> ( cd xen/linux && \
>>          ln -sf ../../../../linux-2.6-xen-sparse/include/xen/public/*.h
.
>> )
>> ( cd xen && rm -f sys && ln -sf linux sys )
>> make libxenctrl.a libxenctrl.so libxenctrl.so.3.0 libxenctrl.so.3.0.0
>> libxenguest.a libxenguest.so libxenguest.so.3.0 libxenguest.so.3.0.0
>> make[3]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
>> gcc  -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99
-Wall
>> -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
>>  -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
>> -D_GNU_SOURCE -Werror -Wmissing-prototypes -fno-strict-aliasing  -I.
>> -I../xenstore -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c
>> cc1: warnings being treated as errors
>> xc_core.c: In function ''xc_core_shdr_get'':
>> xc_core.c:195: error: assuming signed overflow does not occur when
>> assuming that (X + c) < X is always false
>> make[3]: *** [xc_core.o] Error 1
>> make[3]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
>> make[2]: *** [build] Error 2
>> make[2]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
>> make[1]: *** [install] Error 2
>> make[1]: Leaving directory `/root/xen-3.1.0-src/tools''
>> make: *** [install-tools] Error 2
>>
>> Antoine
>>
>> On Thu, Jul 17, 2008 at 10:53 PM, Mark Williamson <
>> mark.williamson@cl.cam.ac.uk
<mailto:mark.williamson@cl.cam.ac.uk>>
>> wrote:
>>
>>    On Thursday 17 July 2008, Antoine Benkemoun wrote:
>>    > I have to admit I am a bit lost here. Concerning userspace
>>    tools, I don''t
>>    > really know what you are talking about.
>>
>>    OK, sorry, lets step back a bit.
>>
>>    If you want your host to *boot* you need the Xen hypervisor
>>    (xen.gz) and
>>    XenLinux (vmlinuz-xen or somesuch) and an initrd.
>>
>>    I understood from your previous e-mails that you''ve
installed
>>    these, set up
>>    menu.lst to boot them and successfully booted into them.  Is that
>>    right?
>>    This means you''ve got a running dom0.
>>
>>    >From this system, you''re then trying to run xend and
it''s giving
>>    loads of
>>    errors about Python C API mismatches.  I''m I correct so
far?
>>
>>    > Also, the command lines you have given me will remove Xen.
After
>>    that''s
>>    > done, do I just reinstall using the binaries or do I do
>>    something else ?
>>
>>    A Xen-based system has three main components: the Xen hypervisor,
>>    the dom0
>>    Linux kernel and the userspace tools.  You seem to have the first
>>    two working
>>    OK, I think?
>>
>>    The problem you''re seeing when starting Xend is strictly a
>>    userspace tools
>>    issue.  xend is just a daemon that''s written in Python and
C which
>>    issues
>>    control hypercalls to Xen to tell it what to do.  To fix this
>>    issue you only
>>    need to fix these tools.
>>
>>    The command lines I gave you will remove all the *userspace* parts
>>    of Xen but
>>    should (if I''ve editted them right) leave the Xen
hypervisor and
>>    the XenLinux
>>    kernel you''re using in place.  This should leave the
machine still
>>    bootable
>>    (assuming I''m correct in thinking you''ve
successfully booted
>>    Xen/XenLinux
>>    already).
>>
>>    Using a source tree of the same version of Xen, "make
>>    install-tools" should
>>    replace the stuff we just removed with a custom-built copy,
>>    allowing you to
>>    start Xend without errors.  That''s the plan.  You
shouldn''t even
>>    need to
>>    reboot.  You should still be able to do this on the box you
didn''t
>>    reboot...
>>
>>    > I am starting to think that this is going to be too complex to
>>    fix. I think
>>    > the big error that I made is trying to install it on a Lenny
>>    Sid. I don''t
>>    > remember that ever working for me... I think just installing it
>>    on a Stable
>>    > Etch should do the trick without having to bother to spend
hours
>>    patching
>>    > this to achieve mediocre stability.
>>    >
>>    > Does anyone happen to have any feedback on install Xen on a
>>    Debian Sid
>>    > Lenny or Sid Etch ? I don''t recall that ever working
on previous
>>    occasions.
>>
>>    I think that Etch, at least, has reasonably recent Xen packages.
>>     How about
>>    just using the Debian-provided packages, at least to start with?
>>     XenSource
>>    don''t guarantee to keep updating their kernels with
security / bug
>>    fixes so
>>    you might find that the Debian kernels are more up-to-date.
>>
>>    Cheers,
>>    Mark
>>
>>    > Antoine
>>    >
>>    > On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
>>    >
>>    > mark.williamson@cl.cam.ac.uk
>>    <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>>    > > On Thursday 17 July 2008, you wrote:
>>    > > > I just did make install-tools and it didn''t
change anything.
>>    I don''t
>>    > > > know if I was supposed to do something else for it to
take
>>    action.
>>    > >
>>    > > Bad luck with getting the free trip, I was hoping to avoid
>>    that for you.
>>    > >
>>    > > :-(
>>    > >
>>    > > make install-tools should work, it''s only a
userspace problem
>>    you have.
>>    > >  Did
>>    > > you try to uninstall the existing userspace tools first as
I
>>    suggested?
>>    > > Reinstalling Xen / XenLinux will *definitely* not help
with
>>    Python <-> C
>>    > > API
>>    > > problems.
>>    > >
>>    > > I went and poked in the Makefile for you and found that
"make
>>    uninstall"
>>    > > runs
>>    > > the following (I''ve removed the lines that delete
the
>>    hypervisor and the
>>    > > XenLinux kernel stuff, since you want to keep those).
>>    > >
>>    > > You should substitute appropriate values for the
environment
>>    variables.
>>    > >  $(D)
>>    > > should be set to the empty string, LIBDIR is probably
>>    /usr/lib.  Please
>>    > > double check the following commands for sanity as you
always
>>    should
>>    > > before rm -rf.  Don''t trust me too much :-)
>>    > >
>>    > >        rm -rf $(D)/etc/init.d/xend*
>>    > >        rm -rf $(D)/etc/hotplug/xen-backend.agent
>>    > >        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
>>    > >        rm -f  $(D)/etc/udev/xen-backend.rules
>>    > >        rm -f  $(D)/etc/sysconfig/xendomains
>>    > >        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
>>    > >        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
>>    > >        rm -rf $(D)/usr/bin/cpuperf-perfcntr
>>    $(D)/usr/bin/cpuperf-xen
>>    > >        rm -rf $(D)/usr/bin/xc_shadow
>>    > >        rm -rf $(D)/usr/bin/pygrub
>>    > >        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
>>    > >        rm -rf $(D)/usr/bin/xsls
>>    > >        rm -rf $(D)/usr/include/xenctrl.h
>>    $(D)/usr/include/xenguest.h
>>    > >        rm -rf $(D)/usr/include/xs_lib.h
$(D)/usr/include/xs.h
>>    > >        rm -rf $(D)/usr/include/xen
>>    > >        rm -rf $(D)$(LIBDIR)/libxenctrl*
$(D)$(LIBDIR)/libxenguest*
>>    > >        rm -rf $(D)$(LIBDIR)/libxenstore*
>>    > >        rm -rf $(D)$(LIBDIR)/python/xen
$(D)$(LIBDIR)/python/grub
>>    > >        rm -rf $(D)$(LIBDIR)/xen/
>>    > >        rm -rf $(D)/usr/lib/xen/
>>    > >        rm -rf $(D)/usr/local/sbin/setmask
$(D)/usr/local/sbin/xen*
>>    > >        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix
>>    $(D)/usr/sbin/xm
>>    > >        rm -rf $(D)/usr/share/doc/xen
>>    > >        rm -rf $(D)/usr/share/xen
>>    > >        rm -rf $(D)/usr/share/man/man1/xen*
>>    > >        rm -rf $(D)/usr/share/man/man8/xen*
>>    > >
>>    > > Cheers,
>>    > > Mark
>>    > >
>>    > > > Antoine
>>    > > >
>>    > > > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun
<
>>    > > >
>>    > > > antoine.benkemoun@gmail.com
>>    <mailto:antoine.benkemoun@gmail.com>> wrote:
>>    > > > > Critical failure... machine doesn''t
boot anymore. I win
>>    the free trip
>>    > > > > !
>>    > > > >
>>    > > > > I am trying to do just make install-tools on the
second
>>    machine just
>>    > > > > to see if it will change something.
>>    > > > >
>>    > > > > Antoine
>>    > > > >
>>    > > > >
>>    > > > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine
Benkemoun <
>>    > > > >
>>    > > > > antoine.benkemoun@gmail.com
>>    <mailto:antoine.benkemoun@gmail.com>> wrote:
>>    > > > >> Ah sorry I didn''t read your email
correctly.
>>    > > > >>
>>    > > > >> I will do that afterwards might just as well
finish since
>>    it''s been
>>    > > > >> running for quite a while...
>>    > > > >>
>>    > > > >> Won''t be forgetting to do the
initrd, thank you for reminder.
>>    > > > >> Already got trapped previously but the PC
was right next
>>    to me so it
>>    > > > >> wasn''t so bad.
>>    > > > >>
>>    > > > >> Thanks !
>>    > > > >>
>>    > > > >> Antoine
>>    > > > >>
>>    > > > >>
>>    > > > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark
Williamson <
>>    > > > >>
>>    > > > >> mark.williamson@cl.cam.ac.uk
>>    <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>>    > > > >>> On Thursday 17 July 2008, Antoine
Benkemoun wrote:
>>    > > > >>> > Thank you for your thorough answer
!
>>    > > > >>> >
>>    > > > >>> > Indeed I am booting Debian with the
Xen kernel
>>    perfectly. I don''t
>>    > > > >>> > know
>>    > > > >>>
>>    > > > >>> what
>>    > > > >>>
>>    > > > >>> > you mean by XenLinux but
I''m guessing it''s what I am
>>    booting or
>>    > > > >>>
>>    > > > >>> something
>>    > > > >>>
>>    > > > >>> > similar enough.
>>    > > > >>>
>>    > > > >>> Sorry.
>>    > > > >>>
>>    > > > >>> By XenLinux I mean the Xen-aware Linux
you''re booting on
>>    top of
>>    > > > >>> Xen.
>>    > > > >>>
>>    > > > >>> > I agree that since it is the same
version it shouldn''t
>>    mess
>>    > > > >>> > things
>>    > >
>>    > > up
>>    > >
>>    > > > >>> too
>>    > > > >>>
>>    > > > >>> > much. I am compiling at the moment
using the same
>>    tutorial (it
>>    > > > >>> > had
>>    > >
>>    > > a
>>    > >
>>    > > > >>> > compiling source page included).
It''s taking for ever
>>    even with a
>>    > > > >>> > Quad
>>    > > > >>>
>>    > > > >>> Core
>>    > > > >>>
>>    > > > >>> > Xen machine with 4GB of RAM...
>>    > > > >>>
>>    > > > >>> If you''re only installing the
tools, as I suggested, you
>>    only
>>    > >
>>    > > actually
>>    > >
>>    > > > >>> need to
>>    > > > >>> do make tools; make install-tools, which
should be much
>>    faster.  If
>>    > >
>>    > > you
>>    > >
>>    > > > >>> just
>>    > > > >>> do "make world" it''ll
build Xen and the XenLinux, which
>>    will take
>>    > >
>>    > > ages
>>    > >
>>    > > > >>> and
>>    > > > >>> you already have those.
>>    > > > >>>
>>    > > > >>> > I''ll keep you updated if
this works or if I get a free
>>    trip to
>>    > > > >>> > the datacentre :P
>>    > > > >>>
>>    > > > >>> I hope you don''t win that prize
:-)
>>    > > > >>>
>>    > > > >>> Cheers,
>>    > > > >>> Mark
>>    > > > >>>
>>    > > > >>> > Antoine
>>    > > > >>> >
>>    > > > >>> > On Thu, Jul 17, 2008 at 9:43 PM,
Mark Williamson <
>>    > > > >>> >
>>    > > > >>> > mark.williamson@cl.cam.ac.uk
>>    <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>>    > > > >>> > > > Thank you for your quick
answer.
>>    > > > >>> > > >
>>    > > > >>> > > > I installed the 3.1.0
binaries on a Lenny Sid
>>    installed. I
>>    > > > >>> > > > followed
>>    > > > >>>
>>    > > > >>> the
>>    > > > >>>
>>    > > > >>> > > > "Perfect Xen 3.0
install" tutorial to the letter.
>>    > > > >>> > > >
>>    > > > >>> > > > I have the possibility to
install from sources but
>>    I am
>>    > >
>>    > > somewhat
>>    > >
>>    > > > >>> afraid
>>    > > > >>>
>>    > > > >>> > > to
>>    > > > >>> > >
>>    > > > >>> > > > do so... Can it crash the
machine if installed ontop a
>>    > > > >>> > > > previous
>>    > > > >>>
>>    > > > >>> install
>>    > > > >>>
>>    > > > >>> > > > ? Basically, the machine
not rebooting correctly
>>    wins me a
>>    > > > >>> > > > trip to
>>    > > > >>>
>>    > > > >>> the
>>    > > > >>>
>>    > > > >>> > > > datacentre and
that''s not fun :P
>>    > > > >>> > >
>>    > > > >>> > > Xen doesn''t play very
well with conflicting
>>    installs.  I guess
>>    > > > >>> > > if
>>    > > > >>>
>>    > > > >>> you''re
>>    > > > >>>
>>    > > > >>> > > installing the same version
from source that you''ve just
>>    > >
>>    > > installed
>>    > >
>>    > > > >>> > > in binaries it''s not
so likely to screw things up.
>>     That said,
>>    > >
>>    > > most
>>    > >
>>    > > > >>> > > of
>>    > > > >>>
>>    > > > >>> the
>>    > > > >>>
>>    > > > >>> > > conflicts are typically in
userspace stuff, which
>>    shouldn''t
>>    > > > >>> > > stop the machine
>>    > > > >>> > > actually booting. 
I''d also not expect such
>>    conflicts to result
>>    > >
>>    > > in
>>    > >
>>    > > > >>> > > a crash at
>>    > > > >>> > > runtime, it just usually means
Xend doesn''t work
>>    properly.
>>    > > > >>> > >
>>    > > > >>> > > > Is it possible to
uninstall a previous Xen install
>>    so it
>>    > >
>>    > > doesn''t
>>    > >
>>    > > > >>> mess
>>    > > > >>>
>>    > > > >>> > > > up everything ?
>>    > > > >>> > >
>>    > > > >>> > > Yes, if you can figure out
which bits to remove.  I
>>    think
>>    > > > >>> > > there''s
>>    > >
>>    > > a
>>    > >
>>    > > > >>> "make
>>    > > > >>>
>>    > > > >>> > > uninstall" target in the
source distribution that
>>    should do
>>    > > > >>> > > this reasonably thoroughly for
you; it''s not
>>    included in the
>>    > > > >>> > > binary distribution you
currently have :-(
>>    > > > >>> > >
>>    > > > >>> > > *however* in your case, you
have successfully
>>    installed Xen and
>>    > > > >>>
>>    > > > >>> XenLinux
>>    > > > >>>
>>    > > > >>> > > by the sound of it and
they''re already booting - am
>>    I reading
>>    > > > >>> > > you
>>    > > > >>>
>>    > > > >>> right?
>>    > > > >>>
>>    > > > >>> > > If you get the source
distribution for the same
>>    version of Xen
>>    > >
>>    > > and
>>    > >
>>    > > > >>> then
>>    > > > >>>
>>    > > > >>> > > just
>>    > > > >>> > > compile / install the
userspace tools, that should
>>    do.  You
>>    > > > >>> > > probably don''t really
need to build Xen / XenLinux
>>    lot again,
>>    > > > >>> > > or even reboot
>>    > > > >>>
>>    > > > >>> for
>>    > > > >>>
>>    > > > >>> > > that matter.
>>    > > > >>> > >
>>    > > > >>> > > You might still need to remove
the old userspace
>>    libraries to
>>    > >
>>    > > make
>>    > >
>>    > > > >>> Xend
>>    > > > >>>
>>    > > > >>> > > work
>>    > > > >>> > > right.  make uninstall should
take them away but it
>>    might
>>    > > > >>> > > remove your
>>    > > > >>>
>>    > > > >>> Xen
>>    > > > >>>
>>    > > > >>> > > / XenLinux too... 
I''d suggest you manually look at
>>    what the
>>    > > > >>> > > Makefile does to see which
libraries / binaries to
>>    remove, then
>>    > >
>>    > > do
>>    > >
>>    > > > >>> > > it
>>    > > > >>>
>>    > > > >>> yourself.
>>    > > > >>>
>>    > > > >>> > > Does that sound reasonably
doable to you?  Don''t use
>>    make
>>    > > > >>> > > uninstall,
>>    > > > >>>
>>    > > > >>> just
>>    > > > >>>
>>    > > > >>> > > use it for inspiration when
uninstalling the
>>    userspace tools.
>>    > >
>>    > >  Then
>>    > >
>>    > > > >>> run
>>    > > > >>>
>>    > > > >>> > > make tools-install to build
and install a new
>>    version of the
>>    > >
>>    > > tools.
>>    > >
>>    > > > >>> > > You may need to install a few
-dev packages to build
>>    > >
>>    > > successfully.
>>    > >
>>    > > > >>> > > Cheers,
>>    > > > >>> > > Mark
>>    > > > >>> > >
>>    > > > >>> > > > On Thu, Jul 17, 2008 at
9:02 PM, Mark Williamson <
>>    > > > >>> > > >
>>    > > > >>> > > >
mark.williamson@cl.cam.ac.uk
>>    <mailto:mark.williamson@cl.cam.ac.uk>> wrote:
>>    > > > >>> > > > > These errors
typically happen when the Xen code
>>    was built
>>    > > > >>> > > > > against
>>    > > > >>>
>>    > > > >>> a
>>    > > > >>>
>>    > > > >>> > > > > different
>>    > > > >>> > > > > version of Python to
the one that''s available at
>>    runtime.
>>    > >
>>    > >  I''ve
>>    > >
>>    > > > >>> > > actually
>>    > > > >>> > >
>>    > > > >>> > > > > found these are
often harmless but that''s
>>    probably not an
>>    > > > >>>
>>    > > > >>> appropriate
>>    > > > >>>
>>    > > > >>> > > > > risk to
>>    > > > >>> > > > > take for a
production machine.
>>    > > > >>> > > > >
>>    > > > >>> > > > > Where exactly did
you get your install source
>>    for Xen from?
>>    > > > >>>
>>    > > > >>>  Could
>>    > > > >>>
>>    > > > >>> > > > > you just build Xen
yourself rather than using a
>>    > > > >>> > > > > pre-compiled
>>    > > > >>>
>>    > > > >>> version?
>>    > > > >>>
>>    > > > >>> > > > > Cheers,
>>    > > > >>> > > > > Mark
>>    > > > >>> > > > >
>>    > > > >>> > > > > On Thursday 17 July
2008, Antoine Benkemoun wrote:
>>    > > > >>> > > > > > Hello,
>>    > > > >>> > > > > >
>>    > > > >>> > > > > > I am trying to
install Xen 3.1.0 on a Debian
>>    Sid. I have
>>    > >
>>    > > been
>>    > >
>>    > > > >>> able
>>    > > > >>>
>>    > > > >>> > > > > > to do this type
of installation correctly with
>>    it working
>>    > > > >>>
>>    > > > >>> perfectly
>>    > > > >>>
>>    > > > >>> > > before
>>    > > > >>> > >
>>    > > > >>> > > > > > but
>>    > > > >>> > > > >
>>    > > > >>> > > > > I
>>    > > > >>> > > > >
>>    > > > >>> > > > > > have to admit I
can''t get this one to work.
>>    > > > >>> > > > > >
>>    > > > >>> > > > > > Here are the
error messages that I get at Xen
>>    startup :
>>    > > > >>> > > > > >
>>    > > > >>> > > > > >
orangene1-hyp:~# /etc/init.d/xend start
>>    > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>>    > > > >>>
>>    > > > >>> RuntimeWarning:
>>    > > > >>> > > Python
>>    > > > >>> > >
>>    > > > >>> > > > > > C API version
mismatch for module
>>    xen.lowlevel.xc: This
>>    > > > >>> > > > > > Python
>>    > > > >>>
>>    > > > >>> has
>>    > > > >>>
>>    > > > >>> > > API
>>    > > > >>> > >
>>    > > > >>> > > > > > version 1013,
module xen.lowlevel.xc has
>>    version 1012.
>>    > > > >>> > > > > >   import
xen.lowlevel.xc
>>    > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
>>    RuntimeWarning:
>>    > > > >>> > > > > > Python
>>    > > > >>>
>>    > > > >>> C
>>    > > > >>>
>>    > > > >>> > > > > > API version
mismatch for module acm: This
>>    Python has API
>>    > > > >>>
>>    > > > >>> version
>>    > > > >>>
>>    > > > >>> > > > > > 1013, module
acm has version 1012.
>>    > > > >>> > > > > >   from
xen.lowlevel import acm
>>    > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>>    > > > >>> > > > > > RuntimeWarning:
Python
>>    > > > >>> > >
>>    > > > >>> > > C
>>    > > > >>> > >
>>    > > > >>> > > > > API
>>    > > > >>> > > > >
>>    > > > >>> > > > > > version
mismatch for module xen.lowlevel.xs:
>>    This Python
>>    > >
>>    > > has
>>    > >
>>    > > > >>> API
>>    > > > >>>
>>    > > > >>> > > > > > version 1013,
module xen.lowlevel.xs has
>>    version 1012.
>>    > > > >>> > > > > >   import
xen.lowlevel.xs
>>    > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
>>    > > > >>> > > > > > RuntimeWarning:
Python
>>    > > > >>> > >
>>    > > > >>> > > C
>>    > > > >>> > >
>>    > > > >>> > > > > API
>>    > > > >>> > > > >
>>    > > > >>> > > > > > version
mismatch for module ptsname: This
>>    Python has API
>>    > > > >>>
>>    > > > >>> version
>>    > > > >>>
>>    > > > >>> > > 1013,
>>    > > > >>> > >
>>    > > > >>> > > > > > module ptsname
has version 1012.
>>    > > > >>> > > > > >   from
xen.lowlevel import ptsname
>>    > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
>>    > > > >>>
>>    > > > >>> RuntimeWarning:
>>    > > > >>> > > Python
>>    > > > >>> > >
>>    > > > >>> > > > > > C API version
mismatch for module
>>    xen.lowlevel.xc: This
>>    > > > >>> > > > > > Python
>>    > > > >>>
>>    > > > >>> has
>>    > > > >>>
>>    > > > >>> > > API
>>    > > > >>> > >
>>    > > > >>> > > > > > version 1013,
module xen.lowlevel.xc has
>>    version 1012.
>>    > > > >>> > > > > >   import
xen.lowlevel.xc
>>    > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
>>    RuntimeWarning:
>>    > > > >>> > > > > > Python
>>    > > > >>>
>>    > > > >>> C
>>    > > > >>>
>>    > > > >>> > > > > > API version
mismatch for module acm: This
>>    Python has API
>>    > > > >>>
>>    > > > >>> version
>>    > > > >>>
>>    > > > >>> > > > > > 1013, module
acm has version 1012.
>>    > > > >>> > > > > >   from
xen.lowlevel import acm
>>    > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
>>    > > > >>> > > > > > RuntimeWarning:
Python
>>    > > > >>> > >
>>    > > > >>> > > C
>>    > > > >>> > >
>>    > > > >>> > > > > API
>>    > > > >>> > > > >
>>    > > > >>> > > > > > version
mismatch for module xen.lowlevel.xs:
>>    This Python
>>    > >
>>    > > has
>>    > >
>>    > > > >>> API
>>    > > > >>>
>>    > > > >>> > > > > > version 1013,
module xen.lowlevel.xs has
>>    version 1012.
>>    > > > >>> > > > > >   import
xen.lowlevel.xs
>>    > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
>>    > > > >>> > > > > > RuntimeWarning:
Python
>>    > > > >>> > >
>>    > > > >>> > > C
>>    > > > >>> > >
>>    > > > >>> > > > > API
>>    > > > >>> > > > >
>>    > > > >>> > > > > > version
mismatch for module ptsname: This
>>    Python has API
>>    > > > >>>
>>    > > > >>> version
>>    > > > >>>
>>    > > > >>> > > 1013,
>>    > > > >>> > >
>>    > > > >>> > > > > > module ptsname
has version 1012.
>>    > > > >>> > > > > >   from
xen.lowlevel import ptsname
>>    > > > >>> > > > > >
>>    > > > >>> > > > > > I have tried to
install python from Sid and Lenny
>>    > > > >>> > > > > > versions but
>>    > > > >>>
>>    > > > >>> none
>>    > > > >>>
>>    > > > >>> > > > > > seem
>>    > > > >>> > > > >
>>    > > > >>> > > > > to
>>    > > > >>> > > > >
>>    > > > >>> > > > > > change any of
this... I have no Python
>>    knowledge at all
>>    > > > >>> > > > > > so
>>    > >
>>    > > I
>>    > >
>>    > > > >>> would
>>    > > > >>>
>>    > > > >>> > > like
>>    > > > >>> > >
>>    > > > >>> > > > > to
>>    > > > >>> > > > >
>>    > > > >>> > > > > > know if anybody
would happen to have an idea
>>    concerning
>>    > >
>>    > > this
>>    > >
>>    > > > >>> > > > > > problem.
>>    > > > >>> > > > > >
>>    > > > >>> > > > > > I will be happy
to give you more info if there is
>>    > > > >>> > > > > > something
>>    > > > >>>
>>    > > > >>> missing
>>    > > > >>>
>>    > > > >>> > > in
>>    > > > >>> > >
>>    > > > >>> > > > > this
>>    > > > >>> > > > >
>>    > > > >>> > > > > > post.
>>    > > > >>> > > > > >
>>    > > > >>> > > > > > Thank you in
advance for your help,
>>    > > > >>> > > > > >
>>    > > > >>> > > > > > Antoine
Benkemoun
>>    > > > >>> > > > >
>>    > > > >>> > > > > --
>>    > > > >>> > > > > Push Me Pull You -
Distributed SCM tool (
>>    > > > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>   
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.u
>>    > > > >>> > > > >k/%7Emaw48/pmpu/>
>>    > >
>>    > > <http://www.cl.cam.ac.uk/%7
>>    > >
>>    > > > >>> > > > >Emaw48/pmpu/>
>>    > > > >>>
>>    > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48
>>    > > > >>>
>>    > > > >>> > > > >/pmpu/>
>>    > > > >>> > >
>>    > > > >>> > >
<http://www.cl.cam.ac.uk/%7Emaw48/pmp
>>    > > > >>> > >
>>    > > > >>> > > > >u/> )
>>    > > > >>> > >
>>    > > > >>> > > --
>>    > > > >>> > > Push Me Pull You - Distributed
SCM tool (
>>    > > > >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>   
<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><http://www.cl.cam.ac.uk/%7
>>    > > > >>> > >Emaw48/pmpu/>
>>    > >
>>    > > <http://www.cl.cam.ac.uk/%7Emaw
>>    > >
>>    > > > >>> > >48/pmpu/>
>>    > > > >>>
>>    > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
>>    > > > >>>
>>    > > > >>> > >u/> )
>>    > > > >>>
>>    > > > >>> --
>>    > > > >>> Push Me Pull You - Distributed SCM tool
(
>>    > > > >>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>    <http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><
>> http://www.cl.cam.ac.uk/%7Emaw
>>    > > > >>>48/pmpu/>
>>    > >
>>    > > <http://www.cl.cam.ac.uk/%7Emaw48/p
>>    > >
>>    > > > >>>mpu/> )
>>    > > > >>
>>    > > > >> --
>>    > > > >> Antoine Benkemoun
>>    > > > >> Tel : 03.51.53.57.00
>>    > > > >> Port : 06.32.88.59.35
>>    > > > >
>>    > > > > --
>>    > > > > Antoine Benkemoun
>>    > > > > Tel : 03.51.53.57.00
>>    > > > > Port : 06.32.88.59.35
>>    > >
>>    > > --
>>    > > Push Me Pull You - Distributed SCM tool (
>>    > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>    <http://www.cl.cam.ac.uk/%7Emaw48/pmpu/><
>> http://www.cl.cam.ac.uk/%7Emaw48/pmp
>>    > >u/> )
>>
>>
>>
>>    --
>>    Push Me Pull You - Distributed SCM tool
>>   
(http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
>>    <http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>)
>>
>>
>>
>>
>> --
>> Antoine Benkemoun
>> Tel : 03.51.53.57.00
>> Port : 06.32.88.59.35
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>

-- 
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35


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

Hello there,

The error you received is a weird one, I''d not seen it before.  What
compiler
version are you using (gcc --version)?  Sorry about that, I''ve never
seen
that before and I''m not sure why it''s happening.  Occasionally
somebody uses
a compiler that doesn''t like the Xen code in one way or another, so
maybe
that''s the problem...

It actually looked like it was only a warning, however the policy in Xen code 
is to treat warnings as errors and solve them as potential bugs, which is why 
the build failed.

I understood from your later e-mails that you''ve now gone to a clean
install,
so don''t worry if this isn''t a problem anymore.  I''m
glad things are working
better for you now!

Cheers,
Mark

On Friday 18 July 2008, Antoine Benkemoun wrote:
> Thank you for taking the time to re-explain everything.
>
> You have understood my situation right.
>
> I have applied your script. Gotten the sources. But make install-tools
> seems to start correctly but fails since /etc/init.d/xend doesn''t
appear
> and errors appear.
>
> Here is the detail :
>
> orangene2-hyp:~/xen-3.1.0-src# make install-tools
> make -C tools install
> make[1]: Entering directory `/root/xen-3.1.0-src/tools''
> make -C check
> make[2]: Entering directory `/root/xen-3.1.0-src/tools/check''
> XENFB_TOOLS=n ./chk build
> Xen CHECK-BUILD  Fri Jul 18 09:07:51 CEST 2008
> Checking check_crypto_lib: OK
> Checking check_libvncserver: unused, OK
> Checking check_openssl_devel: OK
> Checking check_python: OK
> Checking check_python_devel: OK
> Checking check_sdl: unused, OK
> Checking check_x11_devel: OK
> Checking check_xgettext: OK
> Checking check_zlib_devel: OK
> Checking check_zlib_lib: OK
> make[2]: Leaving directory `/root/xen-3.1.0-src/tools/check''
> make[2]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
> mkdir -p xen
> ( cd xen && ln -sf ../../../xen/include/public/*.h . )
> mkdir -p xen/hvm
> ( cd xen/hvm && ln -sf ../../../../xen/include/public/hvm/*.h . )
> mkdir -p xen/io
> ( cd xen/io && ln -sf ../../../../xen/include/public/io/*.h . )
> mkdir -p xen/arch-x86
> ( cd xen/arch-x86 && ln -sf
../../../../xen/include/public/arch-x86/*.h . )
> mkdir -p xen/foreign
> ( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/Makefile
> . )
> ( cd xen/foreign && ln -sf
> ../../../../xen/include/public/foreign/reference.size . )
> ( cd xen/foreign && ln -sf
../../../../xen/include/public/foreign/*.py . )
> make -C xen/foreign
> make[3]: Entering directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
> ./checker > x86_32.size
> diff -u reference.size x86_32.size
> make[3]: Leaving directory
`/root/xen-3.1.0-src/tools/libxc/xen/foreign''
> mkdir -p xen/linux
> ( cd xen/linux && \
>           ln -sf ../../../../linux-2.6-xen-sparse/include/xen/public/*.h .
> ) ( cd xen && rm -f sys && ln -sf linux sys )
> make libxenctrl.a libxenctrl.so libxenctrl.so.3.0 libxenctrl.so.3.0.0
> libxenguest.a libxenguest.so libxenguest.so.3.0 libxenguest.so.3.0.0
> make[3]: Entering directory `/root/xen-3.1.0-src/tools/libxc''
> gcc  -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99 -Wall
> -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
> -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
> -D_GNU_SOURCE -Werror -Wmissing-prototypes -fno-strict-aliasing  -I.
> -I../xenstore -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c
> cc1: warnings being treated as errors
> xc_core.c: In function ''xc_core_shdr_get'':
> xc_core.c:195: error: assuming signed overflow does not occur when assuming
> that (X + c) < X is always false
> make[3]: *** [xc_core.o] Error 1
> make[3]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
> make[2]: *** [build] Error 2
> make[2]: Leaving directory `/root/xen-3.1.0-src/tools/libxc''
> make[1]: *** [install] Error 2
> make[1]: Leaving directory `/root/xen-3.1.0-src/tools''
> make: *** [install-tools] Error 2
>
> Antoine
>
> On Thu, Jul 17, 2008 at 10:53 PM, Mark Williamson <
>
> mark.williamson@cl.cam.ac.uk> wrote:
> > On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > I have to admit I am a bit lost here. Concerning userspace tools,
I
> > > don''t really know what you are talking about.
> >
> > OK, sorry, lets step back a bit.
> >
> > If you want your host to *boot* you need the Xen hypervisor (xen.gz)
and
> > XenLinux (vmlinuz-xen or somesuch) and an initrd.
> >
> > I understood from your previous e-mails that you''ve installed
these, set
> > up menu.lst to boot them and successfully booted into them.  Is that
> > right? This means you''ve got a running dom0.
> >
> > From this system, you''re then trying to run xend and
it''s giving loads of
> > errors about Python C API mismatches.  I''m I correct so far?
> >
> > > Also, the command lines you have given me will remove Xen. After
that''s
> > > done, do I just reinstall using the binaries or do I do something
else
> > > ?
> >
> > A Xen-based system has three main components: the Xen hypervisor, the
> > dom0 Linux kernel and the userspace tools.  You seem to have the first
> > two working
> > OK, I think?
> >
> > The problem you''re seeing when starting Xend is strictly a
userspace
> > tools issue.  xend is just a daemon that''s written in Python
and C which
> > issues control hypercalls to Xen to tell it what to do.  To fix this
> > issue you only
> > need to fix these tools.
> >
> > The command lines I gave you will remove all the *userspace* parts of
Xen
> > but
> > should (if I''ve editted them right) leave the Xen hypervisor
and the
> > XenLinux
> > kernel you''re using in place.  This should leave the machine
still
> > bootable (assuming I''m correct in thinking you''ve
successfully booted
> > Xen/XenLinux already).
> >
> > Using a source tree of the same version of Xen, "make
install-tools"
> > should replace the stuff we just removed with a custom-built copy,
> > allowing you to start Xend without errors.  That''s the plan. 
You
> > shouldn''t even need to reboot.  You should still be able to
do this on
> > the box you didn''t reboot...
> >
> > > I am starting to think that this is going to be too complex to
fix. I
> >
> > think
> >
> > > the big error that I made is trying to install it on a Lenny Sid.
I
> > > don''t remember that ever working for me... I think just
installing it
> > > on a
> >
> > Stable
> >
> > > Etch should do the trick without having to bother to spend hours
> > > patching this to achieve mediocre stability.
> > >
> > > Does anyone happen to have any feedback on install Xen on a
Debian Sid
> > > Lenny or Sid Etch ? I don''t recall that ever working on
previous
> >
> > occasions.
> >
> > I think that Etch, at least, has reasonably recent Xen packages.  How
> > about just using the Debian-provided packages, at least to start with?
> > XenSource don''t guarantee to keep updating their kernels with
security /
> > bug fixes so you might find that the Debian kernels are more
up-to-date.
> >
> > Cheers,
> > Mark
> >
> > > Antoine
> > >
> > > On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
> > >
> > > mark.williamson@cl.cam.ac.uk> wrote:
> > > > On Thursday 17 July 2008, you wrote:
> > > > > I just did make install-tools and it didn''t
change anything. I
> > > > > don''t know if I was supposed to do something
else for it to take
> > > > > action.
> > > >
> > > > Bad luck with getting the free trip, I was hoping to avoid
that for
> >
> > you.
> >
> > > > :-(
> > > >
> > > > make install-tools should work, it''s only a
userspace problem you
> > > > have. Did
> > > > you try to uninstall the existing userspace tools first as I
> > > > suggested? Reinstalling Xen / XenLinux will *definitely* not
help
> > > > with Python <->
> >
> > C
> >
> > > > API
> > > > problems.
> > > >
> > > > I went and poked in the Makefile for you and found that
"make
> >
> > uninstall"
> >
> > > > runs
> > > > the following (I''ve removed the lines that delete
the hypervisor and
> >
> > the
> >
> > > > XenLinux kernel stuff, since you want to keep those).
> > > >
> > > > You should substitute appropriate values for the environment
> > > > variables. $(D)
> > > > should be set to the empty string, LIBDIR is probably
/usr/lib.
> > > > Please double check the following commands for sanity as you
always
> > > > should before rm -rf.  Don''t trust me too much :-)
> > > >
> > > >        rm -rf $(D)/etc/init.d/xend*
> > > >        rm -rf $(D)/etc/hotplug/xen-backend.agent
> > > >        rm -f  $(D)/etc/udev/rules.d/xen-backend.rules
> > > >        rm -f  $(D)/etc/udev/xen-backend.rules
> > > >        rm -f  $(D)/etc/sysconfig/xendomains
> > > >        rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
> > > >        rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
> > > >        rm -rf $(D)/usr/bin/cpuperf-perfcntr
$(D)/usr/bin/cpuperf-xen
> > > >        rm -rf $(D)/usr/bin/xc_shadow
> > > >        rm -rf $(D)/usr/bin/pygrub
> > > >        rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
> > > >        rm -rf $(D)/usr/bin/xsls
> > > >        rm -rf $(D)/usr/include/xenctrl.h
$(D)/usr/include/xenguest.h
> > > >        rm -rf $(D)/usr/include/xs_lib.h
$(D)/usr/include/xs.h
> > > >        rm -rf $(D)/usr/include/xen
> > > >        rm -rf $(D)$(LIBDIR)/libxenctrl*
$(D)$(LIBDIR)/libxenguest*
> > > >        rm -rf $(D)$(LIBDIR)/libxenstore*
> > > >        rm -rf $(D)$(LIBDIR)/python/xen
$(D)$(LIBDIR)/python/grub
> > > >        rm -rf $(D)$(LIBDIR)/xen/
> > > >        rm -rf $(D)/usr/lib/xen/
> > > >        rm -rf $(D)/usr/local/sbin/setmask
$(D)/usr/local/sbin/xen*
> > > >        rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix
> > > > $(D)/usr/sbin/xm rm -rf $(D)/usr/share/doc/xen
> > > >        rm -rf $(D)/usr/share/xen
> > > >        rm -rf $(D)/usr/share/man/man1/xen*
> > > >        rm -rf $(D)/usr/share/man/man8/xen*
> > > >
> > > > Cheers,
> > > > Mark
> > > >
> > > > > Antoine
> > > > >
> > > > > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun
<
> > > > >
> > > > > antoine.benkemoun@gmail.com> wrote:
> > > > > > Critical failure... machine doesn''t boot
anymore. I win the free
> >
> > trip
> >
> > > > > > !
> > > > > >
> > > > > > I am trying to do just make install-tools on the
second machine
> >
> > just
> >
> > > > > > to see if it will change something.
> > > > > >
> > > > > > Antoine
> > > > > >
> > > > > >
> > > > > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine
Benkemoun <
> > > > > >
> > > > > > antoine.benkemoun@gmail.com> wrote:
> > > > > >> Ah sorry I didn''t read your email
correctly.
> > > > > >>
> > > > > >> I will do that afterwards might just as well
finish since it''s
> >
> > been
> >
> > > > > >> running for quite a while...
> > > > > >>
> > > > > >> Won''t be forgetting to do the initrd,
thank you for reminder.
> > > > > >> Already got trapped previously but the PC was
right next to me
> > > > > >> so
> >
> > it
> >
> > > > > >> wasn''t so bad.
> > > > > >>
> > > > > >> Thanks !
> > > > > >>
> > > > > >> Antoine
> > > > > >>
> > > > > >>
> > > > > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark
Williamson <
> > > > > >>
> > > > > >> mark.williamson@cl.cam.ac.uk> wrote:
> > > > > >>> On Thursday 17 July 2008, Antoine
Benkemoun wrote:
> > > > > >>> > Thank you for your thorough answer !
> > > > > >>> >
> > > > > >>> > Indeed I am booting Debian with the
Xen kernel perfectly. I
> >
> > don''t
> >
> > > > > >>> > know
> > > > > >>>
> > > > > >>> what
> > > > > >>>
> > > > > >>> > you mean by XenLinux but I''m
guessing it''s what I am booting
> > > > > >>> > or
> > > > > >>>
> > > > > >>> something
> > > > > >>>
> > > > > >>> > similar enough.
> > > > > >>>
> > > > > >>> Sorry.
> > > > > >>>
> > > > > >>> By XenLinux I mean the Xen-aware Linux
you''re booting on top of
> > > > > >>> Xen.
> > > > > >>>
> > > > > >>> > I agree that since it is the same
version it shouldn''t mess
> > > > > >>> > things
> > > >
> > > > up
> > > >
> > > > > >>> too
> > > > > >>>
> > > > > >>> > much. I am compiling at the moment
using the same tutorial
> > > > > >>> > (it had
> > > >
> > > > a
> > > >
> > > > > >>> > compiling source page included).
It''s taking for ever even
> > > > > >>> > with
> >
> > a
> >
> > > > > >>> > Quad
> > > > > >>>
> > > > > >>> Core
> > > > > >>>
> > > > > >>> > Xen machine with 4GB of RAM...
> > > > > >>>
> > > > > >>> If you''re only installing the
tools, as I suggested, you only
> > > >
> > > > actually
> > > >
> > > > > >>> need to
> > > > > >>> do make tools; make install-tools, which
should be much faster.
> >
> >  If
> >
> > > > you
> > > >
> > > > > >>> just
> > > > > >>> do "make world" it''ll
build Xen and the XenLinux, which will
> > > > > >>> take
> > > >
> > > > ages
> > > >
> > > > > >>> and
> > > > > >>> you already have those.
> > > > > >>>
> > > > > >>> > I''ll keep you updated if
this works or if I get a free trip
> > > > > >>> > to the datacentre :P
> > > > > >>>
> > > > > >>> I hope you don''t win that prize
:-)
> > > > > >>>
> > > > > >>> Cheers,
> > > > > >>> Mark
> > > > > >>>
> > > > > >>> > Antoine
> > > > > >>> >
> > > > > >>> > On Thu, Jul 17, 2008 at 9:43 PM, Mark
Williamson <
> > > > > >>> >
> > > > > >>> > mark.williamson@cl.cam.ac.uk>
wrote:
> > > > > >>> > > > Thank you for your quick
answer.
> > > > > >>> > > >
> > > > > >>> > > > I installed the 3.1.0
binaries on a Lenny Sid installed.
> > > > > >>> > > > I followed
> > > > > >>>
> > > > > >>> the
> > > > > >>>
> > > > > >>> > > > "Perfect Xen 3.0
install" tutorial to the letter.
> > > > > >>> > > >
> > > > > >>> > > > I have the possibility to
install from sources but I am
> > > >
> > > > somewhat
> > > >
> > > > > >>> afraid
> > > > > >>>
> > > > > >>> > > to
> > > > > >>> > >
> > > > > >>> > > > do so... Can it crash the
machine if installed ontop a
> > > > > >>> > > > previous
> > > > > >>>
> > > > > >>> install
> > > > > >>>
> > > > > >>> > > > ? Basically, the machine
not rebooting correctly wins me
> > > > > >>> > > > a trip to
> > > > > >>>
> > > > > >>> the
> > > > > >>>
> > > > > >>> > > > datacentre and
that''s not fun :P
> > > > > >>> > >
> > > > > >>> > > Xen doesn''t play very
well with conflicting installs.  I
> >
> > guess
> >
> > > > > >>> > > if
> > > > > >>>
> > > > > >>> you''re
> > > > > >>>
> > > > > >>> > > installing the same version from
source that you''ve just
> > > >
> > > > installed
> > > >
> > > > > >>> > > in binaries it''s not so
likely to screw things up.  That
> >
> > said,
> >
> > > > most
> > > >
> > > > > >>> > > of
> > > > > >>>
> > > > > >>> the
> > > > > >>>
> > > > > >>> > > conflicts are typically in
userspace stuff, which shouldn''t
> > > > > >>> > > stop the machine
> > > > > >>> > > actually booting.  I''d
also not expect such conflicts to
> >
> > result
> >
> > > > in
> > > >
> > > > > >>> > > a crash at
> > > > > >>> > > runtime, it just usually means
Xend doesn''t work properly.
> > > > > >>> > >
> > > > > >>> > > > Is it possible to uninstall
a previous Xen install so it
> > > >
> > > > doesn''t
> > > >
> > > > > >>> mess
> > > > > >>>
> > > > > >>> > > > up everything ?
> > > > > >>> > >
> > > > > >>> > > Yes, if you can figure out which
bits to remove.  I think
> > > > > >>> > > there''s
> > > >
> > > > a
> > > >
> > > > > >>> "make
> > > > > >>>
> > > > > >>> > > uninstall" target in the
source distribution that should do
> > > > > >>> > > this reasonably thoroughly for
you; it''s not included in
> > > > > >>> > > the binary distribution you
currently have :-(
> > > > > >>> > >
> > > > > >>> > > *however* in your case, you have
successfully installed Xen
> >
> > and
> >
> > > > > >>> XenLinux
> > > > > >>>
> > > > > >>> > > by the sound of it and
they''re already booting - am I
> > > > > >>> > > reading you
> > > > > >>>
> > > > > >>> right?
> > > > > >>>
> > > > > >>> > > If you get the source
distribution for the same version of
> >
> > Xen
> >
> > > > and
> > > >
> > > > > >>> then
> > > > > >>>
> > > > > >>> > > just
> > > > > >>> > > compile / install the userspace
tools, that should do.  You
> > > > > >>> > > probably don''t really
need to build Xen / XenLinux lot
> > > > > >>> > > again, or even reboot
> > > > > >>>
> > > > > >>> for
> > > > > >>>
> > > > > >>> > > that matter.
> > > > > >>> > >
> > > > > >>> > > You might still need to remove
the old userspace libraries
> > > > > >>> > > to
> > > >
> > > > make
> > > >
> > > > > >>> Xend
> > > > > >>>
> > > > > >>> > > work
> > > > > >>> > > right.  make uninstall should
take them away but it might
> > > > > >>> > > remove your
> > > > > >>>
> > > > > >>> Xen
> > > > > >>>
> > > > > >>> > > / XenLinux too...  I''d
suggest you manually look at what
> > > > > >>> > > the Makefile does to see which
libraries / binaries to
> > > > > >>> > > remove,
> >
> > then
> >
> > > > do
> > > >
> > > > > >>> > > it
> > > > > >>>
> > > > > >>> yourself.
> > > > > >>>
> > > > > >>> > > Does that sound reasonably
doable to you?  Don''t use make
> > > > > >>> > > uninstall,
> > > > > >>>
> > > > > >>> just
> > > > > >>>
> > > > > >>> > > use it for inspiration when
uninstalling the userspace
> > > > > >>> > > tools.
> > > >
> > > >  Then
> > > >
> > > > > >>> run
> > > > > >>>
> > > > > >>> > > make tools-install to build and
install a new version of
> > > > > >>> > > the
> > > >
> > > > tools.
> > > >
> > > > > >>> > > You may need to install a few
-dev packages to build
> > > >
> > > > successfully.
> > > >
> > > > > >>> > > Cheers,
> > > > > >>> > > Mark
> > > > > >>> > >
> > > > > >>> > > > On Thu, Jul 17, 2008 at
9:02 PM, Mark Williamson <
> > > > > >>> > > >
> > > > > >>> > > >
mark.williamson@cl.cam.ac.uk> wrote:
> > > > > >>> > > > > These errors typically
happen when the Xen code was
> > > > > >>> > > > > built against
> > > > > >>>
> > > > > >>> a
> > > > > >>>
> > > > > >>> > > > > different
> > > > > >>> > > > > version of Python to
the one that''s available at
> > > > > >>> > > > > runtime.
> > > >
> > > >  I''ve
> > > >
> > > > > >>> > > actually
> > > > > >>> > >
> > > > > >>> > > > > found these are often
harmless but that''s probably not
> > > > > >>> > > > > an
> > > > > >>>
> > > > > >>> appropriate
> > > > > >>>
> > > > > >>> > > > > risk to
> > > > > >>> > > > > take for a production
machine.
> > > > > >>> > > > >
> > > > > >>> > > > > Where exactly did you
get your install source for Xen
> >
> > from?
> >
> > > > > >>>  Could
> > > > > >>>
> > > > > >>> > > > > you just build Xen
yourself rather than using a
> > > > > >>> > > > > pre-compiled
> > > > > >>>
> > > > > >>> version?
> > > > > >>>
> > > > > >>> > > > > Cheers,
> > > > > >>> > > > > Mark
> > > > > >>> > > > >
> > > > > >>> > > > > On Thursday 17 July
2008, Antoine Benkemoun wrote:
> > > > > >>> > > > > > Hello,
> > > > > >>> > > > > >
> > > > > >>> > > > > > I am trying to
install Xen 3.1.0 on a Debian Sid. I
> >
> > have
> >
> > > > been
> > > >
> > > > > >>> able
> > > > > >>>
> > > > > >>> > > > > > to do this type
of installation correctly with it
> >
> > working
> >
> > > > > >>> perfectly
> > > > > >>>
> > > > > >>> > > before
> > > > > >>> > >
> > > > > >>> > > > > > but
> > > > > >>> > > > >
> > > > > >>> > > > > I
> > > > > >>> > > > >
> > > > > >>> > > > > > have to admit I
can''t get this one to work.
> > > > > >>> > > > > >
> > > > > >>> > > > > > Here are the
error messages that I get at Xen startup
> > > > > >>> > > > > > :
> > > > > >>> > > > > >
> > > > > >>> > > > > > orangene1-hyp:~#
/etc/init.d/xend start
> > > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > > > > >>>
> > > > > >>> RuntimeWarning:
> > > > > >>> > > Python
> > > > > >>> > >
> > > > > >>> > > > > > C API version
mismatch for module xen.lowlevel.xc:
> > > > > >>> > > > > > This Python
> > > > > >>>
> > > > > >>> has
> > > > > >>>
> > > > > >>> > > API
> > > > > >>> > >
> > > > > >>> > > > > > version 1013,
module xen.lowlevel.xc has version
> > > > > >>> > > > > > 1012. import
xen.lowlevel.xc
> > > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
> >
> > RuntimeWarning:
> > > > > >>> > > > > > Python
> > > > > >>>
> > > > > >>> C
> > > > > >>>
> > > > > >>> > > > > > API version
mismatch for module acm: This Python has
> >
> > API
> >
> > > > > >>> version
> > > > > >>>
> > > > > >>> > > > > > 1013, module acm
has version 1012.
> > > > > >>> > > > > >   from
xen.lowlevel import acm
> > > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > > > > >>> > > > > > RuntimeWarning:
Python
> > > > > >>> > >
> > > > > >>> > > C
> > > > > >>> > >
> > > > > >>> > > > > API
> > > > > >>> > > > >
> > > > > >>> > > > > > version mismatch
for module xen.lowlevel.xs: This
> >
> > Python
> >
> > > > has
> > > >
> > > > > >>> API
> > > > > >>>
> > > > > >>> > > > > > version 1013,
module xen.lowlevel.xs has version
> > > > > >>> > > > > > 1012. import
xen.lowlevel.xs
> > > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > > > > >>> > > > > > RuntimeWarning:
Python
> > > > > >>> > >
> > > > > >>> > > C
> > > > > >>> > >
> > > > > >>> > > > > API
> > > > > >>> > > > >
> > > > > >>> > > > > > version mismatch
for module ptsname: This Python has
> >
> > API
> >
> > > > > >>> version
> > > > > >>>
> > > > > >>> > > 1013,
> > > > > >>> > >
> > > > > >>> > > > > > module ptsname
has version 1012.
> > > > > >>> > > > > >   from
xen.lowlevel import ptsname
> > > > > >>> > > > > >
/usr/lib/python/xen/xend/server/SrvDaemon.py:20:
> > > > > >>>
> > > > > >>> RuntimeWarning:
> > > > > >>> > > Python
> > > > > >>> > >
> > > > > >>> > > > > > C API version
mismatch for module xen.lowlevel.xc:
> > > > > >>> > > > > > This Python
> > > > > >>>
> > > > > >>> has
> > > > > >>>
> > > > > >>> > > API
> > > > > >>> > >
> > > > > >>> > > > > > version 1013,
module xen.lowlevel.xc has version
> > > > > >>> > > > > > 1012. import
xen.lowlevel.xc
> > > > > >>> > > > > >
/usr/lib/python/xen/util/security.py:25:
> >
> > RuntimeWarning:
> > > > > >>> > > > > > Python
> > > > > >>>
> > > > > >>> C
> > > > > >>>
> > > > > >>> > > > > > API version
mismatch for module acm: This Python has
> >
> > API
> >
> > > > > >>> version
> > > > > >>>
> > > > > >>> > > > > > 1013, module acm
has version 1012.
> > > > > >>> > > > > >   from
xen.lowlevel import acm
> > > > > >>> > > > > >
/usr/lib/python/xen/xend/xenstore/xsutil.py:8:
> > > > > >>> > > > > > RuntimeWarning:
Python
> > > > > >>> > >
> > > > > >>> > > C
> > > > > >>> > >
> > > > > >>> > > > > API
> > > > > >>> > > > >
> > > > > >>> > > > > > version mismatch
for module xen.lowlevel.xs: This
> >
> > Python
> >
> > > > has
> > > >
> > > > > >>> API
> > > > > >>>
> > > > > >>> > > > > > version 1013,
module xen.lowlevel.xs has version
> > > > > >>> > > > > > 1012. import
xen.lowlevel.xs
> > > > > >>> > > > > >
/usr/lib/python/xen/xend/XendBootloader.py:25:
> > > > > >>> > > > > > RuntimeWarning:
Python
> > > > > >>> > >
> > > > > >>> > > C
> > > > > >>> > >
> > > > > >>> > > > > API
> > > > > >>> > > > >
> > > > > >>> > > > > > version mismatch
for module ptsname: This Python has
> >
> > API
> >
> > > > > >>> version
> > > > > >>>
> > > > > >>> > > 1013,
> > > > > >>> > >
> > > > > >>> > > > > > module ptsname
has version 1012.
> > > > > >>> > > > > >   from
xen.lowlevel import ptsname
> > > > > >>> > > > > >
> > > > > >>> > > > > > I have tried to
install python from Sid and Lenny
> > > > > >>> > > > > > versions but
> > > > > >>>
> > > > > >>> none
> > > > > >>>
> > > > > >>> > > > > > seem
> > > > > >>> > > > >
> > > > > >>> > > > > to
> > > > > >>> > > > >
> > > > > >>> > > > > > change any of
this... I have no Python knowledge at
> > > > > >>> > > > > > all so
> > > >
> > > > I
> > > >
> > > > > >>> would
> > > > > >>>
> > > > > >>> > > like
> > > > > >>> > >
> > > > > >>> > > > > to
> > > > > >>> > > > >
> > > > > >>> > > > > > know if anybody
would happen to have an idea
> > > > > >>> > > > > > concerning
> > > >
> > > > this
> > > >
> > > > > >>> > > > > > problem.
> > > > > >>> > > > > >
> > > > > >>> > > > > > I will be happy
to give you more info if there is
> > > > > >>> > > > > > something
> > > > > >>>
> > > > > >>> missing
> > > > > >>>
> > > > > >>> > > in
> > > > > >>> > >
> > > > > >>> > > > > this
> > > > > >>> > > > >
> > > > > >>> > > > > > post.
> > > > > >>> > > > > >
> > > > > >>> > > > > > Thank you in
advance for your help,
> > > > > >>> > > > > >
> > > > > >>> > > > > > Antoine Benkemoun
> > > > > >>> > > > >
> > > > > >>> > > > > --
> > > > > >>> > > > > Push Me Pull You -
Distributed SCM tool (
> > > > > >>> > > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.
> > > > > >>> > > >
>ac.uk/%7Emaw48/pmpu/>
> >
> > <http://www.cl.cam.ac.u
> >
> > > > > >>> > > > >k/%7Emaw48/pmpu/>
> > > >
> > > > <http://www.cl.cam.ac.uk/%7
> > > >
> > > > > >>> > > > >Emaw48/pmpu/>
> > > > > >>>
> > > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48
> > > > > >>>
> > > > > >>> > > > >/pmpu/>
> > > > > >>> > >
> > > > > >>> > >
<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > > > > >>> > >
> > > > > >>> > > > >u/> )
> > > > > >>> > >
> > > > > >>> > > --
> > > > > >>> > > Push Me Pull You - Distributed
SCM tool (
> > > > > >>> > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.u
> > > > > >>> > >k/%7Emaw48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7
> >
> > > > > >>> > >Emaw48/pmpu/>
> > > >
> > > > <http://www.cl.cam.ac.uk/%7Emaw
> > > >
> > > > > >>> > >48/pmpu/>
> > > > > >>>
> > > > > >>> <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> > > > > >>>
> > > > > >>> > >u/> )
> > > > > >>>
> > > > > >>> --
> > > > > >>> Push Me Pull You - Distributed SCM tool (
> > > > > >>>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7
> > > > > >>>Emaw48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw
> >
> > > > > >>>48/pmpu/>
> > > >
> > > > <http://www.cl.cam.ac.uk/%7Emaw48/p
> > > >
> > > > > >>>mpu/> )
> > > > > >>
> > > > > >> --
> > > > > >> Antoine Benkemoun
> > > > > >> Tel : 03.51.53.57.00
> > > > > >> Port : 06.32.88.59.35
> > > > > >
> > > > > > --
> > > > > > Antoine Benkemoun
> > > > > > Tel : 03.51.53.57.00
> > > > > > Port : 06.32.88.59.35
> > > >
> > > > --
> > > > Push Me Pull You - Distributed SCM tool (
> > > >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48
> > > >/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >
> > > >u/> )
> >
> > --
> > Push Me Pull You - Distributed SCM tool (
> >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >u/> )


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

According to Novell, Xen has a flaw that in fact means it is useless. I have a
single supported system with SLES SP2, where I have 3 Windows VM''s and
5 Linux VM''s. In each of the Windows VM''s I have 8 Virtual
CPU''s, because I have a vital SQL Server installed where my company
runs all its business. The data comes precisely from the Linux virtual machines,
and having the database "right there" has proven extremely efficient.
But all my three Windows VM''s crashed simultaneously yesterday and I
lost two hours of business. I am using of course the right Novell drivers, etc.,
every piece of the puzzle in place. Novell already checked that. The engineers
showed me a technical note that says that having more than one Virtual CPU in a
Windows VM leads to crashes. But then we cannot have any windows VM at all,
hello!!! This means that the $35.000 box that I bought is the wrong box, because
now I need to remove my windows VM and create a separate windows installation,
and order more hardware, spend more money. It means that XEN is useless, because
if it only can virtualize Linux, actually Virtuozzo (Open VZ) has a lot less
overhead, far less. The beauty of Xen is that it is supposed to virtualize
Windows and Linux together. Now, that dream is gone. In case somebody wants to
look at my Novell case number, it is



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

Subject: The death of XEN by Novell (case number 10406546031)

According to Novell, Xen has a flaw that in fact means it is useless. I have a
single supported system with SLES SP2, where I have 3 Windows VM''s and
5 Linux VM''s. In each of the Windows VM''s I have 8 Virtual
CPU''s, because I have a vital SQL Server installed where my company
runs all its business. The data comes precisely from the Linux virtual machines,
and having the database "right there" has proven extremely efficient.
But all my three Windows VM''s crashed simultaneously yesterday and I
lost two hours of business. I am using of course the right Novell drivers, etc.,
every piece of the puzzle in place. Novell already checked that. The engineers
showed me a technical note that says that having more than one Virtual CPU in a
Windows VM leads to crashes. But then we cannot have any windows VM at all,
hello!!! This means that the $35.000 box that I bought is the wrong box, because
now I need to remove my windows VM and create a separate windows installation,
and order more hardware, spend more money. It means that XEN is useless, because
if it only can virtualize Linux, actually Virtuozzo (Open VZ) has a lot less
overhead, far less. The beauty of Xen is that it is supposed to virtualize
Windows and Linux together. Now, that dream is gone. In case somebody wants to
look at my Novell case number, it is 10406546031




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

Venefax schreef:
> But all my three Windows VM''s crashed
> simultaneously yesterday and I lost two hours of business.
Going offline without errors in testing sounds like bad testing, mkay?
> I am using
> of course the right Novell drivers, etc., every piece of the puzzle
> in place. Novell already checked that. The engineers showed me a
> technical note that says that having more than one Virtual CPU in a
> Windows VM leads to crashes. But then we cannot have any windows VM
> at all, hello!!! 
It only means that SMP under Windows is badly supported. Are you using 
the OpenSource Xen or the Citrix commercial one?
> The beauty of Xen is that it is supposed to
> virtualize Windows and Linux together. Now, that dream is gone. In
> case somebody wants to look at my Novell case number, it is
Try to limit the Windows installations to only one virtual CPU, no SMP 
troubles, more fun.

So just be wise, disable the 8 VCPU''s per windows installation, and
give
your windows installations one dedictated VCPU, dedicate one to the Dom0 
too, and make your Linux ones float around.


Stefan

35k for one box... that sounds... overpriced :)

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

> 
> Subject: The death of XEN by Novell (case number 10406546031)
> 
> According to Novell, Xen has a flaw that in fact means it is useless.
Is this your interpretation of Novell''s response or have Novell come
out
and said that "Our product is useless"? Are you able to paste the text
of the support ticket or is it bound by some confidentiality agreement?
> I
> have a single supported system with SLES SP2, where I have 3 Windows
VM''s
> and 5 Linux VM''s. In each of the Windows VM''s I have 8
Virtual CPU''s,
> because I have a vital SQL Server installed where my company runs all
its
> business. The data comes precisely from the Linux virtual machines,
and
> having the database "right there" has proven extremely efficient.
But
all
> my three Windows VM''s crashed simultaneously yesterday and I lost
two
> hours of business.
Can you tell us more about the crash?

Was it really simultaneous (as best as you can tell) or did the domains
just crash at about the same time?

What errors were in the logs (xm dmesg, dmesg, /var/log/xen/*)?

Did Dom0 crash as well?

The only time I''ve had more than one domain crash near-simultaneously
was when the oom-killer decided that the qemu-dm processes weren''t
important and killed them to free up memory.
> I am using of course the right Novell drivers, etc.,
> every piece of the puzzle in place. Novell already checked that. The
> engineers showed me a technical note that says that having more than
one
> Virtual CPU in a Windows VM leads to crashes.
Can you post a link to that technical note? Is it ">1 CPU leads to
crashes", or ">1 CPU may lead to crashes on this specific hardware
under
these specific conditions"? Is it a Novell specific problem or a more
general problem? 
> But then we cannot have any
> windows VM at all, hello!!! This means that the $35.000 box that I
bought
> is the wrong box, because now I need to remove my windows VM and
create a
> separate windows installation, and order more hardware, spend more
money.
> It means that XEN is useless, because if it only can virtualize Linux,
> actually Virtuozzo (Open VZ) has a lot less overhead, far less. The
beauty
> of Xen is that it is supposed to virtualize Windows and Linux
together.
> Now, that dream is gone. In case somebody wants to look at my Novell
case
> number, it is 10406546031
Was this an invitation to internal Novell support personal or is it
viewable by anyone?

Are you actually after assistance here or just sounding off? (that''s a
genuine question, imho everyone is allowed to spit the dummy once in a
while.)

Also, Novell aren''t the only suppliers of Xen solutions...

James


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

The Novell engineer showed me, and it has been confirmed in this list, that
Windows with more than one virtual CPU crashes. An crashing it did. I woke
up with angry calls from customers and when I logged in, all my 3 Windows
VM''s (two windows 2008 Datacenter with 32 GB and 8 VCPU and one Windows
2003
Enterprise with 16 GB and 8 VCPU''s)  were in blue screen. The memory
dump
process was stuck I guess because since the hard drives use the Novell
para-virtualized drivers, then at a blue-screen time you cannot collect any
memory dump. But the fact is that the engineer showed me that advisory note
in the Novell web site, saying I had been wasting my time, and now I am
buying a second $15.000 box to relocate my three windows VM´s. This is joke.


-----Original Message-----
From: James Harper [mailto:james.harper@bendigoit.com.au] 
Sent: Sunday, July 20, 2008 12:08 AM
To: Venefax; Mark Williamson; Antoine Benkemoun; Ky Srinivasan; Lynn
Bendixsen
Cc: xen-users@lists.xensource.com; stephen.spector@citrix.com
Subject: RE: [Xen-users] The death of XEN by Novell
> 
> Subject: The death of XEN by Novell (case number 10406546031)
> 
> According to Novell, Xen has a flaw that in fact means it is useless.
Is this your interpretation of Novell''s response or have Novell come
out
and said that "Our product is useless"? Are you able to paste the text
of the support ticket or is it bound by some confidentiality agreement?
> I
> have a single supported system with SLES SP2, where I have 3 Windows
VM''s
> and 5 Linux VM''s. In each of the Windows VM''s I have 8
Virtual CPU''s,
> because I have a vital SQL Server installed where my company runs all
its
> business. The data comes precisely from the Linux virtual machines,
and
> having the database "right there" has proven extremely efficient.
But
all
> my three Windows VM''s crashed simultaneously yesterday and I lost
two
> hours of business.
Can you tell us more about the crash?

Was it really simultaneous (as best as you can tell) or did the domains
just crash at about the same time?

What errors were in the logs (xm dmesg, dmesg, /var/log/xen/*)?

Did Dom0 crash as well?

The only time I''ve had more than one domain crash near-simultaneously
was when the oom-killer decided that the qemu-dm processes weren''t
important and killed them to free up memory.
> I am using of course the right Novell drivers, etc.,
> every piece of the puzzle in place. Novell already checked that. The
> engineers showed me a technical note that says that having more than
one
> Virtual CPU in a Windows VM leads to crashes.
Can you post a link to that technical note? Is it ">1 CPU leads to
crashes", or ">1 CPU may lead to crashes on this specific hardware
under
these specific conditions"? Is it a Novell specific problem or a more
general problem? 
> But then we cannot have any
> windows VM at all, hello!!! This means that the $35.000 box that I
bought
> is the wrong box, because now I need to remove my windows VM and
create a
> separate windows installation, and order more hardware, spend more
money.
> It means that XEN is useless, because if it only can virtualize Linux,
> actually Virtuozzo (Open VZ) has a lot less overhead, far less. The
beauty
> of Xen is that it is supposed to virtualize Windows and Linux
together.
> Now, that dream is gone. In case somebody wants to look at my Novell
case
> number, it is 10406546031
Was this an invitation to internal Novell support personal or is it
viewable by anyone?

Are you actually after assistance here or just sounding off? (that''s a
genuine question, imho everyone is allowed to spit the dummy once in a
while.)

Also, Novell aren''t the only suppliers of Xen solutions...

James


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

On Sun, 2008-07-20 at 00:28 -0400, Venefax wrote:
> The Novell engineer showed me, and it has been confirmed in this list, that
> Windows with more than one virtual CPU crashes. An crashing it did. I woke
> up with angry calls from customers and when I logged in, all my 3 Windows
> VM''s (two windows 2008 Datacenter with 32 GB and 8 VCPU and one
Windows 2003
> Enterprise with 16 GB and 8 VCPU''s)  were in blue screen. The
memory dump
> process was stuck I guess because since the hard drives use the Novell
> para-virtualized drivers, then at a blue-screen time you cannot collect any
> memory dump. But the fact is that the engineer showed me that advisory note
> in the Novell web site, saying I had been wasting my time, and now I am
> buying a second $15.000 box to relocate my three windows VM´s. This is
joke.
While your original design did provide isolation, using only one machine
does introduce a single point of failure.

For around another .... $1000 (give or take, good deals can be found)
you can get 2 10G ethernet cards to give you the ultra low latency
between your physical servers. The people on this list and the Xen
developers can not be held reasonably accountable for the cost of doing
business any more than they can be held accountable for the weather.
Life is what happens while your making other plans.

I would suggest that moving the SQL servers to their own home should
have been part of the original design, regardless of the underlying
operating system or method of virtualization.

Its not Xen''s fault that your design did not work as you planned. Xen
does what Xen does as Xen evolves. Xen does not hide its bugs or
shortcomings, as the Novell engineer pointed out.

Many people come to this list and say:

"Here is my idea, here''s how I hope to implement it,
here''s what I
expect it to do .. any suggestions?"

Upon such a message, some of the best engineers in the industry that
work with Xen daily offer helpful suggestions and point out potential
pitfalls. Many have gone way beyond just deploying Xen, many hack at Xen
daily to get it to do what they need it to do. I don''t remember you
sending such a message, perhaps I missed it?

I do understand your frustration, don''t get me wrong .. but I really
feel as though you might be alienating a valuable future resource.

Regards,
--Tim



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

On Sun, Jul 20, 2008 at 12:28:45AM -0400, Venefax wrote:
> The Novell engineer showed me, and it has been confirmed in this list, that
> Windows with more than one virtual CPU crashes. An crashing it did. I woke
> up with angry calls from customers and when I logged in, all my 3 Windows
> VM''s (two windows 2008 Datacenter with 32 GB and 8 VCPU and one
Windows 2003
> Enterprise with 16 GB and 8 VCPU''s)  were in blue screen. The
memory dump
> process was stuck I guess because since the hard drives use the Novell
> para-virtualized drivers, then at a blue-screen time you cannot collect any
> memory dump. But the fact is that the engineer showed me that advisory note
> in the Novell web site, saying I had been wasting my time, and now I am
> buying a second $15.000 box to relocate my three windows VM´s. This is
joke.
>
Does Novell advertise their Xen in SLES supports Windows SMP? 

"Confirmed in this list" .. can you please send a link to such email? 

Is there a bugzilla entry about this bug in Novell''s bug database or
Xensource''s
bugzilla? 

-- Pasi
 
> 
> -----Original Message-----
> From: James Harper [mailto:james.harper@bendigoit.com.au] 
> Sent: Sunday, July 20, 2008 12:08 AM
> To: Venefax; Mark Williamson; Antoine Benkemoun; Ky Srinivasan; Lynn
> Bendixsen
> Cc: xen-users@lists.xensource.com; stephen.spector@citrix.com
> Subject: RE: [Xen-users] The death of XEN by Novell
> 
> > 
> > Subject: The death of XEN by Novell (case number 10406546031)
> > 
> > According to Novell, Xen has a flaw that in fact means it is useless.
> 
> Is this your interpretation of Novell''s response or have Novell
come out
> and said that "Our product is useless"? Are you able to paste the
text
> of the support ticket or is it bound by some confidentiality agreement?
> 
> > I
> > have a single supported system with SLES SP2, where I have 3 Windows
> VM''s
> > and 5 Linux VM''s. In each of the Windows VM''s I have
8 Virtual CPU''s,
> > because I have a vital SQL Server installed where my company runs all
> its
> > business. The data comes precisely from the Linux virtual machines,
> and
> > having the database "right there" has proven extremely
efficient. But
> all
> > my three Windows VM''s crashed simultaneously yesterday and I
lost two
> > hours of business.
> 
> Can you tell us more about the crash?
> 
> Was it really simultaneous (as best as you can tell) or did the domains
> just crash at about the same time?
> 
> What errors were in the logs (xm dmesg, dmesg, /var/log/xen/*)?
> 
> Did Dom0 crash as well?
> 
> The only time I''ve had more than one domain crash
near-simultaneously
> was when the oom-killer decided that the qemu-dm processes weren''t
> important and killed them to free up memory.
> 
> > I am using of course the right Novell drivers, etc.,
> > every piece of the puzzle in place. Novell already checked that. The
> > engineers showed me a technical note that says that having more than
> one
> > Virtual CPU in a Windows VM leads to crashes.
> 
> Can you post a link to that technical note? Is it ">1 CPU leads to
> crashes", or ">1 CPU may lead to crashes on this specific
hardware under
> these specific conditions"? Is it a Novell specific problem or a more
> general problem? 
> 
> > But then we cannot have any
> > windows VM at all, hello!!! This means that the $35.000 box that I
> bought
> > is the wrong box, because now I need to remove my windows VM and
> create a
> > separate windows installation, and order more hardware, spend more
> money.
> > It means that XEN is useless, because if it only can virtualize Linux,
> > actually Virtuozzo (Open VZ) has a lot less overhead, far less. The
> beauty
> > of Xen is that it is supposed to virtualize Windows and Linux
> together.
> > Now, that dream is gone. In case somebody wants to look at my Novell
> case
> > number, it is 10406546031
> 
> Was this an invitation to internal Novell support personal or is it
> viewable by anyone?
> 
> Are you actually after assistance here or just sounding off?
(that''s a
> genuine question, imho everyone is allowed to spit the dummy once in a
> while.)
> 
> Also, Novell aren''t the only suppliers of Xen solutions...
> 
> James
> 
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Jul 20, 2008 at 04:12:11PM +0300, Pasi Kärkkäinen
wrote:
> On Sun, Jul 20, 2008 at 12:28:45AM -0400, Venefax wrote:
> > The Novell engineer showed me, and it has been confirmed in this list,
that
> > Windows with more than one virtual CPU crashes. An crashing it did. I
woke
> > up with angry calls from customers and when I logged in, all my 3
Windows
> > VM''s (two windows 2008 Datacenter with 32 GB and 8 VCPU and
one Windows 2003
> > Enterprise with 16 GB and 8 VCPU''s)  were in blue screen. The
memory dump
> > process was stuck I guess because since the hard drives use the Novell
> > para-virtualized drivers, then at a blue-screen time you cannot
collect any
> > memory dump. But the fact is that the engineer showed me that advisory
note
> > in the Novell web site, saying I had been wasting my time, and now I
am
> > buying a second $15.000 box to relocate my three windows VM´s. This is
joke.
> >
> 
> Does Novell advertise their Xen in SLES supports Windows SMP? 
>
http://www.novell.com/rc/docrepository/public/37/basedocument.2008-06-10.9752681390/SUSE_Linux_Enterprise_10_SP2_Virtualization_Technology_Support_Technical_White_Paper_en.pdf

"Virtual machine limits per VM"

"Virtual CPUs, full virtualization (FV) 1-4"

"Novell support is currently limited to four virtual CPUs for fully
virtualized VMs"

Where did you read Novell supports 8 vCPUs for Windows? 

With a quick look I didn''t find anything about Novell supported maximum
amount of
memory.. 

-- Pasi

 
> "Confirmed in this list" .. can you please send a link to such
email?
> 
> Is there a bugzilla entry about this bug in Novell''s bug database
or Xensource''s
> bugzilla? 
> 
> -- Pasi
>  
> > 
> > -----Original Message-----
> > From: James Harper [mailto:james.harper@bendigoit.com.au] 
> > Sent: Sunday, July 20, 2008 12:08 AM
> > To: Venefax; Mark Williamson; Antoine Benkemoun; Ky Srinivasan; Lynn
> > Bendixsen
> > Cc: xen-users@lists.xensource.com; stephen.spector@citrix.com
> > Subject: RE: [Xen-users] The death of XEN by Novell
> > 
> > > 
> > > Subject: The death of XEN by Novell (case number 10406546031)
> > > 
> > > According to Novell, Xen has a flaw that in fact means it is
useless.
> > 
> > Is this your interpretation of Novell''s response or have
Novell come out
> > and said that "Our product is useless"? Are you able to
paste the text
> > of the support ticket or is it bound by some confidentiality
agreement?
> > 
> > > I
> > > have a single supported system with SLES SP2, where I have 3
Windows
> > VM''s
> > > and 5 Linux VM''s. In each of the Windows VM''s I
have 8 Virtual CPU''s,
> > > because I have a vital SQL Server installed where my company runs
all
> > its
> > > business. The data comes precisely from the Linux virtual
machines,
> > and
> > > having the database "right there" has proven extremely
efficient. But
> > all
> > > my three Windows VM''s crashed simultaneously yesterday
and I lost two
> > > hours of business.
> > 
> > Can you tell us more about the crash?
> > 
> > Was it really simultaneous (as best as you can tell) or did the
domains
> > just crash at about the same time?
> > 
> > What errors were in the logs (xm dmesg, dmesg, /var/log/xen/*)?
> > 
> > Did Dom0 crash as well?
> > 
> > The only time I''ve had more than one domain crash
near-simultaneously
> > was when the oom-killer decided that the qemu-dm processes
weren''t
> > important and killed them to free up memory.
> > 
> > > I am using of course the right Novell drivers, etc.,
> > > every piece of the puzzle in place. Novell already checked that.
The
> > > engineers showed me a technical note that says that having more
than
> > one
> > > Virtual CPU in a Windows VM leads to crashes.
> > 
> > Can you post a link to that technical note? Is it ">1 CPU
leads to
> > crashes", or ">1 CPU may lead to crashes on this specific
hardware under
> > these specific conditions"? Is it a Novell specific problem or a
more
> > general problem? 
> > 
> > > But then we cannot have any
> > > windows VM at all, hello!!! This means that the $35.000 box that
I
> > bought
> > > is the wrong box, because now I need to remove my windows VM and
> > create a
> > > separate windows installation, and order more hardware, spend
more
> > money.
> > > It means that XEN is useless, because if it only can virtualize
Linux,
> > > actually Virtuozzo (Open VZ) has a lot less overhead, far less.
The
> > beauty
> > > of Xen is that it is supposed to virtualize Windows and Linux
> > together.
> > > Now, that dream is gone. In case somebody wants to look at my
Novell
> > case
> > > number, it is 10406546031
> > 
> > Was this an invitation to internal Novell support personal or is it
> > viewable by anyone?
> > 
> > Are you actually after assistance here or just sounding off?
(that''s a
> > genuine question, imho everyone is allowed to spit the dummy once in a
> > while.)
> > 
> > Also, Novell aren''t the only suppliers of Xen solutions...
> > 
> > James
> > 
> > 
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

The Novell engineer showed me a technical document, which I did not write
the number, on the Novell web site, where it said: windows SMP using the
Novell driver crashes. On Monday I will talk to her and get the number.
Also all the responses to my post in the list confirm that. The point is:
unless SMP works, the whole technology is useless, because what use would it
have a single VCPU machine? That´s why I am jumping over to Hyper-V. The
problem is that I don''t know how good the emulation of Linux is under
Hyper-V. Does the network work fast? I use a SIP Server on the Linux side,
talking hundreds of times per second to SQL Server, so I need SMP 8 ways on
both  ends. But my Linux softswiches also move megabytes of data in and out
of the network, media, voice. It requires low latency. Maybe I need to
forget about virtualizing Windows ands Linux together.

-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@iki.fi] 
Sent: Sunday, July 20, 2008 9:42 AM
To: Venefax
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] The death of XEN by Novell

On Sun, Jul 20, 2008 at 04:12:11PM +0300, Pasi Kärkkäinen
wrote:
> On Sun, Jul 20, 2008 at 12:28:45AM -0400, Venefax wrote:
> > The Novell engineer showed me, and it has been confirmed in this list,
that
> > Windows with more than one virtual CPU crashes. An crashing it did. I
woke
> > up with angry calls from customers and when I logged in, all my 3
Windows
> > VM''s (two windows 2008 Datacenter with 32 GB and 8 VCPU and
one Windows
2003
> > Enterprise with 16 GB and 8 VCPU''s)  were in blue screen. The
memory
dump
> > process was stuck I guess because since the hard drives use the Novell
> > para-virtualized drivers, then at a blue-screen time you cannot
collect
any
> > memory dump. But the fact is that the engineer showed me that advisory
note
> > in the Novell web site, saying I had been wasting my time, and now I
am
> > buying a second $15.000 box to relocate my three windows VM´s. This is
joke.
> >
> 
> Does Novell advertise their Xen in SLES supports Windows SMP? 
>
http://www.novell.com/rc/docrepository/public/37/basedocument.2008-06-10.975
2681390/SUSE_Linux_Enterprise_10_SP2_Virtualization_Technology_Support_Techn
ical_White_Paper_en.pdf

"Virtual machine limits per VM"

"Virtual CPUs, full virtualization (FV) 1-4"

"Novell support is currently limited to four virtual CPUs for fully
virtualized VMs"

Where did you read Novell supports 8 vCPUs for Windows? 

With a quick look I didn''t find anything about Novell supported maximum
amount of
memory.. 

-- Pasi

 
> "Confirmed in this list" .. can you please send a link to such
email?
> 
> Is there a bugzilla entry about this bug in Novell''s bug database
or
Xensource''s
> bugzilla? 
> 
> -- Pasi
>  
> > 
> > -----Original Message-----
> > From: James Harper [mailto:james.harper@bendigoit.com.au] 
> > Sent: Sunday, July 20, 2008 12:08 AM
> > To: Venefax; Mark Williamson; Antoine Benkemoun; Ky Srinivasan; Lynn
> > Bendixsen
> > Cc: xen-users@lists.xensource.com; stephen.spector@citrix.com
> > Subject: RE: [Xen-users] The death of XEN by Novell
> > 
> > > 
> > > Subject: The death of XEN by Novell (case number 10406546031)
> > > 
> > > According to Novell, Xen has a flaw that in fact means it is
useless.
> > 
> > Is this your interpretation of Novell''s response or have
Novell come out
> > and said that "Our product is useless"? Are you able to
paste the text
> > of the support ticket or is it bound by some confidentiality
agreement?
> > 
> > > I
> > > have a single supported system with SLES SP2, where I have 3
Windows
> > VM''s
> > > and 5 Linux VM''s. In each of the Windows VM''s I
have 8 Virtual CPU''s,
> > > because I have a vital SQL Server installed where my company runs
all
> > its
> > > business. The data comes precisely from the Linux virtual
machines,
> > and
> > > having the database "right there" has proven extremely
efficient. But
> > all
> > > my three Windows VM''s crashed simultaneously yesterday
and I lost two
> > > hours of business.
> > 
> > Can you tell us more about the crash?
> > 
> > Was it really simultaneous (as best as you can tell) or did the
domains
> > just crash at about the same time?
> > 
> > What errors were in the logs (xm dmesg, dmesg, /var/log/xen/*)?
> > 
> > Did Dom0 crash as well?
> > 
> > The only time I''ve had more than one domain crash
near-simultaneously
> > was when the oom-killer decided that the qemu-dm processes
weren''t
> > important and killed them to free up memory.
> > 
> > > I am using of course the right Novell drivers, etc.,
> > > every piece of the puzzle in place. Novell already checked that.
The
> > > engineers showed me a technical note that says that having more
than
> > one
> > > Virtual CPU in a Windows VM leads to crashes.
> > 
> > Can you post a link to that technical note? Is it ">1 CPU
leads to
> > crashes", or ">1 CPU may lead to crashes on this specific
hardware under
> > these specific conditions"? Is it a Novell specific problem or a
more
> > general problem? 
> > 
> > > But then we cannot have any
> > > windows VM at all, hello!!! This means that the $35.000 box that
I
> > bought
> > > is the wrong box, because now I need to remove my windows VM and
> > create a
> > > separate windows installation, and order more hardware, spend
more
> > money.
> > > It means that XEN is useless, because if it only can virtualize
Linux,
> > > actually Virtuozzo (Open VZ) has a lot less overhead, far less.
The
> > beauty
> > > of Xen is that it is supposed to virtualize Windows and Linux
> > together.
> > > Now, that dream is gone. In case somebody wants to look at my
Novell
> > case
> > > number, it is 10406546031
> > 
> > Was this an invitation to internal Novell support personal or is it
> > viewable by anyone?
> > 
> > Are you actually after assistance here or just sounding off?
(that''s a
> > genuine question, imho everyone is allowed to spit the dummy once in a
> > while.)
> > 
> > Also, Novell aren''t the only suppliers of Xen solutions...
> > 
> > James
> > 
> > 
> 

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

On Sun, Jul 20, 2008 at 09:51:52AM -0400, Venefax wrote:
> The Novell engineer showed me a technical document, which I did not write
> the number, on the Novell web site, where it said: windows SMP using the
> Novell driver crashes. On Monday I will talk to her and get the number.
Hmm.. so it''s a bug in Novell''s windows driver or? 

And yeah, would be nice to see that document. 
> Also all the responses to my post in the list confirm that. The point is:
> unless SMP works, the whole technology is useless, because what use would
it
> have a single VCPU machine? That´s why I am jumping over to Hyper-V. The
> problem is that I don''t know how good the emulation of Linux is
under
> Hyper-V. Does the network work fast? I use a SIP Server on the Linux side,
> talking hundreds of times per second to SQL Server, so I need SMP 8 ways on
> both  ends. But my Linux softswiches also move megabytes of data in and out
> of the network, media, voice. It requires low latency. Maybe I need to
> forget about virtualizing Windows ands Linux together.
>
If you have two different server hardware now, just run paravirtualized
linux vm''s on the other one, and windows vm''s on the other
one..
 
-- Pasi
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi] 
> Sent: Sunday, July 20, 2008 9:42 AM
> To: Venefax
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] The death of XEN by Novell
> 
> On Sun, Jul 20, 2008 at 04:12:11PM +0300, Pasi Kärkkäinen wrote:
> > On Sun, Jul 20, 2008 at 12:28:45AM -0400, Venefax wrote:
> > > The Novell engineer showed me, and it has been confirmed in this
list,
> that
> > > Windows with more than one virtual CPU crashes. An crashing it
did. I
> woke
> > > up with angry calls from customers and when I logged in, all my 3
> Windows
> > > VM''s (two windows 2008 Datacenter with 32 GB and 8 VCPU
and one Windows
> 2003
> > > Enterprise with 16 GB and 8 VCPU''s)  were in blue
screen. The memory
> dump
> > > process was stuck I guess because since the hard drives use the
Novell
> > > para-virtualized drivers, then at a blue-screen time you cannot
collect
> any
> > > memory dump. But the fact is that the engineer showed me that
advisory
> note
> > > in the Novell web site, saying I had been wasting my time, and
now I am
> > > buying a second $15.000 box to relocate my three windows VM´s.
This is
> joke.
> > >
> > 
> > Does Novell advertise their Xen in SLES supports Windows SMP? 
> >
> 
>
http://www.novell.com/rc/docrepository/public/37/basedocument.2008-06-10.975
>
2681390/SUSE_Linux_Enterprise_10_SP2_Virtualization_Technology_Support_Techn
> ical_White_Paper_en.pdf
> 
> "Virtual machine limits per VM"
> 
> "Virtual CPUs, full virtualization (FV) 1-4"
> 
> "Novell support is currently limited to four virtual CPUs for fully
> virtualized VMs"
> 
> Where did you read Novell supports 8 vCPUs for Windows? 
> 
> With a quick look I didn''t find anything about Novell supported
maximum
> amount of
> memory.. 
> 
> -- Pasi
> 
>  
> > "Confirmed in this list" .. can you please send a link to
such email?
> > 
> > Is there a bugzilla entry about this bug in Novell''s bug
database or
> Xensource''s
> > bugzilla? 
> > 
> > -- Pasi
> >  
> > > 
> > > -----Original Message-----
> > > From: James Harper [mailto:james.harper@bendigoit.com.au] 
> > > Sent: Sunday, July 20, 2008 12:08 AM
> > > To: Venefax; Mark Williamson; Antoine Benkemoun; Ky Srinivasan;
Lynn
> > > Bendixsen
> > > Cc: xen-users@lists.xensource.com; stephen.spector@citrix.com
> > > Subject: RE: [Xen-users] The death of XEN by Novell
> > > 
> > > > 
> > > > Subject: The death of XEN by Novell (case number
10406546031)
> > > > 
> > > > According to Novell, Xen has a flaw that in fact means it is
useless.
> > > 
> > > Is this your interpretation of Novell''s response or have
Novell come out
> > > and said that "Our product is useless"? Are you able to
paste the text
> > > of the support ticket or is it bound by some confidentiality
agreement?
> > > 
> > > > I
> > > > have a single supported system with SLES SP2, where I have 3
Windows
> > > VM''s
> > > > and 5 Linux VM''s. In each of the Windows
VM''s I have 8 Virtual CPU''s,
> > > > because I have a vital SQL Server installed where my company
runs all
> > > its
> > > > business. The data comes precisely from the Linux virtual
machines,
> > > and
> > > > having the database "right there" has proven
extremely efficient. But
> > > all
> > > > my three Windows VM''s crashed simultaneously
yesterday and I lost two
> > > > hours of business.
> > > 
> > > Can you tell us more about the crash?
> > > 
> > > Was it really simultaneous (as best as you can tell) or did the
domains
> > > just crash at about the same time?
> > > 
> > > What errors were in the logs (xm dmesg, dmesg, /var/log/xen/*)?
> > > 
> > > Did Dom0 crash as well?
> > > 
> > > The only time I''ve had more than one domain crash
near-simultaneously
> > > was when the oom-killer decided that the qemu-dm processes
weren''t
> > > important and killed them to free up memory.
> > > 
> > > > I am using of course the right Novell drivers, etc.,
> > > > every piece of the puzzle in place. Novell already checked
that. The
> > > > engineers showed me a technical note that says that having
more than
> > > one
> > > > Virtual CPU in a Windows VM leads to crashes.
> > > 
> > > Can you post a link to that technical note? Is it ">1 CPU
leads to
> > > crashes", or ">1 CPU may lead to crashes on this
specific hardware under
> > > these specific conditions"? Is it a Novell specific problem
or a more
> > > general problem? 
> > > 
> > > > But then we cannot have any
> > > > windows VM at all, hello!!! This means that the $35.000 box
that I
> > > bought
> > > > is the wrong box, because now I need to remove my windows VM
and
> > > create a
> > > > separate windows installation, and order more hardware,
spend more
> > > money.
> > > > It means that XEN is useless, because if it only can
virtualize Linux,
> > > > actually Virtuozzo (Open VZ) has a lot less overhead, far
less. The
> > > beauty
> > > > of Xen is that it is supposed to virtualize Windows and
Linux
> > > together.
> > > > Now, that dream is gone. In case somebody wants to look at
my Novell
> > > case
> > > > number, it is 10406546031
> > > 
> > > Was this an invitation to internal Novell support personal or is
it
> > > viewable by anyone?
> > > 
> > > Are you actually after assistance here or just sounding off?
(that''s a
> > > genuine question, imho everyone is allowed to spit the dummy once
in a
> > > while.)
> > > 
> > > Also, Novell aren''t the only suppliers of Xen
solutions...
> > > 
> > > James
> > > 
> > > 
> > 
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun July 20 2008 9:51:52 am Venefax wrote:
> The Novell engineer showed me a technical document, which I did not write
> the number, on the Novell web site, where it said: windows SMP using the
> Novell driver crashes.
That''s what I thought - the problem is with Novell''s PV
drivers, not Xen.
James had some initial problems with SMP also.
>  I use a SIP Server on the Linux side, talking hundreds of times per second
> to SQL Server, so I need SMP 8 ways on both  ends.
Something I''ve never seen you actually say is that you *tried* vcpu=1,
and the
performance was bad. So far, it sounds like theory to me. Even with 1 vcpu, 
playing with scheduling weights should help.

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

Thanks for your comments. I need SMP since I use SQL Server inside Windows.
The Windows domu is just a wrapper for SQL Server. Without SMP I am dead.
The problem is that it crashes unexpectedly, so it cannot be trusted for
mission critical. You also want me to consider carefully before investing
$15.000. I lost already $5000 in one hour down. My XEN box moves $200.000 a
day in phone calls, all in one box with 6 Linux VM''s and 3 windows
VM''s. Do
you see the point? I don''t care if Novell would have charged me 10
times
more, as long as it works. The problem now is that to co-locate another big
box with 11 Amp of power consumption, I need to pay a lot of money per month
in hosting fees. So the effect is devastating for my business, it affects my
bottom line, since the profit is tiny.

-----Original Message-----
From: eric gisse [mailto:jowr.pi@gmail.com] 
Sent: Sunday, July 20, 2008 10:06 AM
To: Venefax
Subject: Re: [Xen-users] The death of XEN by Novell

I dunno, I''m in the process of setting up a bunch [60] dual core
workstations utilizing Xen with a windows and linux virtual machine
[HVM, PV] which will be utilized for general student work [Windows]
and clustering [Linux]. My testing so far has been remarkably
successful so I''m in the process of fully deploying it on a test
machine in preparation for a full deployment that''s contingent on it
_working_.

Isn''t the point of running Xen that you can have _many_ virtual
machines? Ok - worst case you cannot use many CPUs with a windows HVM.
So what? You have a tremendously powerful box - install more virtual
machines.

As for the performance of linux under virtualization, from the
benchmarks I have read you only lose ~5% performance by using a
_properly_ configured paravirtualized linux. However I''m not exactly
clear on your needs - are you doing the software routing [iptables?
ipcop? zebra? some other software router?] under virtualization or
within the hypervisor itself?

Not to be a purposeful dick though, but did you actually test out the
environment you wanted to build? What troubleshooting have you done?
Are you sure it is Xen and not some fault that propagated back into
the VM''s and killed them?

Since you are now plunking down another 15k on _another_ box, might I
suggest you calm the hell down and think for a little while before
spending more money? It sounds - to me - that rash decisionmaking got
you into this, and it won''t get you out in any painless fashion.

[...]


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

Dear Venefax,

On Sun, Jul 20, 2008 at 4:27 PM, Venefax <venefax@gmail.com> wrote:
> $15.000. I lost already $5000 in one hour down. My XEN box moves $200.000 a
> day in phone calls, all in one box with 6 Linux VM''s and 3 windows
VM''s. Do
>
I''m watching your thread silently, however, just a comment, if I were
you
who to loose $5000 in one hour and passing 200 kEur in a day, I would have
though three times on my system design. For such "realtime" business,
I
would be using load balancing failsafe redundant configurations (at least
two machines) and sleep well at night. I also would have done extensive
testing before I move all the systems to such Xen based configuration.

In such business, it can be deadly to use untested technologies.

Too many eggs in one basket...

Emre


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

On Sunday 20 July 2008, jim burns wrote:
> On Sun July 20 2008 9:51:52 am Venefax wrote:
> > The Novell engineer showed me a technical document, which I did not
write
> > the number, on the Novell web site, where it said: windows SMP using
the
> > Novell driver crashes.
>
> That''s what I thought - the problem is with Novell''s PV
drivers, not Xen.
> James had some initial problems with SMP also.
Right, that''s important.  Novell''s PV drivers are their code
so those drivers
might have limitations that plain Xen does not.  Presumably it would be 
possible to run using fully emulated IO instead of PV drivers but I imagine 
this could have performance problems in your configuration.  Could be worth a 
try, if you can afford to experiment.

If the Windows VMs themselves are crashing due to Novell''s PV drivers
then I''m
afraid this limitation / problem is really Novell''s responsibility and
they
would be the best people to approach for assistance / complaints.  The code 
for those drivers isn''t open, so only Novell can fix them.  If the
Novell PV
drivers are somehow crashing your Linux domains or dom0 or Xen itself then 
that might be a Xen bug and it would be useful to post more details here.

For comparison, Citrix/XenSource supply with their product PV drivers for 
Windows that are - AFAIK - a different codebase and may not have these 
limitations.  So do Virtual Iron, for their Xen-based product.  Both of these 
can only be used with their respective commercial hypervisors, AFAIK.  James 
Harper''s PV drivers for Windows are GPL but still under development and
so I
doubt they''d be recommended for heavy production use.

There are a lot of different PV driver solutions for Windows about and none of 
them are officially part of the OSS Xen project; only one of them is even 
Open Source.
> >  I use a SIP Server on the Linux side, talking hundreds of times per
> > second to SQL Server, so I need SMP 8 ways on both  ends.
>
> Something I''ve never seen you actually say is that you *tried*
vcpu=1, and
> the performance was bad. So far, it sounds like theory to me. Even with 1
> vcpu, playing with scheduling weights should help.
Venefax, are you able to try this?

Thank you,
Mark


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

I am using Xen 3.0 and currently NTP on my virtual image time kept drifting.
I read the XEN documentation and it say to set the independent_clock on the
base machine to 1, But still my virtual image time will drift and screw up.


Any Help or solutions to this problem anybody?


Choon kiat



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

Mark Williamson schrieb:
> On Sunday 20 July 2008, jim burns wrote:
>> On Sun July 20 2008 9:51:52 am Venefax wrote:
>>> The Novell engineer showed me a technical document, which I did not
write
>>> the number, on the Novell web site, where it said: windows SMP
using the
>>> Novell driver crashes.
>> That''s what I thought - the problem is with Novell''s
PV drivers, not Xen.
>> James had some initial problems with SMP also.
> 
> Right, that''s important.  Novell''s PV drivers are their
code so those drivers
> might have limitations that plain Xen does not.  Presumably it would be 
> possible to run using fully emulated IO instead of PV drivers but I imagine
> this could have performance problems in your configuration.  Could be worth
a
> try, if you can afford to experiment.
> 
> If the Windows VMs themselves are crashing due to Novell''s PV
drivers then I''m
> afraid this limitation / problem is really Novell''s responsibility
and they
> would be the best people to approach for assistance / complaints.  The code
> for those drivers isn''t open, so only Novell can fix them.  If the
Novell PV
> drivers are somehow crashing your Linux domains or dom0 or Xen itself then 
> that might be a Xen bug and it would be useful to post more details here.
> 
> For comparison, Citrix/XenSource supply with their product PV drivers for 
> Windows that are - AFAIK - a different codebase and may not have these 
> limitations.  So do Virtual Iron, for their Xen-based product.  Both of
these
> can only be used with their respective commercial hypervisors, AFAIK. 
James
> Harper''s PV drivers for Windows are GPL but still under
development and so I
> doubt they''d be recommended for heavy production use.
> 
> There are a lot of different PV driver solutions for Windows about and none
of
> them are officially part of the OSS Xen project; only one of them is even 
> Open Source.
> 
I really wonder why you run your SQL servers in windows and all the rest 
in Linux???
I asume especially for databases is Windows a bad base, but i have a 
win20008 sharepoint running on xen 3.2.1 with 2 vcpus it works great and 
stable with james drives.
And if you like to use this single Box, you may ask SUN (Solaris and 
SunXvm).

florian
>>>  I use a SIP Server on the Linux side, talking hundreds of times
per
>>> second to SQL Server, so I need SMP 8 ways on both  ends.
>> Something I''ve never seen you actually say is that you *tried*
vcpu=1, and
>> the performance was bad. So far, it sounds like theory to me. Even with
1
>> vcpu, playing with scheduling weights should help.
> 
> Venefax, are you able to try this?
> 
> Thank you,
> Mark
> 
> 


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

SQL Server only runs in Windows. I am now actually learning DB2 in order to
use a Linux-based database. But of course I am not dumb to put my entire
business on a database I cannot support, yet, the way I do with SQL Server.
And the beauty is the with XEN-Windows 2008, SQL Server runs perfectly,
unless Windows crashes.

-----Original Message-----
From: Florian Manschwetus [mailto:florianmanschwetus@gmx.de] 
Sent: Sunday, July 20, 2008 12:30 PM
To: Mark Williamson
Cc: xen-users@lists.xensource.com; Venefax; jim burns
Subject: Re: [Xen-users] The death of XEN by Novell

Mark Williamson schrieb:
> On Sunday 20 July 2008, jim burns wrote:
>> On Sun July 20 2008 9:51:52 am Venefax wrote:
>>> The Novell engineer showed me a technical document, which I did not
write
>>> the number, on the Novell web site, where it said: windows SMP
using the
>>> Novell driver crashes.
>> That''s what I thought - the problem is with Novell''s
PV drivers, not Xen.
>> James had some initial problems with SMP also.
> 
> Right, that''s important.  Novell''s PV drivers are their
code so those
drivers 
> might have limitations that plain Xen does not.  Presumably it would be 
> possible to run using fully emulated IO instead of PV drivers but I
imagine 
> this could have performance problems in your configuration.  Could be
worth a 
> try, if you can afford to experiment.
> 
> If the Windows VMs themselves are crashing due to Novell''s PV
drivers then
I''m 
> afraid this limitation / problem is really Novell''s responsibility
and
they 
> would be the best people to approach for assistance / complaints.  The
code 
> for those drivers isn''t open, so only Novell can fix them.  If the
Novell
PV 
> drivers are somehow crashing your Linux domains or dom0 or Xen itself then
> that might be a Xen bug and it would be useful to post more details here.
> 
> For comparison, Citrix/XenSource supply with their product PV drivers for 
> Windows that are - AFAIK - a different codebase and may not have these 
> limitations.  So do Virtual Iron, for their Xen-based product.  Both of
these 
> can only be used with their respective commercial hypervisors, AFAIK.
James 
> Harper''s PV drivers for Windows are GPL but still under
development and so
I 
> doubt they''d be recommended for heavy production use.
> 
> There are a lot of different PV driver solutions for Windows about and
none of 
> them are officially part of the OSS Xen project; only one of them is even 
> Open Source.
> 
I really wonder why you run your SQL servers in windows and all the rest 
in Linux???
I asume especially for databases is Windows a bad base, but i have a 
win20008 sharepoint running on xen 3.2.1 with 2 vcpus it works great and 
stable with james drives.
And if you like to use this single Box, you may ask SUN (Solaris and 
SunXvm).

florian
>>>  I use a SIP Server on the Linux side, talking hundreds of times
per
>>> second to SQL Server, so I need SMP 8 ways on both  ends.
>> Something I''ve never seen you actually say is that you *tried*
vcpu=1,
and
>> the performance was bad. So far, it sounds like theory to me. Even with
1
>> vcpu, playing with scheduling weights should help.
> 
> Venefax, are you able to try this?
> 
> Thank you,
> Mark
> 
> 


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

Venefax wrote:
> But of course I am not dumb to put my entire
> business on a database I cannot support, yet, the way I do with SQL Server.
> And the beauty is the with XEN-Windows 2008, SQL Server runs perfectly,
> unless Windows crashes.
> 
But of course you will put your entire operation on one machine with no 
redundancy. You are bringing in 200k a day and you buy one server to run 
everything? What testing had you done before hand to ensure that your 
setup would work as planned, and what was your plan for failure?

Your blaming Xen for your lack of testing and foresight is ridiculous at 
best. Xen doesn''t have the flaw, Novell''s drivers have the
flaw. Build
from source or try a different vendor and ask them to validate your 
setup before you go live with mission critical applications.

But now you want to go with M$ and their VM solution and you ask 
questions here? Go ask M$ and let them tell you what you need to do and 
how to do it. But remember their motto, "Marketing, where the rubber 
meets the sky.", or something like that.

Jon

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

Venefax wrote:
> SQL Server only runs in Windows. I am now actually learning DB2 in order to
> use a Linux-based database. But of course I am not dumb to put my entire
> business on a database I cannot support, yet, the way I do with SQL Server.
> And the beauty is the with XEN-Windows 2008, SQL Server runs perfectly,
> unless Windows crashes.
>
>   
The way I see it, Xen (the opensource project) does not have an official 
windows PV driver. Meaning using it to run production Windows is 
downright silly, since you can expect reduced performance. James has 
created gplpv driver, which is good for testing purposes (AFAIK it works 
best on Xen 3.2, linux dom0). I wouldnt use it on production systems yet 
though.

If you want to use Windows, production environment, under Xen, your best 
bet (at the moment) is to try either Novell or Citrix''s commercial 
version. Even then you need to read carefully what configuration they 
support. In this case, when Novell said "windows SMP using the Novell 
driver crashes", then the logical choice would be :
- follow their advice, don''t use SMP, or
- dump Novell, go with Citrix, or
- use other virtualization technology.

Vmware provides Vmware server for free, perhaps that would be better for 
you.

Regards,

Fajar



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

On Sunday 20 July 2008, Fajar A. Nugraha wrote:
> Vmware provides Vmware server for free, perhaps that would be better for
> you.
VMWare Server, being a "Try for free, the next will cost you" product,
is
limited to 2CPU per VM.  Given his requirement of 8CPUs per VM (real or not), 
free VMWare Server is not an option.


-- 
Javier


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

First of all, your boss should fire you for saying "windows 2008 sql  
server runs perfectly unless windows crashes"

Secondly, whoever delivered the xen solution on your 200k per day  
production server should be fired for not understanding the concept of  
single point of failure.

Now that you learned the lesson at 5k per hour,you should dump virtual  
machines and have redundant physical machines for mission critical  
services on your network.  For 200k a day, that is 72million a year  
revenue, you should have a budget of at least 5 to 7 mil to handle  
redundancy issues, which means double or even triple redundancy  
networks and San storage for database servers.

Lastly, I think that either your boss bluffed you with 5k per hour  
cost of downtime, or you did, since I cannot imagine such incompetent  
people running a business valued at 15 times earning or hundreds of  
millions if your 72 million revenue figure is indeed correct.

Btw, xen is maintained by citrix, not Novell.

On Jul 20, 2008, at 11:36 AM, "Venefax" <venefax@gmail.com>
wrote:
> SQL Server only runs in Windows. I am now actually learning DB2 in  
> order to
> use a Linux-based database. But of course I am not dumb to put my  
> entire
> business on a database I cannot support, yet, the way I do with SQL  
> Server.
> And the beauty is the with XEN-Windows 2008, SQL Server runs  
> perfectly,
> unless Windows crashes.
>
> -----Original Message-----
> From: Florian Manschwetus [mailto:florianmanschwetus@gmx.de]
> Sent: Sunday, July 20, 2008 12:30 PM
> To: Mark Williamson
> Cc: xen-users@lists.xensource.com; Venefax; jim burns
> Subject: Re: [Xen-users] The death of XEN by Novell
>
> Mark Williamson schrieb:
>> On Sunday 20 July 2008, jim burns wrote:
>>> On Sun July 20 2008 9:51:52 am Venefax wrote:
>>>> The Novell engineer showed me a technical document, which I did
not
> write
>>>> the number, on the Novell web site, where it said: windows SMP
>>>> using the
>>>> Novell driver crashes.
>>> That''s what I thought - the problem is with
Novell''s PV drivers,
>>> not Xen.
>>> James had some initial problems with SMP also.
>>
>> Right, that''s important.  Novell''s PV drivers are
their code so those
> drivers
>> might have limitations that plain Xen does not.  Presumably it  
>> would be
>> possible to run using fully emulated IO instead of PV drivers but I
> imagine
>> this could have performance problems in your configuration.  Could be
> worth a
>> try, if you can afford to experiment.
>>
>> If the Windows VMs themselves are crashing due to Novell''s PV
>> drivers then
> I''m
>> afraid this limitation / problem is really Novell''s
responsibility
>> and
> they
>> would be the best people to approach for assistance / complaints.   
>> The
> code
>> for those drivers isn''t open, so only Novell can fix them.  If
the
>> Novell
> PV
>> drivers are somehow crashing your Linux domains or dom0 or Xen  
>> itself then
>
>> that might be a Xen bug and it would be useful to post more details  
>> here.
>>
>> For comparison, Citrix/XenSource supply with their product PV  
>> drivers for
>> Windows that are - AFAIK - a different codebase and may not have  
>> these
>> limitations.  So do Virtual Iron, for their Xen-based product.   
>> Both of
> these
>> can only be used with their respective commercial hypervisors, AFAIK.
> James
>> Harper''s PV drivers for Windows are GPL but still under
development
>> and so
> I
>> doubt they''d be recommended for heavy production use.
>>
>> There are a lot of different PV driver solutions for Windows about  
>> and
> none of
>> them are officially part of the OSS Xen project; only one of them  
>> is even
>> Open Source.
>>
> I really wonder why you run your SQL servers in windows and all the  
> rest
> in Linux???
> I asume especially for databases is Windows a bad base, but i have a
> win20008 sharepoint running on xen 3.2.1 with 2 vcpus it works great  
> and
> stable with james drives.
> And if you like to use this single Box, you may ask SUN (Solaris and
> SunXvm).
>
> florian
>
>>>> I use a SIP Server on the Linux side, talking hundreds of times
per
>>>> second to SQL Server, so I need SMP 8 ways on both  ends.
>>> Something I''ve never seen you actually say is that you
*tried*
>>> vcpu=1,
> and
>>> the performance was bad. So far, it sounds like theory to me. Even
>>> with 1
>>> vcpu, playing with scheduling weights should help.
>>
>> Venefax, are you able to try this?
>>
>> Thank you,
>> Mark
>>
>>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

You''re definitely right Tao,

you should take a look at datacore''s HA products for SAN e.g. SAN
melody,
and if you want to virtualize this mission critical servers use Xen with 
Everrun or VMI3 for HA.

With this combo you have enterprise ready great speed and HA!

Cheers,
Alex



Tao Shen schrieb:
> First of all, your boss should fire you for saying "windows 2008 sql 
> server runs perfectly unless windows crashes"
>
> Secondly, whoever delivered the xen solution on your 200k per day 
> production server should be fired for not understanding the concept of 
> single point of failure.
>
> Now that you learned the lesson at 5k per hour,you should dump virtual 
> machines and have redundant physical machines for mission critical 
> services on your network.  For 200k a day, that is 72million a year 
> revenue, you should have a budget of at least 5 to 7 mil to handle 
> redundancy issues, which means double or even triple redundancy 
> networks and San storage for database servers.
>
> Lastly, I think that either your boss bluffed you with 5k per hour 
> cost of downtime, or you did, since I cannot imagine such incompetent 
> people running a business valued at 15 times earning or hundreds of 
> millions if your 72 million revenue figure is indeed correct.
>
> Btw, xen is maintained by citrix, not Novell.
>
> On Jul 20, 2008, at 11:36 AM, "Venefax" <venefax@gmail.com>
wrote:
>
>> SQL Server only runs in Windows. I am now actually learning DB2 in 
>> order to
>> use a Linux-based database. But of course I am not dumb to put my
entire
>> business on a database I cannot support, yet, the way I do with SQL 
>> Server.
>> And the beauty is the with XEN-Windows 2008, SQL Server runs perfectly,
>> unless Windows crashes.
>>
>> -----Original Message-----
>> From: Florian Manschwetus [mailto:florianmanschwetus@gmx.de]
>> Sent: Sunday, July 20, 2008 12:30 PM
>> To: Mark Williamson
>> Cc: xen-users@lists.xensource.com; Venefax; jim burns
>> Subject: Re: [Xen-users] The death of XEN by Novell
>>
>> Mark Williamson schrieb:
>>> On Sunday 20 July 2008, jim burns wrote:
>>>> On Sun July 20 2008 9:51:52 am Venefax wrote:
>>>>> The Novell engineer showed me a technical document, which I
did not
>> write
>>>>> the number, on the Novell web site, where it said: windows
SMP
>>>>> using the
>>>>> Novell driver crashes.
>>>> That''s what I thought - the problem is with
Novell''s PV drivers,
>>>> not Xen.
>>>> James had some initial problems with SMP also.
>>>
>>> Right, that''s important.  Novell''s PV drivers are
their code so those
>> drivers
>>> might have limitations that plain Xen does not.  Presumably it
would be
>>> possible to run using fully emulated IO instead of PV drivers but I
>> imagine
>>> this could have performance problems in your configuration.  Could
be
>> worth a
>>> try, if you can afford to experiment.
>>>
>>> If the Windows VMs themselves are crashing due to Novell''s
PV
>>> drivers then
>> I''m
>>> afraid this limitation / problem is really Novell''s
responsibility and
>> they
>>> would be the best people to approach for assistance / complaints. 
The
>> code
>>> for those drivers isn''t open, so only Novell can fix them.
If the
>>> Novell
>> PV
>>> drivers are somehow crashing your Linux domains or dom0 or Xen 
>>> itself then
>>
>>> that might be a Xen bug and it would be useful to post more details
>>> here.
>>>
>>> For comparison, Citrix/XenSource supply with their product PV 
>>> drivers for
>>> Windows that are - AFAIK - a different codebase and may not have
these
>>> limitations.  So do Virtual Iron, for their Xen-based product. 
Both of
>> these
>>> can only be used with their respective commercial hypervisors,
AFAIK.
>> James
>>> Harper''s PV drivers for Windows are GPL but still under
development
>>> and so
>> I
>>> doubt they''d be recommended for heavy production use.
>>>
>>> There are a lot of different PV driver solutions for Windows about
and
>> none of
>>> them are officially part of the OSS Xen project; only one of them
is
>>> even
>>> Open Source.
>>>
>> I really wonder why you run your SQL servers in windows and all the
rest
>> in Linux???
>> I asume especially for databases is Windows a bad base, but i have a
>> win20008 sharepoint running on xen 3.2.1 with 2 vcpus it works great
and
>> stable with james drives.
>> And if you like to use this single Box, you may ask SUN (Solaris and
>> SunXvm).
>>
>> florian
>>
>>>>> I use a SIP Server on the Linux side, talking hundreds of
times per
>>>>> second to SQL Server, so I need SMP 8 ways on both  ends.
>>>> Something I''ve never seen you actually say is that you
*tried* vcpu=1,
>> and
>>>> the performance was bad. So far, it sounds like theory to me.
Even
>>>> with 1
>>>> vcpu, playing with scheduling weights should help.
>>>
>>> Venefax, are you able to try this?
>>>
>>> Thank you,
>>> Mark
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 
> 3283 (20080721) __________
>
> E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

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

Somehow i dont get the concept of running a claimed multi-million dollar
enterprise that he claims is loosing so much due to downtime in a virtual
environment either
let alone using windows for this type of task, but hey to each their own.
the only right plan is a good plan, the only good plan is a redundent plan
Id be afraid to ask what happens if they were to experience a catastrophic
event, speaking from experience of Hurricanes, Earthquakes, Typhoons and
Tsunamis
What the escape plans ?? and you blame XEN for not functioning in a virtual
environment, Id have your job and your bosses if you worked for me!
I wonder who sleeps better at night, you, your boss or me!

Tao Shen schrieb:
> First of all, your boss should fire you for saying "windows 2008 sql
server
>> runs perfectly unless windows crashes"
>>
>> Secondly, whoever delivered the xen solution on your 200k per day
>> production server should be fired for not understanding the concept of
>> single point of failure.
>>
>> Now that you learned the lesson at 5k per hour,you should dump virtual
>> machines and have redundant physical machines for mission critical
services
>> on your network.  For 200k a day, that is 72million a year revenue, you
>> should have a budget of at least 5 to 7 mil to handle redundancy
issues,
>> which means double or even triple redundancy networks and San storage
for
>> database servers.
>>
>> Lastly, I think that either your boss bluffed you with 5k per hour cost
of
>> downtime, or you did, since I cannot imagine such incompetent people
running
>> a business valued at 15 times earning or hundreds of millions if your
72
>> million revenue figure is indeed correct.
>>
>> Btw, xen is maintained by citrix, not Novell.
>>
>> On Jul 20, 2008, at 11:36 AM, "Venefax"
<venefax@gmail.com> wrote:
>>
>>  SQL Server only runs in Windows. I am now actually learning DB2 in
order
>>> to
>>> use a Linux-based database. But of course I am not dumb to put my
entire
>>> business on a database I cannot support, yet, the way I do with SQL
>>> Server.
>>> And the beauty is the with XEN-Windows 2008, SQL Server runs
perfectly,
>>> unless Windows crashes.
>>>
>>> -----Original Message-----
>>> From: Florian Manschwetus [mailto:florianmanschwetus@gmx.de]
>>> Sent: Sunday, July 20, 2008 12:30 PM
>>> To: Mark Williamson
>>> Cc: xen-users@lists.xensource.com; Venefax; jim burns
>>> Subject: Re: [Xen-users] The death of XEN by Novell
>>>
>>> Mark Williamson schrieb:
>>>
>>>> On Sunday 20 July 2008, jim burns wrote:
>>>>
>>>>> On Sun July 20 2008 9:51:52 am Venefax wrote:
>>>>>
>>>>>> The Novell engineer showed me a technical document,
which I did not
>>>>>>
>>>>> write
>>>
>>>> the number, on the Novell web site, where it said: windows SMP
using the
>>>>>> Novell driver crashes.
>>>>>>
>>>>> That''s what I thought - the problem is with
Novell''s PV drivers, not
>>>>> Xen.
>>>>> James had some initial problems with SMP also.
>>>>>
>>>>
>>>> Right, that''s important.  Novell''s PV drivers
are their code so those
>>>>
>>> drivers
>>>
>>>> might have limitations that plain Xen does not.  Presumably it
would be
>>>> possible to run using fully emulated IO instead of PV drivers
but I
>>>>
>>> imagine
>>>
>>>> this could have performance problems in your configuration. 
Could be
>>>>
>>> worth a
>>>
>>>> try, if you can afford to experiment.
>>>>
>>>> If the Windows VMs themselves are crashing due to
Novell''s PV drivers
>>>> then
>>>>
>>> I''m
>>>
>>>> afraid this limitation / problem is really Novell''s
responsibility and
>>>>
>>> they
>>>
>>>> would be the best people to approach for assistance /
complaints.  The
>>>>
>>> code
>>>
>>>> for those drivers isn''t open, so only Novell can fix
them.  If the
>>>> Novell
>>>>
>>> PV
>>>
>>>> drivers are somehow crashing your Linux domains or dom0 or Xen
itself
>>>> then
>>>>
>>>
>>>  that might be a Xen bug and it would be useful to post more
details
>>>> here.
>>>>
>>>> For comparison, Citrix/XenSource supply with their product PV
drivers
>>>> for
>>>> Windows that are - AFAIK - a different codebase and may not
have these
>>>> limitations.  So do Virtual Iron, for their Xen-based product. 
Both of
>>>>
>>> these
>>>
>>>> can only be used with their respective commercial hypervisors,
AFAIK.
>>>>
>>> James
>>>
>>>> Harper''s PV drivers for Windows are GPL but still
under development and
>>>> so
>>>>
>>> I
>>>
>>>> doubt they''d be recommended for heavy production use.
>>>>
>>>> There are a lot of different PV driver solutions for Windows
about and
>>>>
>>> none of
>>>
>>>> them are officially part of the OSS Xen project; only one of
them is
>>>> even
>>>> Open Source.
>>>>
>>>>  I really wonder why you run your SQL servers in windows and
all the
>>> rest
>>> in Linux???
>>> I asume especially for databases is Windows a bad base, but i have
a
>>> win20008 sharepoint running on xen 3.2.1 with 2 vcpus it works
great and
>>> stable with james drives.
>>> And if you like to use this single Box, you may ask SUN (Solaris
and
>>> SunXvm).
>>>
>>> florian
>>>
>>>  I use a SIP Server on the Linux side, talking hundreds of times
per
>>>>>> second to SQL Server, so I need SMP 8 ways on both 
ends.
>>>>>>
>>>>> Something I''ve never seen you actually say is that
you *tried* vcpu=1,
>>>>>
>>>> and
>>>
>>>> the performance was bad. So far, it sounds like theory to me.
Even with
>>>>> 1
>>>>> vcpu, playing with scheduling weights should help.
>>>>>
>>>>
>>>> Venefax, are you able to try this?
>>>>
>>>> Thank you,
>>>> Mark
>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xensource.com
>>> http://lists.xensource.com/xen-users
>>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version
>> 3283 (20080721) __________
>>
>> E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

WOW, this is funny cause it sounds like you already have, it might not have
been at the database level but it sure was at the virtualization level

On Mon, Jul 21, 2008 at 9:30 AM, Fajar A. Nugraha <fajar@fajar.net> wrote:
> Venefax wrote:
>
>> SQL Server only runs in Windows. I am now actually learning DB2 in
order
>> to
>> use a Linux-based database. But of course I am not dumb to put my
entire
>> business on a database I cannot support, yet, the way I do with SQL
>> Server.
>> And the beauty is the with XEN-Windows 2008, SQL Server runs perfectly,
>> unless Windows crashes.
>>
>

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

I think he''s not blaming XEN.
He only blames himself ;-)

Think we get a little bit offtopic ^^

There seem to be no wise reactions from him, regarding any suggestions.

Cheers,
Alex



Outback Dingo schrieb:
> Somehow i dont get the concept of running a claimed multi-million 
> dollar enterprise that he claims is loosing so much due to downtime in 
> a virtual environment either
> let alone using windows for this type of task, but hey to each their 
> own. the only right plan is a good plan, the only good plan is a 
> redundent plan
> Id be afraid to ask what happens if they were to experience a 
> catastrophic event, speaking from experience of Hurricanes, 
> Earthquakes, Typhoons and Tsunamis
> What the escape plans ?? and you blame XEN for not functioning in a 
> virtual environment, Id have your job and your bosses if you worked 
> for me!
> I wonder who sleeps better at night, you, your boss or me!
>
> Tao Shen schrieb:
>
>         First of all, your boss should fire you for saying "windows
>         2008 sql server runs perfectly unless windows crashes"
>
>         Secondly, whoever delivered the xen solution on your 200k per
>         day production server should be fired for not understanding
>         the concept of single point of failure.
>
>         Now that you learned the lesson at 5k per hour,you should dump
>         virtual machines and have redundant physical machines for
>         mission critical services on your network.  For 200k a day,
>         that is 72million a year revenue, you should have a budget of
>         at least 5 to 7 mil to handle redundancy issues, which means
>         double or even triple redundancy networks and San storage for
>         database servers.
>
>         Lastly, I think that either your boss bluffed you with 5k per
>         hour cost of downtime, or you did, since I cannot imagine such
>         incompetent people running a business valued at 15 times
>         earning or hundreds of millions if your 72 million revenue
>         figure is indeed correct.
>
>         Btw, xen is maintained by citrix, not Novell.
>
>         On Jul 20, 2008, at 11:36 AM, "Venefax"
<venefax@gmail.com
>         <mailto:venefax@gmail.com>> wrote:
>
>             SQL Server only runs in Windows. I am now actually
>             learning DB2 in order to
>             use a Linux-based database. But of course I am not dumb to
>             put my entire
>             business on a database I cannot support, yet, the way I do
>             with SQL Server.
>             And the beauty is the with XEN-Windows 2008, SQL Server
>             runs perfectly,
>             unless Windows crashes.
>
>             -----Original Message-----
>             From: Florian Manschwetus
>             [mailto:florianmanschwetus@gmx.de
>             <mailto:florianmanschwetus@gmx.de>]
>             Sent: Sunday, July 20, 2008 12:30 PM
>             To: Mark Williamson
>             Cc: xen-users@lists.xensource.com
>             <mailto:xen-users@lists.xensource.com>; Venefax; jim
burns
>             Subject: Re: [Xen-users] The death of XEN by Novell
>
>             Mark Williamson schrieb:
>
>                 On Sunday 20 July 2008, jim burns wrote:
>
>                     On Sun July 20 2008 9:51:52 am Venefax wrote:
>
>                         The Novell engineer showed me a technical
>                         document, which I did not
>
>             write
>
>                         the number, on the Novell web site, where it
>                         said: windows SMP using the
>                         Novell driver crashes.
>
>                     That''s what I thought - the problem is with
>                     Novell''s PV drivers, not Xen.
>                     James had some initial problems with SMP also.
>
>
>                 Right, that''s important.  Novell''s PV
drivers are
>                 their code so those
>
>             drivers
>
>                 might have limitations that plain Xen does not.
>                  Presumably it would be
>                 possible to run using fully emulated IO instead of PV
>                 drivers but I
>
>             imagine
>
>                 this could have performance problems in your
>                 configuration.  Could be
>
>             worth a
>
>                 try, if you can afford to experiment.
>
>                 If the Windows VMs themselves are crashing due to
>                 Novell''s PV drivers then
>
>             I''m
>
>                 afraid this limitation / problem is really
Novell''s
>                 responsibility and
>
>             they
>
>                 would be the best people to approach for assistance /
>                 complaints.  The
>
>             code
>
>                 for those drivers isn''t open, so only Novell can
fix
>                 them.  If the Novell
>
>             PV
>
>                 drivers are somehow crashing your Linux domains or
>                 dom0 or Xen itself then
>
>
>                 that might be a Xen bug and it would be useful to post
>                 more details here.
>
>                 For comparison, Citrix/XenSource supply with their
>                 product PV drivers for
>                 Windows that are - AFAIK - a different codebase and
>                 may not have these
>                 limitations.  So do Virtual Iron, for their Xen-based
>                 product.  Both of
>
>             these
>
>                 can only be used with their respective commercial
>                 hypervisors, AFAIK.
>
>             James
>
>                 Harper''s PV drivers for Windows are GPL but still
>                 under development and so
>
>             I
>
>                 doubt they''d be recommended for heavy production
use.
>
>                 There are a lot of different PV driver solutions for
>                 Windows about and
>
>             none of
>
>                 them are officially part of the OSS Xen project; only
>                 one of them is even
>                 Open Source.
>
>             I really wonder why you run your SQL servers in windows
>             and all the rest
>             in Linux???
>             I asume especially for databases is Windows a bad base,
>             but i have a
>             win20008 sharepoint running on xen 3.2.1 with 2 vcpus it
>             works great and
>             stable with james drives.
>             And if you like to use this single Box, you may ask SUN
>             (Solaris and
>             SunXvm).
>
>             florian
>
>                         I use a SIP Server on the Linux side, talking
>                         hundreds of times per
>                         second to SQL Server, so I need SMP 8 ways on
>                         both  ends.
>
>                     Something I''ve never seen you actually say is
that
>                     you *tried* vcpu=1,
>
>             and
>
>                     the performance was bad. So far, it sounds like
>                     theory to me. Even with 1
>                     vcpu, playing with scheduling weights should help.
>
>
>                 Venefax, are you able to try this?
>
>                 Thank you,
>                 Mark
>
>
>
>
>
>             _______________________________________________
>             Xen-users mailing list
>             Xen-users@lists.xensource.com
>             <mailto:Xen-users@lists.xensource.com>
>             http://lists.xensource.com/xen-users
>
>
>         _______________________________________________
>         Xen-users mailing list
>         Xen-users@lists.xensource.com
>         <mailto:Xen-users@lists.xensource.com>
>         http://lists.xensource.com/xen-users
>
>         __________ Hinweis von ESET NOD32 Antivirus,
>         Signaturdatenbank-Version 3283 (20080721) __________
>
>         E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>
>         http://www.eset.com
>
>
>
>
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
>     http://lists.xensource.com/xen-users
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
>   

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

On Mon, Jul 21, 2008 at 9:33 AM, Alexander Hoßdorf
<xen-users@hossdorf.eu> wrote:
> I think he''s not blaming XEN.
> He only blames himself ;-)
>
> Think we get a little bit offtopic ^^
I agree. There''s no point in keeping telling him the _mistakes_ there
seem to be in his plans. Let''s move on.

Gaston
>
> There seem to be no wise reactions from him, regarding any suggestions.
>
> Cheers,
> Alex
>
>
>
> Outback Dingo schrieb:
>>
>> Somehow i dont get the concept of running a claimed multi-million
dollar
>> enterprise that he claims is loosing so much due to downtime in a
virtual
>> environment either
>> let alone using windows for this type of task, but hey to each their
own.
>> the only right plan is a good plan, the only good plan is a redundent
plan
>> Id be afraid to ask what happens if they were to experience a
catastrophic
>> event, speaking from experience of Hurricanes, Earthquakes, Typhoons
and
>> Tsunamis
>> What the escape plans ?? and you blame XEN for not functioning in a
>> virtual environment, Id have your job and your bosses if you worked for
me!
>> I wonder who sleeps better at night, you, your boss or me!
>>
>> Tao Shen schrieb:
>>
>>        First of all, your boss should fire you for saying "windows
>>        2008 sql server runs perfectly unless windows crashes"
>>
>>        Secondly, whoever delivered the xen solution on your 200k per
>>        day production server should be fired for not understanding
>>        the concept of single point of failure.
>>
>>        Now that you learned the lesson at 5k per hour,you should dump
>>        virtual machines and have redundant physical machines for
>>        mission critical services on your network.  For 200k a day,
>>        that is 72million a year revenue, you should have a budget of
>>        at least 5 to 7 mil to handle redundancy issues, which means
>>        double or even triple redundancy networks and San storage for
>>        database servers.
>>
>>        Lastly, I think that either your boss bluffed you with 5k per
>>        hour cost of downtime, or you did, since I cannot imagine such
>>        incompetent people running a business valued at 15 times
>>        earning or hundreds of millions if your 72 million revenue
>>        figure is indeed correct.
>>
>>        Btw, xen is maintained by citrix, not Novell.
>>
>>        On Jul 20, 2008, at 11:36 AM, "Venefax"
<venefax@gmail.com
>>        <mailto:venefax@gmail.com>> wrote:
>>
>>            SQL Server only runs in Windows. I am now actually
>>            learning DB2 in order to
>>            use a Linux-based database. But of course I am not dumb to
>>            put my entire
>>            business on a database I cannot support, yet, the way I do
>>            with SQL Server.
>>            And the beauty is the with XEN-Windows 2008, SQL Server
>>            runs perfectly,
>>            unless Windows crashes.
>>
>>            -----Original Message-----
>>            From: Florian Manschwetus
>>            [mailto:florianmanschwetus@gmx.de
>>            <mailto:florianmanschwetus@gmx.de>]
>>            Sent: Sunday, July 20, 2008 12:30 PM
>>            To: Mark Williamson
>>            Cc: xen-users@lists.xensource.com
>>            <mailto:xen-users@lists.xensource.com>; Venefax; jim
burns
>>            Subject: Re: [Xen-users] The death of XEN by Novell
>>
>>            Mark Williamson schrieb:
>>
>>                On Sunday 20 July 2008, jim burns wrote:
>>
>>                    On Sun July 20 2008 9:51:52 am Venefax wrote:
>>
>>                        The Novell engineer showed me a technical
>>                        document, which I did not
>>
>>            write
>>
>>                        the number, on the Novell web site, where it
>>                        said: windows SMP using the
>>                        Novell driver crashes.
>>
>>                    That''s what I thought - the problem is with
>>                    Novell''s PV drivers, not Xen.
>>                    James had some initial problems with SMP also.
>>
>>
>>                Right, that''s important.  Novell''s PV
drivers are
>>                their code so those
>>
>>            drivers
>>
>>                might have limitations that plain Xen does not.
>>                 Presumably it would be
>>                possible to run using fully emulated IO instead of PV
>>                drivers but I
>>
>>            imagine
>>
>>                this could have performance problems in your
>>                configuration.  Could be
>>
>>            worth a
>>
>>                try, if you can afford to experiment.
>>
>>                If the Windows VMs themselves are crashing due to
>>                Novell''s PV drivers then
>>
>>            I''m
>>
>>                afraid this limitation / problem is really
Novell''s
>>                responsibility and
>>
>>            they
>>
>>                would be the best people to approach for assistance /
>>                complaints.  The
>>
>>            code
>>
>>                for those drivers isn''t open, so only Novell
can fix
>>                them.  If the Novell
>>
>>            PV
>>
>>                drivers are somehow crashing your Linux domains or
>>                dom0 or Xen itself then
>>
>>
>>                that might be a Xen bug and it would be useful to post
>>                more details here.
>>
>>                For comparison, Citrix/XenSource supply with their
>>                product PV drivers for
>>                Windows that are - AFAIK - a different codebase and
>>                may not have these
>>                limitations.  So do Virtual Iron, for their Xen-based
>>                product.  Both of
>>
>>            these
>>
>>                can only be used with their respective commercial
>>                hypervisors, AFAIK.
>>
>>            James
>>
>>                Harper''s PV drivers for Windows are GPL but
still
>>                under development and so
>>
>>            I
>>
>>                doubt they''d be recommended for heavy
production use.
>>
>>                There are a lot of different PV driver solutions for
>>                Windows about and
>>
>>            none of
>>
>>                them are officially part of the OSS Xen project; only
>>                one of them is even
>>                Open Source.
>>
>>            I really wonder why you run your SQL servers in windows
>>            and all the rest
>>            in Linux???
>>            I asume especially for databases is Windows a bad base,
>>            but i have a
>>            win20008 sharepoint running on xen 3.2.1 with 2 vcpus it
>>            works great and
>>            stable with james drives.
>>            And if you like to use this single Box, you may ask SUN
>>            (Solaris and
>>            SunXvm).
>>
>>            florian
>>
>>                        I use a SIP Server on the Linux side, talking
>>                        hundreds of times per
>>                        second to SQL Server, so I need SMP 8 ways on
>>                        both  ends.
>>
>>                    Something I''ve never seen you actually say
is that
>>                    you *tried* vcpu=1,
>>
>>            and
>>
>>                    the performance was bad. So far, it sounds like
>>                    theory to me. Even with 1
>>                    vcpu, playing with scheduling weights should help.
>>
>>
>>                Venefax, are you able to try this?
>>
>>                Thank you,
>>                Mark
>>
>>
>>
>>
>>
>>            _______________________________________________
>>            Xen-users mailing list
>>            Xen-users@lists.xensource.com
>>            <mailto:Xen-users@lists.xensource.com>
>>            http://lists.xensource.com/xen-users
>>
>>
>>        _______________________________________________
>>        Xen-users mailing list
>>        Xen-users@lists.xensource.com
>>        <mailto:Xen-users@lists.xensource.com>
>>        http://lists.xensource.com/xen-users
>>
>>        __________ Hinweis von ESET NOD32 Antivirus,
>>        Signaturdatenbank-Version 3283 (20080721) __________
>>
>>        E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>>
>>        http://www.eset.com
>>
>>
>>
>>
>>
>>    _______________________________________________
>>    Xen-users mailing list
>>    Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
>>    http://lists.xensource.com/xen-users
>>
>>
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>>
>>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


-- 
La única verdad es la realidad.

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

It is definitely at the virtualization level.  I already sent a MSG to  
the venefax suggesting that he should drop virtualization on his 200k  
a day production system.  Obviously, the choice of xen is not  
optimal.  Combine it with windows server os, all hell breaks loose.   
For 72 million dollar a year revenue system, it is a lot safer and  
stable to have redundant physical servers anyways.  It is not really  
wise to try to consolidate to save electricity to introduce single  
point of failures, let alone software driver crashing at the  
virtualization layer.

This whole thing smells like an internal blame game.  I would have  
fired anyone who suggests virtualization on production servers that  
introduced single point of failure on a critical service.

On Jul 21, 2008, at 8:25 AM, "Outback Dingo"
<outbackdingo@gmail.com>
wrote:
> WOW, this is funny cause it sounds like you already have, it might  
> not have been at the database level but it sure was at the  
> virtualization level
>
> On Mon, Jul 21, 2008 at 9:30 AM, Fajar A. Nugraha <fajar@fajar.net>  
> wrote:
> Venefax wrote:
> SQL Server only runs in Windows. I am now actually learning DB2 in  
> order to
> use a Linux-based database. But of course I am not dumb to put my  
> entire
> business on a database I cannot support, yet, the way I do with SQL  
> Server.
> And the beauty is the with XEN-Windows 2008, SQL Server runs  
> perfectly,
> unless Windows crashes.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

Dear Lynn
Why don''t you take ownership of the case since obviously the engineer
is not
up to date?
If you log into the box you may notice that I am pinning the dom0 to VCPU 0,
and excluding the domu''s  from using it. I also restricted dom0 to 4 GB
out
of 127.
Is this setup what causes the issue?
When that happened, a while earlier, I was doing a backup of a large
database over the network. The curious thing is the largest database backup
finished fine. It blew-up when I was backing up the other smaller database,
or maybe the first large database blew some buffer and the second got
affected. I cannot know, but that was the only operation that was unusual
that night. The Windows boxes have a note with a minidump, which probably
can be used to trace what driver is the culprit. I can do the same operation
tonight of somebody wants to set up some traces.

I can be reached at 954 444 7408, 24x7.
Yours
Federico

-----Original Message-----
From: Lynn Bendixsen [mailto:lbendixs@novell.com] 
Sent: Monday, July 21, 2008 7:21 PM
To: ''Mark Williamson''; ''Antoine Benkemoun'';
Venefax; Ky Srinivasan
Cc: stephen.spector@citrix.com; xen-users@lists.xensource.com
Subject: Re: The death of XEN by Novell
>>> On Sat, Jul 19, 2008 at 11:14 AM, in message
<039901c8e9c2$e5dd4530$b197cf90$@com>, "Venefax"
<venefax@gmail.com>
wrote: 
> Subject: The death of XEN by Novell (case number 10406546031)
> 
> According to Novell, Xen has a flaw that in fact means it is useless.
I have 
> a single supported system with SLES SP2, where I have 3 Windows
VM''s
and 5 
> Linux VM''s. In each of the Windows VM''s I have 8 Virtual
CPU''s,
because I 
> have a vital SQL Server installed where my company runs all its
business. The 
> data comes precisely from the Linux virtual machines, and having the
database 
> "right there" has proven extremely efficient. But all my three
Windows VM''s 
> crashed simultaneously yesterday and I lost two hours of business. I
am using 
> of course the right Novell drivers, etc., every piece of the puzzle
in place. 
> Novell already checked that. The engineers showed me a technical note
that 
> says that having more than one Virtual CPU in a Windows VM leads to
crashes.

The technical note you refer to here is outdated.  It is for SLES 10
SP1 and earlier. Here is a link to our current Support Document for Xen
in SLES 10 SP2.
http://www.novell.com/rc/docrepository/public/37/basedocument.2008-06-10.975
2681390/SUSE_Linux_Enterprise_10_SP2_Virtualization_Technology_Support_Techn
ical_White_Paper_en.pdf
To summarize breifly: we support multiple vcpus for Windows guests in
our SLES10 SP2 and later hosts.  Any issues encountered with multiple
VCPUs in windows should be reported and its certainly a high priority
for us to help you get it working.  All of the testing we do has 2 or 4
vcpus by default in each Windows VM.
> But then we cannot have any windows VM at all, hello!!! This means
that the 
> $35.000 box that I bought is the wrong box, because now I need to
remove my 
> windows VM and create a separate windows installation, and order more
> hardware, spend more money. It means that XEN is useless, because if
it only 
> can virtualize Linux, actually Virtuozzo (Open VZ) has a lot less
overhead, 
> far less. The beauty of Xen is that it is supposed to virtualize
Windows and 
> Linux together. Now, that dream is gone. In case somebody wants to
look at my 
> Novell case number, it is 10406546031


Lynn Bendixsen
Software Engineer
lbendixs@novell.com
801-861-2887

Novell, Inc. 
SUSE* Linux Enterprise 10 SP2
Your Linux is more than ready 
http://www.novell.com/linux



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

Federico,

I have been out of the office for a while and just read this thread.  Did you
get your issue resolved?  Was Lynn (or someone else from Novell) able to help
you?  Please let me know.  Thanks.

Jason
>>> On Mon, Jul 21, 2008 at  6:06 PM, in message
<000001c8eb8e$bb469e70$31d3db50$@com>, "Venefax"
<venefax@gmail.com> wrote: 
> Dear Lynn
> Why don''t you take ownership of the case since obviously the
engineer is not
> up to date?
> If you log into the box you may notice that I am pinning the dom0 to VCPU
0,
> and excluding the domu''s  from using it. I also restricted dom0 to
4 GB out
> of 127.
> Is this setup what causes the issue?
> When that happened, a while earlier, I was doing a backup of a large
> database over the network. The curious thing is the largest database backup
> finished fine. It blew-up when I was backing up the other smaller database,
> or maybe the first large database blew some buffer and the second got
> affected. I cannot know, but that was the only operation that was unusual
> that night. The Windows boxes have a note with a minidump, which probably
> can be used to trace what driver is the culprit. I can do the same
operation
> tonight of somebody wants to set up some traces.
> 
> I can be reached at 954 444 7408, 24x7.
> Yours
> Federico
> 
> -----Original Message-----
> From: Lynn Bendixsen [mailto:lbendixs@novell.com] 
> Sent: Monday, July 21, 2008 7:21 PM
> To: ''Mark Williamson''; ''Antoine
Benkemoun''; Venefax; Ky Srinivasan
> Cc: stephen.spector@citrix.com; xen-users@lists.xensource.com
> Subject: Re: The death of XEN by Novell
> 
>>>> On Sat, Jul 19, 2008 at 11:14 AM, in message
> <039901c8e9c2$e5dd4530$b197cf90$@com>, "Venefax"
<venefax@gmail.com>
> wrote: 
>> Subject: The death of XEN by Novell (case number 10406546031)
>> 
>> According to Novell, Xen has a flaw that in fact means it is useless.
> I have 
>> a single supported system with SLES SP2, where I have 3 Windows
VM''s
> and 5 
>> Linux VM''s. In each of the Windows VM''s I have 8
Virtual CPU''s,
> because I 
>> have a vital SQL Server installed where my company runs all its
> business. The 
>> data comes precisely from the Linux virtual machines, and having the
> database 
>> "right there" has proven extremely efficient. But all my
three
> Windows VM''s 
>> crashed simultaneously yesterday and I lost two hours of business. I
> am using 
>> of course the right Novell drivers, etc., every piece of the puzzle
> in place. 
>> Novell already checked that. The engineers showed me a technical note
> that 
>> says that having more than one Virtual CPU in a Windows VM leads to
> crashes.
> 
> The technical note you refer to here is outdated.  It is for SLES 10
> SP1 and earlier. Here is a link to our current Support Document for Xen
> in SLES 10 SP2.
>
http://www.novell.com/rc/docrepository/public/37/basedocument.2008-06-10.975
>
2681390/SUSE_Linux_Enterprise_10_SP2_Virtualization_Technology_Support_Techn
> ical_White_Paper_en.pdf
> To summarize breifly: we support multiple vcpus for Windows guests in
> our SLES10 SP2 and later hosts.  Any issues encountered with multiple
> VCPUs in windows should be reported and its certainly a high priority
> for us to help you get it working.  All of the testing we do has 2 or 4
> vcpus by default in each Windows VM.
> 
>> But then we cannot have any windows VM at all, hello!!! This means
> that the 
>> $35.000 box that I bought is the wrong box, because now I need to
> remove my 
>> windows VM and create a separate windows installation, and order more
> 
>> hardware, spend more money. It means that XEN is useless, because if
> it only 
>> can virtualize Linux, actually Virtuozzo (Open VZ) has a lot less
> overhead, 
>> far less. The beauty of Xen is that it is supposed to virtualize
> Windows and 
>> Linux together. Now, that dream is gone. In case somebody wants to
> look at my 
>> Novell case number, it is 10406546031
> 
> 
> 
> Lynn Bendixsen
> Software Engineer
> lbendixs@novell.com
> 801-861-2887
> 
> Novell, Inc. 
> SUSE* Linux Enterprise 10 SP2
> Your Linux is more than ready 
> http://www.novell.com/linux
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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