Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Xen: Users

compiling an old XEN version

 

 

Xen users RSS feed   Index | Next | Previous | View Threaded


maheen_butt26 at yahoo

Aug 8, 2012, 10:49 PM

Post #1 of 8 (343 views)
Permalink
compiling an old XEN version

hi all,
I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0. 
For compilation I followed following instruction given by Jeremie Le Hen
% mkdir build
% wget http://bits.xensource.com/oss-xen/release/3.2.0/xen-3.2.0.tar.gz % tar xzf xen-3.2.0.tar.gz
% # Download the xenifid kernel tree manually, but NOT in xen-3.2.0/
% # because the buildconfig/select-repository script would skip it.
% # ! xen-3.2.0/ and linux-2.6.18-xen.hg/ must be at the same level !
% hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg % cd xen-3.2.0
% make prep-kernels
% cp /boot/config-2.6.18-my build-linux-2.6.18-xen_x86_32/.config
% make dist

everything was going  good until I gave commang 'make dist' I encountered with following errorsIn file included from grant_table.c:1520:0:

compat/grant_table.c: At top level:
compat/grant_table.c:9:214: error: variably modified ‘__checkFstruct_grant_entry__flags’ at file scope [-Werror]
compat/grant_table.c:9:350: error: variably modified ‘__checkFstruct_grant_entry__domid’ at file scope [-Werror]
compat/grant_table.c:9:486: error: variably modified ‘__checkFstruct_grant_entry__frame’ at file scope [-Werror]
In file included from grant_table.c:1520:0:
compat/grant_table.c:13:267: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__host_addr’ at file scope [-Werror]
compat/grant_table.c:13:434: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__flags’ at file scope [-Werror]
compat/grant_table.c:13:593: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__ref’ at file scope [-Werror]
compat/grant_table.c:13:750: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__dom’ at file scope [-Werror]
compat/grant_table.c:13:913: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__status’ at file scope [-Werror]
compat/grant_table.c:13:1079: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__handle’ at file scope [-Werror]
compat/grant_table.c:13:1257: error: variably modified ‘__checkFstruct_gnttab_map_grant_ref__dev_bus_addr’ at file scope [-Werror]
In file included from grant_table.c:1520:0:
compat/grant_table.c:17:277: error: variably modified ‘__checkFstruct_gnttab_unmap_grant_ref__host_addr’ at file scope [-Werror]
compat/grant_table.c:17:464: error: variably modified ‘__checkFstruct_gnttab_unmap_grant_ref__dev_bus_addr’ at file scope [-Werror]
compat/grant_table.c:17:642: error: variably modified ‘__checkFstruct_gnttab_unmap_grant_ref__handle’ at file scope [-Werror]
compat/grant_table.c:17:814: error: variably modified ‘__checkFstruct_gnttab_unmap_grant_ref__status’ at file scope [-Werror]
In file included from grant_table.c:1520:0:
compat/grant_table.c:21:287: error: variably modified ‘__checkFstruct_gnttab_unmap_and_replace__host_addr’ at file scope [-Werror]
compat/grant_table.c:21:472: error: variably modified ‘__checkFstruct_gnttab_unmap_and_replace__new_addr’ at file scope [-Werror]
compat/grant_table.c:21:652: error: variably modified ‘__checkFstruct_gnttab_unmap_and_replace__handle’ at file scope [-Werror]
compat/grant_table.c:21:830: error: variably modified ‘__checkFstruct_gnttab_unmap_and_replace__status’ at file scope [-Werror]
In file included from grant_table.c:1520:0:
compat/grant_table.c:29:240: error: variably modified ‘__checkFstruct_gnttab_dump_table__dom’ at file scope [-Werror]
compat/grant_table.c:29:394: error: variably modified ‘__checkFstruct_gnttab_dump_table__status’ at file scope [-Werror]
cc1: all warnings being treated as errors
make[4]: *** [grant_table.o] Error 1
make[4]: Leaving directory `/home/khansa/xen-3.2.0/xen/common'
make[3]: *** [/home/khansa/xen-3.2.0/xen/common/built_in.o] Error 2
make[3]: Leaving directory `/home/khansa/xen-3.2.0/xen/arch/x86'
make[2]: *** [/home/khansa/xen-3.2.0/xen/xen] Error 2
make[2]: Leaving directory `/home/khansa/xen-3.2.0/xen'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/home/khansa/xen-3.2.0/xen'
make: *** [install-xen] Error 2

Any idea why am I getting this error? 
My operating system is fedora 17 with  gcc version 4.7.0

Thanks


list at fajar

Aug 8, 2012, 11:00 PM

Post #2 of 8 (300 views)
Permalink
Re: compiling an old XEN version [In reply to]

On Thu, Aug 9, 2012 at 12:49 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
> hi all,
> I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0.

My first question would be "why"?
Most of the time, latest upstream version, or distro-provided version
should work better instead of manually compiling an old version
yourself.

> Any idea why am I getting this error?
> My operating system is fedora 17 with gcc version 4.7.0

It's quite common that certain software can only be compiled with
certain versions of gcc. Since you're using an old, unmaintained
version, I doubt anyone is going to fix that. I suggest you either:
- use distro-provided version (e.g. RHEL5's xen-3.1.2+), or
- try latest stable version (4.1.2), or at least latest 3.x version to
see if the problem is fixed there

--
Fajar

_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users


s.seitz at netzhaut

Aug 8, 2012, 11:29 PM

Post #3 of 8 (316 views)
Permalink
Re: compiling an old XEN version [In reply to]

Hi,

3.2 is a few days old. I think it's more likely to have compile errors
with gcc 4.7 than
a clean build result.

I'ld try it with rhel/centos 5 or debian lenny tools.

cheers,


Am Mittwoch, den 08.08.2012, 22:49 -0700 schrieb maheen butt:
> hi all,
> I want to use Xenlinux and an old version of Xen hypervisor xen
> 3.2.0.
> For compilation I followed following instruction given by Jeremie Le
> Hen
> % mkdir build
> % wget http://bits.xensource.com/oss-xen/release/3.2.0/xen-3.2.0.tar.gz
> % tar xzf xen-3.2.0.tar.gz
> % # Download the xenifid kernel tree manually, but NOT in xen-3.2.0/
> % # because the buildconfig/select-repository script would skip it.
> % # ! xen-3.2.0/ and linux-2.6.18-xen.hg/ must be at the same level !
> % hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg
> % cd xen-3.2.0
> % make prep-kernels
> % cp /boot/config-2.6.18-my build-linux-2.6.18-xen_x86_32/.config
> % make dist
>
>
>
> everything was going good until I gave commang 'make dist' I
> encountered with following errorsIn file included from
> grant_table.c:1520:0:
>
>
> compat/grant_table.c: At top level:
> compat/grant_table.c:9:214: error: variably modified
> ‘__checkFstruct_grant_entry__flags’ at file scope [-Werror]
> compat/grant_table.c:9:350: error: variably modified
> ‘__checkFstruct_grant_entry__domid’ at file scope [-Werror]
> compat/grant_table.c:9:486: error: variably modified
> ‘__checkFstruct_grant_entry__frame’ at file scope [-Werror]
> In file included from grant_table.c:1520:0:
> compat/grant_table.c:13:267: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__host_addr’ at file scope
> [-Werror]
> compat/grant_table.c:13:434: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__flags’ at file scope [-Werror]
> compat/grant_table.c:13:593: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__ref’ at file scope [-Werror]
> compat/grant_table.c:13:750: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__dom’ at file scope [-Werror]
> compat/grant_table.c:13:913: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__status’ at file scope [-Werror]
> compat/grant_table.c:13:1079: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__handle’ at file scope [-Werror]
> compat/grant_table.c:13:1257: error: variably modified
> ‘__checkFstruct_gnttab_map_grant_ref__dev_bus_addr’ at file scope
> [-Werror]
> In file included from grant_table.c:1520:0:
> compat/grant_table.c:17:277: error: variably modified
> ‘__checkFstruct_gnttab_unmap_grant_ref__host_addr’ at file scope
> [-Werror]
> compat/grant_table.c:17:464: error: variably modified
> ‘__checkFstruct_gnttab_unmap_grant_ref__dev_bus_addr’ at file scope
> [-Werror]
> compat/grant_table.c:17:642: error: variably modified
> ‘__checkFstruct_gnttab_unmap_grant_ref__handle’ at file scope
> [-Werror]
> compat/grant_table.c:17:814: error: variably modified
> ‘__checkFstruct_gnttab_unmap_grant_ref__status’ at file scope
> [-Werror]
> In file included from grant_table.c:1520:0:
> compat/grant_table.c:21:287: error: variably modified
> ‘__checkFstruct_gnttab_unmap_and_replace__host_addr’ at file scope
> [-Werror]
> compat/grant_table.c:21:472: error: variably modified
> ‘__checkFstruct_gnttab_unmap_and_replace__new_addr’ at file scope
> [-Werror]
> compat/grant_table.c:21:652: error: variably modified
> ‘__checkFstruct_gnttab_unmap_and_replace__handle’ at file scope
> [-Werror]
> compat/grant_table.c:21:830: error: variably modified
> ‘__checkFstruct_gnttab_unmap_and_replace__status’ at file scope
> [-Werror]
> In file included from grant_table.c:1520:0:
> compat/grant_table.c:29:240: error: variably modified
> ‘__checkFstruct_gnttab_dump_table__dom’ at file scope [-Werror]
> compat/grant_table.c:29:394: error: variably modified
> ‘__checkFstruct_gnttab_dump_table__status’ at file scope [-Werror]
> cc1: all warnings being treated as errors
> make[4]: *** [grant_table.o] Error 1
> make[4]: Leaving directory `/home/khansa/xen-3.2.0/xen/common'
> make[3]: *** [/home/khansa/xen-3.2.0/xen/common/built_in.o] Error 2
> make[3]: Leaving directory `/home/khansa/xen-3.2.0/xen/arch/x86'
> make[2]: *** [/home/khansa/xen-3.2.0/xen/xen] Error 2
> make[2]: Leaving directory `/home/khansa/xen-3.2.0/xen'
> make[1]: *** [install] Error 2
> make[1]: Leaving directory `/home/khansa/xen-3.2.0/xen'
> make: *** [install-xen] Error 2
>
>
> Any idea why am I getting this error?
> My operating system is fedora 17 with gcc version 4.7.0
>
>
> Thanks
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users [at] lists
> http://lists.xen.org/xen-users
Attachments: signature.asc (0.48 KB)


maheen_butt26 at yahoo

Aug 27, 2012, 4:27 AM

Post #4 of 8 (265 views)
Permalink
Re: compiling an old XEN version [In reply to]

________________________________
From: Fajar A. Nugraha <list [at] fajar>
To: maheen butt <maheen_butt26 [at] yahoo>
Cc: "xen-users [at] lists" <xen-users [at] lists>
Sent: Thursday, August 9, 2012 11:00 AM
Subject: Re: [Xen-users] compiling an old XEN version

On Thu, Aug 9, 2012 at 12:49 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
> hi all,
> I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0.

My first question would be "why"?

For MS thesis I'm considering Xen to port it for MIPS. as there is no PV_ops 
support available in case of MIPS so I'm forced to use old versions of Xen


Most of the time, latest upstream version, or distro-provided version
should work better instead of manually compiling an old version
yourself.

> Any idea why am I getting this error?
> My operating system is fedora 17 with  gcc version 4.7.0

It's quite common that certain software can only be compiled with
certain versions of gcc. Since you're using an old, unmaintained
version, I doubt anyone is going to fix that. I suggest you either:
- use distro-provided version (e.g. RHEL5's xen-3.1.2+), or

I 'm using RHEL5.0, and install prebuild rpm packages provided by xen.org
http://xen.org/download/dl_31rhel5.html
As directed in ReadMe after installing given RPM's, I change grub.conf as follows
title My Distro with Xen (2.6.18-xen_3.1.0) root (hd0,0) kernel /xen-3.1.0.gz module /vmlinuz-2.6.18-xen_3.1.0 ro root=/dev/sda1 module /initrd-2.6.18-xen_3.1.0.img
where /dev/sda1 is the partition where RHEL5.0 lies.
when I rebooted and selected Xen kernel from grub menu
kernel did not booted showing following error
switchroot:mount failed no such file or directory
and it cant able to mount rootfile system as it repoted
"could not find file system /dev/root"
would you please tell me how can I resolve this issue?- try latest stable version (4.1.2), or at least latest 3.x version to
see if the problem is fixed there

--
Fajar

_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users


list at fajar

Aug 27, 2012, 4:41 AM

Post #5 of 8 (268 views)
Permalink
Re: compiling an old XEN version [In reply to]

On Mon, Aug 27, 2012 at 6:27 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
>
>
>
>
> ________________________________
> From: Fajar A. Nugraha <list [at] fajar>
> To: maheen butt <maheen_butt26 [at] yahoo>
> Cc: "xen-users [at] lists" <xen-users [at] lists>
> Sent: Thursday, August 9, 2012 11:00 AM
> Subject: Re: [Xen-users] compiling an old XEN version
>
> On Thu, Aug 9, 2012 at 12:49 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
>> hi all,
>> I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0.
>
> My first question would be "why"?
>
> For MS thesis I'm considering Xen to port it for MIPS. as there is no PV_ops
> support available in case of MIPS so I'm forced to use old versions of Xen

Then your questions should be to xen-devel. That is, assuming you
already have the basics knowledge and skill required to port a
software to a new architecture.


> I 'm using RHEL5.0, and install prebuild rpm packages provided by xen.org
> http://xen.org/download/dl_31rhel5.html

If you use RHEL5 (do NOT use 5.0. 5.8 is out already), then simply use
the included xen rpm. Do NOT download anything from xen.org. If you
want to modify something, download the SRPM, and do the modifications
there.

Seriously though, if your goal is to port it to MIPS, start with
xen-unstable from mercurial, using a new-enough dom0 (e.g. latest
fedora/rhel/whatever). Don't bother porting old version.

--
Fajar

_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users


Ian.Campbell at citrix

Aug 28, 2012, 1:51 AM

Post #6 of 8 (264 views)
Permalink
Re: compiling an old XEN version [In reply to]

On Mon, 2012-08-27 at 12:27 +0100, maheen butt wrote:
> On Thu, Aug 9, 2012 at 12:49 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
> > hi all,
> > I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0.
>
> My first question would be "why"?
>
> For MS thesis I'm considering Xen to port it for MIPS. as there is no PV_ops
> support available in case of MIPS so I'm forced to use old versions of Xen

pvops is an internal implementation detail of the upstream Linux x86
port to Xen. It has absolutely no bearing on which version of Xen you
run and it isn't really relevant for anything other than x86 unless you
intend to replicate that infrastructure on MIPS.

There is also no particular link between Xen and the dom0/domU kernel (this
is the reason Xen stopped shipping a patched kernel tree). If you are
working on a new port then I would strongly suggest that you use
xen-unstable and upstream Linux kernel as your starting point. You will
find there is very little interest in the developer community in
supporting a port to anything older.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users


Ian.Campbell at citrix

Aug 28, 2012, 1:52 AM

Post #7 of 8 (267 views)
Permalink
Re: compiling an old XEN version [In reply to]

On Tue, 2012-08-28 at 09:51 +0100, Ian Campbell wrote:
> On Mon, 2012-08-27 at 12:27 +0100, maheen butt wrote:
> > On Thu, Aug 9, 2012 at 12:49 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
> > > hi all,
> > > I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0.
> >
> > My first question would be "why"?
> >
> > For MS thesis I'm considering Xen to port it for MIPS. as there is no PV_ops
> > support available in case of MIPS so I'm forced to use old versions of Xen
>
> pvops is an internal implementation detail of the upstream Linux x86
> port to Xen. It has absolutely no bearing on which version of Xen you
> run and it isn't really relevant for anything other than x86 unless you
> intend to replicate that infrastructure on MIPS.
>
> There is also no particular link between Xen and the dom0/domU kernel (this
> is the reason Xen stopped shipping a patched kernel tree). If you are
> working on a new port then I would strongly suggest that you use
> xen-unstable and upstream Linux kernel as your starting point. You will
> find there is very little interest in the developer community in
> supporting a port to anything older.

Also you should discuss this on xen-devel to avoid duplicating work with
others. I'm aware of at least one previous port to the MIPS architecture
although it was some time ago and I've not seen any code posted
upstream.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users


pasik at iki

Aug 28, 2012, 10:29 AM

Post #8 of 8 (255 views)
Permalink
Re: compiling an old XEN version [In reply to]

On Tue, Aug 28, 2012 at 09:52:41AM +0100, Ian Campbell wrote:
> On Tue, 2012-08-28 at 09:51 +0100, Ian Campbell wrote:
> > On Mon, 2012-08-27 at 12:27 +0100, maheen butt wrote:
> > > On Thu, Aug 9, 2012 at 12:49 PM, maheen butt <maheen_butt26 [at] yahoo> wrote:
> > > > hi all,
> > > > I want to use Xenlinux and an old version of Xen hypervisor xen 3.2.0.
> > >
> > > My first question would be "why"?
> > >
> > > For MS thesis I'm considering Xen to port it for MIPS. as there is no PV_ops
> > > support available in case of MIPS so I'm forced to use old versions of Xen
> >
> > pvops is an internal implementation detail of the upstream Linux x86
> > port to Xen. It has absolutely no bearing on which version of Xen you
> > run and it isn't really relevant for anything other than x86 unless you
> > intend to replicate that infrastructure on MIPS.
> >
> > There is also no particular link between Xen and the dom0/domU kernel (this
> > is the reason Xen stopped shipping a patched kernel tree). If you are
> > working on a new port then I would strongly suggest that you use
> > xen-unstable and upstream Linux kernel as your starting point. You will
> > find there is very little interest in the developer community in
> > supporting a port to anything older.
>
> Also you should discuss this on xen-devel to avoid duplicating work with
> others. I'm aware of at least one previous port to the MIPS architecture
> although it was some time ago and I've not seen any code posted
> upstream.
>

I think there's a Xen MIPS talk at XenSummit today.

-- Pasi


_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users

Xen users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.