[Qemu-devel] bug report
hi all I found a bug in qemu, when i invoke: cpu_physical_memory_rw(addr, mem_buf, noOfBytes, 0); where addr=0x0 and noOfBytes=50, qemu will has segmentation fault. I call the cpu_physical_memory_rw right after the qemu is started (haven't run yet) with gdb. Thanksfrom Peter
[Qemu-devel] the way i read the registers may wrong
Hi all I am using the following code to read registers, i can read the value
of EIP, but when i dump the value pointed by EIP, all are zero, byte code
should not be zero, so i think my code is wrong. Please point me out thanks?
static void gkd_read_registers(CPUState *cpu, char *buffer) {
printf(gkd_read_registers()\n);
CPUArchState *env = cpu-env_ptr;
sprintf(buffer,
cs=%x,eip=%x,ds=%x,es=%x,fs=%x,gs=%x,ss=%x,eflags=%x,eax=%x,ebx=%x,ecx=%x,edx=%x,esi=%x,edi=%x,ebp=%x,esp=%x,cr0=%x,cr2=%x,cr3=%x,cr4=%x,
env-segs[R_CS].base, env-eip, env-segs[R_DS].base,
env-segs[R_ES].base,
env-segs[R_FS].base, env-segs[R_GS].base,
env-segs[R_SS].base,
env-eflags, env-regs[R_EAX], env-regs[R_EBX],
env-regs[R_ECX], env-regs[R_EDX], env-regs[R_ESI],
env-regs[R_EDI], env-regs[R_EBP], env-regs[R_ESP],
env-cr[0],
env-cr[2], env-cr[3], env-cr[4]);
sprintf(buffer + strlen(buffer),
,dr0=%x,dr1=%x,dr2=%x,dr3=%x,dr6=%x,dr7=%x,
env-dr[0],
env-dr[1], env-dr[2], env-dr[3], env-dr[6],
env-dr[7]);
sprintf(buffer + strlen(buffer), ,gdtr=%x,gdtr_limit=%x,
env-gdt.base,
env-gdt.limit);
sprintf(buffer + strlen(buffer), ,ldtr=%x,ldtr_limit=%x,
env-ldt.base,
env-ldt.limit);
sprintf(buffer + strlen(buffer), ,idtr=%x,idtr_limit=%x,
env-idt.base,
env-idt.limit);
sprintf(buffer + strlen(buffer), ,tr=%x, env-tr);
}
Thanksfrom Peter
[Qemu-devel] single step is too slow, if compare to bochs
Hi Alli have written a java program, keep sending the gdb single step command to qemu, i can execute ~60 single steps per seconds. But in bochs i can execute ~130. How can I make qemu run faster in single step? Thanksfrom Peter
Re: [Qemu-devel] single step is too slow, if compare to bochs
The socket is lagging, i keep sending gdb command to qemu and read the result, for every 60 commands, i got 4 seconds lagging, it hangs on the socket:read() in my side for 4 seconds. The qemu is using g_io_channel_write_chars() function to send back the data through socket, anyway to optimize it? Thanksfrom Peter From: mcheun...@hotmail.com To: qemu-devel@nongnu.org Date: Sun, 18 Aug 2013 08:48:02 +0800 Subject: [Qemu-devel] single step is too slow, if compare to bochs Hi Alli have written a java program, keep sending the gdb single step command to qemu, i can execute ~60 single steps per seconds. But in bochs i can execute ~130. How can I make qemu run faster in single step? Thanksfrom Peter
[Qemu-devel] question about gdb + qemu
Hi2. I have compile my qemu to --target-list=x86_64-softmmu , in gdb, why the registers is 32 bits? (gdb) i reax0x0 0ecx0xf7247edx 0x19a804 1681412ebx0x137 311esp0x19a0d0 0x19a0d0ebp0x9000 0x9000esi0x19a120 1679648edi 0x0 0eip0x1098b70x1098b7eflags 0x246 582cs 0x10 16ss 0x18 24ds 0x18 24es 0x18 24fs 0x2b 43gs 0x18 24 2. How can i view CR0 register in gdb? Thanksfrom Peter
[Qemu-devel] mac -vnc has bug
Hi Allqemu 1.6.1 has bug when starting it with -vnc, when i connect it using vncviewer, the vncviewer will close automatically. $uname -aDarwin Peters-MacBook-Air.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 compile by:./configure --enable-cocoa --target-list=x86_64-softmmu --audio-drv-list=coreaudio --prefix=/Users/peter/qemu --enable-debug --disable-werror --extra-cflags=-O2 --enable-vnc Start qemu by:~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -k en-us -m 256m -vnc :1 Thanksfrom Peter
[Qemu-devel] porting peter-bochs to qemu
Hi I am porting peter-bochs debugger to qemu. I am stuck into the breakpoint-continue part. Anybody want to give a help to finish the debugger stub? https://www.dropbox.com/s/aidxcm9l1vnia1b/GKD.png https://www.dropbox.com/s/76a778f1a76ga7v/LibGKD.png?m Thanksfrom Peter
[Qemu-devel] qemu-1.5.0 gdb not working
qemu-1.5.0 gdb not working In mac OSX, compile by :./configure --cc=/opt/local/bin/gcc-mp-4.8 --enable-cocoa --target-list=x86_64-softmmu --audio-drv-list=coreaudio --prefix=/Users/peter/qemu --enable-debug --disable-werror --extra-cflags=-O2 --enable-vnc start qemu by:~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -gdb tcp::1234 -k en-us -S -m 256m i start gdb and insert two breakpoints at 0x7c00 and 0x7c01, after c, it hit 0x7c00. Then i c again, it stay in 0x7c00, but it should execute 0x7c01. [New thread 1]warning: Error 268435459 getting port names from mach_port_names[Switching to process 1 thread 0x0]0xfff0 in ?? ()Breakpoint 1 at 0x7c00Breakpoint 2 at 0x7c01(gdb) cContinuing. Breakpoint 1, 0x7c00 in ?? ()(gdb) cContinuing. Breakpoint 1, 0x7c00 in ?? ()(gdb) cContinuing. Breakpoint 1, 0x7c00 in ?? ()(gdb) cContinuing. Breakpoint 1, 0x7c00 in ?? ()(gdb) cContinuing. Breakpoint 1, 0x7c00 in ?? ()(gdb)
Re: [Qemu-devel] qemu-1.5.0 gdb not working
stepi is working. Date: Sat, 15 Jun 2013 20:56:57 +0200 From: fred.kon...@greensocs.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] qemu-1.5.0 gdb not working On 15/06/2013 20:37, Peter Cheung wrote: qemu-1.5.0 gdb not working In mac OSX, compile by : ./configure --cc=/opt/local/bin/gcc-mp-4.8 --enable-cocoa --target-list=x86_64-softmmu --audio-drv-list=coreaudio --prefix=/Users/peter/qemu --enable-debug --disable-werror --extra-cflags=-O2 --enable-vnc start qemu by: ~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -gdb tcp::1234 -k en-us -S -m 256m i start gdb and insert two breakpoints at 0x7c00 and 0x7c01, after c, it hit 0x7c00. Then i c again, it stay in 0x7c00, but it should execute 0x7c01. [New thread 1] warning: Error 268435459 getting port names from mach_port_names [Switching to process 1 thread 0x0] 0xfff0 in ?? () Breakpoint 1 at 0x7c00 Breakpoint 2 at 0x7c01 (gdb) c Continuing. Breakpoint 1, 0x7c00 in ?? () (gdb) c Continuing. Hi, What if you type stepi? Breakpoint 1, 0x7c00 in ?? () (gdb) c Continuing. Breakpoint 1, 0x7c00 in ?? () (gdb) c Continuing. Breakpoint 1, 0x7c00 in ?? () (gdb) c Continuing. Breakpoint 1, 0x7c00 in ?? () (gdb)
[Qemu-devel] how to do performance monitor for single VM?
Dear AllMy name is Peter, i am working on a open source project called Pandora. It is a new admin console for openstack. http://peter.kingofcoders.com/?p=663How to do performance monitor for single VM? For public cloud billing system, i need to know information about CPU/memory/IO traction/Network bandwidth for that VM Thanksfrom Peter
Re: [Qemu-devel] latest qemu with gdb remote not working
Sorry about that, i forgot i am in a mailing list Date: Mon, 3 Jun 2013 06:19:56 -0600 From: ebl...@redhat.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] latest qemu with gdb remote not working On 06/01/2013 02:09 PM, Peter Cheung wrote: i start my qemu by this ~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -gdb tcp::1234 -k en-us -S -m 256m it was working before, but not for the latest code. When i use GDB to connect to it, it show up a warning message and i was unable to start qemu. Please take a look the attachment. thanks Posting 1 megabyte screenshots is considered poor netiquette - your 1M incoming is multiplied to several hundred megabytes outgoing based on the large number of subscribers to this list, which puts a burden on the mail server. Then, not everyone has cheap fast internet connections, and downloading a megabyte message is not trivial. And several list readers prefer to see only plain text emails by default, where your screenshot requires lots of extra work to even see what you are talking about. Please, don't send images when a copy-and-paste of the terminal contents will do; or at a minimum consider posting the screenshot to a website then posting only the URL to that website in your mail message. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org
Re: [Qemu-devel] latest qemu with gdb remote not working
Hi Peter I just git pull the latest code, the gdb still fail to run after sending a c command. Thanksfrom Peter Date: Mon, 3 Jun 2013 09:47:41 +0200 From: pbonz...@redhat.com To: peter.crosthwa...@xilinx.com CC: peter.mayd...@linaro.org; qemu-devel@nongnu.org; mcheun...@hotmail.com Subject: Re: [Qemu-devel] latest qemu with gdb remote not working Il 03/06/2013 09:42, Peter Crosthwaite ha scritto: Hi Peter and Peter :) On Sun, Jun 2, 2013 at 7:27 PM, Peter Maydell peter.mayd...@linaro.org wrote: On 2 June 2013 06:46, Peter Cheung mcheun...@hotmail.com wrote: I just tried to compile the latest qemu on Fedora 18 64 bits, it is also fail. When i press c in gdb, the qemu won't start running. Good. This significantly increases the chances that somebody will investigate. I think I may have replicated as well. qemu-system-arm on Ubuntu 10.04 host. And it works again for me after a revert of: commit 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc Author: Paolo Bonzini pbonz...@redhat.com Date: Thu May 30 13:20:40 2013 +0200 gdbstub: do not restart crashed guest If a guest has crashed with an internal error or similar, detaching gdb (or any other debugger action) should not restart it. Cc: Jan Kiszka jan.kis...@siemens.com Signed-off-by: Paolo Bonzini pbonz...@redhat.com Reviewed-by: Laszlo Ersek ler...@redhat.com Message-id: 1369912840-18577-1-git-send-email-pbonz...@redhat.com Signed-off-by: Anthony Liguori aligu...@us.ibm.com Oops, indeed you need to type cont in both gdb and the monitor after this patch. Funny I didn't notice; the fix should be to use !runstate_needs_reset() instead of runstate_check(RUN_STATE_DEBUG). But it is likely a different bug than the Mac OS X one. Paolo Ill dig further before sending through minimal replication instructions (gotta run!) but Peter Cheung, can you please try your test case after reverting this commit, to see if its perhaps the same bug? $ git revert 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc Regards, Peter But one thing fedora is different than mac, when i connect gdb to qemu, it won't say warning: Error 268435459 getting port names from mach_port_names That looks like a Mac GDB specific issue. In my mac, i use gcc from mac port, here is the version detail: /Users/petergcc -v gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00) This is pretty ancient -- I'd suggest using clang to build QEMU instead. (It probably won't fix your problem here, though.) What command line are you using to configure and build QEMU? thanks -- PMM
Re: [Qemu-devel] latest qemu with gdb remote not working
Hi Peter CrosthwaiteI haven't git pull the code for two months. Thanksfrom Peter Date: Sun, 2 Jun 2013 08:57:37 +1000 From: peter.crosthwa...@xilinx.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] latest qemu with gdb remote not working Hi Peter, On Sun, Jun 2, 2013 at 6:09 AM, Peter Cheung mcheun...@hotmail.com wrote: i start my qemu by this ~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -gdb tcp::1234 -k en-us -S -m 256m it was working before, but not for the latest code. When was before and are you able to git bisect it? Regards, Peter When i use GDB to connect to it, it show up a warning message and i was unable to start qemu. Please take a look the attachment. thanks
Re: [Qemu-devel] latest qemu with gdb remote not working
Dear MaydellI just tried to compile the latest qemu on Fedora 18 64 bits, it is also fail. When i press c in gdb, the qemu won't start running.But one thing fedora is different than mac, when i connect gdb to qemu, it won't say warning: Error 268435459 getting port names from mach_port_names In my mac, i use gcc from mac port, here is the version detail: /Users/petergcc -vUsing built-in specs.Target: i686-apple-darwin11Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.1~22/src/configure --disable-checking --enable-werror --prefix=/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.1~22/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1Thread model: posixgcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00) /Users/peterld -v@(#)PROGRAM:ld PROJECT:ld64-134.9configured to support archs: i386 x86_64LTO support using: llvm version 3.0 Thanksfrom Peter From: peter.mayd...@linaro.org Date: Sun, 2 Jun 2013 00:09:38 +0100 Subject: Re: [Qemu-devel] latest qemu with gdb remote not working To: peter.crosthwa...@xilinx.com CC: mcheun...@hotmail.com; qemu-devel@nongnu.org On 1 June 2013 23:57, Peter Crosthwaite peter.crosthwa...@xilinx.com wrote: On Sun, Jun 2, 2013 at 6:09 AM, Peter Cheung mcheun...@hotmail.com wrote: i start my qemu by this ~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -gdb tcp::1234 -k en-us -S -m 256m it was working before, but not for the latest code. When was before and are you able to git bisect it? The other important question is: can you reproduce on something other than MacOSX host? (Also, please don't attach screenshots for error messages: you can just cut-and-paste them into your email.) thanks -- PMM
Re: [Qemu-devel] This is an out of tree build but your source tree
Thanks gentlemen :-) Date: Mon, 20 May 2013 08:17:33 +0200 From: stefa...@gmail.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] This is an out of tree build but your source tree On Mon, May 20, 2013 at 4:33 AM, Peter Cheung mcheun...@hotmail.com wrote: /Users/peter/workspace/qemu_latestmake Makefile:16: *** This is an out of tree build but your source tree (/Users/peter/workspace/qemu_latest) seems to have been used for an in-tree build. You can fix this by running make distclean rm -rf *-linux-user *-softmmu in your source tree. Stop. even i run make distclean rm -rf *-linux-user *-softmmu, it doesn't help. Are you trying to do an out-of-tree build? If yes, run the distclean command in the _source tree_ and not in your out-of-tree directory. If you are not trying to do an out-of-tree build then maybe the Makefile is buggy here on Mac OS X: ifneq ($(realpath $(SRC_PATH)),$(realpath .)) Please add $(realpath $(SRC_PATH)) and $(realpath .) to the error message. That way you can confirm whether the path matching makes sense. Stefan
Re: [Qemu-devel] This is an out of tree build but your source tree
Nice idea, thanks Andreas Date: Mon, 20 May 2013 17:59:12 +0200 From: afaer...@suse.de To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] This is an out of tree build but your source tree Hi, Am 20.05.2013 04:33, schrieb Peter Cheung: Hi all I have this problem in my Mac /Users/peter/workspace/qemu_latestmake Makefile:16: *** This is an out of tree build but your source tree (/Users/peter/workspace/qemu_latest) seems to have been used for an in-tree build. You can fix this by running make distclean rm -rf *-linux-user *-softmmu in your source tree. Stop. even i run make distclean rm -rf *-linux-user *-softmmu, it doesn't help. If nothing else works, commit all your changes to your source tree and run in the source directory `rm -rf *` (this should delete all non-hidden files, leaving .git intact) followed by `git reset --hard` to restore all files from the index. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
[Qemu-devel] compile the latest source in mac error
compile the latest source in mac error /Users/peter/q/qemumake installinstall -d -m 0755 /Users/peter/qemu/share/doc/qemuinstall -c -m 0644 qemu-doc.html qemu-tech.html /Users/peter/qemu/share/doc/qemuinstall -c -m 0644 QMP/qmp-commands.txt /Users/peter/qemu/share/doc/qemuinstall -d -m 0755 /Users/peter/qemu/share/man/man1install -c -m 0644 qemu.1 qemu-img.1 /Users/peter/qemu/share/man/man1install -d -m 0755 /Users/peter/qemu/share/man/man8install -c -m 0644 qemu-nbd.8 /Users/peter/qemu/share/man/man8install -d -m 0755 /Users/peter/qemu/share/qemuinstall -d -m 0755 /Users/peter/qemu/etc/qemuinstall -c -m 0644 /Users/peter/q/qemu/sysconfigs/target/target-x86_64.conf /Users/peter/qemu/etc/qemuinstall -d -m 0755 /Users/peter/qemu/binlibtool --quiet --mode=install install -c -m 0755 qemu-ga qemu-nbd qemu-img qemu-io /Users/peter/qemu/binlibtool: unknown option character `-' in: --quietUsage: libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT]Usage: libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table filename] [-seg_addr_table_filename file_system_path] [-all_load] [-noall_load]make: *** [install] Error 1
Re: [Qemu-devel] Is is a bug? (window scale)
Sorry about the attachment size, i didn't look out the file size.Is here the right mailing list to report bug? or the team have something like bugzilla? Thanksfrom Peter Date: Mon, 18 Mar 2013 17:36:15 -0600 From: ebl...@redhat.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Is is a bug? (window scale) On 03/17/2013 10:34 PM, Peter Cheung wrote: Hi All Is is a bug? (window scale) I am running Fedora 18 64 bits. Sending a 1.8 megabyte email, with a question embedded in the attached image instead of in the plain-text portion of the email, is a waste of bandwidth and considered not very polite on a list that is widely distributed to lots of readers, many of whom prefer text-only communication. If you MUST describe a bug via a screenshot, compress the image to be less than a 200k, and/or host the image externally and merely post a URL to the image, instead of attaching it, and make sure that you have done your best to describe the situation without having to view the image. Additionally, it would help if you gave more details when reporting your bug, such as what command line you used to start qemu, what version of qemu you are using (we don't know if you are using the version bundled in Fedora 18, or if you built your own), whether there is any other package involved (such as using libvirt to spawn qemu instead of starting qemu directly from the command line yourself), and so on. For the benefit of those readers who have their mail client set up to not display images automatically, I will transcribe your question out of your image, although I'm not able to answer it myself. If i resize the qemu windows by dragging the corner, the screen won' t be scale (red arrow). But if i resize the window by the border, screen can scale (green arrow). Is it a bug? -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org
[Qemu-devel] OOM don't like qemu-kvm
Hi AllMy compuer is i7 with 32 GB ram without swap, i try to launch 28 vm with 1GB ram each, it runs smoothly.If I launch 64 VMs, after the VMs eat up all the memory, the linux hang. If the linux is lack of memory, the OOM will try to kill process, right? And the OOM should pick those qemu-kvm processes to kill, but seems the OOM don't pick qemu-kvm or the OOM failed to kill qemu-kvm processes. If I turn on swap, although 64 VMs with 1GB ram each will make my computer very slow, but at least it won't hang. Can anybody explain this? below is my computer information: CPUinfo: /rootcat /proc/cpuinfo processor : 0vendor_id: GenuineIntelcpu family: 6model: 58model name : Intel(R) Core(TM) i7-3770K CPU @ 3.50GHzstepping : 9microcode: 0x13cpu MHz : 3501.000cache size: 8192 KBphysical id: 0siblings : 8core id : 0cpu cores: 4apicid : 0initial apicid : 0fpu : yesfpu_exception : yescpuid level: 13wp : yesflags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep ermsbogomips : 7000.26clflush size : 64cache_alignment : 64address sizes : 36 bits physical, 48 bits virtualpower management: /rootfree -m total used free sharedbuffers cachedMem: 32133 25910 6222 0263 3062-/+ buffers/cache: 22583 9549Swap:0 0 0 /rootuname -aLinux localhost.localdomain 3.7.2-204.fc18.x86_64 #1 SMP Wed Jan 16 16:22:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux /rootrpm -qa|grep qemulibvirt-daemon-driver-qemu-0.10.2.3-1.fc18.x86_64qemu-system-m68k-1.2.2-4.fc18.x86_64qemu-common-1.2.2-4.fc18.x86_64qemu-system-unicore32-1.2.2-4.fc18.x86_64ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarchqemu-system-sh4-1.2.2-4.fc18.x86_64qemu-kvm-1.2.2-4.fc18.x86_64qemu-system-arm-1.2.2-4.fc18.x86_64qemu-system-s390x-1.2.2-4.fc18.x86_64qemu-user-1.2.2-4.fc18.x86_64qemu-1.2.2-4.fc18.x86_64qemu-system-microblaze-1.2.2-4.fc18.x86_64qemu-system-mips-1.2.2-4.fc18.x86_64qemu-system-xtensa-1.2.2-4.fc18.x86_64qemu-system-ppc-1.2.2-4.fc18.x86_64qemu-img-1.2.2-4.fc18.x86_64qemu-system-alpha-1.2.2-4.fc18.x86_64qemu-system-sparc-1.2.2-4.fc18.x86_64qemu-system-lm32-1.2.2-4.fc18.x86_64libvirt-daemon-qemu-0.10.2.3-1.fc18.x86_64qemu-system-or32-1.2.2-4.fc18.x86_64qemu-system-cris-1.2.2-4.fc18.x86_64qemu-system-x86-1.2.2-4.fc18.x86_64 /rootrpm -qa|grep kvmlibvirt-daemon-kvm-0.10.2.3-1.fc18.x86_64qemu-kvm-1.2.2-4.fc18.x86_64 Thanksfrom Peter
Re: [Qemu-devel] Is is a bug? (window scale)
Thank you MR Huang Thanksfrom Peter Date: Wed, 20 Mar 2013 09:26:38 +0800 From: riegama...@gmail.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Is is a bug? (window scale) On Wed, Mar 20, 2013 at 1:12 AM, Peter Cheung mcheun...@hotmail.com wrote: Sorry about the attachment size, i didn't look out the file size. Is here the right mailing list to report bug? or the team have something like bugzilla? Please report your bug here: https://bugs.launchpad.net/qemu It's QEMU's bug tracker. Thanks from Peter Date: Mon, 18 Mar 2013 17:36:15 -0600 From: ebl...@redhat.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Is is a bug? (window scale) On 03/17/2013 10:34 PM, Peter Cheung wrote: Hi All Is is a bug? (window scale) I am running Fedora 18 64 bits. Sending a 1.8 megabyte email, with a question embedded in the attached image instead of in the plain-text portion of the email, is a waste of bandwidth and considered not very polite on a list that is widely distributed to lots of readers, many of whom prefer text-only communication. If you MUST describe a bug via a screenshot, compress the image to be less than a 200k, and/or host the image externally and merely post a URL to the image, instead of attaching it, and make sure that you have done your best to describe the situation without having to view the image. Additionally, it would help if you gave more details when reporting your bug, such as what command line you used to start qemu, what version of qemu you are using (we don't know if you are using the version bundled in Fedora 18, or if you built your own), whether there is any other package involved (such as using libvirt to spawn qemu instead of starting qemu directly from the command line yourself), and so on. For the benefit of those readers who have their mail client set up to not display images automatically, I will transcribe your question out of your image, although I'm not able to answer it myself. If i resize the qemu windows by dragging the corner, the screen won' t be scale (red arrow). But if i resize the window by the border, screen can scale (green arrow). Is it a bug? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org -- Best Regards, Dunrong Huang
[Qemu-devel] correct step to invoke a single step?
Hi AllIs it the correct step to invoke a single step? It will fail when currec IP hit a breakpoint, but i can't find any different than the gdb stub. static int sstep_flags = SSTEP_ENABLE | SSTEP_NOIRQ | SSTEP_NOTIMER;CPUArchState *cpu = first_cpu;cpu_single_step(cpu, sstep_flags);vm_start(); Thanksfrom Peter
[Qemu-devel] single step not working after hit a break point
Hi All I use the following code to insert a breakpoint in physical address 0×160CPUArchState *cpu = first_cpu; hwaddr addr; sscanf(command + 2, %ld, addr); int err = cpu_breakpoint_insert(cpu, addr, BP_GDB, NULL );qemu successfully hit the breakpoint and stop, then i try to single-step by the following code:CPUArchState *cpu = first_cpu; cpu_single_step(cpu, sstep_flags); vm_start();Nothing happened, the EIP still stay in 0×160, but if i delete the breakpoint, the single step just work again. Am I missed something? thanks
Re: [Qemu-devel] read memory by virtual address?
To: qemu-devel@nongnu.org From: i.mitsya...@samsung.com Date: Mon, 3 Dec 2012 23:05:39 +0400 CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] read memory by virtual address? On 12/03/2012 08:53 PM, Peter Cheung wrote: Dear All I can read memory by a physical address cpu_physical_memory_map(), but how can i read it by linear address or virtual address? Thanks from Peter Hi, Peter, you can use cpu_memory_rw_debug/cpu_get_phys_page_debug for this. -- Mitsyanko Igor ASWG, Moscow RD center, Samsung Electronics email: i.mitsya...@samsung.com thanks so much
[Qemu-devel] func call to safely shutdown VM and quit qemu?
Hi Is there a func call to safely shutdown VM and quit qemu? Thanksfrom Peter
Re: [Qemu-devel] func call to safely shutdown VM and quit qemu?
Date: Mon, 3 Dec 2012 10:30:41 +0100 From: laurent.desnog...@gmail.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] func call to safely shutdown VM and quit qemu? On Mon, Dec 3, 2012 at 9:43 AM, Peter Cheung mcheun...@hotmail.com wrote: Hi Is there a func call to safely shutdown VM and quit qemu? I am using qemu_system_shutdown_request(). I don't know it that's the best way of quitting, but it works for me. HTH, Laurent thanks gentleman
[Qemu-devel] read memory by virtual address?
Dear AllI can read memory by a physical address cpu_physical_memory_map(), but how can i read it by linear address or virtual address? Thanksfrom Peter
[Qemu-devel] manually refresh the screen
Hi All Which code i can refresh the screen manually? Thanksfrom Peter
[Qemu-devel] no monitor after disable vnc
Dear All When i compile qemu in ubuntu 12.10 with ./configure --target-list=i386-softmmu --prefix=/root/qemu --enable-debug --disable-vnc --disable-werror , after i start qemu, no screen output, how to enable it? Thanksfrom Peter
Re: [Qemu-devel] no monitor after disable vnc
Hi --enable-sdl can come up with a monitor screen, thanks Thanksfrom Peter Date: Mon, 19 Nov 2012 14:38:45 +0100 From: pbonz...@redhat.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: no monitor after disable vnc Il 19/11/2012 14:25, Peter Cheung ha scritto: Dear All When i compile qemu in ubuntu 12.10 with ./configure --target-list=i386-softmmu --prefix=/root/qemu --enable-debug --disable-vnc --disable-werror , after i start qemu, no screen output, how to enable it? Please attach your config.log. Paolo
[Qemu-devel] multiple gdbserver
Hi all I just rad the qemu source code, when it allows us to start multiple gdbserver? what is the reason doing that? Thanksfrom Peter
Re: [Qemu-devel] multiple gdbserver
OK, thanks, then my question would be: why one gdbserver hosting two tcp ports? not useful, right? Thanksfrom Peter Date: Thu, 15 Nov 2012 09:29:20 +0100 From: jan.kis...@siemens.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: multiple gdbserver On 2012-11-15 09:01, Peter Cheung wrote: Hi all I just rad the qemu source code, when it allows us to start multiple gdbserver? what is the reason doing that? I think you misread the code: There can only be a single instance of the gdbserver. There is also only a single instance of gdbserver_state. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux
Re: [Qemu-devel] multiple gdbserver
sorry, i misunderstood. when i specifed two port to gdbserver, althought the code will loop them all, but only the last one will be used. Thanksfrom Peter Date: Thu, 15 Nov 2012 09:37:31 +0100 From: jan.kis...@siemens.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: multiple gdbserver On 2012-11-15 09:33, Peter Cheung wrote: OK, thanks, then my question would be: why one gdbserver hosting two tcp ports? not useful, right? And therefore it's not the case. What are you referring to? Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux
Re: [Qemu-devel] Adding another debug protocol
Hi All I still prefer to create my debug server, i think this would be more flexible. I will provide a patch from my website, although the changes can't be commit to qemu source, but people still able to patch it by themselves. thanks Thanksfrom Peter Date: Thu, 15 Nov 2012 09:02:39 +0100 From: jan.kis...@web.de To: mcheun...@hotmail.com CC: peter.mayd...@linaro.org; qemu-devel@nongnu.org Subject: Re: Adding another debug protocol On 2012-11-15 02:58, Peter Cheung wrote: Date: Wed, 14 Nov 2012 17:43:12 +0100 From: jan.kis...@siemens.com To: mcheun...@hotmail.com CC: peter.mayd...@linaro.org; qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Adding another debug protocol On 2012-11-14 17:28, Peter Cheung wrote: hi Jan, you are the maintainer of the gdb server of qemu? Not formally. I'm heavily using it for kernel debugging for a couple of years. Therefore, I'm fixing and enhancing it from time to time. I think if I can't create my debug protocol, it is not easy to adopt peter-bochs debugger to qemu, in peter-bochs, there are some features I think current gdb protocol doesn't care, such as profiling, kernel module monitoring, call graph history, real time address probeing. I know qemu is made by a lots of people, seems not easy to convince everyone. A good general rule, not only in open source, is to at least try to fix existing infrastructure. If that fails provably, you can come up with a new version to replace or augment things. E.g., you didn't explain yet why the gdb protocol and our existing stub cannot be extended in a backward compatible way that allows your debugger to attach to it. That way not only your debugger (is it Windows hosted?) could benefit from the improvements but the whole (x86) gdb world. Jan PS: Please don't top-post, cite what you comment on. -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux sorry the top-posting, hotmail and gmail just changed to top-post years ago. In GDB protocol, they don't have a repeat command, when i do profiling my kernel, let's say 10 mins, i probably need to send 100,000 s command to gdb, i think this will slow down the qemu, this already happen. GDB tracepoints are able to model this. They are set up over the remote protocol, thus the events themselves can be handled on the server side only, here inside QEMU or KVM. That takes the latency of the remote protocol out of the loop. If you browse the archive here, you'll see that I proposed this already and someone even did a prototype. In GDB, i don't know how to set a pbreakpoint (physical address), breakpoint (linear address). I guess gdb is natural to all cpu platforms, so they don't provide this x86-specified breakpoint setting. It will be trivial to extend the existing breakpoint command (Z0..4) by another mode that means watch physical memory access and teach this also to gdb. A gdb server does not have to support all modes, thus it's fine if QEMU would be the only provider initially. If really not possible to add this feature, can we do it : i compile all my code into an .a file, and qemu dynamically load it? then i don't need to modify the qemu source. Plugins are a hot topic in the QEMU project. Your example won't be a good candidate to motivate them. Also, we heard no technical reasons so far for introducing a complete new protocol at all. Jan
[Qemu-devel] Adding another debug protocol
Dear AllI am going to add another debugger server into QEMU, so i need to1) create another socket server, similar than gdbserver, to receive the command from debugger2) add another option, such as --start-debugger-server to start the socket server. After I work out the whole thing, how can i ask for the qemu maintainer to accept my code? I believe i should write a proposal first. Thanksfrom Peter
Re: [Qemu-devel] Adding another debug protocol
Hi Cannot use gdb protocol, because it is slow.Also, the original gdb stub can dump out GDT/IDT/CR0 directly. Thanksfrom Peter Date: Wed, 14 Nov 2012 10:54:02 + From: peter.mayd...@linaro.org To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Adding another debug protocol On 14 November 2012 10:45, Peter Cheung mcheun...@hotmail.com wrote: Dear All I am going to add another debugger server into QEMU, so i need to 1) create another socket server, similar than gdbserver, to receive the command from debugger 2) add another option, such as --start-debugger-server to start the socket server. After I work out the whole thing, how can i ask for the qemu maintainer to accept my code? I believe i should write a proposal first. Probably worth including a summary of why your second debug protocol couldn't be implemented as a translation layer between gdbserver protocol and whatever it is you need. -- PMM
Re: [Qemu-devel] Adding another debug protocol
hi Jan, you are the maintainer of the gdb server of qemu? I think if I can't create my debug protocol, it is not easy to adopt peter-bochs debugger to qemu, in peter-bochs, there are some features I think current gdb protocol doesn't care, such as profiling, kernel module monitoring, call graph history, real time address probeing. I know qemu is made by a lots of people, seems not easy to convince everyone. 從我的 iPad 傳送 Jan Kiszka jan.kis...@siemens.com 於 2012年11月14日 下午11:13 寫道： On 2012-11-14 15:40, Peter Cheung wrote: Hi Cannot use gdb protocol, because it is slow. For any practical purpose I came across so far while debugging guest kernels, that is not true when running against QEMU. Sure, if you want to dump gigabytes of RAM this way, it will be a bottleneck. But when do you have to do this while interactively debugging? Printing the content will still take longer than transmitting it. Also, the original gdb stub can dump out GDT/IDT/CR0 directly. That is true, but it should be addressed in gdb. Folks there are aware of the issue and will happily discuss extension proposals and likely also take the necessary patches. It will be trivial to adapt QEMU to such an extension afterward. Also, this is a temporary, just too long pending issue for x86. I'm not aware of such limitations for other architectures. And there is actually workaround for the meantime: issue monitor info registers in the gdb session to obtain also those registers. monitor cpu N will allow you to switch between CPUs. It's not nice but saved my days a few times already. Jan Thanksfrom Peter Date: Wed, 14 Nov 2012 10:54:02 + From: peter.mayd...@linaro.org To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Adding another debug protocol On 14 November 2012 10:45, Peter Cheung mcheun...@hotmail.com wrote: Dear All I am going to add another debugger server into QEMU, so i need to 1) create another socket server, similar than gdbserver, to receive the command from debugger 2) add another option, such as --start-debugger-server to start the socket server. After I work out the whole thing, how can i ask for the qemu maintainer to accept my code? I believe i should write a proposal first. Probably worth including a summary of why your second debug protocol couldn't be implemented as a translation layer between gdbserver protocol and whatever it is you need. -- PMM -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux
Re: [Qemu-devel] Adding another debug protocol
Date: Wed, 14 Nov 2012 17:43:12 +0100 From: jan.kis...@siemens.com To: mcheun...@hotmail.com CC: peter.mayd...@linaro.org; qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Adding another debug protocol On 2012-11-14 17:28, Peter Cheung wrote: hi Jan, you are the maintainer of the gdb server of qemu? Not formally. I'm heavily using it for kernel debugging for a couple of years. Therefore, I'm fixing and enhancing it from time to time. I think if I can't create my debug protocol, it is not easy to adopt peter-bochs debugger to qemu, in peter-bochs, there are some features I think current gdb protocol doesn't care, such as profiling, kernel module monitoring, call graph history, real time address probeing. I know qemu is made by a lots of people, seems not easy to convince everyone. A good general rule, not only in open source, is to at least try to fix existing infrastructure. If that fails provably, you can come up with a new version to replace or augment things. E.g., you didn't explain yet why the gdb protocol and our existing stub cannot be extended in a backward compatible way that allows your debugger to attach to it. That way not only your debugger (is it Windows hosted?) could benefit from the improvements but the whole (x86) gdb world. Jan PS: Please don't top-post, cite what you comment on. -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux sorry the top-posting, hotmail and gmail just changed to top-post years ago. In GDB protocol, they don't have a repeat command, when i do profiling my kernel, let's say 10 mins, i probably need to send 100,000 s command to gdb, i think this will slow down the qemu, this already happen. In GDB, i don't know how to set a pbreakpoint (physical address), breakpoint (linear address). I guess gdb is natural to all cpu platforms, so they don't provide this x86-specified breakpoint setting. If really not possible to add this feature, can we do it : i compile all my code into an .a file, and qemu dynamically load it? then i don't need to modify the qemu source. thanks
[Qemu-devel] qemu-kvm not listed by command virsh list --all
Dear All Run a VM by qemu-kvm, and then i cannot list it by command virsh list --all. Why?I am sure the VM is running because i can vnc to it. Thanksfrom Peter
Re: [Qemu-devel] peter-bochs with QEMU
Thank youfrom Peter Date: Sun, 11 Nov 2012 16:26:05 +0800 From: riegama...@gmail.com To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] peter-bochs with QEMU Hi Peter, 2012/11/11 Peter Cheung mcheun...@hotmail.com Dear All Developers My name is Peter Cheung, from Hong Kong, my debugger http://peter-bochs.googlecode.com is riding on bochs, i tried to use it to debug the linux kernel, but bochs runs too slowly. So I want to modify the qemu-kvm (not qemu) to work with peter-bochs, so that I can debug linux kernel using qemu-kvm. I want to know the code-commit-process. If i developed/modified something on qemu, how can i commit my code? Do I need to pass through some approval process? or some UAT process? May I know which guys are response for this for qemu-kvm? Anyone can sbumit patches. After you have finished your patches, run scripts/get_maintainer.pl your_patch_file to get maintainers who should review your patches, then use git -send-email to send your patches to qemu-devel mailing list, with cc'ing to maintainers mentioned above. You should take a look at this guide: http://wiki.qemu.org/Contribute/SubmitAPatch Thanks from Peter (mcheun...@hotmail.com) -- Best Regards, Dunrong Huang
Re: [Qemu-devel] add debugger command
Good, thanks a lot. I will give it a try tonight. Why I got double-email from the mailing list. I subscribe twice? Thanksfrom Peter Date: Wed, 28 Dec 2011 09:25:01 +0100 From: s...@weilnetz.de To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] add debugger command Am 28.12.2011 07:35, schrieb Peter Cheung: Dear All Please take a look http://peter-bochs.googlecode.com , I am an operating system developer, bochs has a great build in command-line debugger, but it is not good enough for normal use, so I created peter-bochs for it. But bochs has a deadly weak point, it runs very slow. So I want to add debugger feature for qemu. To let peter-bochs works with qemu, need to add these to qemu 1) able to let peter-bochs pause qemu during running. In bochs, peter-bochs just sending a ctrl-c command to bochs, then it pause. 2) magic breakpoint, in bochs, when bochs execute a intstruction xchg bx,bx, it will pause 3) able to send debug command to qemu, through pipeline/socket/whatever. Is QEMU a tai wan project? I am living in hong kong. Thanks from Peter Hello Peter, QEMU is not a national project. The QEMU contributors and users are living all over the world. See http://www.ohloh.net/p/qemu/map. QEMU has no built-in debugger, but it supports the GDB remote protocol which allows remote debugging via TCP socket, for example. See http://sourceware.org/gdb/onlinedocs/gdb/Remote-Debugging.html and http://sourceware.org/gdb/onlinedocs/gdb/Remote-Protocol.html for more information on this protocol and http://qemu.weilnetz.de/qemu-doc.html#gdb_005fusage for instructions how to use this remote debugging feature with QEMU. So it should be possible to attach you Java application to QEMU without any changes of the QEMU source code. All you have to do is extend your application to support the GDB remote protocol. There are other graphical debugging front ends (for example DDD or Insight) which work like this. Please note that QEMU is not limited to 80x86 emulation. Any debugging interface must be able to support all QEMU emulation targets. Regards, Stefan Weil
[Qemu-devel] add debugger command
Dear QEMU team I want to add some debug command for qemu so my peter-bochs (http://peter-bochs.googlecode.com) debugger can support qemu. So I have these questions:1) QEMU use SVN?2) How to apply a role to submit code to their svn? Thanksfrom Peter
Re: [Qemu-devel] add debugger command
Hi, I am chinese too. Am I welcome to add some debug command to the qemu internal debugger? I have some bad experiment before on other project, the project owner is not willing to add feature by other people. Thanksfrom Peter Date: Wed, 28 Dec 2011 13:44:07 +0800 From: che...@iis.sinica.edu.tw To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] add debugger command Hi Cheung, On Wed, Dec 28, 2011 at 05:40:20AM +, Peter Cheung wrote: Dear QEMU team I want to add some debug command for qemu so my peter-bochs (http://peter-bochs.googlecode.com) debugger can support qemu. So I have these questions:1) QEMU use SVN?2) How to apply a role to submit code to their svn? A1. It use git. See http://wiki.qemu.org/Download . A2. http://wiki.qemu.org/Contribute/SubmitAPatch Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj
Re: [Qemu-devel] add debugger command
Take a look the tutorial here http://code.google.com/p/peter-bochs/w/list Thanksfrom Peter Date: Wed, 28 Dec 2011 14:29:08 +0800 Subject: Re: [Qemu-devel] add debugger command From: zwu.ker...@gmail.com To: mcheun...@hotmail.com CC: che...@iis.sinica.edu.tw; qemu-devel@nongnu.org 2011/12/28 Peter Cheung mcheun...@hotmail.com: Hi, I am chinese too. Am I welcome to add some debug command to the qemu Sure, if your debugger idea is good enough. I think that you should send out your idea at first before working on it. Unfortunately, some maintainers are enjoying their holiday. internal debugger? I have some bad experiment before on other project, the project owner is not willing to add feature by other people. Thanks from Peter Date: Wed, 28 Dec 2011 13:44:07 +0800 From: che...@iis.sinica.edu.tw To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] add debugger command Hi Cheung, On Wed, Dec 28, 2011 at 05:40:20AM +, Peter Cheung wrote: Dear QEMU team I want to add some debug command for qemu so my peter-bochs (http://peter-bochs.googlecode.com) debugger can support qemu. So I have these questions:1) QEMU use SVN?2) How to apply a role to submit code to their svn? A1. It use git. See http://wiki.qemu.org/Download . A2. http://wiki.qemu.org/Contribute/SubmitAPatch Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj -- Regards, Zhi Yong Wu
Re: [Qemu-devel] add debugger command
Dear AllPlease take a look http://peter-bochs.googlecode.com , I am an operating system developer, bochs has a great build in command-line debugger, but it is not good enough for normal use, so I created peter-bochs for it. But bochs has a deadly weak point, it runs very slow. So I want to add debugger feature for qemu. To let peter-bochs works with qemu, need to add these to qemu1) able to let peter-bochs pause qemu during running. In bochs, peter-bochs just sending a ctrl-c command to bochs, then it pause.2) magic breakpoint, in bochs, when bochs execute a intstruction xchg bx,bx, it will pause3) able to send debug command to qemu, through pipeline/socket/whatever. Is QEMU a tai wan project? I am living in hong kong. Thanksfrom Peter Date: Wed, 28 Dec 2011 14:29:08 +0800 Subject: Re: [Qemu-devel] add debugger command From: zwu.ker...@gmail.com To: mcheun...@hotmail.com CC: che...@iis.sinica.edu.tw; qemu-devel@nongnu.org 2011/12/28 Peter Cheung mcheun...@hotmail.com: Hi, I am chinese too. Am I welcome to add some debug command to the qemu Sure, if your debugger idea is good enough. I think that you should send out your idea at first before working on it. Unfortunately, some maintainers are enjoying their holiday. internal debugger? I have some bad experiment before on other project, the project owner is not willing to add feature by other people. Thanks from Peter Date: Wed, 28 Dec 2011 13:44:07 +0800 From: che...@iis.sinica.edu.tw To: mcheun...@hotmail.com CC: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] add debugger command Hi Cheung, On Wed, Dec 28, 2011 at 05:40:20AM +, Peter Cheung wrote: Dear QEMU team I want to add some debug command for qemu so my peter-bochs (http://peter-bochs.googlecode.com) debugger can support qemu. So I have these questions:1) QEMU use SVN?2) How to apply a role to submit code to their svn? A1. It use git. See http://wiki.qemu.org/Download . A2. http://wiki.qemu.org/Contribute/SubmitAPatch Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj -- Regards, Zhi Yong Wu
