virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Gabriel Barazer <gabriel@oxeva.fr>, Andi Kleen <ak@suse.de>,
	Jim Mattson <jmattson@vmware.com>,
	linux-kernel@vger.kernel.org,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: 2.6.22 x86_64 : kernel initial decompression hangs on vmware
Date: Fri, 10 Aug 2007 04:48:06 +0300	[thread overview]
Message-ID: <46BBC3D6.902@qumranet.com> (raw)
In-Reply-To: <46BBA310.6060706@vmware.com>

Zachary Amsden wrote:
> Avi Kivity wrote:
>>
>> We haven't seen any issue with the 2.6.22 boot decompressor.  Which 
>> of the four (fs, gs, ldt, or tr) were proving problematic and why?
>
> It was tr that was affecting Workstation, since we boot through normal 
> BIOS path, and only a 16-bit task was loaded at this point.
>

Ah.  Maybe we didn't have an exit while we were in long mode with the 
16-bit tss, so VT didn't notice the illegal combination.

      reply	other threads:[~2007-08-10  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46A7E606.4030001@oxeva.fr>
     [not found] ` <46A7E606.4030001-KSe8qvLY914@public.gmane.org>
2007-08-04 16:23   ` 2.6.22 x86_64 : kernel initial decompression hangs on vmware Zachary Amsden
     [not found]     ` <46B4A7E4.4030907-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2007-08-04 17:18       ` Gabriel Barazer
2007-08-09 20:57       ` Avi Kivity
     [not found]         ` <46BB7FCC.4040509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-09 23:28           ` Zachary Amsden
2007-08-10  1:48             ` Avi Kivity [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=46BBC3D6.902@qumranet.com \
    --to=avi@qumranet.com \
    --cc=ak@suse.de \
    --cc=gabriel@oxeva.fr \
    --cc=jmattson@vmware.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=zach@vmware.com \
    /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).