From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: John Stoffel <john@stoffel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Booting up an old Windows 3.1 harddisk image
Date: Tue, 18 Oct 2011 15:21:49 +0200 [thread overview]
Message-ID: <4E9D7D6D.8050308@siemens.com> (raw)
In-Reply-To: <4E9D7B83.4020402@redhat.com>
On 2011-10-18 15:13, Avi Kivity wrote:
> On 10/18/2011 03:07 PM, Jan Kiszka wrote:
>>>
>>> It's probably a bug in kvm. Try collecting a complete trace as in
>>> http://www.linux-kvm.org/page/Tracing and posting it here, maybe
>>> something will jump out.
>>>
>>> Also try out -no-kvm.
>>
>> A shot from the hips: Jörg and I are just hunting down 16 bit task
>> switch issues on AMD hosts. If this problem may be related can be
>> checked by loading kvm-amd with npt=0, ie. disabling nested paging.
>
> Do you mean that you suspect that kvm's task switch emulation is more
> accurate than the hardware? Gleb will have a heart attack.
As it looks like (for AMD). But the last proof is yet missing - /me is
instrumenting right now.
> Another area to look at is A20 emulation, based on where the hang occurs.
Yeah, maybe. Traces may tell.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-10-18 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 0:59 Booting up an old Windows 3.1 harddisk image John Stoffel
2011-10-18 10:42 ` Avi Kivity
2011-10-18 13:07 ` Jan Kiszka
2011-10-18 13:13 ` Avi Kivity
2011-10-18 13:21 ` Jan Kiszka [this message]
2011-10-18 13:08 ` John Stoffel
2011-10-18 13:11 ` Avi Kivity
2011-10-18 17:08 ` John Stoffel
2011-10-18 17:31 ` Avi Kivity
2011-10-19 2:02 ` Jun Koi
2011-10-19 2:06 ` Jun Koi
2011-10-19 13:55 ` John Stoffel
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=4E9D7D6D.8050308@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=john@stoffel.org \
--cc=kvm@vger.kernel.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 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.