From owner-freebsd-emulation Sun Nov 26 7:38:20 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id D36EF37B479 for ; Sun, 26 Nov 2000 07:38:17 -0800 (PST) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.1/8.11.0) with ESMTP id eAQFi2900485 for ; Sun, 26 Nov 2000 16:44:02 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Sun, 26 Nov 2000 16:44:02 +0100 (CET) From: "O. Hartmann" To: freebsd-emulation@freebsd.org Subject: NCAR Graphics and FreeBSD (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sirs. I just received ncarg-4.2.2 as sourcecode and ncarg-4.2.1 as Linux tarball. We want to use NCAR Graphics libraries for some Fortran projects and Fortran on FreeBSd ist Portland group (PGI) Fortran 90 for Linux, running sucessful under Linux emulation. Because these libraries will be used from PGI Fortran I'm a little bit confused whether it is a good task to compile sources under FreeBSD. On the other hand, I run into minor trouble when trying to install the Linux distribution, because the INSTALL routine messed up some things, so I simply untared the TAR files into the destination and hope now that all the stuff finds its way. Some minor modifications to some specific shell scripts were made already. So, primary question is: installing Linux libraries being used by a Fotran compiler used by Linux emulation seems more reasonable than compiling sources under FreeBSD and then using them by an Linux Fortran compiler. Is this right? Has anybody installed and used successfully NCARG libraries? Thanks in advance, O. Hartmann - MfG O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz BRD/Germany Tel: +496131/3924662 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Nov 26 12: 8:45 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from liliput.tmp.com.br (liliput.tmp.com.br [200.244.62.12]) by hub.freebsd.org (Postfix) with ESMTP id CBA4137B479 for ; Sun, 26 Nov 2000 12:08:40 -0800 (PST) Received: (from macedo@localhost) by liliput.tmp.com.br (8.8.8/8.8.8) id SAA20391 for freebsd-emulation@freebsd.org; Sun, 26 Nov 2000 18:08:36 -0200 Date: Sun, 26 Nov 2000 18:08:36 -0200 From: Sergio Macedo To: freebsd-emulation@freebsd.org Subject: Vmware2 on 4.1-RELEASE Message-ID: <20001126180819.D19849@tmp.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-URL: http://www.tmp.com.br Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings. I'm trying to run vmware2 on a box but just get the following at the command line: yamato::macedo[110]: vmware Abort trap yamato::macedo[111]: In the /var/log/messages: Nov 26 17:23:11 yamato /kernel: /dev/vmmon: ALLOW_CORE_DUMP called Nov 26 17:23:11 yamato /kernel: /dev/vmmon: ALLOW_CORE_DUMP called Nov 26 17:23:11 yamato /kernel: pid 6929 (vmware), uid 1000: exited on signal 6 Nov 26 17:23:11 yamato /kernel: /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages: 0 I believe the problem is in the physical disk handling functions because if I set it up to use a virtual disk, I'm at least able to boot the virtual machine with a W95 floppy. However, the floppy doesn't finish the boot. It gets frozen just after the Windows copyright message.... Here are some data about my box and the vmware port I'm using: Physical Mem: 96Mb Hard Disk: IDE 4Gb OS & ports: 4.1-RELEASE linux_base-6.1 rtc-2000-05-05 vmware2-2.0.1.570 vmmon-freebsd-0.95.1.tar.gz vmnet-freebsd-0.11.tar.gz I found some messages reporting flawless installing and running under 4.1-STABLE and 4.2-BETA... Would my only option to upgrade my system? Or was anyone else able to run vmware2 on 4.1-RELEASE? Thanks in advance for any advice. -- TMP Consultoria Sergio Macedo TEL (21) 556-3791 FAX (21) 556-4398 - "Conscience is what hurts when everything else feels so good." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Nov 26 12:47:54 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 1A0AF37B4C5 for ; Sun, 26 Nov 2000 12:47:50 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id C11EC6C; Sun, 26 Nov 2000 12:47:48 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id MAA21003; Sun, 26 Nov 2000 12:47:39 -0800 (PST) Message-ID: <3A2176EA.ABA0E2E1@cup.hp.com> Date: Sun, 26 Nov 2000 12:47:38 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "O. Hartmann" Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: NCAR Graphics and FreeBSD (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "O. Hartmann" wrote: > > So, primary question is: installing Linux libraries being used by a > Fotran compiler used by Linux emulation seems more reasonable than > compiling sources under FreeBSD and then using them by an Linux Fortran > compiler. Is this right? Yes. You can't mix FreeBSD libraries and Linux binaries (and vice versa). You can however compile Linux libraries on FreeBSD as well. To do that, install the linux_devtools port from the ports collection and build the library from within a Linux shell. By doing that, you'll use the Linux compiler to compile and thus end up with a Linux library. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Nov 27 0:30: 6 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from yog-sothoth.sgi.com (unknown [192.48.160.10]) by hub.freebsd.org (Postfix) with ESMTP id ACFBD37B4C5 for ; Mon, 27 Nov 2000 00:29:56 -0800 (PST) Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id JAA5619460; Mon, 27 Nov 2000 09:29:29 +0100 (CET) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA18539; Mon, 27 Nov 2000 09:29:20 +0100 Received: from sgi.com by cuckoo.munich.sgi.com via ESMTP (980427.SGI.8.8.8/911001.SGI) id JAA80589; Mon, 27 Nov 2000 09:29:15 +0100 (MET) Message-ID: <3A03C8D9.670998CE@sgi.com> Date: Sat, 04 Nov 2000 09:29:13 +0100 From: "Georg-W. Koltermann" Organization: SGI X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Sergio Macedo Cc: freebsd-emulation@freebsd.org Subject: Re: Vmware2 on 4.1-RELEASE References: <20001126180819.D19849@tmp.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sergio Macedo wrote: > Greetings. > [...] > > I believe the problem is in the physical disk handling functions because > if I set it up to use a virtual disk, I'm at least able to boot the virtual > machine with a W95 floppy. However, the floppy doesn't finish the boot. > It gets frozen just after the Windows copyright message.... I believe you must first install Windows in a virtual disk of your VM, and then setup access to your Windows hard disk partitions. At least that is what worked for me. Afaik, you cannot use the same boot partition for native Windows and Windows in a VM. I am using 4.1-RELEASE and vmware2 straight from the ports. Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Nov 27 3: 8:36 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from solo.ned.dem.csiro.au (solo.ned.dem.CSIRO.AU [130.116.144.65]) by hub.freebsd.org (Postfix) with ESMTP id E4A6D37B479 for ; Mon, 27 Nov 2000 03:08:31 -0800 (PST) Received: from truro-gc.ned.dem.csiro.au (truro-gc.ned.dem.CSIRO.AU [130.116.145.114]) by solo.ned.dem.csiro.au (8.9.1a/8.9.0) with ESMTP id TAA07406 for ; Mon, 27 Nov 2000 19:08:13 +0800 (WST) Message-Id: <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> X-Sender: peterho@solo.ned.dem.csiro.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 27 Nov 2000 16:45:41 +0800 To: freebsd-emulation@freebsd.org From: Peter Hornby Subject: Re: Vmware2 on 4.1-RELEASE In-Reply-To: <20001126180819.D19849@tmp.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, >yamato::macedo[110]: vmware > >as disk and R/W access for it on the correspondent windows> >crash> >Abort trap >yamato::macedo[111]: >In the /var/log/messages: >Nov 26 17:23:11 yamato /kernel: /dev/vmmon: ALLOW_CORE_DUMP called >Nov 26 17:23:11 yamato /kernel: /dev/vmmon: ALLOW_CORE_DUMP called >Nov 26 17:23:11 yamato /kernel: pid 6929 (vmware), uid 1000: exited on >signal 6 >Nov 26 17:23:11 yamato /kernel: /dev/vmmon: Vmx86_DestroyVM: unlocked >pages: 0, unlocked dirty pages: 0 > >I believe the problem is in the physical disk handling functions because >if I set it up to use a virtual disk, I'm at least able to boot the virtual >machine with a W95 floppy. However, the floppy doesn't finish the boot. >It gets frozen just after the Windows copyright message.... I've been waiting for some time for this problem to go away. Currently running vmware2 on FreeBSD 4.2-BETA. Works fine(ish) from virtual disk, got ethernet bridge to work, can even sync a palm pilot via the serial line to a mapped disk on an old DEC UNIX box on the network! The problems are:- 1) Attempts to set all forms of physical/raw disk crash the vmware configuration editor. This crash generally occurs when filling in the appropriate field in the configuration editor dialog. (The wizard seems to manage OK though). If one edits the files by hand, (or uses the wizard) then vmware crashes when it tries to access the disks. This occurs whether one says the disk is /dev/hda, /compat/linux/dev/hda, /dev/wd0 (hey, I'll try anything!). 2) This is more an X thing. If the vmware window is minimised, or on another desktop that is not currently being displayed, then ctrl-alt-F8 ing to the vmware full screen mode kills the vmware machine. (This usually rightly stuffs the sync on my old DEC monitor too :) Other than that, it's looking pretty viable. A word of warning about booting native and a vm-machine from the same partition though. You may think that by setting two windows configurations that you will deal with the different hardware configurations seen by windows. If you think this will work, you don't know M$ very well. Alternate hardware profiles may indeed deal with the odd serial port, modem, or even an ethernet card going missing, but if you think M$ ever contemplated dealing with the entire BIOS, motherboard, graphics card etc. etc. etc. changing from one configuration to another, then think again. I've spent hours trying to tip-toe through this mine field.... auto-detecting hardware ad nauseam, trying this that & the other order of hardware additions, vmware corrupting registries.....and this is with a (real) chipset the same as the virtual one (though the real machine is dual CPU). If anyone has a way around this............. Has anyone ported the linux perl (python? I forget) script that mounts vmware virtual disks, and allows access to them from the host operating system? Regards, _________________________________________________________ Dr P. Hornby CSIRO Exploration & Mining , 39 Fairway, PO Box 437, Nedlands, WA 6009 Australia Phone +61 8 9389 8421 Fax +61 8 9389 1906 e-mail p.hornby@dem.csiro.au __________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Nov 27 8: 0:18 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0FC6B37B479 for ; Mon, 27 Nov 2000 08:00:16 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA10080; Mon, 27 Nov 2000 11:00:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eARG0Fv79359; Mon, 27 Nov 2000 11:00:15 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 27 Nov 2000 11:00:14 -0500 (EST) To: Peter Hornby Cc: freebsd-emulation@freebsd.org Subject: Re: Vmware2 on 4.1-RELEASE In-Reply-To: <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> References: <20001126180819.D19849@tmp.com.br> <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14882.33448.840576.154563@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Hornby writes: <..> > 1) Attempts to set all forms of physical/raw disk crash the vmware > configuration editor. This crash generally occurs when filling in the > appropriate field in the configuration editor dialog. (The wizard seems to > manage OK though). If one edits the files by hand, (or uses the wizard) > then vmware crashes when it tries to access the disks. This occurs whether > one says the disk is /dev/hda, /compat/linux/dev/hda, /dev/wd0 (hey, I'll > try anything!). Have you tried reading /usr/local/share/doc/vmware/Hints.FreeBSD? Specifically, you should be using a "plain" disk. See Hints.FreeBSD for more details. I've set up both my wife's laptop (Win98) and my boss's desktop (win2k) like this, both work flawlessly under vmware. My wife actually boots natively occasionally, my boss never hase -- I installed w2k under vmware on a fresh disk installed into his box just for w2k under vmware. I've set up both of these machine manually (eg, not used the configuration editor). <..> > booting native and a vm-machine from the same partition though. You may > think that by setting two windows configurations that you will deal with > the different hardware configurations seen by windows. If you think this > will work, you don't know M$ very well. Alternate hardware profiles may > indeed deal with the odd serial port, modem, or even an ethernet card going > missing, but if you think M$ ever contemplated dealing with the entire > BIOS, motherboard, graphics card etc. etc. etc. changing from one > configuration to another, then think again. I've spent hours trying to > tip-toe through this mine field.... auto-detecting hardware ad nauseam, > trying this that & the other order of hardware additions, vmware corrupting > registries.....and this is with a (real) chipset the same as the virtual > one (though the real machine is dual CPU). If anyone has a way around > this............. This is indeed a royal pain in the butt. I managed to get my wife's laptop working after a day or so of fiddling. There was some initial schizophrenia regarding the video card, but the profiles seem to just work now. I have no idea what the problem with the video card was in the first place... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Nov 27 12:38:16 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 0995937B479 for ; Mon, 27 Nov 2000 12:38:14 -0800 (PST) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.33 2000/11/21 19:27:27 smothers Exp $) with ESMTP id UAA26876; Mon, 27 Nov 2000 20:41:51 GMT Received: from arc083.ch.intel.com (arc083.ch.intel.com [143.182.202.33]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id NAA13477; Mon, 27 Nov 2000 13:37:54 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by arc083.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id NAA26551; Mon, 27 Nov 2000 13:37:52 -0700 (MST) X-Authentication-Warning: arc083.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14882.50720.46600.575175@arc083.ch.intel.com> Date: Mon, 27 Nov 2000 13:37:52 -0700 (MST) To: Peter Hornby Cc: freebsd-emulation@freebsd.org Subject: Re: Vmware2 on 4.1-RELEASE In-Reply-To: <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> References: <20001126180819.D19849@tmp.com.br> <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> X-Mailer: VM 6.75 under Emacs 20.6.1 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Monday, November 27, Peter Hornby wrote: ] > > booting native and a vm-machine from the same partition though. You may > think that by setting two windows configurations that you will deal with > the different hardware configurations seen by windows. If you think this > will work, you don't know M$ very well. Alternate hardware profiles may > indeed deal with the odd serial port, modem, or even an ethernet card going > missing, but if you think M$ ever contemplated dealing with the entire > BIOS, motherboard, graphics card etc. etc. etc. changing from one > configuration to another, then think again. I've spent hours trying to > tip-toe through this mine field.... auto-detecting hardware ad nauseam, > trying this that & the other order of hardware additions, vmware corrupting > registries.....and this is with a (real) chipset the same as the virtual > one (though the real machine is dual CPU). If anyone has a way around > this............. Just wanted to add my "me too" here. If you're going to run VMware especially with a win98 client, don't expect the "dual hardware profile" thing to work at all. You'll need to setup Win98 under a virtual disk. Period. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Nov 28 5:12:27 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.ciac.jl.cn (unknown [202.98.16.1]) by hub.freebsd.org (Postfix) with ESMTP id EC25A37B400 for ; Tue, 28 Nov 2000 05:12:21 -0800 (PST) Received: from 11 ([159.226.123.49]) by ns.ciac.jl.cn (8.9.1/8.9.1) with SMTP id VAA07063 for ; Tue, 28 Nov 2000 21:04:21 +0800 (CST) Message-ID: <006401b99ec2$763f4020$317be29f@11> From: "S.W.Liu" To: Subject: why I can't use rtc-2000.09.22 on FreeBSD-current( src4619)? Date: Mon, 28 Nov 1994 21:17:57 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org d2h5IEkgcGtnX2FkZCBydGMtMjAwMC4wOS4yMiBhbmQgSSByZXN0YXJ0IGl0IHNheToNCg0KIHJ0 Y2tsZGxvYWQ6IGNhbid0IGxvYWQgL2Jvb3Qva2VybmVsL3J0Yy5rbzogRXhlYyBmb3JtYXQgZXJy b3INCnVzYWdlOiB2bXdhcmUuc2gge3N0YXJ0fHN0b3B9DQprbGRsb2FkOiBjYW4ndCBsb2FkIC91 c3IvbG9jYWwvbGliL3Ztd2FyZS9saWIvbW9kdWxlcy92bW1vbl91cC5rbzogRXhlYyBmb3JtYXQg ZXJyb3INCnN5c2N0bDogdW5rbm93biBvaWQgJ25ldC5saW5rLmV0aGVyLmJyaWRnZV9yZWZyZXNo Jw0Ka2xkbG9hZDogY2FuJ3QgbG9hZCBpZl90YXAua286IEZpbGUgZXhpc3RzDQogVk13YXJlDQoN CndoeT8NCg0KQmVzdCBSZWdhcmQhDQoNCg0KDQoNCg== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Nov 29 12:27:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from rebel.org (m16-tapolca.elender.hu [212.108.215.143]) by hub.freebsd.org (Postfix) with ESMTP id 14EA737B401 for ; Wed, 29 Nov 2000 12:27:29 -0800 (PST) Received: (from root@localhost) by rebel.org (8.11.1/8.11.1) id eAT995I00203 for freebsd-emulation@FreeBSD.org; Wed, 29 Nov 2000 09:09:05 GMT (envelope-from root) Date: Wed, 29 Nov 2000 09:09:05 GMT From: Uveges Balint Message-Id: <200011290909.eAT995I00203@rebel.org> To: freebsd-emulation@FreeBSD.org Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Nov 30 6:53:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from solo.ned.dem.csiro.au (solo.ned.dem.CSIRO.AU [130.116.144.65]) by hub.freebsd.org (Postfix) with ESMTP id C855737B400 for ; Thu, 30 Nov 2000 06:53:27 -0800 (PST) Received: from ned.dem.csiro.au (truro.ned.dem.CSIRO.AU [130.116.145.99]) by solo.ned.dem.csiro.au (8.9.1a/8.9.0) with ESMTP id WAA12060; Thu, 30 Nov 2000 22:53:16 +0800 (WST) Message-ID: <3A266A7F.FB8B67BA@ned.dem.csiro.au> Date: Thu, 30 Nov 2000 22:55:59 +0800 From: Peter Hornby Organization: CSIRO Exploration and Mining. X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-emulation@freebsd.org Subject: Re: Vmware2 on 4.1-RELEASE References: <20001126180819.D19849@tmp.com.br> <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> <14882.33448.840576.154563@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > Peter Hornby writes: > <..> > > 1) Attempts to set all forms of physical/raw disk crash the vmware > > configuration editor. This crash generally occurs when filling in the > > > > Have you tried reading /usr/local/share/doc/vmware/Hints.FreeBSD? > Specifically, you should be using a "plain" disk. See Hints.FreeBSD > for more details. > Thanx Drew. One more wrinkle. The following plain disk config ========================= DRIVETYPE ide CYLINDERS 13410 HEADS 15 SECTORS 63 # Partition type: MBR ACCESS "/home/truro1/peterho/vmware/hda/wd0.mbr" 0 63 # Partition type: Win95 FAT32 ACCESS "/dev/rwd0s1" 63 4096512 # Partition type: Win95 FAT32 ACCESS "/dev/rwd0s5" 4096575 4289292 # Partition type: Win95 FAT32 ACCESS "/dev/rwd0s6" 8385867 4273227 # Partition type: Padding RDONLY "/dev/null" 12659094 13356 ========================== Only links in the first partition into the device chain in the VM (ie. windows only sees the first partition). The workaround is ugly but obvious, define three plain disks. That works, so the partitions are all OK etc.. Am I being stupid? or is this a bug? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Nov 30 6:59:47 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id CE29237B400 for ; Thu, 30 Nov 2000 06:59:41 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA19266; Thu, 30 Nov 2000 09:59:41 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAUExfM02585; Thu, 30 Nov 2000 09:59:41 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 30 Nov 2000 09:59:41 -0500 (EST) To: Peter Hornby Cc: freebsd-emulation@freebsd.org Subject: Re: Vmware2 on 4.1-RELEASE In-Reply-To: <3A266A7F.FB8B67BA@ned.dem.csiro.au> References: <20001126180819.D19849@tmp.com.br> <4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au> <14882.33448.840576.154563@grasshopper.cs.duke.edu> <3A266A7F.FB8B67BA@ned.dem.csiro.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14886.27359.274083.576046@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Hornby writes: > Andrew Gallatin wrote: > > > Peter Hornby writes: > > <..> > > > 1) Attempts to set all forms of physical/raw disk crash the vmware > > > configuration editor. This crash generally occurs when filling in the > > > > > > > Have you tried reading /usr/local/share/doc/vmware/Hints.FreeBSD? > > Specifically, you should be using a "plain" disk. See Hints.FreeBSD > > for more details. > > > > Thanx Drew. One more wrinkle. The following plain disk config > ========================= > DRIVETYPE ide > CYLINDERS 13410 > HEADS 15 > SECTORS 63 > > # Partition type: MBR > ACCESS "/home/truro1/peterho/vmware/hda/wd0.mbr" 0 63 > > # Partition type: Win95 FAT32 > ACCESS "/dev/rwd0s1" 63 4096512 > > # Partition type: Win95 FAT32 > ACCESS "/dev/rwd0s5" 4096575 4289292 > > # Partition type: Win95 FAT32 > ACCESS "/dev/rwd0s6" 8385867 4273227 > > # Partition type: Padding > RDONLY "/dev/null" 12659094 13356 > ========================== > > Only links in the first partition into the device chain in the VM (ie. windows > only sees the first partition). > The workaround is ugly but obvious, define three plain disks. That works, so the > partitions are all OK etc.. > Am I being stupid? or is this a bug? I really don't know -- I've never used more than one windows partition. Uhm.. Are rwd0s5 and rwd0s6 extended partitions? Can FreeBSD even see extended partitions? Eg, can you mount -t msdos them? If FreeBSD can't see them, then VMware running under FreeBSD can't see them. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Dec 1 7:50:10 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from solo.ned.dem.csiro.au (solo.ned.dem.CSIRO.AU [130.116.144.65]) by hub.freebsd.org (Postfix) with ESMTP id BF7ED37B400 for ; Fri, 1 Dec 2000 07:50:04 -0800 (PST) Received: from ned.dem.csiro.au (truro-gc.ned.dem.CSIRO.AU [130.116.145.114]) by solo.ned.dem.csiro.au (8.9.1a/8.9.0) with ESMTP id XAA24696 for ; Fri, 1 Dec 2000 23:49:58 +0800 (WST) Message-ID: <3A27C855.62A7FF5E@ned.dem.csiro.au> Date: Fri, 01 Dec 2000 23:48:37 +0800 From: Peter Hornby Organization: CSIRO Exploration and Mining. X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Subject: Re: Vmware2 on 4.2-STABLE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a line FYae. The trick is.... 1) try to create a raw disk in order to get the wizard to make the following file for you ====== DEVICE /compat/linux/dev/hda # Partition type: MBR RDONLY 0 62 # Partition type: Win95 FAT32 NO_ACCESS 63 4096574 # Extended partition hole RDONLY 4096575 4096637 # Partition type: Win95 FAT32 ACCESS 4096638 8385929 # Extended partition hole RDONLY 8385930 8385992 # Partition type: Win95 FAT32 ACCESS 8385993 12659219 ======== 2) Hack this into a plain disk format along the lines of the Hints file. ======== DRIVETYPE ide CYLINDERS 13410 HEADS 15 SECTORS 63 # Partition type: MBR RDONLY "/home//vmware/hda/wd0.mbr" 0 63 # Partition type: Win95 FAT32 RDONLY "/dev/rwd0s1" 63 4096512 # Extended partition hole RDONLY "/home//vmware/hda/wd0.eph1" 4096575 63 # Partition type: Win95 FAT32 ACCESS "/dev/rwd0s5" 4096638 4289292 # Extended partition hole RDONLY "/home//vmware/hda/wd0.eph2" 8385930 63 # Partition type: Win95 FAT32 ACCESS "/dev/rwd0s6" 8385993 4273227 # padding RDONLY "/dev/null" 12659220 13230 ========== 3) Grab the partition tables and MBR & put then in the indicated files above eg. dd if=/dev/rwd0 of=wd0.eph1 bs=1b count=63 skip=4096575 etc.... 3a) Now install this disk in a VM config somewhere, and see if it's OK.(Don't boot from it). 4) Now do a dd if=/dev/rwd0s1 of=whatever bs=1b count=4096512 to get a copy of the first partition, and point the plain disk's first partition at this instead of the real disk slice (and make it ACCESS instead of RDONLY). 5) boot with this plain disk, and see what the damage is..... Cheers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Dec 1 11:19:10 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from arcticbears.com (a00d4382b30gj.bc.hsia.telus.net [216.232.254.184]) by hub.freebsd.org (Postfix) with ESMTP id 776D637B401 for ; Fri, 1 Dec 2000 11:19:07 -0800 (PST) Received: from WorldClient [127.0.0.1] by arcticbears.com [216.232.254.184] with SMTP (MDaemon.v3.0.3.R) for ; Fri, 01 Dec 2000 11:17:56 -0800 Date: Fri, 01 Dec 2000 11:17:55 -0800 From: "Eric Paynter" To: "FreeBSD Emulation" Subject: Could not open /dev/vmnet1: Device not configured X-Mailer: WorldClient Standard 3.0.2 X-MDaemon-Deliver-To: freebsd-emulation@freebsd.org X-Return-Path: eric@arcticbears.com X-MDRcpt-To: freebsd-emulation@freebsd.org X-MDRemoteIP: 127.0.0.1 Message-Id: <20001201191907.776D637B401@hub.freebsd.org> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get vmware to run under FBSD 4.1 and when I enable the network interface, I get Could not open /dev/vmnet1: Device not configured Failed to configure ethernet0. What is left for me to configure? Some info from the command line: bash-2.04# ifconfig vmnet1 vmnet1: flags=843 mtu 1500 inet 192.168.100.100 netmask 0xffffff00 broadcast 192.168.100.255 ether 00:50:56:ea:c1:a9 bash-2.04# ls -l /dev | grep vmnet1 crw-r--r-- 1 root wheel 201, 1 Oct 18 14:04 vmnet1 bash-2.04# ls -l /compat/linux/dev | grep vmnet1 crw-r--r-- 1 root wheel 149, 0x00010001 Oct 18 11:18 vmnet1 bash-2.04# cat /etc/vmware/config vmware.fullpath = "/usr/local/lib/vmware/bin/vmware" wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard" dhcpd.fulpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd" loop.fullpath = "/usr/local/lib/vmware/bin/vmware-loop" libdir = "/usr/local/lib/vmware/lib" vmnet1.HostOnlyAddress = "192.168.100.100" vmnet1.HostOnlyNetMask = "255.255.255.0" bash-2.04# Thanks for any help! -Eric ------------------------------------------------------- arctic bears - the internet - your way. 50000 domain names were reserved today. was yours? domains from US$25/year, name resolution, mail hosting. http://www.arcticbears.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message