Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Jul 2000 14:43:15 -0400
From:      mwhalen@uucom.com
To:        mike ryan <msr@elision.org>
Cc:        freebsd-stable@FreeBSD.ORG, larse@ISI.EDU, joseph.scott@owp.csus.edu
Subject:   Re: vmware2 and xfree86-4.0.1 
Message-ID:  <200007141843.OAA05107@tangerine.uucom.com>
In-Reply-To: Message from mike ryan <msr@elision.org>  of "Thu, 13 Jul 2000 12:26:35 EDT." <20000713122635.A67937@medianstrip.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
I think I heard mike ryan say:
>On Thu, Jul 13, 2000 at 11:44:17AM -0400, Matthew Whalen wrote:
>> 
>> I have a new machine that I'm trying to configure.  It's very similar
>> to my regular home machine (PIII 700 vs K7 700).  They both run
>> 4.0-stable (home was build last about 1 month ago, new machine yesterday).
>> I have xf86 4 on this new machine, and 3 at home.
>> 
>> My vmware on the new machine dies cathing with a SIGSEGV and "Abort trap"
>> being printed to the screen.  I know that vmware doesn't officially support
>> XF86 4, but this doesn't really sound a lot like an Xserver problem
>> to me.  There isn't much in the vmware log to note.  Has anyone tried
>> vmware2 with XF86 4 yet?  If so, did you get the same result?  Is there
>> something else going on?
>
>i've had the same result.  i'm also running 4.0-stable built within
>the last few days and xfree86 4.0.1, on a sony vaio z505hs laptop.
>
>on my system at least, there appears to be a correlation with disk
>modes -- virtual machines configured with raw disks abort on boot,
>virtual machines with virtual disks work fine.



Thank you. This fixed the problem.  I wonder why a new release of X would
break disk access...   I guess I'll wait a while before upgrading at home
since I have my virtual machine installed on a raw disk partition so 
that I could boot NT >ick< if I wanted to outside of VMware.

-matthew



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007141843.OAA05107>