Xen on vmware

Xen on vmware

[eXeC001er]

[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 1487 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Problems upgrading 3.4 to 4.0? WAS: Xen on vmware

[Dan Magenheimer]

[-- Attachment #1.1: Type: text/plain, Size: 1564 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 8992 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Problems upgrading 3.4 to 4.0? WAS: Xen on vmware

[Keir Fraser]

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.
> 

Re: Problems upgrading 3.4 to 4.0? WAS: Xen on vmware

[M A Young]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 554 bytes --]

On Wed, 5 May 2010, Dan Magenheimer wrote:

> 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.)

I am wondering if this is because you are trying to talk to a 3.4 
hypervisor with 4.0 xend. I saw a post on the Fedora virt list
http://lists.fedoraproject.org/pipermail/virt/2010-May/002038.html
yesterday from a person who saw a similar error where this was probably 
the case.

 	Michael Young

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

RE: Problems upgrading 3.4 to 4.0? WAS: Xen on vmware

[Dan Magenheimer]

> I am wondering if this is because you are trying to talk to a 3.4
> hypervisor with 4.0 xend.

Thanks, this turned out to be the problem... I had
a mess of symbolic links in /boot and my grub entry
was finding an old 3.4 xen.gz! :-}

> -----Original Message-----
> From: M A Young [mailto:m.a.young@durham.ac.uk]
> Sent: Thursday, May 06, 2010 6:15 AM
> To: Dan Magenheimer
> Cc: eXeC001er; Xen-devel
> Subject: Re: [Xen-devel] Problems upgrading 3.4 to 4.0? WAS: Xen on
> vmware
> 
> On Wed, 5 May 2010, Dan Magenheimer wrote:
> 
> > 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.)
> 
> I am wondering if this is because you are trying to talk to a 3.4
> hypervisor with 4.0 xend. I saw a post on the Fedora virt list
> http://lists.fedoraproject.org/pipermail/virt/2010-May/002038.html
> yesterday from a person who saw a similar error where this was probably
> the case.
> 
>  	Michael Young