Re: [Qemu-devel] how could I analysis the trace log?

2012-02-12 Thread 陳韋任
> I just guess the format of input events file of the simpletrace.py. > For so many available events, how could I specify the format of all > those events? http://repo.or.cz/w/qemu/stefanha.git/blob_plain/refs/heads/tracing:/docs/tracing.txt Reading "Trace events" might be help. Regards, ch

Re: [Qemu-devel] [PATCH v2 22/27] qdev: access properties via QOM

2012-02-12 Thread Paolo Bonzini
On 02/11/2012 04:46 PM, Blue Swirl wrote: Program received signal SIGSEGV, Segmentation fault. qdev_prop_set_chr (dev=0x1365580, name=0x6ed811 "chrB", value=0x0) at /src/qemu/hw/qdev-properties.c:1142 1142assert(value->label); (gdb) bt #0 qdev_prop_set_chr (dev=0x1365580, name=0x6ed8

Re: [Qemu-devel] [PATCH] oslib: make error handling more reasonable

2012-02-12 Thread Stefan Weil
Am 13.02.2012 03:37, schrieb Zhi Yong Wu: On Fri, Feb 10, 2012 at 11:53 PM, Stefan Weil wrote: Am 10.02.2012 16:13, schrieb Zhi Yong Wu: On Fri, Feb 10, 2012 at 10:41 PM, Daniel P. Berrange wrote: On Fri, Feb 10, 2012 at 10:34:13PM +0800, Zhi Yong Wu wrote: From: Zhi Yong Wu Signed-off

Re: [Qemu-devel] [PATCH] network: Added option to disable NIC option roms

2012-02-12 Thread Gerhard Wiesinger
On Fri, 27 Jan 2012, Gerhard Wiesinger wrote: On Thu, 26 Jan 2012, Markus Armbruster wrote: Gerd Hoffmann writes: On 01/26/12 08:45, Markus Armbruster wrote: Gerhard Wiesinger writes: Option ROM for network interface cards (NICs) can now explicitly disabled with romfile=disabled (or ro

[Qemu-devel] Missing patch in QEMU which is in QEMU-KVM

2012-02-12 Thread Gerhard Wiesinger
Hello, I miss the following patch in QEMU which is in QEMU-KVM: http://article.gmane.org/gmane.comp.emulators.kvm.devel/13557 commit a7fe0297840908a4fd65a1cf742481ccd45960eb Author: Andreas Winkelbauer Date: Sun Feb 24 10:33:27 2008 +0200 Extend vram size to 16MB this is useful for

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
On Mon, Feb 13, 2012 at 03:18:13AM +0200, Michael S. Tsirkin wrote: > > I also see this: > > > > device_add virtio-net-pci,netdev=foo,mac=52:54:00:12:34:56,id=bla > > device_del bla > > *** glibc detected *** /home/mst/qemu-test/bin/qemu-system-x86_64: > > corrupted double-linked list: 0x7fae4

Re: [Qemu-devel] how could I analysis the trace log?

2012-02-12 Thread Wei Yang
Hi, this kind of trace is not popular? 2012/2/12 Wei Yang : > All > > I enable the trace function with --enable-trace-backend=simple and I > create the event file like this > g_realloc > g_malloc > > Then I start the qemu with following command. > ./i386-softmmu/qemu-system-i386 -enable-kvm -drive

Re: [Qemu-devel] [PATCH] oslib: make error handling more reasonable

2012-02-12 Thread Zhi Yong Wu
On Sat, Feb 11, 2012 at 2:35 AM, Eric Blake wrote: > On 02/10/2012 07:41 AM, Daniel P. Berrange wrote: > >>> @@ -80,7 +80,7 @@ void *qemu_oom_check(void *ptr) >>>  { >>>      if (ptr == NULL) { >>>          fprintf(stderr, "Failed to allocate memory: %s\n", >>> strerror(errno)); >>> -        abor

Re: [Qemu-devel] [PATCH] oslib: make error handling more reasonable

2012-02-12 Thread Zhi Yong Wu
On Fri, Feb 10, 2012 at 11:53 PM, Stefan Weil wrote: > Am 10.02.2012 16:13, schrieb Zhi Yong Wu: > >> On Fri, Feb 10, 2012 at 10:41 PM, Daniel P. Berrange >> wrote: >>> >>> On Fri, Feb 10, 2012 at 10:34:13PM +0800, Zhi Yong Wu wrote: From: Zhi Yong Wu Signed-off-by: Zhi Yong

Re: [Qemu-devel] [PATCH v2 2/8] qemu-ga: move channel/transport functionalit

2012-02-12 Thread MATSUDA, Daiki
(2012/02/10 13:51), Michael Roth wrote: On Fri, Feb 10, 2012 at 11:26:32AM +0900, MATSUDA, Daiki wrote: (2012/02/04 2:07), Michael Roth wrote: On 02/02/2012 10:25 PM, MATSUDA, Daiki wrote: Hi, Michael! Thank you for your working. And I have a question the process id written in pid file. If qe

Re: [Qemu-devel] [RFC][PATCH 00/16 v6] introducing a new, dedicated memory dump mechanism

2012-02-12 Thread Wen Congyang
At 02/09/2012 11:16 AM, Wen Congyang Wrote: > Hi, all > > 'virsh dump' can not work when host pci device is used by guest. We have > discussed this issue here: > http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00736.html > > We have determined to introduce a new command dump to dump me

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
On Mon, Feb 13, 2012 at 02:17:35AM +0200, Michael S. Tsirkin wrote: > On Sun, Feb 12, 2012 at 02:19:19PM -0600, Anthony Liguori wrote: > > On 02/12/2012 02:15 PM, Michael S. Tsirkin wrote: > > >On Sun, Feb 12, 2012 at 02:04:29PM -0600, Anthony Liguori wrote: > > >>On 02/12/2012 11:57 AM, Michael S.

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 02:19:19PM -0600, Anthony Liguori wrote: > On 02/12/2012 02:15 PM, Michael S. Tsirkin wrote: > >On Sun, Feb 12, 2012 at 02:04:29PM -0600, Anthony Liguori wrote: > >>On 02/12/2012 11:57 AM, Michael S. Tsirkin wrote: > >>>On Sun, Feb 12, 2012 at 11:38:24AM -0600, Anthony Liguo

Re: [Qemu-devel] virtio-blk performance regression and qemu-kvm

2012-02-12 Thread Rusty Russell
On Fri, 10 Feb 2012 15:36:39 +0100, Dongsu Park wrote: > Hi, > > Recently I observed performance regression regarding virtio-blk, > especially different IO bandwidths between qemu-kvm 0.14.1 and 1.0. > So I want to share the benchmark results, and ask you what the reason > would be. Interesting

Re: [Qemu-devel] slirp-related crash

2012-02-12 Thread Jan Kiszka
On 2012-02-12 19:34, Michael S. Tsirkin wrote: > It seems somewhat easy to crash qemu with slirp if we queue multiple packets. > I didn't investigate further yet so I don't know if this > is a regression. Anyone knowledgeable about slirp wants to take a look? > > /home/mst/qemu-test/bin/qemu-syste

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Anthony Liguori
On 02/12/2012 02:15 PM, Michael S. Tsirkin wrote: On Sun, Feb 12, 2012 at 02:04:29PM -0600, Anthony Liguori wrote: On 02/12/2012 11:57 AM, Michael S. Tsirkin wrote: On Sun, Feb 12, 2012 at 11:38:24AM -0600, Anthony Liguori wrote: From: Anthony Liguori Date: Sun, 12 Feb 2012 11:36:24 -0600 Subj

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 02:04:29PM -0600, Anthony Liguori wrote: > On 02/12/2012 11:57 AM, Michael S. Tsirkin wrote: > >On Sun, Feb 12, 2012 at 11:38:24AM -0600, Anthony Liguori wrote: > >>From: Anthony Liguori > >>Date: Sun, 12 Feb 2012 11:36:24 -0600 > >>Subject: [PATCH] device_add: don't add a /

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Anthony Liguori
On 02/12/2012 11:57 AM, Michael S. Tsirkin wrote: On Sun, Feb 12, 2012 at 11:38:24AM -0600, Anthony Liguori wrote: From: Anthony Liguori Date: Sun, 12 Feb 2012 11:36:24 -0600 Subject: [PATCH] device_add: don't add a /peripheral link until init is complete Otherwise we end up with a dangling ref

[Qemu-devel] slirp-related crash

2012-02-12 Thread Michael S. Tsirkin
It seems somewhat easy to crash qemu with slirp if we queue multiple packets. I didn't investigate further yet so I don't know if this is a regression. Anyone knowledgeable about slirp wants to take a look? /home/mst/qemu-test/bin/qemu-system-x86_64 -enable-kvm -m 1G -drive file=/home/mst/rhel6.q

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 07:20:07PM +0100, Andreas Färber wrote: > Am 12.02.2012 16:06, schrieb Michael S. Tsirkin: > > So I think the following is right? > > > > > > commit 02aa79aac9bec1c8c17d1b7b5405b59b649dfdb9 > > Author: Michael S. Tsirkin > > Date: Wed Feb 8 17:16:35 2012 +0200 > > > >

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Andreas Färber
Am 12.02.2012 16:06, schrieb Michael S. Tsirkin: > So I think the following is right? > > > commit 02aa79aac9bec1c8c17d1b7b5405b59b649dfdb9 > Author: Michael S. Tsirkin > Date: Wed Feb 8 17:16:35 2012 +0200 > > docs: memory.txt document the endian field > > This is an attempt to

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 11:38:24AM -0600, Anthony Liguori wrote: > On 02/12/2012 11:31 AM, Michael S. Tsirkin wrote: > >On Sun, Feb 12, 2012 at 07:07:43PM +0200, Michael S. Tsirkin wrote: > >>I got this assert when working on qemu: pci hotplug > >>callback failed so qdev_free was called. > >> > >>(

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Anthony Liguori
On 02/12/2012 11:31 AM, Michael S. Tsirkin wrote: On Sun, Feb 12, 2012 at 07:07:43PM +0200, Michael S. Tsirkin wrote: I got this assert when working on qemu: pci hotplug callback failed so qdev_free was called. (gdb) where #0 0x75fa1905 in raise () from /lib64/libc.so.6 #1 0x7

Re: [Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 07:07:43PM +0200, Michael S. Tsirkin wrote: > I got this assert when working on qemu: pci hotplug > callback failed so qdev_free was called. > > (gdb) where > #0 0x75fa1905 in raise () from /lib64/libc.so.6 > #1 0x75fa30e5 in abort () from /lib64/libc.so.6

[Qemu-devel] weird qdev error

2012-02-12 Thread Michael S. Tsirkin
I got this assert when working on qemu: pci hotplug callback failed so qdev_free was called. (gdb) where #0 0x75fa1905 in raise () from /lib64/libc.so.6 #1 0x75fa30e5 in abort () from /lib64/libc.so.6 #2 0x77413a7f in g_assertion_message () from /lib64/libglib-2.0.so.0 #

Re: [Qemu-devel] How to follow a child process created in the guest OS?

2012-02-12 Thread Wei Yang
2012/2/11 malc : > On Sat, 11 Feb 2012, Andreas F?rber wrote: > >> Am 10.02.2012 11:26, schrieb ???: >> > On Fri, Feb 10, 2012 at 08:14:41AM +, Stefan Hajnoczi wrote: >> >> On Thu, Feb 09, 2012 at 06:33:16PM +0800, ??? wrote: >> >>> I am running a tiny OS on QEMU and debugging it with gdbstub.

Re: [Qemu-devel] How to follow a child process created in the guest OS?

2012-02-12 Thread 陳韋任
On Fri, Feb 10, 2012 at 11:48:05PM +, Paul Brook wrote: > > I am running this tiny OS on QEMU then using GDB to connect it. > > > > I want to follow task 1 after the forking, but it seems that GDB > > stick with task 0 and cannot follow task 1 even I do `set follow-fork-mode > > child`. > >

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Avi Kivity
On 02/12/2012 05:06 PM, Michael S. Tsirkin wrote: > > It's really really simple: > > > > If the device spec says "big endian, specify DEVICE_BIG_ENDIAN, and > > treat the data naturally in the callback. > > If the device spec says "little endian, specify DEVICE_LITTLE_ENDIAN, > > and treat the dat

[Qemu-devel] how could I analysis the trace log?

2012-02-12 Thread Wei Yang
All I enable the trace function with --enable-trace-backend=simple and I create the event file like this g_realloc g_malloc Then I start the qemu with following command. ./i386-softmmu/qemu-system-i386 -enable-kvm -drive file=../../kvm/ubuntu.img -boot dc -m 512 -usb -monitor stdio -trace events

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 03:55:20PM +0200, Avi Kivity wrote: > On 02/12/2012 03:47 PM, Michael S. Tsirkin wrote: > > On Sun, Feb 12, 2012 at 03:02:11PM +0200, Avi Kivity wrote: > > > On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote: > > > > This is an attempt to document the endian > > > > field in

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Avi Kivity
On 02/12/2012 03:47 PM, Michael S. Tsirkin wrote: > On Sun, Feb 12, 2012 at 03:02:11PM +0200, Avi Kivity wrote: > > On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote: > > > This is an attempt to document the endian > > > field in memory API. As this is a confusing topic, > > > it's best to make the

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Michael S. Tsirkin
On Sun, Feb 12, 2012 at 03:02:11PM +0200, Avi Kivity wrote: > On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote: > > This is an attempt to document the endian > > field in memory API. As this is a confusing topic, > > it's best to make the text as explicit as possible. > > > > Signed-off-by: Michael

Re: [Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Avi Kivity
On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote: > This is an attempt to document the endian > field in memory API. As this is a confusing topic, > it's best to make the text as explicit as possible. > > Signed-off-by: Michael S. Tsirkin > --- > docs/memory.txt | 28 +++

[Qemu-devel] [PATCH] docs: memory.txt document the endian field

2012-02-12 Thread Michael S. Tsirkin
This is an attempt to document the endian field in memory API. As this is a confusing topic, it's best to make the text as explicit as possible. Signed-off-by: Michael S. Tsirkin --- docs/memory.txt | 28 1 files changed, 28 insertions(+), 0 deletions(-) diff --gi

Re: [Qemu-devel] [PATCH] libcacard configure fixes

2012-02-12 Thread Alon Levy
On Thu, Feb 09, 2012 at 07:05:29PM +, Paul Brook wrote: > libcacard is only used by system emulation. > Only define libcacard_libs/cflags once. > ACK. Anthony, do you want a single patch pull request in general or is it ok to ask that you pick this directly? Alon > Signed-off-by: Paul Broo

Re: [Qemu-devel] [Spice-devel] [PATCH] server: support IPV6 addresses in channel events sent to qemu

2012-02-12 Thread Alon Levy
On Wed, Feb 08, 2012 at 03:39:35PM +0200, Yonit Halperin wrote: > RHBZ #788444 769512 ACK, just a few comment fixes (take it or leave it). > > CC: Gerd Hoffmann > > Signed-off-by: Gerd Hoffmann > Signed-off-by: Yonit Halperin > --- > server/reds.c | 21 + > server/spi