From: Zachary Amsden <zach@vmware.com>
To: Gabriel Barazer <gabriel@oxeva.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22 x86_64 : kernel initial decompression hangs on vmware
Date: Wed, 25 Jul 2007 17:19:29 -0700 [thread overview]
Message-ID: <46A7E891.1020006@vmware.com> (raw)
In-Reply-To: <46A7E606.4030001@oxeva.fr>
Gabriel Barazer wrote:
> Hi,
>
> After upgrading kernel to 2.6.22 on a Vmware workstation guest version
> 5.5 and 6 , the kernel decompression stage ("Decompressing Linux...")
> is hanging for a very long time (~5 minutes) before finally
> succeeding (displaying "done.\nBooting the kernel.\n"). During this
> time, the VM process is eating all the CPU time during the
> decompression, like an infinite loop.
LKML is not the right place for this question. You are running on Intel
hardware?
Bring the discussion over to http://www.vmware.com/community forums
Zach
next prev parent reply other threads:[~2007-07-26 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 0:08 2.6.22 x86_64 : kernel initial decompression hangs on vmware Gabriel Barazer
2007-07-26 0:19 ` Zachary Amsden [this message]
2007-08-04 16:23 ` Zachary Amsden
2007-08-04 17:18 ` Gabriel Barazer
2007-08-09 20:57 ` Avi Kivity
2007-08-09 23:28 ` Zachary Amsden
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=46A7E891.1020006@vmware.com \
--to=zach@vmware.com \
--cc=gabriel@oxeva.fr \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox