I'm unable to connect to VMware Server 2 via https://127.0.0.1:8333. The connection times out. I've been reading fragments of reports elsewhere on the web that others are running into major problems with VMware Server 2 on 64-bit F10. They all say they can't shut down VMware services or re-run vmware-config.pl without hard resetting via the power switch. Some have suggested shutting down SELinux (add selinux=0 to grub.conf), but this doesn't fix the problem. Others have suggested shutting down the firewall. Again, no joy.
Can anyone point me to a working solution?
--Doc Savage Fairview Heights, IL
Robert G. (Doc) Savage wrote:
I'm unable to connect to VMware Server 2 via https://127.0.0.1:8333. The connection times out. I've been reading fragments of reports elsewhere on the web that others are running into major problems with VMware Server 2 on 64-bit F10. They all say they can't shut down VMware services or re-run vmware-config.pl without hard resetting via the power switch. Some have suggested shutting down SELinux (add selinux=0 to grub.conf), but this doesn't fix the problem. Others have suggested shutting down the firewall. Again, no joy.
Can anyone point me to a working solution?
--Doc Savage Fairview Heights, IL
Did you finish the install by running "vmware-config.pl" ? Its a must. and you must have your kernel dev packages installed to do it. Second: do "service vmware status" to see if the services are up ... if not start them. Also try your non https port at 8222 (which is the default, you can change it in the config script). wcn
On Thu, 2009-04-02 at 07:30 -0600, Wendell Nichols wrote:
Robert G. (Doc) Savage wrote:
I'm unable to connect to VMware Server 2 via https://127.0.0.1:8333. The connection times out. I've been reading fragments of reports elsewhere on the web that others are running into major problems with VMware Server 2 on 64-bit F10. They all say they can't shut down VMware services or re-run vmware-config.pl without hard resetting via the power switch. Some have suggested shutting down SELinux (add selinux=0 to grub.conf), but this doesn't fix the problem. Others have suggested shutting down the firewall. Again, no joy.
Can anyone point me to a working solution?
--Doc Savage Fairview Heights, IL
Did you finish the install by running "vmware-config.pl" ? Its a must. and you must have your kernel dev packages installed to do it. Second: do "service vmware status" to see if the services are up ... if not start them. Also try your non https port at 8222 (which is the default, you can change it in the config script). wcn
I run 2 servers with VMware Server on F10 at my church and have seen this before. I think it's a bug somewhere, but am not really sure. I think it's that something gets crossed up with kernel versions in the VMware Server configuration.
What I usually do to fix the problem - believe it or not - is to shutdown and reboot the server. Twice.
What this seems to do is to force VMware to figure out that it isn't properly configured and then allows you to run vmware-config.pl successfully.
As to the questions about selinux and the firewall:
- Yes, selinux must be disabled. Nobody has yet figured out exactly why. It's an ongoing issue. Permissive mode doesn't cut it. But you can disable it from the selinux menu (System --> Administration --> SELinux Administration).
- No you do NOT have to disable the firewall. But you DO have to allow communication on ports 901, 902, 8222, and 8333. I usually open them up for both TCP and UDP, even though UDP is probably not needed.
Hope that helps!
Cheers,
Chris
-- ============================= "The most effective way to do it is to do it."
--Amelia Earhart, American Aviation Pioneer
On Thu, 2009-04-02 at 08:47 -0600, Christopher A. Williams wrote:
On Thu, 2009-04-02 at 07:30 -0600, Wendell Nichols wrote:
Robert G. (Doc) Savage wrote:
I'm unable to connect to VMware Server 2 via https://127.0.0.1:8333. The connection times out. I've been reading fragments of reports elsewhere on the web that others are running into major problems with VMware Server 2 on 64-bit F10. They all say they can't shut down VMware services or re-run vmware-config.pl without hard resetting via the power switch. Some have suggested shutting down SELinux (add selinux=0 to grub.conf), but this doesn't fix the problem. Others have suggested shutting down the firewall. Again, no joy.
Can anyone point me to a working solution?
--Doc Savage Fairview Heights, IL
Did you finish the install by running "vmware-config.pl" ? Its a must. and you must have your kernel dev packages installed to do it. Second: do "service vmware status" to see if the services are up ... if not start them. Also try your non https port at 8222 (which is the default, you can change it in the config script). wcn
I run 2 servers with VMware Server on F10 at my church and have seen this before. I think it's a bug somewhere, but am not really sure. I think it's that something gets crossed up with kernel versions in the VMware Server configuration.
What I usually do to fix the problem - believe it or not - is to shutdown and reboot the server. Twice.
What this seems to do is to force VMware to figure out that it isn't properly configured and then allows you to run vmware-config.pl successfully.
As to the questions about selinux and the firewall:
- Yes, selinux must be disabled. Nobody has yet figured out exactly why.
It's an ongoing issue. Permissive mode doesn't cut it. But you can disable it from the selinux menu (System --> Administration --> SELinux Administration).
- No you do NOT have to disable the firewall. But you DO have to allow
communication on ports 901, 902, 8222, and 8333. I usually open them up for both TCP and UDP, even though UDP is probably not needed.
Hope that helps!
Cheers,
Chris
Chris,
Very interesting. I'll try your recommendations and let you know how they worked. Thanks a bunch.
--Doc
On Thu, 2009-04-02 at 21:53 -0500, Robert G. (Doc) Savage wrote:
Chris,
Very interesting. I'll try your recommendations and let you know how they worked. Thanks a bunch.
--Doc
Following up... Opening up those four ports solves the logon problem. I was able to begin creating a VM for Fedora 11 64-bit, but things ground to an absolute halt when it came time to format a 24GB virtual disk. It didn't seem to matter whether it was contiguous or in 2GB chunks. That's as far as I've been able to proceed. I have no idea if it's a Fedora 10 problem or a VMware Server 2 problem.
I need to do some more checking to see if I can shut down the vmware services without having to use the power button.
--Doc
On Fri, 2009-04-03 at 21:41 -0500, Robert G. (Doc) Savage wrote:
On Thu, 2009-04-02 at 21:53 -0500, Robert G. (Doc) Savage wrote:
Chris,
Very interesting. I'll try your recommendations and let you know how they worked. Thanks a bunch.
--Doc
Following up... Opening up those four ports solves the logon problem. I was able to begin creating a VM for Fedora 11 64-bit, but things ground to an absolute halt when it came time to format a 24GB virtual disk. It didn't seem to matter whether it was contiguous or in 2GB chunks. That's as far as I've been able to proceed. I have no idea if it's a Fedora 10 problem or a VMware Server 2 problem.
I need to do some more checking to see if I can shut down the vmware services without having to use the power button.
That is rather odd - My server VMs are all 25GB or bigger and are as happy as a clam. Are you reserving all of the space for the disk in advance or allowing it to grow dynamically?
In my case, I have a single disk file (I find 2GB chunks a pain to track / move around, and they're really not needed with the newer file systems). I also usually tend to set them as growable as opposed to reserving the space in advance. I use that as a crude form of thin provisioning.
Fortunately, I have not had to reboot servers very often for the configuration problem. At this point I see it crop up on occasion after a kernel upgrade, where I'm already going to reboot the box anyway. Booting it twice at that stage has been more of an annoying inconvenience than anything else.
Glad the firewall port fix helped!
Cheers,
Chris
-- ============================= "You see things as they are and ask, 'Why?' I dream things as they never were and ask, 'Why not?'"
-- George Bernard Shaw
-
Christopher A Williams -
Robert G. (Doc) Savage -
Wendell Nichols