From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Ingmar Schraub <is@eseco.de>, Avi Kivity <avi@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released
Date: Tue, 15 Dec 2009 15:41:33 +0100 [thread overview]
Message-ID: <4B27A01D.6010304@redhat.com> (raw)
In-Reply-To: <4B279DB2.4050204@codemonkey.ws>
>> 2.) If you specify an USB device at the command line like -usbdevice
>> host:0421:00ab and the device is not available (not plugged-in) when you
>> start the guest, qemu segfaults.
>
> Haven't heard this one yet. I'm assuming it's a qdev interaction.
No. It is monitor_printf(NULL, ...
Patch adding checks to usb-linux.c is on the qemu-devel list already.
I've seen someone posted another patch which makes monitor_printf not
barf on mon == NULL, which would fix the segfault too.
cheers,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Ingmar Schraub <is@eseco.de>, Avi Kivity <avi@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released
Date: Tue, 15 Dec 2009 15:41:33 +0100 [thread overview]
Message-ID: <4B27A01D.6010304@redhat.com> (raw)
In-Reply-To: <4B279DB2.4050204@codemonkey.ws>
>> 2.) If you specify an USB device at the command line like -usbdevice
>> host:0421:00ab and the device is not available (not plugged-in) when you
>> start the guest, qemu segfaults.
>
> Haven't heard this one yet. I'm assuming it's a qdev interaction.
No. It is monitor_printf(NULL, ...
Patch adding checks to usb-linux.c is on the qemu-devel list already.
I've seen someone posted another patch which makes monitor_printf not
barf on mon == NULL, which would fix the segfault too.
cheers,
Gerd
next prev parent reply other threads:[~2009-12-15 14:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 18:33 [ANNOUNCE] qemu-kvm-0.12.0-rc2 released Avi Kivity
2009-12-14 21:58 ` Dustin Kirkland
2009-12-14 21:58 ` [Qemu-devel] " Dustin Kirkland
2009-12-15 9:10 ` Avi Kivity
2009-12-15 9:10 ` [Qemu-devel] " Avi Kivity
2009-12-15 14:23 ` Lennart Sorensen
2009-12-15 14:23 ` Lennart Sorensen
2009-12-15 14:29 ` Anthony Liguori
2009-12-15 14:29 ` [Qemu-devel] " Anthony Liguori
2009-12-15 15:21 ` Dustin Kirkland
2009-12-15 15:21 ` [Qemu-devel] " Dustin Kirkland
2009-12-18 4:51 ` Dustin Kirkland
2009-12-18 4:51 ` [Qemu-devel] " Dustin Kirkland
2009-12-20 16:25 ` Avi Kivity
2009-12-20 16:25 ` [Qemu-devel] " Avi Kivity
2009-12-21 3:39 ` Dustin Kirkland
2009-12-21 3:39 ` [Qemu-devel] " Dustin Kirkland
2009-12-21 9:30 ` Avi Kivity
2009-12-21 9:30 ` [Qemu-devel] " Avi Kivity
2009-12-15 8:28 ` Ingmar Schraub
2009-12-15 9:07 ` Avi Kivity
2009-12-15 9:07 ` [Qemu-devel] " Avi Kivity
2009-12-15 9:47 ` Daniel Bareiro
2009-12-15 14:31 ` Anthony Liguori
2009-12-15 14:31 ` [Qemu-devel] " Anthony Liguori
2009-12-15 14:41 ` Gerd Hoffmann [this message]
2009-12-15 14:41 ` Gerd Hoffmann
2009-12-15 18:22 ` Luiz Capitulino
2009-12-15 18:22 ` Luiz Capitulino
2009-12-15 9:51 ` [PATCH] " Bernhard Held
2009-12-15 10:18 ` Avi Kivity
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=4B27A01D.6010304@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=is@eseco.de \
--cc=kvm@vger.kernel.org \
--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.