From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: KVM call agenda for Oct 26
Date: Tue, 26 Oct 2010 15:24:24 +0200 [thread overview]
Message-ID: <20101026132424.GG26191@redhat.com> (raw)
In-Reply-To: <4CC6D61E.9060003@codemonkey.ws>
On Tue, Oct 26, 2010 at 08:22:38AM -0500, Anthony Liguori wrote:
> On 10/26/2010 08:04 AM, Avi Kivity wrote:
> > On 10/26/2010 02:49 PM, Anthony Liguori wrote:
> >>On 10/26/2010 03:20 AM, Avi Kivity wrote:
> >>> On 10/25/2010 09:51 PM, Juan Quintela wrote:
> >>>>Please send in any agenda items you are interested in covering.
> >>>>
> >>>
> >>>0.13.1
> >>>
> >>>At least two fatal issues:
> >>>- vmmouse is broken
> >>>- assertion failure in block layer
> >>
> >>There's actually a fair bit. I'm hoping to also get the hotplug
> >>fixes because tose are pretty important IMHO. I don't want to
> >>wait too long though.
> >
> >Also, a new seabios for the SCI level triggered fix.
>
> You mean:
>
> commit 6d5a2172f2b76900572107868ec080400c4f615d
> Author: Kevin O'Connor <kevin@koconnor.net>
> Date: Wed Oct 20 21:59:11 2010 -0400
>
> mark irq9 active high in DSDT
>
> In PIIX4 SCI (irq9) is active high. Seabios marks it so in interrupt
> override table, but some OSes (FreeBSD) require the same information to
> be present in DSDT too. Make it so.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
>
> If so, what's the impact of it not being there? I wanted to stick
Power down from qemu monitor does not work for FreeBSD.
> to 0.6.1 for stable-0.13, updating to a git snapshot is going to
> pull a lot of things in that would be better to avoid for stable.
> We can talk to Kevin about a stable branch but I'd like to
> understand what the real impact here is first.
>
> Regards,
>
> Anthony Liguori
>
> >>
> >>What's the assertion in the block layer?
> >
> >https://bugzilla.redhat.com/show_bug.cgi?id=646538
> >
> >This is qemu-img, so maybe not so critical. I confused this with
> >a runtime assertion failure in the block layer, for which a fix
> >was merged post rc3.
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gleb.
next prev parent reply other threads:[~2010-10-26 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 19:51 [Qemu-devel] KVM call agenda for Oct 26 Juan Quintela
2010-10-25 19:53 ` [Qemu-devel] " Chris Wright
2010-10-26 8:20 ` Avi Kivity
2010-10-26 12:49 ` Anthony Liguori
2010-10-26 13:04 ` Avi Kivity
2010-10-26 13:22 ` Anthony Liguori
2010-10-26 13:24 ` Gleb Natapov [this message]
2010-10-26 13:23 ` [Qemu-devel] [PATCH] qcow2: Fix segfault when qcow2 preallocate fails Stefan Hajnoczi
2010-10-26 13:48 ` [Qemu-devel] " Kevin Wolf
2010-10-26 14:04 ` Stefan Hajnoczi
2010-10-26 13:09 ` [Qemu-devel] Re: KVM call agenda for Oct 26 Gleb Natapov
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=20101026132424.GG26191@redhat.com \
--to=gleb@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).