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@xxxxxxxxxxxx> > 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@xxxxxxxxxx> > > 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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
