Sorry Christian,
A lot of us have been at a conference this week.
Anyway... All our bits are in the the proper Xen development repositories
The build instructions are the same, but you get the bits from there.
-JX

On Sep 26, 2007, at 2:07 AM, Christian Kaiser2 wrote:

Hi,

I found out that "http://xenbits.xensource.com/ext/ppc/xen- unstable.hg" tree builds and works fine for me. What I described in my last post was for
"http://xenbits.xensource.com/xen-unstable.hg"; tree.

But there is still another thing that does not work for me. I've build the hypervisor, the kernel and the tools. I can boot into the hypervisor (using yaboot), the hypervisor is able to load the kernel. Xend executes with some
errors:

ioctl32(blktapctrl:3415): Unknown cmd fd(4) cmd(00000003){00} arg (00000003)
on /dev/xen/blktap0
ioctl32(blktapctrl:3415): Unknown cmd fd(4) cmd(00000004){00} arg (00000d57)
on /dev/xen/blktap0

The main problem is to create a domU. It fails with the error that cannot open "/proc/xen/balloon". The balloon driver is disabled for ppc in the xen linux kernel. So how can I prevent the tools or xend of using the balloon
driver??

Mit freundlichen Grüßen / Best Regards
Christian Kaiser
--
IBM Deutschland Entwicklung GmbH
Open Systems Firmware Development
mail: [EMAIL PROTECTED]

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[EMAIL PROTECTED] wrote on 09/24/2007 04:03:01 PM:


Hi all,

I tried to build xen on a JS21 blade today but some hints at the build
page
(http://wiki.xensource.com/xenwiki/XenPPC/Build) are confusing me.

The wiki says clone this:
"http://xenbits.xensource.com/ext/ppc/xen-unstable.hg";
But later it is two times mentioning the "xenppc-unstable" tree.

So was there a switch from "xenppc-unstable" to "xen-unstable"??
Which repository should be used to build the hypervisor?

The "xen-unstable" tree cannot be build on my machine. I get the
following
error:

gcc -O2 -fomit-frame-pointer -DELFSIZE=64 -DNDEBUG -fno-strict- aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -m64 -ffreestanding -fno-builtin
-fno-common
-iwithprefix include -Werror -pipe
-I/root/xen/xen-unstable.hg/xen/include
-I/root/xen/xen-unstable.hg/xen/include/asm-powerpc/mach-generic
-I/root/xen/xen-unstable.hg/xen/include/asm-powerpc/mach-default
-Wredundant-decls -Wpacked -msoft-float -O2 -g -D__XEN__ -c domain.c -o
domain.o
cc1: warnings being treated as errors
In file included from domain.c:22:
/root/xen/xen-unstable.hg/xen/include/xen/hypercall.h:117: warning:
redundant redeclaration of ‘do_xsm_op’
/root/xen/xen-unstable.hg/xen/include/xsm/xsm.h:24: warning: previous
declaration of ‘do_xsm_op’ was here
make[3]: *** [domain.o] Error 1
make[3]: Leaving directory `/root/xen/xen-unstable.hg/xen/common'
make[2]: *** [/root/xen/xen-unstable.hg/xen/common/built_in.o] Error 2 make[2]: Leaving directory `/root/xen/xen-unstable.hg/xen/arch/ powerpc'
make[1]: *** [/root/xen/xen-unstable.hg/xen/xen] Error 2
make[1]: Leaving directory `/root/xen/xen-unstable.hg/xen'
make: *** [build] Error 2
make: Leaving directory `/root/xen/xen-unstable.hg/xen'

After omitting "-Werror" in "xen/arch/powerpc/Rules.mk" I get this error:

gcc -O2 -fomit-frame-pointer -DELFSIZE=64 -DNDEBUG -fno-strict- aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -m64 -ffreestanding -fno-builtin
-fno-common
-iwithprefix include -pipe -I/root/xen/xen-unstable.hg/xen/include
-I/root/xen/xen-unstable.hg/xen/include/asm-powerpc/mach-generic
-I/root/xen/xen-unstable.hg/xen/include/asm-powerpc/mach-default
-Wredundant-decls -Wpacked -msoft-float -O2 -g -D__XEN__ -Wundef
-Wmissing-prototypes -Wmissing-declarations -Wshadow -nodefaultlibs
-nostartfiles -Wl,--omagic -Wl,-T,xen.lds start.o
/root/xen/xen-unstable.hg/xen/common/built_in.o
/root/xen/xen-unstable.hg/xen/drivers/built_in.o
/root/xen/xen-unstable.hg/xen/xsm/built_in.o
/root/xen/xen-unstable.hg/xen/arch/powerpc/built_in.o
/root/xen/xen-unstable.hg/xen/common/symbols-dummy.o -o .xen-syms
/root/xen/xen-unstable.hg/xen/arch/powerpc/built_in.o: In function
`do_physdev_op':
../x86/physdev.c:94: undefined reference to `xsm_apic'
../x86/physdev.c:77: undefined reference to `xsm_apic'
../x86/physdev.c:112: undefined reference to `xsm_assign_vector'
/root/xen/xen-unstable.hg/xen/arch/powerpc/built_in.o: In function
`__start_xen':
/root/xen/xen-unstable.hg/xen/arch/powerpc/setup.c:353: undefined
reference
to `acm_init'
/root/xen/xen-unstable.hg/xen/arch/powerpc/built_in.o: In function
`__hypercall_table':
(.data+0x2e1278): undefined reference to `do_acm_op'
collect2: ld returned 1 exit status
make[2]: *** [.xen-syms] Error 1
make[2]: Leaving directory `/root/xen/xen-unstable.hg/xen/arch/ powerpc'
make[1]: *** [/root/xen/xen-unstable.hg/xen/xen] Error 2
make[1]: Leaving directory `/root/xen/xen-unstable.hg/xen'
make: *** [build] Error 2
make: Leaving directory `/root/xen/xen-unstable.hg/xen'

I tried to play around with ACM and XSM but couldn't solve the problem.
Can
someone help me on this?

Mit freundlichen Grüßen / Best Regards
Christian Kaiser
--
IBM Deutschland Entwicklung GmbH
Open Systems Firmware Development
mail: [EMAIL PROTECTED]

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB
243294_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


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

Reply via email to