xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
	eXeC001er <execooler@gmail.com>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Problems upgrading 3.4 to 4.0?  WAS: Xen on vmware
Date: Thu, 6 May 2010 08:24:02 +0100	[thread overview]
Message-ID: <C8082D22.1361D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <e313a54e-06ea-472c-ad51-e6e2f21b2b52@default>

Xc.xeninfo is part of 4.0's Xc extension package. It should get installed
along with the rest of xend. So yes you probably have 3.4 detritus somewhere
else on your python path (in particular, xc.so).

 K.

On 06/05/2010 00:14, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> Hmmm... I am having the same problem BUT not on VMware.
>  
> I built and installed xen-4.0.0.tar.gz on a xen-3.4 based system (Oracle VM)
> and got the same problem (xc.xeninfo not implemented).  (Yes, I built and
> installed tools and dom0 (2.6.18-xen) too.)
>  
> Then I tried xen-4.0-testing.hg  and got the same thing.
>  
> I wonder if there¹s some 3.4 residue that is screwing up 4.0 installs?
>  
> I hate to reinstall the whole system from scratch, but I can if necessary.
>  
> 
> From: eXeC001er [mailto:execooler@gmail.com]
> Sent: Friday, April 23, 2010 9:43 AM
> To: Xen-devel
> Subject: [Xen-devel] Xen on vmware
>  
> Hi.
> 
>  
> 
> I tried to start Xen Dom0 in vmware virtual machine (Debian Squeeze).
> 
>  
> 
> xen-tools from xen-unstable.
> 
>  
> 
> xen-4.1 (from mercurial xen-unstable) - PASS (kernel, hypervisor, xend)
> 
>  
> 
> xen-3.4 (from Debian Squeeze) - FAIL (kernel (PASS), hypervisor (PASS), xend
> (FAIL))
> 
>  
> 
> log:
> 
> [2010-04-23 03:01:35 1472] INFO (SrvDaemon:332) Xend Daemon started
> 
> [2010-04-23 03:01:35 1472] ERROR (SrvDaemon:349) Exception starting xend ((38,
> 'Function not implemented'))
> 
> Traceback (most recent call last):
> 
>   File "usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py", line
> 335, in run
> 
>     xinfo = xc.xeninfo()
> 
> Error: (38, 'Function not implemented')
> 
> [2010-04-23 03:01:35 1471] INFO (SrvDaemon:220) Xend exited with status 1.
> 
>  
> 
>  
> 
> What is the difference?
> 
>  
> 
> p.s.: xen-tools from xen-unstable and xen-3.4 works fine on bare-metal
> 
>  
> 
> Thanks.
> 

  reply	other threads:[~2010-05-06  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 15:43 Xen on vmware eXeC001er
2010-05-05 23:14 ` Problems upgrading 3.4 to 4.0? WAS: " Dan Magenheimer
2010-05-06  7:24   ` Keir Fraser [this message]
2010-05-06 12:14   ` M A Young
2010-05-06 13:29     ` Dan Magenheimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C8082D22.1361D%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=execooler@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).