From owner-freebsd-bugs Mon Jun 17 1:33:42 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C90C937B408; Mon, 17 Jun 2002 01:33:39 -0700 (PDT) Received: (from roam@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g5H8XdI64689; Mon, 17 Jun 2002 01:33:39 -0700 (PDT) (envelope-from roam) Date: Mon, 17 Jun 2002 01:33:39 -0700 (PDT) From: Message-Id: <200206170833.g5H8XdI64689@freefall.freebsd.org> To: sauber@netcom.com, roam@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/39394: 4.6 does not run as VMware guest OS Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: 4.6 does not run as VMware guest OS State-Changed-From-To: open->feedback State-Changed-By: roam State-Changed-When: Mon Jun 17 01:30:41 PDT 2002 State-Changed-Why: Could you try entering the 'visual userconfig' phase before the installation kernel boots, and then disabling some of the devices that the kernel will later probe for? If "stripping down" the kernel configuration to only the devices that your virtual system has fixes the problem, it would be very helpful if you could then retry the installation a couple of times to find out just which devices do cause the hang during probing. http://www.freebsd.org/cgi/query-pr.cgi?pr=39394 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message