On Thu, 2011-01-20 at 16:49 +0000, chris wrote:
> On Thu, Jan 20, 2011 at 3:38 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> > On Wed, 2011-01-19 at 22:34 +0000, chris wrote:
> >> On Wed, Jan 19, 2011 at 2:29 PM, chris <tknchris@xxxxxxxxx> wrote:
> >> > I have pulled the latest from xen-unstable on a new machine, I run
> >> > make world and make install and after rebooting into xen, when i run
> >> > xm list or anything else i get:
> >> >
> >> > # xm list
> >> > Traceback (most recent call last):
> >> > File "/usr/sbin/xm", line 5, in <module>
> >> > from xen.xm import main
> >> > ImportError: No module named xen.xm
> >> >
> >> > I also tried going into the tools dir and make install, because i read
> >> > that somewhere on google.
> >> >
> >> > I don't get any errors when compiling or installing so I don't know
> >> > where to go from here?
> >> >
> >> > - chris
> >> >
> >>
> >> I just tried this again after pulling everything down again and
> >> recompiling. Is something broken?
> >
> > Nothing currently known.
> >
> > Which host OS are you running?
> >
> > Do:
> > $ python
> >>>> import sys
> >>>> print sys.path
> >
> > This should tell you the python path which is where python is looking
> > for stuff. The install process should have dropped xen/xm/main.py
> > somewhere on the system, the build log or "find" should tell you where.
> > Do they correspond?
> >
> > Ian.
> >
> >
>
> This is debian squeeze. I'm guessing something just changed in the
> python package?
>
> # python
> Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48)
> [GCC 4.4.5] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import sys
> >>> print sys.path
> ['', '/usr/lib/python2.6', '/usr/lib/python2.6/plat-linux2',
> '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old',
> '/usr/lib/python2.6/lib-dynload',
> '/usr/local/lib/python2.6/dist-packages',
> '/usr/lib/python2.6/dist-packages', '/usr/lib/pymodules/python2.6']
>
>
> Any idea where to go from here? I don't know a whole lot about python
As I said before -- use "find" or the build log to figure out where Xen
installed itself to, then we can try and figure out where it went wrong.
Ian.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home