From: Jan Kiszka <jan.kiszka@siemens.com>
To: Tom Horsley <tom.horsley@att.net>
Cc: kvm@vger.kernel.org
Subject: Re: bad leakage between virtual machines?
Date: Wed, 20 Jan 2010 18:36:54 +0100 [thread overview]
Message-ID: <4B573F36.7000703@siemens.com> (raw)
In-Reply-To: <4B564BC9.5010407@web.de>
Jan Kiszka wrote:
> Jan Kiszka wrote:
>> Tom Horsley wrote:
>>> On Fri, 15 Jan 2010 18:37:57 +0100
>>> Jan Kiszka wrote:
>>>
>>>> Tom Horsley wrote:
>>>>> I just submitted this fedora bug with lots of details:
>>>>>
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=555788
>>>>>
>>>>> It sure seems to me like the contents of the debug
>>>>> address trap registers are leaking across virtual machines
>>>>> (at least for opterons on this motherboard :-).
>>>> Are only AMD boxes affected, or did you also test on Intel?
>>> I haven't explicitly tested on Intel, but we did just see a
>>> compile on a guest on the Intel host also get the same
>>> Breakpoint/Trap error out of the blue, so it looks as if it
>>> does happen on intel as well as amd.
>> OK, will have a look at your test application once time permits.
>>
>
> Just did so with bleeding-edge kvm-kmod and qemu-kvm-0.12.1.2 on an
> Intel host. But nothing exciting happened.
>
> Are you sure that test on an Intel host was really an Intel? In your bug
> report you write the contrary. Anyway, will have my hands on an AMD box
> tomorrow and try to reproduce there.
No success reproducing on AMD either. This time I'm using
kvm-kmod-2.6.32.3 (so none of today's debug register patches applied)
and qemu-kvm-0.12.1.2.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-01-20 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 15:17 bad leakage between virtual machines? Tom Horsley
2010-01-15 17:37 ` Jan Kiszka
2010-01-15 18:21 ` Tom Horsley
2010-01-15 18:38 ` Jan Kiszka
2010-01-20 0:18 ` Jan Kiszka
2010-01-20 17:36 ` Jan Kiszka [this message]
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=4B573F36.7000703@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=tom.horsley@att.net \
/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.