From owner-freebsd-emulation Mon Jul 24 17: 2:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 82CA137B51E for ; Mon, 24 Jul 2000 17:02:28 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny10-15.ix.netcom.com [198.211.18.79]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id UAA15704; Mon, 24 Jul 2000 20:02:25 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id UAA00521; Mon, 24 Jul 2000 20:02:23 -0400 (EDT) (envelope-from vsilyaev) Date: Mon, 24 Jul 2000 20:02:23 -0400 (EDT) From: "Vladimir N. Silyaev" Message-Id: <200007250002.UAA00521@jupiter.delta.ny.us> To: jreynold@sedona.ch.intel.com Cc: freebsd-emulation@freebsd.org Subject: Re: latest VMware port dumping core. Please advise vmware newbie ... In-Reply-To: <14716.26696.719757.828831@hip186.ch.intel.com> References: <14716.26696.719757.828831@hip186.ch.intel.com> Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In muc.lists.freebsd.emulation, you wrote: [skipped] >I was trying to use an existing partition win98 partition on ad0 (which I'd >already setup with its own "vmware" hardware profile with nothing "fancy" >installed--just plain jane win98 installation). As I wen through the >configuration wizard, things seemed to make sense. I saved everything then >clicked on the "power on" button and vmware immediate core-dumped and gave me >this: > >Jul 23 16:54:11 whale /WHALE: /dev/vmmon: ALLOW_CORE_DUMP called >Jul 23 16:54:12 whale /WHALE: /dev/vmmon: ALLOW_CORE_DUMP called >Jul 23 16:54:12 whale /WHALE: pid 72293 (vmware), uid 0: exited on signal 6 > (core dumped) >Jul 23 16:54:12 whale /WHALE: /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, > unlocked dirty pages: 0 > >Does this ring a bell to anybody? It's looks like old problem with raw devices. Under FreeBSD it's impossible to get real configuration of hard drive. And gueses about that not always right. In you situation it has a sense to read the file /usr/local/share/doc/vmware/Hints.FreeBSD and using not a raw device, but plain disk. Required numbers you could get from configuration file for raw device (and to do some work about substraction and addition on them). [skipped] >I messed around with some more configurations and chose one that used a >virtual disk. AT this point I could get my win98 bootup disk to almost boot >(went almost the whole way through then it seemed to "hang" ...). Unfortunatly I can't get any clue about vmware hanging - it should works at the same way as under Linux. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message