From: Gerd Hoffmann <kraxel@redhat.com>
To: "Denis V. Lunev" <den-lists@virtuozzo.com>
Cc: Thomas Lamprecht <thomas@lamprecht.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Regression with windows 7 VMs and VGA CVE-2016-3712 fix (2.6.0 and 2.5.1.1)
Date: Wed, 18 May 2016 13:58:26 +0200 [thread overview]
Message-ID: <1463572706.30045.54.camel@redhat.com> (raw)
In-Reply-To: <573C39AB.5010008@virtuozzo.com>
Hi,
> we have (may be) similar stuff with win2k3. With these patches merged
> we have win2k3 crashed with the bug check below.
> We are using qemu-kvm-2.3.0-31.2.13
>
> There are a bunch of VMs in this state and semi-reliable reproduction.
Does https://patchwork.ozlabs.org/patch/622965/ help?
cheers,
Gerd
next prev parent reply other threads:[~2016-05-18 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 23:13 [Qemu-devel] Regression with windows 7 VMs and VGA CVE-2016-3712 fix (2.6.0 and 2.5.1.1) Thomas Lamprecht
2016-05-15 9:28 ` Stefan Weil
2016-05-15 10:07 ` Thomas Lamprecht
2016-05-18 9:45 ` Denis V. Lunev
2016-05-18 11:58 ` Gerd Hoffmann [this message]
2016-05-24 11:25 ` Denis V. Lunev
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=1463572706.30045.54.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=den-lists@virtuozzo.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas@lamprecht.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 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).