From: Jeff Cody <jcody@redhat.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: Kevin Wolf <kwolf@redhat.com>,
Teruaki Ishizaki <ishizaki.teruaki@lab.ntt.co.jp>,
Hitoshi Mitake <mitake.hitoshi@gmail.com>,
Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
qemu-devel@nongnu.org, sheepdog-ng@googlegroups.com,
morita.kazutaka@gmail.com, sheepdog@lists.wpkg.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Liu Yuan <namei.unix@gmail.com>
Subject: Re: [Qemu-devel] [sheepdog] [PATCH] sheepdog: fix overlapping metadata update
Date: Wed, 5 Aug 2015 14:58:44 -0400 [thread overview]
Message-ID: <20150805185844.GD9878@localhost.localdomain> (raw)
In-Reply-To: <CACaajQsm1JXtZp+xA++7S8+JKydgxkiwhGqxQ4zK3T8H2AoYGA@mail.gmail.com>
On Tue, Aug 04, 2015 at 11:07:16AM +0300, Vasiliy Tolstov wrote:
> 2015-08-03 3:41 GMT+03:00 Liu Yuan <namei.unix@gmail.com>:
> > What did you mean by 'not able to completely install'? It is a installation
> > problem or something else?
> >
>
> i have simple test that works as:
> 1) boot 3.18.x kernel and initrd with static compiled golang binary
> 2) binary bringup dhcp network
> 3) fetch from http gzipped raw qemu image
> 3) in parallel decompress gzipped image and write it to disk
>
> this use-case determine previous error in qemu (that brings this discussion)
>
> > My QEMU or my patch? I guess you can test the same QEMU with my patch and with
> > Hitoshi's patch separately. You know, different QEMU base might cover the
> > difference.
> >
>
> I'm test you and Hitoshi patch with qemu 2.4-rc0, i'm compile two
> independent debian packages with you patch and with Hitoshi.
> Install qemu with you patch to one node and with Hitoshi on another.
> Runs sheep with local cluster driver.
> I don't know how to determine qemu segfault in my case, does it
> possible to build qemu with debugging via configure flags ang get more
> detailed descriptions?
>
Hi Vasiliy,
If you run configure with --disable-strip, it will not strip the
debugging symbols from the binary after the build. Then, you can run
gdb on qemu, and do a backtrace after you hit the segfault ('bt').
That may shed some light, and is a good place to start.
Thanks,
Jeff
next prev parent reply other threads:[~2015-08-05 18:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 4:02 [Qemu-devel] [PATCH] sheepdog: fix overlapping metadata update Liu Yuan
2015-07-29 5:04 ` [Qemu-devel] [sheepdog] " Hitoshi Mitake
2015-07-29 9:31 ` Liu Yuan
2015-07-30 6:41 ` Vasiliy Tolstov
2015-07-30 9:13 ` Liu Yuan
2015-07-30 9:29 ` Vasiliy Tolstov
2015-07-30 13:27 ` Jeff Cody
2015-07-31 11:55 ` Vasiliy Tolstov
2015-07-31 12:08 ` Vasiliy Tolstov
2015-08-02 2:06 ` Liu Yuan
2015-08-02 11:52 ` Vasiliy Tolstov
2015-08-02 12:07 ` Vasiliy Tolstov
2015-08-03 0:41 ` Liu Yuan
2015-08-04 8:07 ` Vasiliy Tolstov
2015-08-05 18:58 ` Jeff Cody [this message]
2015-08-09 14:03 ` Vasiliy Tolstov
2015-08-10 10:44 ` Stefan Hajnoczi
2015-08-03 2:01 ` Liu Yuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150805185844.GD9878@localhost.localdomain \
--to=jcody@redhat.com \
--cc=ishizaki.teruaki@lab.ntt.co.jp \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@gmail.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=morita.kazutaka@gmail.com \
--cc=namei.unix@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog-ng@googlegroups.com \
--cc=sheepdog@lists.wpkg.org \
--cc=stefanha@redhat.com \
--cc=v.tolstov@selfip.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).