From: Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>,
Virtualization Mailing List
<virtualization-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Jim Mattson <jmattson-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
Gabriel Barazer <gabriel-KSe8qvLY914@public.gmane.org>
Subject: Re: 2.6.22 x86_64 : kernel initial decompression hangs on vmware
Date: Thu, 09 Aug 2007 16:28:16 -0700 [thread overview]
Message-ID: <46BBA310.6060706@vmware.com> (raw)
In-Reply-To: <46BB7FCC.4040509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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.
Just to make the state comprehensive, I opted to reload everything.
Zach
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-09 23:28 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 [this message]
2007-08-10 1:48 ` Avi Kivity
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=46BBA310.6060706@vmware.com \
--to=zach-pghwnbhtmq7qt0dzr+alfa@public.gmane.org \
--cc=ak-l3A5Bk7waGM@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=gabriel-KSe8qvLY914@public.gmane.org \
--cc=jmattson-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=virtualization-qjLDD68F18O7TbgM5vRIOg@public.gmane.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).