Re: [Qemu-discuss] session parameters and error codes
> From: David Brenner > > Is there an easy way to get the command line parameters for a (already > started) specific QEMU session? The ideal way is to have copied down the command that started Qemu. Other than that, "cat /proc/[process number]/cmdline" (on Linux, anyway) tells what the command line arguments for the process were. There might be a command inside the Qemu monitor to tell what the device configuration is. Dale
[Qemu-discuss] Make problem on migration-rdma.o
Hello guys, I'm using the branch described on http://wiki.qemu.org/Features/MicroCheckpointing Using libnl 3.2.16, my last problem was: "ERROR: glib-2.12 required to compile QEMU", but I solved with: sudo apt-get install libglib2.0-dev export PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig ./configure --enable-mc Now, the configure has finished, but I got some error on make: CCmigration-rdma.o migration-rdma.c: In function ‘qemu_rdma_dump_id’: migration-rdma.c:961:21: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’ migration-rdma.c:962:22: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’ migration-rdma.c:962:37: error: ‘IBV_LINK_LAYER_INFINIBAND’ undeclared (first use in this function) migration-rdma.c:962:37: note: each undeclared identifier is reported only once for each function it appears in migration-rdma.c:963:24: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’ migration-rdma.c:963:39: error: ‘IBV_LINK_LAYER_ETHERNET’ undeclared (first use in this function) migration-rdma.c: In function ‘qemu_rdma_broken_ipv6_kernel’: migration-rdma.c:1055:26: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’ migration-rdma.c:1055:41: error: ‘IBV_LINK_LAYER_INFINIBAND’ undeclared (first use in this function) migration-rdma.c:1057:33: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’ migration-rdma.c:1057:48: error: ‘IBV_LINK_LAYER_ETHERNET’ undeclared (first use in this function) migration-rdma.c:1096:18: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’ make: *** [migration-rdma.o] Error 1 Do you know how to solve this? Thanks! -- -- Tiago Cruz
[Qemu-discuss] gdb and qemu-system-aarch64 setup - breakpoint not reached
Dear All,
I am using qemu-system emulator (qemu-system-aarch64) and gdb
(aarch64-linux-gnu-gdb) to debug a c program, both running on the same
system, i686-pc-linux-gnu on Ubuntu 12.04 LTS. However, with the gdb,
if I set a breakpoint and issue 'continue' command, it shows
continuingand never reaches the breakpoint set.
I am requesting help towards understanding the problem and resolving
it. Thanks in advance.
Qemu version: 2.0.50 and gdb version : 7.8
The steps I followed to set up debugging aarch64 program in qemu-system are:
Terminal 1
==
$ cd /home/user1/qemu-aarch64/qemu.
git
/home/user1/qemu-aarch64/qemu.git$
./aarch64-softmmu/qemu-system-aarch64 -machine virt -cpu cortex-a57
-machine type=virt -nographic -smp 1 -m 2047 -kernel
../linux.git/arch/arm64/boot/Image -s -S
Now, the execution freezes and I presume qemu along with gdbserver is
listening on port 1234
Terminal 2
==
$ export PATH=/home/user1/aarch64-crossbuild-gcc4.9.1/install/bin:$PATH
$ aarch64-linux-gnu-gcc adds2.c -g --save-temps -o adds2-output
The source file adds2.c (available at
https://github.com/gcc-mirror/gcc/blob/master/gcc/testsuite/gcc.target/aarch64/adds2.c)
code snippet of adds2.c
---
85
86 int main ()
87 {
88 int x;
89 s64 y;
90
91 x = adds_si_test1 (29, 4, 5);
92 if (x != 42)
93 abort ();
94
95 x = adds_si_test1 (5, 2, 20);
---
#Invoking cross gdb
$ aarch64-linux-gnu-gdb
... some intro and copyright messages .
This GDB was configured as "--host=i686-pc-linux-gnu --target=aarch64-linux-gnu"
..
(gdb) set sysroot /home/user1/aarch64-crossbuild-gcc4.9.1/sysroot
(gdb) set solib-absolute-prefix /home/user1/aarch64-crossbuild-gcc4.9.1/sysroot
(gdb) file ./adds2-output
Reading symbols from ./adds2-output...done.
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
Reading symbols from
/home/user1/aarch64-crossbuild-gcc4.9.1/sysroot/lib/ld-linux-aarch64.so.1...done.
Loaded symbols for
/home/user1/aarch64-crossbuild-gcc4.9.1/sysroot/lib/ld-linux-aarch64.so.1
0x4000 in _start ()
from
/home/user1/aarch64-crossbuild-gcc4.9.1/sysroot/lib/ld-linux-aarch64.so.1
(gdb) b adds2.c:92
Breakpoint 1 at 0x400700: file adds2.c, line 91.
(gdb) info registers
x0 0x00
x1 0x00
x2..x29...are set to 0
x300x00
sp 0x00x0
pc 0x40000x4000 <_start>
cpsr 0x43c51073742789
fpsr 0x00
fpcr 0x00
(gdb) c
Continuing.
After waiting for ~approx 20 mins, I pressed
^C
Program received signal SIGINT, Interrupt.
0xffc92a88 in ?? ()
In case, if more info is needed, I will be happy to provide it.
Thanks & Best Regards,
Raghunath Lolur.
Re: [Qemu-discuss] gdb and qemu-system-aarch64 setup - breakpoint not reached
On 7 August 2014 21:45, Raghunath Lolur wrote: > I am using qemu-system emulator (qemu-system-aarch64) and gdb > (aarch64-linux-gnu-gdb) to debug a c program, both running on the same > system, i686-pc-linux-gnu on Ubuntu 12.04 LTS. However, with the gdb, > if I set a breakpoint and issue 'continue' command, it shows > continuingand never reaches the breakpoint set. > > I am requesting help towards understanding the problem and resolving > it. Thanks in advance. > > Qemu version: 2.0.50 and gdb version : 7.8 > > The steps I followed to set up debugging aarch64 program in qemu-system are: > > Terminal 1 > == > $ cd /home/user1/qemu-aarch64/qemu. > git > > /home/user1/qemu-aarch64/qemu.git$ > ./aarch64-softmmu/qemu-system-aarch64 -machine virt -cpu cortex-a57 > -machine type=virt -nographic -smp 1 -m 2047 -kernel > ../linux.git/arch/arm64/boot/Image -s -S > > Now, the execution freezes and I presume qemu along with gdbserver is > listening on port 1234 This looks a bit odd. You haven't provided a guest filesystem, so how are you putting your adds2-output test program inside the guest OS? If you don't use "-s -S" does QEMU successfully boot your guest OS image and let you run the test program somehow? Do you really want to run an entire AArch64 guest OS kernel and your test program inside it, then attempt to debug the test program using the QEMU debug stub? There's no awareness in this configuration of individual guest OS processes, so if you put a breakpoint on a particular address then it will fire when execution hits that address for *any* process, not just the test binary. Maybe you wanted to use linux-user mode instead? If you really do want to debug one process inside a complete guest OS, then you would be better off with running a gdb or gdbserver inside the guest and attaching to that, but unfortunately we haven't implemented that support quite yet. It ought to be in QEMU 2.2 though since I'm working on it at the moment. thanks -- PMM
[Qemu-discuss] Cheap Kítchen Sale
Cheap Kítchen Sale. Thirty Ex Display Kítchens To Clear. www,exdis pla yKítc hens1.co.uk £ 595 Each with appliances. -- View this message in context: http://qemu.11.n7.nabble.com/Cheap-Kitchen-Sale-tp282242.html Sent from the Discuss mailing list archive at Nabble.com.
