Re: [Qemu-devel] Question/problems with Qemu and 64Bit Opensuse 10.2

2006-12-23 Thread Werner Dittmann
When Qemu seems to loop I switched to monitor mode stop the emulator
and gathered the output of some info operations. The info registers
show that registers contain the strange values, for example:

RBX=80523028
RSP=80522dc0
RIP=8025e67c

Is it normal that e.g. the instruction pointer (RIP) can have such a
value? Any clue where to look why this loop happens?

Just as a side note: trying to print registers using p /x $r15 this
show the content of R15, but using p /x $rip or p /x $rbx gives an
unknown register error message.

Regards,
Werner


Werner Dittmann wrote:
 Just forgot to give the info about my system:
 
 Qemu was built and runs on a Suse 10.1 64 bit system (AMD CPU). Also,
 while compiling Qemu I got quite some warning about casting pointers to
 integer of different size (64bit vs 32 bit). Is this ok?
 
 Regards,
 Werner
 
 Werner Dittmann wrote:
 All,

 currently I'm trying to install an Opensuse 10.2 64Bit version in Qemu.

 Using a plain 0.82 didn't work out, after the Install screen Qemu goes
 in a loop. I've tried several parameters (witout net, ACPI, kqemu, etc).
 I could not even stop Qemu but had to use kill -9 .
 Because of some mail in the list that reported similar errors I
 downloaded the latest CVS version and built it using a gcc 3.3.

 That didn't solve the problem: It seems to be in a loop but I can close
 the qemu window and the window also grabs the mouse cursor (that was not
 the case  with the 0.8.2 version).

 After loading the kernel I get the following message on the console
 (only in VESA mode):

 
 Decompressing Linux ... done.
 Booting the kernel.
 

 and at the bottom of the console screen the message (without the qutes):

 kernel direct mapping tables up to 1 @ 8000-d000

 I tried to switch on some -d but I don't know which one is relevant
 here. I tried -d int but this produced about 90MB log data in just
 some seconds.

 Which info do you need to get down to the problem? What can I try to
 tackle the problem?

 Regards,
 Werner

 PS: Because I'm somewhat experienced with security software I would ask
 if there is any interest to have a TPM module (Software based TPM) for
 Qemu that looks like a real HW TPM according the the TPM specs? If yes I
 would start to look how to do it for Qemu. There is a software based TPM
 avaliable with a GPL licence. The only thing to do would be to wrap it
 with the HW interface functions (it's a memory mapped interface) so that
 standard drivers would see it as standard TPM module.

 Werner




 ___
 Qemu-devel mailing list
 Qemu-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/qemu-devel

 
 
 
 
 ___
 Qemu-devel mailing list
 Qemu-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/qemu-devel
 



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Question/problems with Qemu and 64Bit Opensuse 10.2

2006-12-23 Thread Thiemo Seufer
Werner Dittmann wrote:
 When Qemu seems to loop I switched to monitor mode stop the emulator
 and gathered the output of some info operations. The info registers
 show that registers contain the strange values, for example:
 
 RBX=80523028
 RSP=80522dc0
 RIP=8025e67c
 
 Is it normal that e.g. the instruction pointer (RIP) can have such a
 value? Any clue where to look why this loop happens?

They look like they were truncated to 32-bit (sign-extended negative)
values. Some operations probably assume 32-bit register width.


Thiemo


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] Question/problems with Qemu and 64Bit Opensuse 10.2

2006-12-23 Thread Werner Dittmann
Just for info: the 32 bit version of Opensuse 10.2 works and
installation runs. Thus the problem seems to be something with the 64
bit emulation.

Werner

Werner Dittmann wrote:
 When Qemu seems to loop I switched to monitor mode stop the emulator
 and gathered the output of some info operations. The info registers
 show that registers contain the strange values, for example:
 
 RBX=80523028
 RSP=80522dc0
 RIP=8025e67c
 
 Is it normal that e.g. the instruction pointer (RIP) can have such a
 value? Any clue where to look why this loop happens?
 
 Just as a side note: trying to print registers using p /x $r15 this
 show the content of R15, but using p /x $rip or p /x $rbx gives an
 unknown register error message.
 
 Regards,
 Werner
 
 
 Werner Dittmann wrote:
 Just forgot to give the info about my system:

 Qemu was built and runs on a Suse 10.1 64 bit system (AMD CPU). Also,
 while compiling Qemu I got quite some warning about casting pointers to
 integer of different size (64bit vs 32 bit). Is this ok?

 Regards,
 Werner

 Werner Dittmann wrote:
 All,

 currently I'm trying to install an Opensuse 10.2 64Bit version in Qemu.

 Using a plain 0.82 didn't work out, after the Install screen Qemu goes
 in a loop. I've tried several parameters (witout net, ACPI, kqemu, etc).
 I could not even stop Qemu but had to use kill -9 .
 Because of some mail in the list that reported similar errors I
 downloaded the latest CVS version and built it using a gcc 3.3.

 That didn't solve the problem: It seems to be in a loop but I can close
 the qemu window and the window also grabs the mouse cursor (that was not
 the case  with the 0.8.2 version).

 After loading the kernel I get the following message on the console
 (only in VESA mode):

 
 Decompressing Linux ... done.
 Booting the kernel.
 

 and at the bottom of the console screen the message (without the qutes):

 kernel direct mapping tables up to 1 @ 8000-d000

 I tried to switch on some -d but I don't know which one is relevant
 here. I tried -d int but this produced about 90MB log data in just
 some seconds.

 Which info do you need to get down to the problem? What can I try to
 tackle the problem?

 Regards,
 Werner

 PS: Because I'm somewhat experienced with security software I would ask
 if there is any interest to have a TPM module (Software based TPM) for
 Qemu that looks like a real HW TPM according the the TPM specs? If yes I
 would start to look how to do it for Qemu. There is a software based TPM
 avaliable with a GPL licence. The only thing to do would be to wrap it
 with the HW interface functions (it's a memory mapped interface) so that
 standard drivers would see it as standard TPM module.

 Werner




 ___
 Qemu-devel mailing list
 Qemu-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/qemu-devel




 ___
 Qemu-devel mailing list
 Qemu-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/qemu-devel

 
 
 
 ___
 Qemu-devel mailing list
 Qemu-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/qemu-devel
 



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] patch for supporting SMB on Solaris host

2006-12-23 Thread Ben Taylor

 Lennert Buytenhek [EMAIL PROTECTED] wrote: 
 On Fri, Dec 22, 2006 at 08:40:27PM -0500, Ben Taylor wrote:
 
  -snprintf(smb_cmdline, sizeof(smb_cmdline), /usr/sbin/smbd -s %s,
  - smb_conf);
  +snprintf(smb_cmdline, sizeof(smb_cmdline), % -s %s,
  + SMBD_BINARY, smb_conf);
 
 Doesn't look right to me?  (s/%/%s/)

Good catch.   otherwise, the patch is better?

Ben



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu elf_ops.h loader.c hw/mips_r4k.c target-ar...

2006-12-23 Thread Thiemo Seufer
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 06/12/23 14:18:40

Modified files:
.  : elf_ops.h loader.c 
hw : mips_r4k.c 
target-arm : cpu.h 
target-i386: cpu.h 
target-m68k: cpu.h 
target-mips: cpu.h 
target-ppc : cpu.h 
target-sh4 : cpu.h 
target-sparc   : cpu.h 

Log message:
Check ELF binaries for machine type and endianness.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/elf_ops.h?cvsroot=qemur1=1.3r2=1.4
http://cvs.savannah.gnu.org/viewcvs/qemu/loader.c?cvsroot=qemur1=1.3r2=1.4
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/mips_r4k.c?cvsroot=qemur1=1.27r2=1.28
http://cvs.savannah.gnu.org/viewcvs/qemu/target-arm/cpu.h?cvsroot=qemur1=1.17r2=1.18
http://cvs.savannah.gnu.org/viewcvs/qemu/target-i386/cpu.h?cvsroot=qemur1=1.38r2=1.39
http://cvs.savannah.gnu.org/viewcvs/qemu/target-m68k/cpu.h?cvsroot=qemur1=1.1r2=1.2
http://cvs.savannah.gnu.org/viewcvs/qemu/target-mips/cpu.h?cvsroot=qemur1=1.15r2=1.16
http://cvs.savannah.gnu.org/viewcvs/qemu/target-ppc/cpu.h?cvsroot=qemur1=1.23r2=1.24
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sh4/cpu.h?cvsroot=qemur1=1.3r2=1.4
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/cpu.h?cvsroot=qemur1=1.25r2=1.26


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] qemu elf_ops.h loader.c hw/mips_r4k.c target-ar...

2006-12-23 Thread Thiemo Seufer
Fabrice Bellard wrote:
 Your change in elf_ops.h regarding the labels fail1 and fail2 is not 
 necessary: qemu_free(NULL) is perfectly valid and there are many pieces 
 of code relying on it. Please revert.

Changed accordingly.


Thiemo


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu vl.c

2006-12-23 Thread Paul Brook
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook pbrook 06/12/23 15:37:34

Modified files:
.  : vl.c 

Log message:
Solaris SMBD hacks (Ben Taylor).

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/vl.c?cvsroot=qemur1=1.226r2=1.227


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu vl.c

2006-12-23 Thread Thiemo Seufer
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 06/12/23 22:51:27

Modified files:
.  : vl.c 

Log message:
Null character instead of numeric null.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/vl.c?cvsroot=qemur1=1.227r2=1.228


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel