From: Kashyap Chamarthy <kchamart@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] QEMU segfault: Booting an overlay with backing_file over NBD: nbd.c:nbd_receive_request():L756: read failed
Date: Fri, 30 Jan 2015 19:41:43 +0100 [thread overview]
Message-ID: <20150130184143.GA9654@tesla.redhat.com> (raw)
In-Reply-To: <20150130171521.GD24537@noname.redhat.com>
On Fri, Jan 30, 2015 at 06:15:21PM +0100, Kevin Wolf wrote:
> Am 29.01.2015 um 17:25 hat Kashyap Chamarthy geschrieben:
> > $ qemu-system-x86_64 \
> > -nographic \
> > -nodefconfig \
> > -nodefaults \
> > -m 2048 \
> > -device virtio-scsi-pci,id=scsi \
> > -device virtio-serial-pci \
> > -serial stdio \
> > -drive file=./overlay1.qcow2,format=qcow2,if=virtio,cache=writeback
> > Segmentation fault (core dumped)
> >
> >
> > On the shell where `qemu-nbd` is running, I notice this
> >
> > nbd.c:nbd_receive_request():L756: read failed
> >
> >
> > Haven't investigated further with GDB, thought I'd bring it up here
> > first.
> >
> >
> > Versions
> > --------
> >
> > $ rpm -q qemu; uname -r
> > qemu-2.1.2-7.fc21.x86_64
> > 3.17.8-300.fc21.x86_64
>
> Copying Stefan because he's the master of AIO contexts and it is
> bs->aio_context that becomes NULL. I couldn't see anything obvious.
>
>
> In the meantime, could you retest on git master?
Just tested from git, and I can still reproduce it.
That's the commit I'm at:
$ git describe
v2.2.0-682-g16017c4
Run the NBD server, from git:
$ /home/kashyapc/build/qemu/qemu-nbd -f qcow2 \
-p10809 ./f21vm.qcow2 -t
Create the overlay:
$ /home/kashyapc/build/qemu/qemu-img create \
-f qcow2 -F nbd -o backing_file=nbd://localhost overlay2-of-f21vm.qcow2
Segmentation fault (core dumped)
Creating the overlay from the git-compiled `qemu-img` binary fails.
So, let's create the overlay using the `qemu-img` binary from the system
(RPM version noted above) and boot the overlay from the just compiled
QEMU x86_64 binary from git, still core dumps:
$ /home/kashyapc/build/qemu/x86_64-softmmu/qemu-system-x86_64 \
-nographic \
-nodefconfig \
-nodefaults \
-m 2048 \
-device virtio-scsi-pci,id=scsi \
-device virtio-serial-pci \
-serial stdio \
-drive file=./overlay2-f21vm.qcow2,format=qcow2,if=virtio,cache=writeback
Segmentation fault (core dumped)
PS: I'm traveling, so I'll be a little slow to respond here, but can
provide more debugging info from the coredump of `qemu-img` binary as I
have access to a real computer.
--
/kashyap
next prev parent reply other threads:[~2015-01-30 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:25 [Qemu-devel] QEMU segfault: Booting an overlay with backing_file over NBD: nbd.c:nbd_receive_request():L756: read failed Kashyap Chamarthy
2015-01-29 16:47 ` Richard W.M. Jones
2015-01-29 17:22 ` Kashyap Chamarthy
2015-01-29 23:33 ` Kashyap Chamarthy
2015-01-30 17:15 ` Kevin Wolf
2015-01-30 18:41 ` Kashyap Chamarthy [this message]
2015-01-30 19:32 ` Max Reitz
2015-01-30 22:13 ` Kashyap Chamarthy
2015-02-02 8:14 ` Stefan Hajnoczi
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=20150130184143.GA9654@tesla.redhat.com \
--to=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).