From owner-freebsd-bugs  Mon Jul 17 12:30: 7 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 7247A37BB05
	for <freebsd-bugs@FreeBSD.org>; Mon, 17 Jul 2000 12:30:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id MAA45939;
	Mon, 17 Jul 2000 12:30:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from tangerine.uucom.com (temp-229.uucom.com [198.202.217.229])
	by hub.freebsd.org (Postfix) with ESMTP id CF3F437BB7B
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 17 Jul 2000 12:20:02 -0700 (PDT)
	(envelope-from dakota@tangerine.uucom.com)
Received: (from dakota@localhost)
	by tangerine.uucom.com (8.9.3/8.9.3) id OAA00642;
	Mon, 17 Jul 2000 14:20:11 GMT
	(envelope-from dakota)
Message-Id: <200007171420.OAA00642@tangerine.uucom.com>
Date: Mon, 17 Jul 2000 14:20:11 GMT
From: Matthew Whalen <dakota@tangerine.uucom.com>
Reply-To: dakota@tangerine.uucom.com
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/19991: VMware partition access broken in mid-june with kernel/sys update
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         19991
>Category:       kern
>Synopsis:       VMware partition access broken in mid-june with kernel/sys update
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 17 12:30:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Matthew Whalen
>Release:        FreeBSD 4.1-RC i386
>Organization:
N/A
>Environment:

	vmware2-2.0.1.570, linprocfs-0.1, linux_base-6.1

>Description:

	My home system, built last on June 13, works properly, but
	my work system (rebuilt on July 14) has a problem with VMware.
	I've been told by another user that this problem began for
	him when he rebuilt his OS and kernel in mid-June. VMware
	gives an "Abort Trap" message with vmmon receiving a
	SEGV when powering on the virtual machine configured for
	access to a raw partition.  Access to a virtual disk in
	the filesystem still works properly.  This appears to
	likely be a kernel issue.

>How-To-Repeat:

	With current kernel, configure VMware to book from a physical
	disk partition and power on.  I will gladly provide any
	additional information if given instructions on how to get
	the data.

>Fix:

	None known.


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message