Accepted Solutions
I'm really sorry if I have offended somebody or if I'm missing something totally obvious 😕 I'm not a n00b to computers/development but I am to Fusion/CentOS and I could be missing something very obvious. Either that, or I need some more specialised debugging tips than the ones easily available.
I was hoping somebody on this seemingly very competent and helpful forum had encountered similar problems and found a solution... 
/nik
Thanks a whole lot for spending time here
I did as you suggest, the error message is indeed gone, but I still don't have network. This time I tested network connection by doing a simple whois query, I got time out and "unable to connect to remote host" back.
If of any value, here is what I get in Terminal when restarting Fusion. To me it looks like there are some errors being reported, but then again I'm a complete novice as far as Fusion is concerned:
VMware Fusion 94249: Shutting down VMware Fusion:
No matching processes were found
No matching processes were found
No matching processes were found
No matching processes were found
kextunload: unload id com.vmware.kext.vmcrosstalk failed (result code 0xe00002c2)
kextunload: unload id com.vmware.kext.vmmon failed (result code 0xe00002c2)
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmmon.kext succeeded
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmci.kext succeeded
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmioplug.kext succeeded
kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmnet.kext succeeded
VMware Fusion 94249: Starting VMware Fusion:
kextload: /Library/Application Support/VMware Fusion/kexts/vmmon.kext loaded successfully
kextload: /Library/Application Support/VMware Fusion/kexts/vmci.kext loaded successfully
kextload: /Library/Application Support/VMware Fusion/kexts/vmioplug.kext loaded successfully
kextload: /Library/Application Support/VMware Fusion/kexts/vmnet.kext loaded successfully
Internet Software Consortium DHCP Server 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
Configured subnet: 172.16.168.0
Setting vmnet-dhcp IP address: 172.16.168.254
Opened:
Recving on VNet/vmnet8/172.16.168.0
Sending on VNet/vmnet8/172.16.168.0
Internet Software Consortium DHCP Server 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
WoodyZ, I *really appreciate you looking into this The very fact that you can tell you have got CentOS up and running is good to know!
OK, I installed DSL (neat indeed that thing!), fired up Firefox and voilà - connection in first try, in LAN mode. I didn't adjust anything, it just connected. This is even in a different context than before in that I'm currently travelling, connecting my Mac via a 3G wireless modem; not via my home wifi.
So, what have we got now - my original problem with CentOS is not the host machine, and its not my Fusion installation. Then it *must be how I setup CentOS, right? Just fired up my CentOS 4.6 machine, still no connection.
What I have done so far to install CentOS is:
- download a CentOS 4.6 installer image here: http://mirror.steadfast.net/centos/4.6/isos/i386/CentOS-4.6-i386-binDVD.iso
- start Fusion and select New in the Machine Library, select Linux -> Red Hat Enterprise Linux 4
- follow the CentOS-as-server setup steps found in this guide: http://www.howtoforge.com/perfect_setup_centos_4.4
The reason I want CentOS 4.X and not 5.X is that once I have it running I want to install a server plugin (Lasso) which only runs on 4, not 5. The setup guide is indeed for CentOS 4.4 where I try with a 4.6. Of course it doesn't help that I'm a total Linux-n00b...
What would you do, WoodyZ, in order to install a working CentOS 4.X - preferably with some GUI like GNOME or something similar?
Again: thanks a lot for spending time with this!
/nik
OK, I installed DSL (neat indeed that thing!), fired up Firefox and voilà - connection in first try, in LAN mode. I didn't adjust anything, it just connected.
You do not need to install DSL just download the ISO Image and boot the target Virtual Machine with the ISO Image. Also I'm not sure what you're referring to when you say "LAN mode" because a VMware Virtual Machine's Network can be set to NAT, Bridged or Host Only and technically all three create a LAN Connection although the last is a connection between the Host and the Guest only, yet two computers physical and or virtual joined together comprise a LAN albeit a very small one.
This is even in a different context than before in that I'm currently travelling, connecting my Mac via a 3G wireless modem; not via my home wifi.
So, what have we got now - my original problem with CentOS is not the host machine, and its not my Fusion installation. Then it *must be how I setup CentOS, right? Just fired up my CentOS 4.6 machine, still no connection.
Yes, at this point if you booted the CentOS 4.6 Virtual Machine with the DSL ISO Image and had Network Connectivity then I'd have to say this comes down to a CentOS 4.6 Install Configuration Issue specifically in the area of the Network Settings.
In a Terminal (/Applications/Utilities/Terminal) copy and paste the following command and this will create a file on your Desktop named host_ifconfig.txt for you to attach to a reply post.
ifconfig > ~/Desktop/host_ifconfig.txt
On the Guest what is the output of ifconfig and for that if you don't have VMware Tools installed so you can copy/paste or drag/drop a file a trimmed screenshot will suffice. Note: If not logged in as root in CentOS you may have to type: /sbin/ifconfig
I know you're traveling at the moment so the Host's Network Adpter's information is not going to match your Home and or Office however I'd like to know what the IP Address being assigned to vmnet8 is to discuss this in more technical detail using actual realtime information then just examples although your answer to my next question will determine more specifically what changes will need to be made. Also is your intent for the use of this Virtual Machine to be accessible to other computers on the LAN or just between the Host and the Guest?
I know in your OP you said "CentOS is configured with a static IP (192.168.0.100) because I want to use it as server." however is that IP Address appropriate for your LAN? What is the IP Address of the Router and if it's using DHCP what it the Scope of the Router's DHCP Server's IP Address Pool and is that IP Address in or out of Scope (because it should be out of Scope although within the Subnet)?
Anyway I have CentOS 5.1 running without any Network Connectivity issue and downloaded a CentOS 4.6 Server Appliance and it connects as well so I'd have to say you just didn't configure something right and without additional information to verify network settings that's about all for now.
Message was edited by: WoodyZ
You do not need to install DSL just download the ISO Image and boot the target Virtual Machine with the ISO Image.
OK, this I don't understand then
How do I "boot the target Virtual Machine with the ISO Image"?
Also I'm not sure what you're referring to when you say "LAN mode" because a VMware Virtual Machine's Network can be set to NAT, Bridged or Host Only
Sorry, I meant NAT
As soon as I figure out how I boot with the ISO Image, then I'll go on with the other suggestions you posted.
Thanks again!
/nik
You do not need to install DSL just download the ISO Image and boot the target Virtual Machine with the ISO Image.OK, this I don't understand then
Aside from reading what I wrote in also read...
Have a look at: VMware Fusion menu bar > Help > VMware Fusion Help > Managing Virtual Machines > Configuring the CD/DVD Drive > To connect and configure a CD/DVD drive
Specifically Step 6.
Message was edited by: WoodyZ
So I'm perfectly clear you boot the target problematic Virtual Machine with the DSL ISO Image so as to preform diagnostics on the Virtual Hardware and configuration there of to determine that the target Virtual Machine as a container and as configured Network wise has the ability to connect to the Internet with a Know Good Working OS and booting DSL from the ISO Image provides this type of diagnostics. It basically eliminates troubleshooting from everything but the install Guest OS then thus making it much easier to resolve the issue. Understand?
Hi WoodyZ,
I understand what you are after but whichever of your indications I try to follow I fail...
I understand how I can choose a disk image in Settings > CD/DVD > Use disk image, but when I try to invoke the boot menu following your instructions as they appear in that other XP-thread, pressing ESC at the moment you indicate, I do get a menu (see attached screenshot) but none seems to be the Image. So I'm stuck already here.
Also, in the .vmx file of the package of the problematic CentOS-guest I cannot find a line saying bios.bootDelay.
I include two ifconfig files if of any use to you. They are from my current (travelling) condition.
Its like this attempt of mine to use Fusion/Linux is doomed, but hell, I'll keep trying...
/nik
Doh |-(
Once I got added the boot delay I could see where I had to hit ESC, before the delay it passed *so fast that I hardly perceived anything...
However, you spotted the root of the problem: once I changed the Guest's static IP (I took 172.16.168.3) then I had network
Now I can proceed to install my server software and try to do my testing. One last thing: if I want to hit the Guest's webserver from the Host machine with a browser, then how do I do that?
As a conclusion I would say that my problem arrose as a combination of a non-standard install, my incompetence in this new area, and - frankly - the lack of a note somewhere in the Fusion docs about assigning static IP.
Thanks a lot for your patient help, without you I had given up long ago
Take care
/nik
One last thing: if I want to hit the Guest's webserver from the Host machine with a browser, then how do I do that?
Since your using a Static IP Address for the target Virtual Machine I would add the Servers Domain Name to the Host's /etc/hosts file.
Example: On the Host in a Terminal (/Applications/Utilities/Terminal) type (or copy and paste) the following commands:
Backup the existing hosts file...
sudo cp /etc/hosts /etc/hosts.bak
Edit the existing hosts file...
sudo nano /etc/hosts
Add the following lines...
172.16.168.3 domain_name.com
172.16.168.3 www.domain_name.com
Where domain_name is the Domain Name given to the Server.
You would then be able to access the Virtual Machine's Web Server from the Host Web Browser via the following...
Thanks a lot for your patient help, without you I had given up long ago
Your welcome and I'm glad that's behind you as I'm sure there will be bigger hurdles to jump coming up.
Hey, I wanted to add that although you may not have used the DSL ISO Image to boot the target Virtual Machine nonetheless it's a good tool to have as well as my directions on modifying the .vmx configuration file as it may come in handy in the future for other things you may want to try or have an issue with.
Also there is another Linux Live OS CD/DVD ISO Image you may what to look at and download. Its Knoppix and specifically “KNOPPIX_V5.1.1CD-2007-01-04-EN.iso” as this is the latest CD ISO Image and it can boot a VMware Virtual Machine and recognize the VMware SCSI Virtual Hard Drive and Mount them without the need for anything else. One can then load the Samba Server and then be able to access the Virtual Machine's Virtual Hard Drive from the Host to effect data recovery in the event the Virtual Machine cannot boot the installed OS (providing of course the virtual hard drive is not damaged to a point not capable of recovery). It also has many other uses although Data Recovery and Diagnostics are the main reasons I like using it. AFAIC Both DSL and Knoppix are a must have if you're going to be playing around in the Virtual Machine world.