From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: ronnie sahlberg <ronniesahlberg@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Ubuntu/Debian Installer + Virtio-SCSI -> Bad ram pointer
Date: Tue, 30 Oct 2012 09:32:42 +0100 [thread overview]
Message-ID: <20121030083242.GC9918@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <508E8E21.6080406@dlhnet.de>
On Mon, Oct 29, 2012 at 03:09:37PM +0100, Peter Lieven wrote:
> Hi,
Bug subject should be virtio-blk, not virtio-scsi. virtio-scsi is a
different virtio device type from virtoi-blk and is not present in the
backtrace you posted.
Sounds pedantic but I want to make sure this gets chalked up against the
right device :).
> If I try to Install Ubuntu 12.04 LTS / 12.10 64-bit on a virtio
> storage backend that supports iSCSI
> qemu-kvm crashes reliably with the following error:
Are you using vanilla qemu-kvm-1.2.0 or are there patches applied?
Have you tried qemu-kvm.git/master?
Have you tried a local raw disk image to check whether libiscsi is
involved?
> Bad ram pointer 0x3039303620008000
>
> This happens directly after the confirmation of the Timezone before
> the Disk is partitioned.
>
> If I specify -global virtio-blk-pci.scsi=off in the cmdline this
> does not happen.
>
> Here is a stack trace:
>
> Thread 1 (Thread 0x7ffff7fee700 (LWP 8226)):
> #0 0x00007ffff63c0a10 in abort () from /lib/x86_64-linux-gnu/libc.so.6
> No symbol table info available.
> #1 <https://github.com/sahlberg/libiscsi/issues/1>
> 0x00005555557b751d in qemu_ram_addr_from_host_nofail (
> ptr=0x3039303620008000) at /usr/src/qemu-kvm-1.2.0/exec.c:2835
> ram_addr = 0
> #2 <https://github.com/sahlberg/libiscsi/issues/2>
> 0x00005555557b9177 in cpu_physical_memory_unmap (
> buffer=0x3039303620008000, len=4986663671065686081, is_write=1,
> access_len=1) at /usr/src/qemu-kvm-1.2.0/exec.c:3645
buffer and len are ASCII junk. It appears to be hex digits and it's not
clear where they come from.
It would be interesting to print *elem one stack frame up in #3
virtqueue_fill() to show the iovecs and in/out counts.
> addr1 = 93825009559312
> #3 <https://github.com/sahlberg/libiscsi/issues/3>
> 0x000055555580a9ca in virtqueue_fill (vq=0x5555565da710,
> elem=0x555556722238, len=1, idx=0)
> at /usr/src/qemu-kvm-1.2.0/hw/virtio.c:240
> size = 1
> offset = 0
> i = 0
Stefan
next prev parent reply other threads:[~2012-10-30 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 14:09 [Qemu-devel] Ubuntu/Debian Installer + Virtio-SCSI -> Bad ram pointer Peter Lieven
2012-10-30 8:32 ` Stefan Hajnoczi [this message]
2012-10-30 9:43 ` [Qemu-devel] Ubuntu/Debian Installer + Virtio-BLK " Peter Lieven
2012-10-30 15:56 ` [Qemu-devel] Ubuntu/Debian Installer + Virtio-SCSI " Peter Lieven
2012-10-30 18:27 ` Stefan Hajnoczi
2012-10-30 19:37 ` Peter Lieven
2012-10-30 21:09 ` ronnie sahlberg
2012-10-31 5:48 ` Stefan Hajnoczi
2012-10-31 14:08 ` ronnie sahlberg
2012-11-05 15:19 ` Peter Lieven
2012-11-08 15:26 ` Peter Lieven
2012-11-19 17:20 ` Stefan Hajnoczi
2012-11-22 14:10 ` Peter Lieven
2012-10-31 5:53 ` Stefan Hajnoczi
2012-10-30 20:24 ` Peter Lieven
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=20121030083242.GC9918@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlhnet.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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).