On Wed, Mar 02, 2011 at 12:34:24PM +0100, Jan Kiszka wrote: > On 2011-03-02 11:56, Alon Levy wrote: > > On Wed, Mar 02, 2011 at 09:22:35AM +0100, Jan Kiszka wrote: > >> On 2011-03-01 13:58, Alon Levy wrote: > >>> On Sun, Feb 27, 2011 at 08:11:26PM +0100, Jan Kiszka wrote: > >>>> On 2011-02-27 20:03, Alon Levy wrote: > >>>>> On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote: > >>>>>> On 2011-02-26 12:43, xming wrote: > >>>>>>> When trying to start X (and it loads qxl driver) the kvm process just crashes. > >>>>> > >>>>> This is fixed by Gerd's attached patch (taken from rhel repository, don't know > >>>>> why it wasn't pushed to qemu-kvm upstream). I'll send it to kvm list as well (separate email). > >>>> > >>>> Patch looks OK on first glance, but the changelog is misleading: This > >>>> was broken for _both_ trees, but upstream didn't detect the bug. > >>> > >>> So I didn't test with qemu not having this patch, but according to the discussion in the > >>> launchpad bug the problem only happens with qemu-kvm. This doesn't rule out it being a > >>> bug, perhaps it is just triggered much less frequently I guess. > >> > >> Again: qemu-kvm has the instrumentation to detect the bug, qemu is > >> lacking this, but both trees will break subtly if cpu_current_env is not > >> properly restored. > > > > ok, so what do you want to be done further before this patch is applied? > > The patch posted to qemu-devel just requires a changelog that correctly > reflects what it addresses (and where). Just sent, Alon > > Jan > -- 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
