-2

I have installed vmware server 2.0.2 on CentOS 6.2. I hit the issue Error opening the remote virtual machine 192.168.1.91:8333\32: A connection to the host could not be established when powering on a virtual machine and opening VMware Remote Console. (where 192.168.1.91 is the eth0 address of the host machine)

After some googling, I found a common solution is to either set up static IP or point to dns server to 127.0.0.1. But I'm not quite sure what it means.

Here is what I've tried.

  • add 127.0.0.1 192.168.1.91 to my /etc/hosts file
  • change domain-name-server in /etc/vmware/vmnet1/dhcpd/dhcpd.conf to 127.0.0.1 (so I use Host-Only for my virtual machine)
  • add nameserver 127.0.0.1 to my /etc/resolv.conf

None of the above works.

I've spent hours of time on the issue and really want to get it over with.

Please clarify it for me . Thanks.

closed as too localized by Michael Hampton, HopelessN00b, Magellan, Zoredache, ewwhite Mar 28 '13 at 22:25

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Spend a few bucks and pick up a copy of Vmware Workstation. Go with ESXi if the host is purely for VMs and has supported hardware. Or use virtualbox/kvm/xen/etc. Vmware Server is dead. – Zoredache Mar 28 '13 at 22:10
  • @Zoredache the host is not purely for VMs. Also, I have to log on it via a jump machine or access web ui through socks proxy, which means no GUI is available. So which product would you recommend in my situation? – manuzhang Mar 29 '13 at 5:00
4

Oh, easy.

Don't install new instances of VMWare server, and migrate off any VMWare Server instances you do have now.

In January 2010, VMware announced the End of Support for VMware Server with support ending on June 30, 2011. Users are free to continue using VMware Server but are recommended to migrate to another VMware offering to gain the benefits of newer technologies.

There are several VMware offerings that can replace VMware Server depending on the functionality needed. These offerings range from VMware Player for running one or two virtual machines to VMware vSphere Hypervisor for virtualizing on physical host, to VMware vSphere for running more than 100 virtual machines with centralized management and cloud scalability. See the Compare tab for a comparison of the offerings.

Replace Server with Player or ESXi (there's a free version), then try to set up virtual machines and virtual networking and all that.

  • Smart alec answer, but doesn't answer the question. The product in question didn't just stop working overnight, just because they don't support it doesn't mean people still can't be helpful. – JamesRyan Mar 28 '13 at 20:23
  • @JamesRyan Do it right, or don't do it at all. There's absolutely no way you can slice it where installing VMWare Server is "doing it right" now that it's EOS. Honestly, helping someone blow their foot off isn't what most reasonable folks would consider helpful. – HopelessN00b Mar 28 '13 at 20:31
  • It is not faulty, its simply not being updated anymore. Sorry but there are many cases where you want to be compatible with other vmware products but need a base OS on a machine where it is entirely appropriate to still use it. What is 'right' is merely your opinion and that is not what stackexchange is here for. – JamesRyan Mar 28 '13 at 20:42
  • @JamesRyan Fine, install Windows 3.11 on all the things. It is not faulty, its simply not being updated anymore. Must be an appropriate solution to suggest on a StackExchange Site for Information Technology Professionals, right? – HopelessN00b Mar 28 '13 at 20:47
  • 4
    The product in question didn't just stop working overnight, just because they don't support it doesn't mean people still can't be helpful. - Given that Vmware heavily depends on various kernel modules successfully compiling and working, it is perfectly reasonable to say that a kernel that is ~3 years newer then the last official release might just have breaking changes, which cannot be fixed. – Zoredache Mar 28 '13 at 22:13
0

Run vmware-config.pl. And allow port 8333 in iptables.

  • 1
    Nice in theory. My bet is that he is running a kernel new enough that the module compilation is failing. – Zoredache Mar 28 '13 at 22:14

Not the answer you're looking for? Browse other questions tagged or ask your own question.