Re: [Qemu-devel] Typo in get_reloc_expr (dyngen.c)
Fabrice or Paul: Can we get this added? This patch has been posted to the list 4 or 5 times in various incarnations in the last year or soj. I posted a long message with the logs from the compile on why the current code is wrong, and why this patch fixes it. The basic problem is that code uses a sizeof construct, instead of the size of the string. What happens is all the labels end up being truncated, and the op.c won't compile on sparc. see analysis of this problem in http://lists.gnu.org/archive/html/qemu-devel/2006-04/msg00494.html Ben Stuart Brady [EMAIL PROTECTED] wrote: Hi, There's a small bug in get_reloc_expr in dyngen.c. It should only affect SPARC hosts, but it can't be causing any real problems, or someone would have noticed it by now. I'm trying to port QEMU to PA-RISC[0], and needed this code, so it did actually affect me. I've attached the (one-line) patch. -- Stuart Brady [0] http://homepage.ntlworld.com/wholehog/stuart/qemu/guest.html ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Ask for debugging linux kernel with Qemu 0.8.1 on Msys
Hi All,I've compiled Linux kernel 2.6.16 with kgdb on Linux. And after that, I've tried to debug this kernel with Qemu 0.8.1 on Msys to simulate ARM Processor. In fact, I've run the command below:qemu-system-arm -kernel myKernel -initrd arm_root.img -sBut I can't make the connection from arm-toolchain-gdb to the port 1234 (by default, this port must be openned by Qemu when using the option -s for debugging)Furthermore, I've confirmed if the port 1234 is openned or not with the command: netstat -ao and there is not port 1234 openned. I've also try the option -p 123456 to change the default port for debugging of Qemu but I've got the same result.Do you know where the problem arrive?Thank you so much for your support.Best regards.Thanh Sneak preview the all-new Yahoo.com. It's not radically different. Just radically better. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Ask for debugging linux kernel with Qemu 0.8.1 on Msys
On Tue, 6 Jun 2006 05:35:13 -0700 (PDT) Tieu Ma Dau [EMAIL PROTECTED] wrote: Hi All, I've compiled Linux kernel 2.6.16 with kgdb on Linux. And after that, I've tried to debug this kernel with Qemu 0.8.1 on Msys to simulate ARM Processor. In fact, I've run the command below: qemu-system-arm -kernel myKernel -initrd arm_root.img -s But I can't make the connection from arm-toolchain-gdb to the port 1234 (by default, this port must be openned by Qemu when using the option -s for debugging) Furthermore, I've confirmed if the port 1234 is openned or not with the command: netstat -ao and there is not port 1234 openned. I've also try the option -p 123456 to change the default port for debugging of Qemu but I've got the same result. Do you know where the problem arrive? Port 1234 is the port on the virtual machine's IP address, not the port on the real machine's IP address. So you need to be able to access the virtual machine's IP address from the real machine. For this you can use tun/tap networking - see the docs. It is not possible to do this with user-mode networking. -- Robin ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Ask for debugging linux kernel with Qemu 0.8.1 on Msys
In fact, I can connect by using the port 1234 on Linux with the command: (I use arm-toolchain and run the command: arm-linux-gdb vmlinux) (gdb) target remote localhost:1234 And the debugging mode run well (normally) but the problem arrives when running on Windows with Msys/MinGW Furthermore, I had tried make the connection for debugging (target remote qemu-machine:1234) between localhost and Qemu as 2 computers on a LAN but it is not possible; although I can make ping between these 2 computers Do you have any suggestions for this problem? Best regards Thanh Robin Green [EMAIL PROTECTED] wrote: On Tue, 6 Jun 2006 05:35:13 -0700 (PDT)Tieu Ma Dau wrote: Hi All, I've compiled Linux kernel 2.6.16 with kgdb on Linux. And after that, I've tried to debug this kernel with Qemu 0.8.1 on Msys to simulate ARM Processor. In fact, I've run the command below: qemu-system-arm -kernel myKernel -initrd arm_root.img -s But I can't make the connection from arm-toolchain-gdb to the port 1234 (by default, this port must be openned by Qemu when using the option -s for debugging) Furthermore, I've confirmed if the port 1234 is openned or not with the command: netstat -ao and there is not port 1234 openned. I've also try the option -p 123456 to change the default port for debugging of Qemu but I've got the same result. Do you know where the problem arrive?Port 1234 is the port on the virtual machine's IP address, not the porton the real machine's IP address. So you need to be able to access thevirtual machine's IP address from the real machine. For this you can usetun/tap networking - see the docs. It is not possible to do this withuser-mode networking.-- Robin Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Ask for debugging linux kernel with Qemu 0.8.1 on Msys
Hi, On 06/06/06, Robin Green [EMAIL PROTECTED] wrote: On Tue, 6 Jun 2006 05:35:13 -0700 (PDT) Tieu Ma Dau [EMAIL PROTECTED] wrote: Hi All, I've compiled Linux kernel 2.6.16 with kgdb on Linux. And after that, I've tried to debug this kernel with Qemu 0.8.1 on Msys to simulate ARM Processor. In fact, I've run the command below: qemu-system-arm -kernel myKernel -initrd arm_root.img -s But I can't make the connection from arm-toolchain-gdb to the port 1234 (by default, this port must be openned by Qemu when using the option -s for debugging) Furthermore, I've confirmed if the port 1234 is openned or not with the command: netstat -ao and there is not port 1234 openned. I've also try the option -p 123456 to change the default port for debugging of Qemu but I've got the same result. Do you know where the problem arrive? Port 1234 is the port on the virtual machine's IP address, not the port on the real machine's IP address. So you need to be able to access the virtual machine's IP address from the real machine. For this you can use tun/tap networking - see the docs. It is not possible to do this with user-mode networking. Acutally you don't need networking in the guest. QEMU listens on the host's port 1234 (and I think it listens on all interfaces, not only localhost, but I'm not sure of this one -- if this is not the case, make a ssh tunnel to debug remotely). -- Robin ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel Regards, Andrew -- balrog 2oo6 Dear Outlook users: Please remove me from your address books http://www.newsforge.com/article.pl?sid=03/08/21/143258 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [Patch] Kqemu patch for 2.6.17-rc2
Hi, I'm attaching a small update to Thomas's patch which conditionally enables this based on kernel version. As far as I can tell (from very brief research), module_param became available very late in 2.4. Also, the old version (MODULE_PARM) is supported in most 2.6 kernels as well. I picked arbitrarily 2.6.10 as the break-off point - it's really easy to change that to be something else. In any case, Fabrice, can you think about applying this, or something very similar, as it looks like MODULE_PARM has been finally abandoned in the latest kernels. Regards, Leo Reiter Thomas Petazzoni wrote: Hi, On 2.6.17-rc2, the MODULE_PARM() way of declaring module parameters seems to have disappeared (it is anyway deprecated since the beginning of the 2.6 series). As such, kqemu-1.3.0pre7 doesn't compile. -- Leonardo E. Reiter Vice President of Product Development, CTO Win4Lin, Inc. Virtual Computing that means Business Main: +1 512 339 7979 Fax: +1 512 532 6501 http://www.win4lin.com --- kqemu-linux.c.orig 2006-06-06 10:06:03.0 -0400 +++ kqemu-linux.c 2006-06-06 10:09:41.0 -0400 @@ -49,7 +49,11 @@ /* if 0 is used, then devfs/udev is used to automatically create the device */ int major = 250; +#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,10) MODULE_PARM(major,i); +#else +module_param(major, int, 0); +#endif /* Lock the page at virtual address 'user_addr' and return its physical address (page index). Return a host OS private user page ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Ask for debugging linux kernel with Qemu 0.8.1 on Msys
Hi, Have you already read my previous reply? I wrote that: [quote]In fact, I can connect by using the port 1234 on Linux with the command: (I use arm-toolchain and run the command: arm-linux-gdb vmlinux) (gdb) target remote localhost:1234 And the debugging mode run well (normally) but the problem arrives when running on Windows with Msys/MinGW Furthermore, I had tried make the connection for debugging (target remote qemu-machine:1234) between localhost and Qemu as 2 computers on a LAN but it is not possible; although I can make ping between these 2 computers [/quote] So as you wrote, it must make the UDP connection between localhost and qemu? Because I don't understand exactly what you want to say in term of "ssh tunnel to debug remotely". Best regards Thanhandrzej zaborowski [EMAIL PROTECTED] wrote: Hi,On 06/06/06, Robin Green wrote: On Tue, 6 Jun 2006 05:35:13 -0700 (PDT) Tieu Ma Dau wrote: Hi All,I've compiled Linux kernel 2.6.16 with kgdb on Linux. And after that, I've tried to debug this kernel with Qemu 0.8.1 on Msys to simulate ARM Processor. In fact, I've run the command below: qemu-system-arm -kernel myKernel -initrd arm_root.img -s But I can't make the connection from arm-toolchain-gdb to the port 1234 (by default, this port must be openned by Qemu when using the option -s for debugging) Furthermore, I've confirmed if the port 1234 is openned or not with the command: netstat -ao and there is not port 1234 openned. I've also try the option -p 123456 to change the default port for debugging of Qemu but I've got the same result. Do you know where the problem arrive? Port 1234 is the port on the virtual machine's IP address, not the port on the real machine's IP address. So you need to be able to access the virtual machine's IP address from the real machine. For this you can use tun/tap networking - see the docs. It is not possible to do this with user-mode networking.Acutally you don't need networking in the guest. QEMU listens on thehost's port 1234 (and I think it listens on all interfaces, not onlylocalhost, but I'm not sure of this one -- if this is not the case,make a ssh tunnel to debug remotely). -- Robin ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-develRegards,Andrew-- balrog 2oo6Dear Outlook users: Please remove me from your address bookshttp://www.newsforge.com/article.pl?sid=03/08/21/143258___Qemu-devel mailing listQemu-devel@nongnu.orghttp://lists.nongnu.org/mailman/listinfo/qemu-devel Do you Yahoo!? Next-gen email? Have it all with the all-new Yahoo! Mail Beta.___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Ask for debugging linux kernel with Qemu 0.8.1 on Msys
On Tue, 6 Jun 2006 16:10:39 +0200 andrzej zaborowski [EMAIL PROTECTED] wrote: Acutally you don't need networking in the guest. QEMU listens on the host's port 1234 Yes, you're right. Sorry - I had misread the email and assumed the original poster was trying to connect to a debugger running on the guest. -- Robin ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] getting the 5446 in 1152x864 mode
Julian Seward [EMAIL PROTECTED] wrote: Using the latest cvs sources on x86 SuSE 10.0 host, Win2K guest, the 1152x864 mode offered to me by Windows doesn't work. Instead I just get moved to 640x480, it looks like. The modes on either side of it - 1024x768 and 1280x1024 work fine. Is 1152x864 supported by the driver? I've been able to get 1152x864 out of the Solaris Xorg gdm5446 driver so there must be something else that's causing you problems. I think I've gotten win98se to do it as well. Ben ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
