All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of	QEMU
Date: Tue, 8 Dec 2009 10:52:06 +0000	[thread overview]
Message-ID: <20091208105206.GA16596@redhat.com> (raw)
In-Reply-To: <4B1E2D36.6030800@redhat.com>

On Tue, Dec 08, 2009 at 11:40:54AM +0100, Gerd Hoffmann wrote:
> On 12/07/09 19:34, Daniel P. Berrange wrote:
> >On Sun, Dec 06, 2009 at 04:43:03PM -0600, Anthony Liguori wrote:
> >>
> >>It can be downloaded from Savannah at:
> >>
> >>http://download.savannah.gnu.org/releases/qemu/qemu-0.12.0-rc1.tar.gz
> >>
> >>Please send testing feedback (positive or negative) to qemu-devel and
> >>file bugs against the release candidate at:
> >
> >A couple of hotplug issues with the old monitor
> >
> >
> >It crashes with an assertion failure when hot-plugging without ACPI 
> >enabled.
> >Previously this worked, but that was perhaps just by luck rather than
> >design.
> 
> "worked" as in "guest actually sees the new device (without reboot)" or
> "worked" as in "qemu didn't abort" ?

The latter. The guest does not see it, but it at least does not abort.
It is the 'does not abort' behaviour I'm interested in - quite OK with
this returning an error to the monitor client when acpi is disabled.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-12-08 10:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 22:43 [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU Anthony Liguori
2009-12-07 12:49 ` Luiz Capitulino
2009-12-07 13:45   ` Anthony Liguori
2009-12-07 13:59     ` Luiz Capitulino
2009-12-07 14:30     ` [Qemu-devel] " Michael S. Tsirkin
2009-12-07 14:36       ` Anthony Liguori
2009-12-07 14:45         ` Michael S. Tsirkin
2009-12-07 14:56           ` Anthony Liguori
2009-12-07 18:34 ` [Qemu-devel] " Daniel P. Berrange
2009-12-07 19:43   ` Anthony Liguori
2009-12-07 20:25     ` Daniel P. Berrange
2009-12-08 10:40   ` Gerd Hoffmann
2009-12-08 10:52     ` Daniel P. Berrange [this message]
2009-12-08 12:52       ` Gerd Hoffmann
2009-12-08 13:07         ` Gerd Hoffmann
2009-12-09 10:21           ` Daniel P. Berrange
2009-12-07 20:18 ` [Qemu-devel] [PULL] pci compliance fixes Michael S. Tsirkin
2009-12-09 10:27 ` [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU Ian Molton
2009-12-09 16:56 ` Daniel P. Berrange
2009-12-10  9:22   ` Gerd Hoffmann
2009-12-10 12:16     ` Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2009-12-14 14:06 Anthony Liguori
2009-12-14 16:08 ` Artyom Tarasenko
2009-12-14 16:20   ` Anthony Liguori
2009-12-14 16:56     ` Blue Swirl
2009-12-14 17:00 ` Avi Kivity
2009-12-14 17:28   ` Anthony Liguori
2009-12-16  3:19 ` Ryan Harper

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=20091208105206.GA16596@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=kraxel@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.