From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 00:10:00 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16D8816A41F for ; Sun, 23 Oct 2005 00:10:00 +0000 (GMT) (envelope-from robin@extaci.com) Received: from firewall.extaci.com (dhcp-83-219-108-27.customers.tvtnet.ch [83.219.108.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9795843D45 for ; Sun, 23 Oct 2005 00:09:59 +0000 (GMT) (envelope-from robin@extaci.com) Received: from localhost (localhost [127.0.0.1]) by firewall.extaci.com (Postfix) with ESMTP id 9F53D83C2C for ; Sun, 23 Oct 2005 02:09:57 +0200 (CEST) Received: from firewall.extaci.com ([127.0.0.1]) by localhost (chiark [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25306-06 for ; Sun, 23 Oct 2005 02:09:56 +0200 (CEST) Received: from [10.1.0.11] (narcotropic.grayarea [10.1.0.11]) by firewall.extaci.com (Postfix) with ESMTP id 1B76E83C25 for ; Sun, 23 Oct 2005 02:09:56 +0200 (CEST) Message-ID: <435AD4D3.5090005@extaci.com> Date: Sun, 23 Oct 2005 02:09:55 +0200 From: Robin User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at extaci.com Subject: FreeBSD 6.0 rc1 guest under vmware-workstation-5.0.0.13124-r2 on linux host (boot error) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2005 00:10:00 -0000 Hello all, I thought I'd give the new RC a whirl under vmware, after setting the guest to boot from the CDROM (which was the CD1 .ISO), shortly I recieved this error: http://xs.mw/temp/freebsd6rc1_vmware_boot_error.png (BTX halted) Has anyone else experienced this? Is this a vmware problem or a freebsd one? All help appreciated, cheers, Robin