From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Lieven <pl@dlhnet.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
ronnie sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [Qemu-devel] qemu segfault parsing iscsi options
Date: Tue, 19 Mar 2013 10:47:30 +0100 [thread overview]
Message-ID: <51483432.6010208@redhat.com> (raw)
In-Reply-To: <877gl44pux.fsf@blackfin.pond.sub.org>
Il 18/03/2013 17:47, Markus Armbruster ha scritto:
> Peter Lieven <pl@dlhnet.de> writes:
>
>> On 18.03.2013 13:52, Markus Armbruster wrote:
>>> Peter Lieven <pl@dlhnet.de> writes:
>>>
>>>> Hi,
>>>>
>>>> with recent qemu from git qemu segfaults with the following commandline:
>>>>
>>>> x86_64-softmmu/qemu-system-x86_64 -iscsi test
>>>>
>>>> qemu-system-x86_64: -iscsi test: There is no option group 'iscsi'
>>>> Speicherzugriffsfehler (Speicherabzug geschrieben)
>>>>
>>>> It seems that there is something missing regarding the iscsi options
>>>> in qemu-option.hx.
>>>>
>>>> This was working with qemu-kvm-1.2.0.
>>>
>>> Works for me with current master 225dc991.
>>>
>>
>> for me it doesn't...
>>
>> ~/git/qemu$ git log -1 --oneline
>> 225dc99 s390: Fix cpu refactoring fallout.
>>
>> there is definetly missing some parts in qemu-options.hx for -iscsi
>
> Hmm, I got CONFIG_LIBISCSI off. What do I have to install to flip it to
> on (Fedora 17)?
It is only in Fedora 18, but I think it will install just fine if you
download the packages from Koji.
Paolo
next prev parent reply other threads:[~2013-03-19 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 11:07 [Qemu-devel] qemu segfault parsing iscsi options Peter Lieven
2013-03-18 12:52 ` Markus Armbruster
2013-03-18 15:32 ` Peter Lieven
2013-03-18 16:47 ` Markus Armbruster
2013-03-18 17:32 ` Peter Lieven
2013-03-19 9:47 ` Paolo Bonzini [this message]
2013-03-19 8:25 ` Markus Armbruster
2013-03-19 8:33 ` 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=51483432.6010208@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--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).