From: "Andreas Färber" <afaerber@suse.de>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] microblaze qemu broken
Date: Tue, 15 May 2012 15:53:33 +0200 [thread overview]
Message-ID: <4FB25FDD.7010003@suse.de> (raw)
In-Reply-To: <20120515112309.GA9435@edde.se.axis.com>
Hi,
Am 15.05.2012 13:23, schrieb Edgar E. Iglesias:
> Not sure when this happened but what ever options I pass to qemu microblaze result in:
>
> % qemu-system-microblaze
> qemu-system-microblaze: there is no option group "fsdev"
> Segmentation fault
>
> Does any one know whats going on?
Not really, but my suggestion would be to bisect changes to QemuOpts.
Another option would be to do a clean rebuild, just in case.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-15 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 11:23 [Qemu-devel] microblaze qemu broken Edgar E. Iglesias
2012-05-15 13:53 ` Andreas Färber [this message]
2012-05-15 13:17 ` Edgar E. Iglesias
2012-05-15 13:59 ` Peter Maydell
2012-05-15 14:10 ` Andreas Färber
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=4FB25FDD.7010003@suse.de \
--to=afaerber@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.