From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] fsdev - broken qemu-system-?
Date: Fri, 10 Jun 2011 15:04:01 +0200 [thread overview]
Message-ID: <20110610130401.GA24494@laped.lan> (raw)
In-Reply-To: <87vcwdev9a.fsf@linux.vnet.ibm.com>
On Fri, Jun 10, 2011 at 05:47:05PM +0530, Aneesh Kumar K.V wrote:
> On Fri, 10 Jun 2011 12:12:33 +0200, "Edgar E. Iglesias" <edgar.iglesias@gmail.com> wrote:
> > At least CRIS, Microblaze and lm32 are broken on latest git. Things fail with
> > the following message:
> > qemu-system-cris: there is no option group "fsdev"
> >
> > Under GDB I see a segfault...
> >
> > % gdb --args ~/src/c/qemu/git/build-qemu/cris-softmmu/qemu-system-cris -M axis-dev88 -kernel kimage -serial stdio
....
> > envp=<value optimized out>) at /home/edgar/src/c/qemu/git/qemu/vl.c:3015
> > (gdb) q
> > A debugging session is active.
> >
> > Inferior 1 [process 1473] will be killed.
> >
>
> Can you try this patch
It works, thanks!
Cheers
>
> diff --git a/fsdev/qemu-fsdev-dummy.c b/fsdev/qemu-fsdev-dummy.c
> index 619e163..4e700dd 100644
> --- a/fsdev/qemu-fsdev-dummy.c
> +++ b/fsdev/qemu-fsdev-dummy.c
> @@ -13,8 +13,16 @@
> #include <stdio.h>
> #include <string.h>
> #include "qemu-fsdev.h"
> +#include "qemu-config.h"
>
> int qemu_fsdev_add(QemuOpts *opts)
> {
> return 0;
> }
> +
> +static void fsdev_register_config(void)
> +{
> + qemu_add_opts(&qemu_fsdev_opts);
> + qemu_add_opts(&qemu_virtfs_opts);
> +}
> +machine_init(fsdev_register_config);
prev parent reply other threads:[~2011-06-10 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 10:12 [Qemu-devel] fsdev - broken qemu-system-? Edgar E. Iglesias
2011-06-10 12:17 ` Aneesh Kumar K.V
2011-06-10 13:04 ` Edgar E. Iglesias [this message]
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=20110610130401.GA24494@laped.lan \
--to=edgar.iglesias@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.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 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).