Problems Building Xen 4.0.x on ia64 (various releases)

Problems Building Xen 4.0.x on ia64 (various releases)

[Julio C. Ortega]

Good morning

Sorry to post this problem in this list, i wasn't sure that posting to  
xen-users got me a reply


I've faced a couple of problems building Xen 4.0.0, 4.0.1 and 4.0.2rc1
from sources on an itanium2 machine running debian 6.0

I'll describe the problems i've faced with all three releases.

XEN 4.0.0:

Downloaded with hg:

hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
xen-4.0.0

Almost everything compiles, the problem i'm facing it's when make world
it's building the xen tools:

gcc  -O2 -fomit-frame-pointer -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-D__XEN_TOOLS__ -MMD -MF .xc_dom_ia64.o.d  -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../xen/common/libelf -Iia64
-Werror -Wmissing-prototypes  -I. -I../xenstore -I../include -c -o
xc_dom_ia64.o xc_dom_ia64.c
In file included from xc_dom_ia64.c:26:
ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
directory
In file included from xc_dom_ia64.c:26:
ia64/asm/dom_fw_common.h:65: error: expected specifier-qualifier-list
before ?fpswa_interface_t?
make[5]: *** [xc_dom_ia64.o] Error 1
make[5]: exiting `/root/xen-4.0.0/tools/libxc'
make[4]: *** [build] Error 2
make[4]: exiting `/root/xen-4.0.0/tools/libxc'
make[3]: *** [subdir-install-libxc] Error 2
make[3]: exiting `/root/xen-4.0.0/tools'
make[2]: *** [subdirs-install] Error 2
make[2]: exiting `/root/xen-4.0.0/tools'

This particular problem also occurs in 4.0.1 and 4.0.2rc1 (testing) when
issuing: "make tools"

It must be something i'm missing, but i can't see what it could be (all
the build dependencies are met), i'm using gcc-4.4.5

XEN 4.0.1 & XEN 4.0.2rc1 (testing)

This two releases were downloaded also cloning with mercurial.

In addition to the problem compiling "tools" that i've described above
,this happens when making core xen or issuing "make world":

4.0.1:

d -g  -T xen.lds.s -N -Map /root/xen-4.0.1/xen/.xen-syms.0.map
linux-xen/head.o /root/xen-4.0.1/xen/common/built_in.o
/root/xen-4.0.1/xen/drivers/built_in.o
/root/xen-4.0.1/xen/xsm/built_in.o
/root/xen-4.0.1/xen/arch/ia64/built_in.o \
                 /root/xen-4.0.1/xen/common/symbols-dummy.o -o
/root/xen-4.0.1/xen/.xen-syms.0
/root/xen-4.0.1/xen/common/built_in.o: In function `kexec_exec':
/root/xen-4.0.1/xen/common/kexec.c:493: undefined reference to
`continue_hypercall_on_cpu'
make[3]: *** [/root/xen-4.0.1/xen/xen-syms] Error 1

4.0.2rc1:

ld -g  -T xen.lds.s -N -Map /root/xen-4.0.2rc1/xen/.xen-syms.0.map
linux-xen/head.o /root/xen-4.0.2rc1/xen/common/built_in.o
/root/xen-4.0.2rc1/xen/drivers/built_in.o
/root/xen-4.0.2rc1/xen/xsm/built_in.o
/root/xen-4.0.2rc1/xen/arch/ia64/built_in.o \
                 /root/xen-4.0.2rc1/xen/common/symbols-dummy.o -o
/root/xen-4.0.2rc1/xen/.xen-syms.0
/root/xen-4.0.2rc1/xen/common/built_in.o: In function `kexec_exec':
/root/xen-4.0.2rc1/xen/common/kexec.c:493: undefined reference to
`continue_hypercall_on_cpu'
make[3]: *** [/root/xen-4.0.2rc1/xen/xen-syms] Error 1


Digging up and googling i've found out nothing, but seems weird that
particularly continue_hypercall_on_cpu() it's only present in
architecture specific include files.

Any help would be greatly appreciated, even if it's pointing me to the
right direction for a successfull build.


Have a nice day.

-- 
------------------------------------
Julio C. Ortega
Technical Coordinator
Infrastructure
ONUVA
http://www.onuva.com

Re: Problems Building Xen 4.0.x on ia64 (various releases)

[KUWAMURA Shin'ya]

[-- Attachment #1: Type: Text/Plain, Size: 1368 bytes --]

Hi,

>>>>> On Sun, 19 Dec 2010 10:08:16 -0430
>>>>> jortega@onuva.com("Julio C. Ortega")  said:
> 
> I've faced a couple of problems building Xen 4.0.0, 4.0.1 and 4.0.2rc1
> from sources on an itanium2 machine running debian 6.0
> I'll describe the problems i've faced with all three releases.
> 
> XEN 4.0.0:
> In file included from xc_dom_ia64.c:26:
> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
> directory

Could you try gcc-4.1 instead of gcc-4.4? Building xen with GCC 4.4
has a known problem and using GCC 4.1 can avoid it:
http://lists.xensource.com/archives/html/xen-ia64-devel/2010-05/msg00007.html

> XEN 4.0.1 & XEN 4.0.2rc1 (testing)
> /root/xen-4.0.1/xen/common/built_in.o: In function `kexec_exec':
> /root/xen-4.0.1/xen/common/kexec.c:493: undefined reference to
> `continue_hypercall_on_cpu'
> 4.0.2rc1:
> /root/xen-4.0.2rc1/xen/common/built_in.o: In function `kexec_exec':
> /root/xen-4.0.2rc1/xen/common/kexec.c:493: undefined reference to
> `continue_hypercall_on_cpu'
> make[3]: *** [/root/xen-4.0.2rc1/xen/xen-syms] Error 1
> Digging up and googling i've found out nothing, but seems weird that
> particularly continue_hypercall_on_cpu() it's only present in
> architecture specific include files.

You are right. Could you apply the attached patch?
# Notice that this fix is ad hoc.

Best regards,
-- 
  KUWAMURA Shin'ya

[-- Attachment #2: fix-kexec-continue_hypercall_on_cpu.patch --]
[-- Type: Text/X-Patch, Size: 569 bytes --]

diff -r b536ebfba183 xen/common/kexec.c
--- a/xen/common/kexec.c	Wed Aug 25 09:22:42 2010 +0100
+++ b/xen/common/kexec.c	Mon Dec 20 14:44:33 2010 +0900
@@ -490,7 +490,12 @@ static int kexec_exec(XEN_GUEST_HANDLE(v
     {
     case KEXEC_TYPE_DEFAULT:
         image = &kexec_image[base + pos];
+#ifdef CONFIG_X86
         ret = continue_hypercall_on_cpu(0, kexec_reboot, image);
+#else
+        one_cpu_only();
+        machine_reboot_kexec(image); /* Does not return */
+#endif
         break;
     case KEXEC_TYPE_CRASH:
         kexec_crash(); /* Does not return */

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

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

Re: Problems Building Xen 4.0.x on ia64 (various releases)

[Julio C. Ortega]

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

El 20/12/10 04:40, KUWAMURA Shin'ya escribió:
> Hi,

Hello, thanks for your reply, mine's inline.

> 
>>
>> XEN 4.0.0:
>> In file included from xc_dom_ia64.c:26:
>> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
>> directory
> 
> Could you try gcc-4.1 instead of gcc-4.4? Building xen with GCC 4.4
> has a known problem and using GCC 4.1 can avoid it:
> http://lists.xensource.com/archives/html/xen-ia64-devel/2010-05/msg00007.html
> 

I've tried with GCC 4.1, also to no avail. The error message doesn't
change (i've cleaned the tree and rebuilt, of course)

I'll repaste the error:

gcc  -O2 -fomit-frame-pointer -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-D__XEN_TOOLS__ -MMD -MF .xc_dom_ia64.o.d  -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../xen/common/libelf -Iia64
-Werror -Wmissing-prototypes  -I. -I../xenstore -I../include -c -o
xc_dom_ia64.o xc_dom_ia64.c
In file included from xc_dom_ia64.c:26:
ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
directory
In file included from xc_dom_ia64.c:26:
ia64/asm/dom_fw_common.h:65: error: expected specifier-qualifier-list
before ‘fpswa_interface_t’


>> XEN 4.0.1 & XEN 4.0.2rc1 (testing)
>> /root/xen-4.0.1/xen/common/built_in.o: In function `kexec_exec':
>> /root/xen-4.0.1/xen/common/kexec.c:493: undefined reference to
>> `continue_hypercall_on_cpu'
>> 4.0.2rc1:
>> /root/xen-4.0.2rc1/xen/common/built_in.o: In function `kexec_exec':
>> /root/xen-4.0.2rc1/xen/common/kexec.c:493: undefined reference to
>> `continue_hypercall_on_cpu'
>> make[3]: *** [/root/xen-4.0.2rc1/xen/xen-syms] Error 1
>> Digging up and googling i've found out nothing, but seems weird that
>> particularly continue_hypercall_on_cpu() it's only present in
>> architecture specific include files.
> 
> You are right. Could you apply the attached patch?
> # Notice that this fix is ad hoc.

With this patch applied "make xen" doesn't fail anymore. ¡Thanks!


> 
> Best regards,

Thanks Shin'ya can you give me any pointers on the "asm/fpswa.h" build
error?

Have a nice day.

-- 
------------------------------------
Julio C. Ortega
Technical Coordinator
Infrastructure
ONUVA
http://www.onuva.com


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 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 Building Xen 4.0.x on ia64 (various releases)

[KUWAMURA Shin'ya]

[-- Attachment #1: Type: Text/Plain, Size: 1291 bytes --]

Hi,

>>>>> On Mon, 20 Dec 2010 08:44:25 -0430
>>>>> jortega@onuva.com("Julio C. Ortega")  said:
> 
> >> XEN 4.0.0:
> >> In file included from xc_dom_ia64.c:26:
> >> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
> >> directory
> > 
> > Could you try gcc-4.1 instead of gcc-4.4? Building xen with GCC 4.4
> > has a known problem and using GCC 4.1 can avoid it:
> > http://lists.xensource.com/archives/html/xen-ia64-devel/2010-05/msg00007.html
> 
> I've tried with GCC 4.1, also to no avail. The error message doesn't
> change (i've cleaned the tree and rebuilt, of course)
> 
> I'll repaste the error:
> 
> gcc  -O2 -fomit-frame-pointer -fno-strict-aliasing -std=gnu99 -Wall
> -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
> -D__XEN_TOOLS__ -MMD -MF .xc_dom_ia64.o.d  -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../xen/common/libelf -Iia64
> -Werror -Wmissing-prototypes  -I. -I../xenstore -I../include -c -o
> xc_dom_ia64.o xc_dom_ia64.c
> In file included from xc_dom_ia64.c:26:
> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
> directory

Could you try the attached patch?

The header asm/fpswa.h was at /usr/include/asm/fpswa.h, but it was
removed in recent kernel.

Best regards,
-- 
  KUWAMURA Shin'ya

[-- Attachment #2: fix-ia64-fpswa.patch --]
[-- Type: Text/X-Patch, Size: 577 bytes --]

diff -r b536ebfba183 tools/libxc/ia64/Makefile
--- a/tools/libxc/ia64/Makefile	Wed Aug 25 09:22:42 2010 +0100
+++ b/tools/libxc/ia64/Makefile	Wed Dec 22 10:41:21 2010 +0900
@@ -49,6 +49,7 @@ mk-symlinks-acpi: $(IA64_HDR_DIRS) $(IA6
 	( cd ia64/xen && ln -sf ../../$(XEN_ROOT)/xen/include/xen/acpi.h .)
 mk-symlinks-misc: $(IA64_HDR_DIRS)
 	( cd ia64/asm && ln -sf ../../$(XEN_ROOT)/xen/include/asm-ia64/linux-xen/asm/kregs.h .)
+	( cd ia64/asm && ln -sf ../../$(XEN_ROOT)/xen/include/asm-ia64/linux/asm/fpswa.h .)
 build: mk-symlinks-acpi mk-symlinks-misc
 
 clean: ia64-clean

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

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

Re: Problems Building Xen 4.0.x on ia64 (various releases)

[Julio C. Ortega]

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

El 21/12/10 21:19, KUWAMURA Shin'ya escribió:
> Hi,
> 
>>>>>> On Mon, 20 Dec 2010 08:44:25 -0430
>>>>>> jortega@onuva.com("Julio C. Ortega")  said:
>>
>>>> XEN 4.0.0:
>>>> In file included from xc_dom_ia64.c:26:
>>>> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
>>>> directory
>>>
>>> Could you try gcc-4.1 instead of gcc-4.4? Building xen with GCC 4.4
>>> has a known problem and using GCC 4.1 can avoid it:
>>> http://lists.xensource.com/archives/html/xen-ia64-devel/2010-05/msg00007.html
>>
>> I've tried with GCC 4.1, also to no avail. The error message doesn't
>> change (i've cleaned the tree and rebuilt, of course)
>>
>> I'll repaste the error:
>>
>> gcc  -O2 -fomit-frame-pointer -fno-strict-aliasing -std=gnu99 -Wall
>> -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
>> -D__XEN_TOOLS__ -MMD -MF .xc_dom_ia64.o.d  -D_LARGEFILE_SOURCE
>> -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../xen/common/libelf -Iia64
>> -Werror -Wmissing-prototypes  -I. -I../xenstore -I../include -c -o
>> xc_dom_ia64.o xc_dom_ia64.c
>> In file included from xc_dom_ia64.c:26:
>> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
>> directory
> 
> Could you try the attached patch?
> 
> The header asm/fpswa.h was at /usr/include/asm/fpswa.h, but it was
> removed in recent kernel.
> 
> Best regards,

Hello Shin'ya

I'm really thankful for all your provided help. I've got now a
successfull build, that i'm going to test ASAP.

However, i would like to know if it's possible to use a newer kernel
(like 2.6.30 or newer) with Xen 4.0 in Dom0 / DomU configuration to take
advantage of the new features in it.

I've tried jeremy's patchset (2.6.3x-stable) and it doesn't compile on IA64.

Anyhow, i'll shortly post details on how to successfully build al xen
vanilla components on Debian IA64.

Have a nice day.

-- 
------------------------------------
Julio C. Ortega
Technical Coordinator
Infrastructure
ONUVA
http://www.onuva.com


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 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 Building Xen 4.0.x on ia64 (various releases)

[Konrad Rzeszutek Wilk]

> > Could you try the attached patch?
> > 
> > The header asm/fpswa.h was at /usr/include/asm/fpswa.h, but it was
> > removed in recent kernel.
> > 
> > Best regards,
> 
> Hello Shin'ya
> 
> I'm really thankful for all your provided help. I've got now a
> successfull build, that i'm going to test ASAP.
> 
> However, i would like to know if it's possible to use a newer kernel
> (like 2.6.30 or newer) with Xen 4.0 in Dom0 / DomU configuration to take
> advantage of the new features in it.
> 
> I've tried jeremy's patchset (2.6.3x-stable) and it doesn't compile on IA64.

<nods> Have not looked at IA64 under pvops at all. If you have patches for this, please do
send them.

Re: Problems Building Xen 4.0.x on ia64 (various releases)

[KUWAMURA Shin'ya]

Hi,

>>>>> On Wed, 22 Dec 2010 17:33:47 -0430
>>>>> jortega@onuva.com("Julio C. Ortega")  said:
> 
> However, i would like to know if it's possible to use a newer kernel
> (like 2.6.30 or newer) with Xen 4.0 in Dom0 / DomU configuration to take
> advantage of the new features in it.

On ia64, the newer kernel cannot be used as dom0, since the feature of
dom0 is not implemented in it.

But it may be used as domU.

Best regards,
-- 
  KUWAMURA Shin'ya