From: Jan Kiszka <jan.kiszka@web.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin O'Connor <kevin@koconnor.net>,
qemu-devel <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] virtio-blk broken after system reset
Date: Sat, 13 Nov 2010 08:51:50 +0100 [thread overview]
Message-ID: <4CDE4396.8070708@web.de> (raw)
In-Reply-To: <AANLkTikJRV4JFKhs7P=p5usacqMvt3PbKYZNheHG3S1C@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
Am 13.11.2010 08:49, Stefan Hajnoczi wrote:
> On Fri, Nov 12, 2010 at 10:02 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Hi,
>>
>> both after hard and guest-initiated reset, something is seriously broken
>> with virtio block devices. If I reset my Linux guest while still in
>> grub, the bios will simply fail to read from the disk after the reboot. If I
>> reset after Linux touched the device, qemu terminates:
>>
>> Breakpoint 1, 0x00007ffff4b945b0 in _exit () from /lib64/libc.so.6
>> (gdb) bt
>> #0 0x00007ffff4b945b0 in _exit () from /lib64/libc.so.6
>> #1 0x00007ffff4b2948d in __run_exit_handlers () from /lib64/libc.so.6
>> #2 0x00007ffff4b29535 in exit () from /lib64/libc.so.6
>> #3 0x0000000000568da3 in virtqueue_num_heads (vq=0x17040e0, idx=0) at /data/qemu/hw/virtio.c:258
>> #4 0x0000000000569511 in virtqueue_pop (vq=0x17040e0, elem=0x17cea58) at /data/qemu/hw/virtio.c:388
>> #5 0x0000000000419e31 in virtio_blk_get_request (s=0x1704010) at /data/qemu/hw/virtio-blk.c:132
>> #6 virtio_blk_handle_output (vdev=0x1704010, vq=<value optimized out>) at /data/qemu/hw/virtio-blk.c:369
>>
>> This is with current qemu.git head, haven't tried older versions. Known bug?
>
> This is a known issue. Gleb has posted a SeaBIOS fix:
>
> http://www.mail-archive.com/qemu-devel@nongnu.org/msg45849.html
>
> Currently the patch only appears in SeaBIOS master. Gleb and Kevin
> have discussed putting it into 0.6.1.2 stable (see linked thread).
> QEMU should then pick that release up.
Ah, good.
And what about the guest-triggerable qemu exit above?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-11-13 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 22:02 [Qemu-devel] virtio-blk broken after system reset Jan Kiszka
2010-11-13 7:49 ` Stefan Hajnoczi
2010-11-13 7:51 ` Jan Kiszka [this message]
2010-11-13 10:01 ` Michael Tokarev
2010-11-13 10:09 ` Jan Kiszka
2010-11-13 10:54 ` Stefan Hajnoczi
2010-11-13 11:08 ` Jan Kiszka
2010-11-15 10:42 ` Kevin Wolf
2010-11-15 21:16 ` Anthony Liguori
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=4CDE4396.8070708@web.de \
--to=jan.kiszka@web.de \
--cc=gleb@redhat.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.