Welcome to FreeBSDFreaks.net!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

VMWare 2 works on FreeBSD 4.10-Stable (except for NIC)

 
   FreeBSD Hosting (Home) -> FreeBSD Stable RSS
Next:  freebsd-stable packages on freebsd-release-4.9  
Author Message
bsdfsse

External


Since: Oct 03, 2004
Posts: 1



(Msg. 1) Posted: Sun Oct 03, 2004 2:34 am
Post subject: VMWare 2 works on FreeBSD 4.10-Stable (except for NIC)
Archived from groups: mailing>freebsd>questions (more info?)

I have everything working except for the networking (which is proving to
be very difficult).

I followed Phusion's guide for VMWare 2 and FreeBSD 4.10 located here:

http://www.packetwatch.net/documents/guides/freebsd/vmware2.php

Previously I had tried 4.10, but I think at that time I was erroneously
entering "vmnet1" in to the NIC config, instead of "/dev/vmnet1". I was
also getting ATA errors on that particular machine's 200GB drives, which
is prolly a completely different problem.

My Win 2000 Pro virtual machine can ping itself, but not the host
machine, or any of my other LAN machines. Christian emailed me some
instructions that differ from Phusion's regarding the configuration of
the /usr/local/etc/vmware/config file. Christian has these 2 lines
while Phusion does not (and I tried it both ways):

vmnet1.Bridged = "YES"
vmnet1.BridgedInterface = "x10"

Phusion does mention the "x10" in his instructions for the /etc/rc.firewall.

My IP setting are:

Linksys Router: 192.168.0.1

FreeBSD 4.10-Stable PC
Static IP: 192.168.0.24
DNS Server: 167.206.1.103
Gateway: 192.168.0.1
SubnetMask: 255.255.255.0

VMWare /usr/local/etc/vmware/config:
vmnet1.HostOnlyAddress = "192.168.0.10"
vmnet1.HostOnlyNetMask = "255.255.255.0"
(also from Christian's doc)
vmnet1.Bridged = "YES"
vmnet1.BridgedInterface = "x10"


Win2000 Pro Virtual PC
Static IP: 192.168.0.11
Gateway: 192.168.0.10
SubnetMask: 255.255.255.0

I made the changes to my kernel, /etc/rc.conf, /etc/rc.firewall, and
/etc/fstab that Phusion indicated.

Any ideas why my Virtual Machine cannot ping either the "HostOnly" IP or
the FreeBSD's machine normal IP? It also cannot ping my Linksys router,
or any of my other machines.

Inside the VM I have the NIC defined as "Custom" and "/dev/vmnet1". The
HostOnly and Bridged options did not work, as they seemed to be
leaving off the "/dev/" in front of vmnet0 and vmnet1 (as I did too!).

Aside from no networking, Win 2000 Pro seems to be running pretty well
inside VMWare 2.0.

thx!

_______________________________________________
freebsd-questions RemoveThis @freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

 >> Stay informed about: VMWare 2 works on FreeBSD 4.10-Stable (except for NIC) 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Freebsd STABLE - I am using 5.2 realese and using CTM to get STABLE In the CTM ftp I found these folders 08/07/03 12:00AM <DIR> cvs-cur 01/04/02 12:00AM <DIR> ports-cur 02/11/01 12:00AM <DIR> src-2.2 08/07/03 12:00AM ...

FreeBSD 5-STABLE - ... is it production quality? I do notice they say Production Release on the FreeBSD.org page, and 4.10 being legacy, but from experience.. has anyone had any significant problems? I'd be doing it from a fresh-install, rather than an upgrade.. and m...

FreeBSD 5.4-STABLE - I re-built my 5.3 system yesterday after cvsup ran yesterday in the A.M. After a rebooting I get: # uname -v FreeBSD 5.4-STABLE #5: Sun Apr 17 16:32:09 CDT 2005 jjr@www.larush.com:/usr/obj/usr/src/sys/GENERIC I didn't see any annoucement about..

ohphone 1.4.1 FreeBSD 5.3 Stable - Hello, anybody there has tried ohphone 1.4.1 in FreeBSD 5.3 Stable? I have working sound (output good. Input, well the mic records sound, not good quality). Ophone registers to gatekeeper, but no sound is produced while a call is in course. Error..

talk / freebsd 4.8-stable - hi group for some reason (probably after a buildworld) my talk utility stopped working. I thought initially it might have been due to inetd.conf being overwritten but this is not the case: [snip] # ntalk is required for the 'talk' utility to work..
   FreeBSD Hosting (Home) -> FreeBSD Stable All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]