From: Rick Vernam <rickv@hobi.com>
To: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
Cc: qemu-devel@nongnu.org, Corentin Chary <corentin.chary@gmail.com>
Subject: Re: [Qemu-devel] qemu: qemu_mutex_lock: Invalid argument
Date: Mon, 27 Sep 2010 12:04:48 -0500 [thread overview]
Message-ID: <201009271204.52176.rickv@hobi.com> (raw)
In-Reply-To: <AANLkTincmw-X4qxgNGv3T_vkvb9nA=ZbDZs4Wb-o=bL-@mail.gmail.com>
On Wednesday 15 September 2010 05:46:55 Yoshiaki Tamura wrote:
> Hi Rick,
>
> 2010/9/15 Corentin Chary <corentin.chary@gmail.com>:
> > On Tue, Sep 14, 2010 at 10:00 PM, Rick Vernam <rickv@hobi.com> wrote:
> >> I don't have nearly enough info to file a proper bug report.
> >>
> >> I am running qemu-kvm-0.13.0 rc1
> >> starting qemu like so:
> >> /root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
> >> file=/root/qemu/w2k3_server.raw,if=virtio,aio=native -net
> >> nic,model=virtio,macaddr=52:54:00:12:34:56 -net tap,ifname=tap0
> >> -localtime - usb -usbdevice tablet -vga std -vnc :25581 -monitor stdio
> >> -m 512 -runas rick
> >>
> >> Every now and again, qemu will up and quit leaving only the following
> >> message: qemu: qemu_mutex_lock: Invalid argument
> >>
> >> At the moment I can't stop what I'm doing to go learn how to debug qemu,
> >> but I'd be happy if anybody is interested in suggesting something I
> >> could do to provide some info about this bug...
> >> Would it be helpful to build with -O0 -g and run in gdb, then get a bt
> >> when it dies?
> >> I haven't put this into production yet, so I can still afford downtime &
> >> re- compiles...etc.
> >>
> >> thanks..
> >>
> >> host machine is:
> >> 2.6.32-gentoo-r7 x86_64 Intel(R) Xeon(R) CPU E5450 @ 3.00GHz
> >> GenuineIntel GNU/Linux
> >>
> >> guest os is Windows Server 2003, Standard Edition. Service Pack 2.
> >> Red Het VirtIO Ethernet Adapter Driver Version: 5.1.209.605
> >> Red Hat VirtIO SCSI Controller Driver Version: 6.0.0.10
> >>
> >> here is how I ran configure:
> >> ./configure --prefix=/root/qemu --target-list=x86_64-softmmu
> >> --extra-cflags="- march=native -O2 -pipe"
> >> --extra-ldflags="-march=native -O2 -pipe" --audio-drv- list=
> >> --audio-card-list= --disable-curses --disable-curl --enable-vnc-tls --
> >> enable-vnc-sasl --enable-vnc-jpeg --enable-vnc-png --enable-vnc-thread
> >
> > There is two patch for that
> > http://patchwork.ozlabs.org/patch/62420/
>
> Can you try the patch above? If it works, I need to ask Anthony to
> pick it up for 0.13.
I have not encountered this problem since applying the patch. So I sure would
like to see it in 0.13.
Thanks,
-Rick
>
> Thanks,
>
> Yoshi
>
> > http://patchwork.ozlabs.org/patch/62263/
> >
> > On of these patch is already in master:
> > http://git.qemu.org/qemu.git/commit/?id=ac71103dc6b408775ae72067790ab3679
> > 12f75ec
> >
> > --
> > Corentin Chary
> > http://xf.iksaif.net
next prev parent reply other threads:[~2010-09-27 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 20:00 [Qemu-devel] qemu: qemu_mutex_lock: Invalid argument Rick Vernam
2010-09-15 5:35 ` Corentin Chary
2010-09-15 10:46 ` Yoshiaki Tamura
2010-09-27 17:04 ` Rick Vernam [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-15 15:00 Rick Vernam
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=201009271204.52176.rickv@hobi.com \
--to=rickv@hobi.com \
--cc=corentin.chary@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tamura.yoshiaki@lab.ntt.co.jp \
/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).