Re: [XenPPC] 64bit apps in DomU should get a more useful error message [Fixed]
Jimi Xenidis wrote: Now Executed in a xenppc DomU ./hellobit.32 Hello World! ./hellobit.64 -bash: ./hellobit.64: No such file or directory hmm.. this works just fine for me and should have nothing to do with Xen at all, unless your block device does not work :) can you cat it? ls it? file it? Yes I can (tested it already). Hollis suggested that there may be some compat libraries missing but I did not find an obvious one missing. And thats right, some links in /lib64 were broken while I created the DomU image files from my Dom0 some months ago. I should never trust rpm -qa without checking file existence ;-) =Fixed, the following is just a bit of output how it looks like so that everyone with a similar issue will find some help here via google. DomU: uname -a Linux xen_SLES10_G1 2.6.18-Xen #25 SMP Sun Jul 29 00:29:02 CEST 2007 ppc64 ppc64 ppc64 GNU/Linux file hellobit.32 hellobit.64 hellobit.32: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped hellobit.64: ELF 64-bit MSB executable, cisco 7500, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped ldd hellobit.32 linux-vdso32.so.1 = (0x0010) libc.so.6 = /lib/power4/libc.so.6 (0x0fe8b000) /lib/ld.so.1 (0xf7fe1000) ldd hellobit.64 not a dynamic executable Dom0: uname -a Linux pbclient4 2.6.18-Xen #25 SMP Sun Jul 29 00:29:02 CEST 2007 ppc64 ppc64 ppc64 GNU/Linux file hellobit.32 hellobit.64 hellobit.32: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped hellobit.64: ELF 64-bit MSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped ldd hellobit.32 linux-vdso32.so.1 = (0x0010) libc.so.6 = /lib/libc.so.6 (0x0fe8d000) /lib/ld.so.1 (0xf7fe1000) ldd hellobit.64 linux-vdso64.so.1 = (0x0010) libc.so.6 = /lib64/libc.so.6 (0x04055000) /lib64/ld64.so.1 (0x0400) -- Grüsse / regards, Christian Ehrhardt IBM Linux Technology Center, Open Virtualization +49 7031/16-3385 [EMAIL PROTECTED] [EMAIL PROTECTED] IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Johann Weihen 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
Re: [XenPPC] 64bit apps in DomU should get a more useful error message [Fixed]
On Jul 10, 2007, at 9:22 AM, Christian Ehrhardt wrote: Jimi Xenidis wrote: Now Executed in a xenppc DomU ./hellobit.32 Hello World! ./hellobit.64 -bash: ./hellobit.64: No such file or directory hmm.. this works just fine for me and should have nothing to do with Xen at all, unless your block device does not work :) can you cat it? ls it? file it? Yes I can (tested it already). Hollis suggested that there may be some compat libraries missing but I did not find an obvious one missing. And thats right, some links in /lib64 were broken while I created the DomU image files from my Dom0 some months ago. I should never trust rpm -qa without checking file existence ;-) ahh I see, so the No such file or directory refers to /lib64/ ld64.so.1 which is the interpreter for the dynamic executable? $ objdump -s -j .interp hellobit.64 ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
[XenPPC] 64bit apps in DomU should get a more useful error message
Example:
#include stdio.h
main()
{
printf (Hello World!\n);
}
Compiled (on Dom0):
gcc -m32 hellobit.c -o hellobit.32
gcc -m64 hellobit.c -o hellobit.64
Now Executed in a xenppc DomU
./hellobit.32
Hello World!
./hellobit.64
-bash: ./hellobit.64: No such file or directory
As far as I remember xenppc DomU systems are 32bit (please correct me if
not) even if our kernel may say otherwise:
uname -a
Linux linux 2.6.18-Xen #25 SMP Sun Jul 29 00:29:02 CEST 2007 ppc64 ppc64
ppc64 GNU/Linux
I played a bit around with powerpc32 which changes the env so that e.g.
uname -m will report a 32bit system, but this did neither help me to get
64bit apps running (expected) nor better error messages.
The problem is not that 64bit apps do not run, but I think the message
should be something better than No such file or directory
-My question now: could/should we add a more sophisticated mechanism to
give the user running into this something like you are not 64bit ?
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
[EMAIL PROTECTED]
[EMAIL PROTECTED]
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen
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
Re: [XenPPC] 64bit apps in DomU should get a more useful error message
On Jul 9, 2007, at 7:47 AM, Christian Ehrhardt wrote:
Example:
#include stdio.h
main()
{
printf (Hello World!\n);
}
Compiled (on Dom0):
gcc -m32 hellobit.c -o hellobit.32
gcc -m64 hellobit.c -o hellobit.64
Now Executed in a xenppc DomU
./hellobit.32
Hello World!
./hellobit.64
-bash: ./hellobit.64: No such file or directory
hmm.. this works just fine for me and should have nothing to do with
Xen at all, unless your block device does not work :)
can you cat it? ls it? file it?
-JX
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
