Hi All,
I have installed VMWare 2.0.2-203138_x64 on a CentOS 5.4 x64. Everything appears to work fine. I can create the virtual machine but when I power it on the whole vmware web access is unreachable on default port 8222/8333.
[root@Panda]# uname -a Linux Panda 2.6.18-164.10.1.el5 #1 SMP Thu Jan 7 19:54:26 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
Does anybody know if there is a compatibility problem with the new kernel 2.6.180164.10.1 ?
[root@Panda vmware-server-distrib]# /usr/bin/vmware @@PRODUCT_NAME@@ is installed, but it has not been (correctly) configured for the running kernel. To (re-)configure it, invoke the following command: /usr/bin/vmware-config.pl.
Has anyone else experienced this issue? If so have you found a fix?
Thx, A.
********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ********************************
Quoting attila.mathe@orange-ftgroup.com:
Hi All,
I have installed VMWare 2.0.2-203138_x64 on a CentOS 5.4 x64. Everything appears to work fine. I can create the virtual machine but when I power it on the whole vmware web access is unreachable on default port 8222/8333.
[root@Panda]# uname -a Linux Panda 2.6.18-164.10.1.el5 #1 SMP Thu Jan 7 19:54:26 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
Does anybody know if there is a compatibility problem with the new kernel 2.6.180164.10.1 ?
[root@Panda vmware-server-distrib]# /usr/bin/vmware @@PRODUCT_NAME@@ is installed, but it has not been (correctly) configured for the running kernel. To (re-)configure it, invoke the following command: /usr/bin/vmware-config.pl.
Has anyone else experienced this issue? If so have you found a fix?
did you run the command /usr/bin/vmware-config.pl ?
-- Eero
Yep, here's the output:
[root@Panda vmware-server-distrib]# /usr/bin/vmware-config.pl Making sure services for VMware Server are stopped.
Stopping VMware autostart virtual machines: Virtual machines [FAILED] Stopping VMware management services: VMware Virtual Infrastructure Web Access VMware Server Host Agent [FAILED] Stopping VMware services: VMware Authentication Daemon [ OK ] VM communication interface socket family: [ OK ] Virtual machine communication interface [ OK ] Virtual machine monitor [ OK ] Bridged networking on /dev/vmnet0 [ OK ] Host network detection [ OK ] DHCP server on /dev/vmnet1 [ OK ] Host-only networking on /dev/vmnet1 [ OK ] DHCP server on /dev/vmnet8 [ OK ] NAT service on /dev/vmnet8 [ OK ] Host-only networking on /dev/vmnet8 [ OK ] Virtual ethernet [FAILED] Unable to stop services for VMware Server
Execution aborted.
I'm not able to stop the vm machines or restart the web access, just by killing all vmware related pid's.
A
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Eero Volotinen Sent: Tuesday, January 12, 2010 11:31 AM To: centos@centos.org Subject: Re: [CentOS] VMWare server 2
Quoting attila.mathe@orange-ftgroup.com:
Hi All,
I have installed VMWare 2.0.2-203138_x64 on a CentOS 5.4 x64. Everything appears to work fine. I can create the virtual machine but when I power it on the whole
vmware
web access is unreachable on default port 8222/8333.
[root@Panda]# uname -a Linux Panda 2.6.18-164.10.1.el5 #1 SMP Thu Jan 7 19:54:26 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
Does anybody know if there is a compatibility problem with the new kernel 2.6.180164.10.1 ?
[root@Panda vmware-server-distrib]# /usr/bin/vmware @@PRODUCT_NAME@@ is installed, but it has not been (correctly) configured for the running kernel. To (re-)configure it, invoke the following command: /usr/bin/vmware-config.pl.
Has anyone else experienced this issue? If so have you found a fix?
did you run the command /usr/bin/vmware-config.pl ?
-- Eero
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ********************************
On Tue, Jan 12, 2010 at 11:27 AM, attila.mathe@orange-ftgroup.com wrote:
I have installed VMWare 2.0.2-203138_x64 on a CentOS 5.4 x64. Everything appears to work fine.
What does that mean? Does it work fine or does it only pretend to work (fine)?
I can create the virtual machine but when I power it on the whole vmware web access is unreachable on default port 8222/8333.
SELinux is in which state?
Regards,
Ralph
On Tue, Jan 12, 2010 at 2:27 AM, attila.mathe@orange-ftgroup.com wrote:
Hi All,
I have installed VMWare 2.0.2-203138_x64 on a CentOS 5.4 x64. Everything appears to work fine. I can create the virtual machine but when I power it on the whole vmware web access is unreachable on default port 8222/8333.
There is a known issue with VMware Server 2.0.x and CentOS 5.4 as reported here:
http://bugs.centos.org/view.php?id=3884
A workaround can be found there.
Akemi
On Tue, Jan 12, 2010 at 8:17 AM, Akemi Yagi amyagi@gmail.com wrote:
I have installed VMWare 2.0.2-203138_x64 on a CentOS 5.4 x64. Everything appears to work fine. I can create the virtual machine but when I power it on the whole vmware web access is unreachable on default port 8222/8333.
There is a known issue with VMware Server 2.0.x and CentOS 5.4 as reported here:
http://bugs.centos.org/view.php?id=3884
A workaround can be found there.
The workaround resolved a similar issue on my system..
BTW, you may also need to configure the firewall to allow 8222/8333 through via system-config-securitylevel