I had installed the vmware server ( VMware-server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
Thanks
Am 26.04.2010 um 19:36 schrieb Agnello George:
I had installed the vmware server ( VMware- server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
v2.0 uses a servlet running on an included tomcat container for administration-tasks. It boils down to a plugin that runs in Firefox and only on Linux +Windows.
It's slow as a snail.
Rainer
On 4/26/2010 12:36 PM, Agnello George wrote:
I had installed the vmware server ( VMware-server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
The 2.x server doesn't have a separate console program like the 1.x series did - remote access is browser-based. Connect via http on port 8882 or https on 8883. But, there are problems with the glibc library in RHEL/CentOS5 updates that may not be resolved yet. Do you even have the server running?
On Mon, Apr 26, 2010 at 1:48 PM, Les Mikesell lesmikesell@gmail.com wrote:
On 4/26/2010 12:36 PM, Agnello George wrote:
I had installed the vmware server ( VMware-server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
The 2.x server doesn't have a separate console program like the 1.x series did - remote access is browser-based. Connect via http on port 8882 or https on 8883. But, there are problems with the glibc library in RHEL/CentOS5 updates that may not be resolved yet. Do you even have the server running?
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
Am 26.04.2010 um 19:52 schrieb Kwan Lowe:
On Mon, Apr 26, 2010 at 1:48 PM, Les Mikesell lesmikesell@gmail.com wrote:
On 4/26/2010 12:36 PM, Agnello George wrote:
I had installed the vmware server ( VMware- server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
The 2.x server doesn't have a separate console program like the 1.x series did - remote access is browser-based. Connect via http on port 8882 or https on 8883. But, there are problems with the glibc library in RHEL/CentOS5 updates that may not be resolved yet. Do you even have the server running?
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
I switched to ESX4i and use a Windows VM with VI-Client to manage it - there's no other way to do it, unfortunately. For something that works on Windows exclusively (Dot-Net...), it's horribly slow and buggy. I don't see how a Java-solution would have been slower.
Rainer
On 4/26/2010 1:01 PM, Rainer Duffner wrote:
I switched to ESX4i and use a Windows VM with VI-Client to manage it - there's no other way to do it, unfortunately. For something that works on Windows exclusively (Dot-Net...), it's horribly slow and buggy. I don't see how a Java-solution would have been slower.
You only need the client up to the point where you get the network set up. Then you can switch to a better native remote access method directly to the guest target, like ssh/freenx for Centos, remote desktop/vnc for windows - just like you would with a physical machine.
On 4/26/2010 1:01 PM, Rainer Duffner wrote:
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
I switched to ESX4i and use a Windows VM with VI-Client to manage it - there's no other way to do it, unfortunately. For something that works on Windows exclusively (Dot-Net...), it's horribly slow and buggy. I don't see how a Java-solution would have been slower.
For what it's worth, I was still able to download and install the 1.x version of VMware server (1.0.10) on an up to date Centos 5.4. The only down side to an 'unsupported' host is that you have to have the kernel headers and a compiler installed so the vmware-config.pl script can build the kernel module. And the remote console client is nicer than the web based access in the 2.x versions. But, for anything other than pretending to keep some old and dying host running for a service that would be hard to port, I'd start with ESXi instead. I did just run across an odd problem with ESXi, though. Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
On Wed, 2010-04-28 at 12:39 -0500, Les Mikesell wrote:
Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
--- Well for those that must have a Windows OS heres the hack:
You must go to microsoft.com search for the tools to allow that. What it does is Relax The Windows IDE Checks so the disk or image can be used as a VM or on other hardware. You must also have the same ACPI Options in your hypervisor.
This must be done before you use the vmware tools to create the image.
John
On 4/28/2010 12:55 PM, JohnS wrote:
On Wed, 2010-04-28 at 12:39 -0500, Les Mikesell wrote:
Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
Well for those that must have a Windows OS heres the hack:
You must go to microsoft.com search for the tools to allow that. What it does is Relax The Windows IDE Checks so the disk or image can be used as a VM or on other hardware. You must also have the same ACPI Options in your hypervisor.
This must be done before you use the vmware tools to create the image.
Thanks - I assumed it had something to do with the old style bios geometry because I can boot the VM with a linux rescue disk and see what I expect, but the boot loader can't find it. What seems odd to me is that it works fine when the conversion is to a VMware server image file but not when going directly to ESXi (which I'd expect to be smarter). I haven't tried it yet, but I'll bet that I can run the converter again, using the .vmx as the source and ESXi as the target and it will work without any changes to the windows OS.
On Wed, 2010-04-28 at 13:17 -0500, Les Mikesell wrote:
On 4/28/2010 12:55 PM, JohnS wrote:
On Wed, 2010-04-28 at 12:39 -0500, Les Mikesell wrote:
Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
Well for those that must have a Windows OS heres the hack:
You must go to microsoft.com search for the tools to allow that. What it does is Relax The Windows IDE Checks so the disk or image can be used as a VM or on other hardware. You must also have the same ACPI Options in your hypervisor.
This must be done before you use the vmware tools to create the image.
Thanks - I assumed it had something to do with the old style bios geometry because I can boot the VM with a linux rescue disk and see what I expect, but the boot loader can't find it. What seems odd to me is that it works fine when the conversion is to a VMware server image file but not when going directly to ESXi (which I'd expect to be smarter). I haven't tried it yet, but I'll bet that I can run the converter again, using the .vmx as the source and ESXi as the target and it will work without any changes to the windows OS.
--
Well, thinking in that term it should work. Lets us know. I do know when I first tried it doing images from real hardware is when I hit the problem. VM to VM should work in theory.
John
On 4/28/2010 1:28 PM, JohnS wrote:
Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
Well for those that must have a Windows OS heres the hack:
You must go to microsoft.com search for the tools to allow that. What it does is Relax The Windows IDE Checks so the disk or image can be used as a VM or on other hardware. You must also have the same ACPI Options in your hypervisor.
This must be done before you use the vmware tools to create the image.
Thanks - I assumed it had something to do with the old style bios geometry because I can boot the VM with a linux rescue disk and see what I expect, but the boot loader can't find it. What seems odd to me is that it works fine when the conversion is to a VMware server image file but not when going directly to ESXi (which I'd expect to be smarter). I haven't tried it yet, but I'll bet that I can run the converter again, using the .vmx as the source and ESXi as the target and it will work without any changes to the windows OS.
--
Well, thinking in that term it should work. Lets us know. I do know when I first tried it doing images from real hardware is when I hit the problem. VM to VM should work in theory.
Yep - running live->image, then image->ESXi worked where the direct live->ESXi did not. I had 2 IDE based Dell machines like that (one had the hidden Dell recovery partition, one didn't) but a similar-vintage Dell SCSI worked fine with the direct conversion. I tried an assortment of mbr/boot fixups on the failing conversions but none worked - another guy poked around a little more and thought it had the bios C/H/S settings wrong in the direct conversion.
Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
Never used Server, but I use ESXi and I know what your issue is: Mass Storage Drivers, you need to make sure the Critical Device Database is populated with the driver in the destination system, such as an LSI SCSI or SAS and that that service start type is set to "boot".
Install the driver then add it to the crit dev db in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
Follow one of the necessarily existing PCI#VEN_xxxx&DEV_xxxx for syntax.
Change the Service Start Type: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nnnn
From probably 4 to 0.
http://support.microsoft.com/kb/103000
I use the LSI SAS for everything...
jlc
Ps. I think the current version of ESXi allows an ide controller to avoid this...
On 4/28/2010 1:16 PM, Joseph L. Casale wrote:
Running the VMware converter tool from an old Dell Win2k server with an IDE disk to produce an ESXi image went through the motions but the image wouldn't boot - but doing the same thing to a vmware server (v1) image file over a network share worked. Has anyone seen that before?
Never used Server, but I use ESXi and I know what your issue is: Mass Storage Drivers, you need to make sure the Critical Device Database is populated with the driver in the destination system, such as an LSI SCSI or SAS and that that service start type is set to "boot".
Install the driver then add it to the crit dev db in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
Follow one of the necessarily existing PCI#VEN_xxxx&DEV_xxxx for syntax.
Change the Service Start Type: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nnnn
From probably 4 to 0.
http://support.microsoft.com/kb/103000
I use the LSI SAS for everything...
jlc
Ps. I think the current version of ESXi allows an ide controller to avoid this...
I've seen that - and it gives a windows blue-screen. This is some other problem that doesn't even get past the bios boot loader. I did tell the converter to keep the source disk controller type - and when going to ESXi it can install vmware tools on the fly which should fix up the drivers once you get that far.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Kwan Lowe Sent: Tuesday, 27 April 2010 3:52 AM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
So that's why the management interfaces from vmware 2 appear to keep crashing!
Also, the console plugin seems to work fine in Firefox on Fedora 12, for me anyway.
On 4/26/10 4:57 PM, "Dan Irwin" dan@jackies.com.au wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Kwan Lowe Sent: Tuesday, 27 April 2010 3:52 AM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
So that's why the management interfaces from vmware 2 appear to keep crashing!
Also, the console plugin seems to work fine in Firefox on Fedora 12, for me anyway.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
The current work around is to downgrade glibc to that of 5.3, at least until the next update from VMWare comes out that should fix this issue.
On Mon, Apr 26, 2010 at 8:05 PM, Gary Greene ggreene@minervanetworks.com wrote:
On 4/26/10 4:57 PM, "Dan Irwin" dan@jackies.com.au wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Kwan Lowe Sent: Tuesday, 27 April 2010 3:52 AM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
So that's why the management interfaces from vmware 2 appear to keep crashing!
Also, the console plugin seems to work fine in Firefox on Fedora 12, for me anyway.
The current work around is to downgrade glibc to that of 5.3, at least until the next update from VMWare comes out that should fix this issue.
-- Gary L. Greene, Jr.
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
Thanks for the mantis link, it was very informative.
Cheers,
Dan
On Tue, Apr 27, 2010 at 8:49 AM, Dan Irwin dan@jackies.com.au wrote:
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
Thanks for the mantis link, it was very informative.
Cheers,
Dan _______________________________________________ CentOS mailing list CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
so many replies ... so my best option is to install VMware-server-1 ???
On Tue, Apr 27, 2010 at 8:49 AM, Dan Irwin dan@jackies.com.au wrote:
so many replies ... so my best option is to install VMware-server-1 ???
- Doesn't work on RHEL5 (only RHEL4u3 or u4?) - supported guest-OSs: similarly ancient
If it's a server, I'd go for ESX4i right away (if the hardware is supported - but if you have a decent NIC, it should not be a problem) For a workstation, go Virtual-Box, if you don't have much legacy stuff sitting around.
Regards, Rainer
rainer@ultra-secure.de wrote:
On Tue, Apr 27, 2010 at 8:49 AM, Dan Irwin dan@jackies.com.au wrote:
so many replies ... so my best option is to install VMware-server-1 ???
- Doesn't work on RHEL5 (only RHEL4u3 or u4?)
- supported guest-OSs: similarly ancient
I have some VMware-server 1.x versions running under Centos5.4 - and have Centos 5.4 running as a guest. I haven't had much trouble with it other than vmware-config.pl having to recompile the kernel module after every update.
If it's a server, I'd go for ESX4i right away (if the hardware is supported - but if you have a decent NIC, it should not be a problem)
Have to agree with that - ESXi is better, but then you have to run everything on the guests. Where I'm running Server the host also runs some apps.
For a workstation, go Virtual-Box, if you don't have much legacy stuff sitting around.
VMware Player might also be a reasonable choice if you are running things locally and always want the console attached to the session.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Brian Mathis Sent: Monday, April 26, 2010 7:06 PM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
On Mon, Apr 26, 2010 at 8:05 PM, Gary Greene ggreene@minervanetworks.com wrote:
On 4/26/10 4:57 PM, "Dan Irwin" dan@jackies.com.au wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Kwan Lowe Sent: Tuesday, 27 April 2010 3:52 AM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
There's the glibc issue that's still unresolved. There's another issue with using Firefox as the admin client. It *might* let you in, but the console plugin doesn't appear to be working again. Only client that works for me is InternetExploder.
So that's why the management interfaces from vmware 2 appear to keep crashing!
Also, the console plugin seems to work fine in Firefox on Fedora 12, for me anyway.
The current work around is to downgrade glibc to that of 5.3, at least until the next update from VMWare comes out that should fix this issue.
-- Gary L. Greene, Jr.
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine.
On 4/27/2010 10:29 AM, Gary Greene wrote:
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine.
Does anyone else think it is extremely strange that Red Hat introduced an incompatible base library change late in the life of their enterprise OS? Or that VMware hasn't followed with a matching change in subsequent updates? I don't get it.
Les Mikesell wrote:
Does anyone else think it is extremely strange that Red Hat introduced an incompatible base library change late in the life of their enterprise OS? Or that VMware hasn't followed with a matching change in subsequent updates? I don't get it
VMware appears to be intentionally slow-motion killing their VMware Server product in favor of ESX/ESXi. They declined to publish needed security updates for Server in the latest round and if you check the lifecycle support web page they say "VMware Server was declared End Of Availability on January 2010. Support will be limited to Technical Guidance for the duration of the support term." They also are not offering support contracts for it as far as I can see.
I wouldn't count on any meaningful updates for it.
On 4/27/2010 11:51 AM, Benjamin Franz wrote:
Les Mikesell wrote:
Does anyone else think it is extremely strange that Red Hat introduced an incompatible base library change late in the life of their enterprise OS? Or that VMware hasn't followed with a matching change in subsequent updates? I don't get it
VMware appears to be intentionally slow-motion killing their VMware Server product in favor of ESX/ESXi. They declined to publish needed security updates for Server in the latest round and if you check the lifecycle support web page they say "VMware Server was declared End Of Availability on January 2010. Support will be limited to Technical Guidance for the duration of the support term." They also are not offering support contracts for it as far as I can see.
I wouldn't count on any meaningful updates for it.
Yes, but that doesn't explain Red Hat releasing an incompatible library update in the first place when nearly the entire reason for using their enterprise product or things based on it is that they had a reputation for not breaking things with updates and they used to be good at it.
On Tue, Apr 27, 2010 at 12:51 PM, Benjamin Franz jfranz@freerun.com wrote:
Les Mikesell wrote:
Does anyone else think it is extremely strange that Red Hat introduced an incompatible base library change late in the life of their enterprise OS? Or that VMware hasn't followed with a matching change in subsequent updates? I don't get it
VMware appears to be intentionally slow-motion killing their VMware Server product in favor of ESX/ESXi. They declined to publish needed security updates for Server in the latest round and if you check the lifecycle support web page they say "VMware Server was declared End Of Availability on January 2010. Support will be limited to Technical Guidance for the duration of the support term." They also are not offering support contracts for it as far as I can see.
I wouldn't count on any meaningful updates for it.
-- Benjamin Franz
According to the VMware support page (http://www.vmware.com/support/policies/lifecycle/general/), for VMware Server 2.0 the end of General Support is 2011/06/30.
I agree that they are exceedingly slow on updates, but it'll still be around for a while. I'm sure a new version will then come out, as they still have to compete with other free offerings, and it's a nice entry-level solution where people will eventually upgrade to a paid version.
Brian Mathis wrote:
On Tue, Apr 27, 2010 at 12:51 PM, Benjamin Franz jfranz@freerun.com wrote:
VMware appears to be intentionally slow-motion killing their VMware Server product in favor of ESX/ESXi. They declined to publish needed security updates for Server in the latest round and if you check the lifecycle support web page they say "VMware Server was declared End Of Availability on January 2010. Support will be limited to Technical Guidance for the duration of the support term." They also are not offering support contracts for it as far as I can see.
I wouldn't count on any meaningful updates for it.
According to the VMware support page (http://www.vmware.com/support/policies/lifecycle/general/), for VMware Server 2.0 the end of General Support is 2011/06/30.
I agree that they are exceedingly slow on updates, but it'll still be around for a while. I'm sure a new version will then come out, as they still have to compete with other free offerings, and it's a nice entry-level solution where people will eventually upgrade to a paid version.
There is conflicting information on that page. In one place it says that General Support will continue to 2011/06/30, in another it states that "VMware Server was declared End Of Availability on January 2010. Support will be limited to Technical Guidance for the duration of the support term."
As I remember also seeing a statement to the effect that it was being switched to 'Technical Guidance' only support in the forums there, I would say that *although* it is still technically in "General Support" they are not going to provide anything more than technical guidance for it. The lack of security fixes for it in the latest round of updates as well as the fact that it has severe problems such as the 'creeping load' that have been present and reported *since the 2.0 beta release* and the glibc incompatibility which has been known since the 2.0.1 release indicates they are absolutely not interested in supporting it.
"It's an ex-parrot."
As for competing with other free offerings: That is what ESXi is for now.
on 4-27-2010 8:46 AM Les Mikesell spake the following:
On 4/27/2010 10:29 AM, Gary Greene wrote:
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine.
Does anyone else think it is extremely strange that Red Hat introduced an incompatible base library change late in the life of their enterprise OS? Or that VMware hasn't followed with a matching change in subsequent updates? I don't get it.
RedHat will post a change like that if the needed fixes cannot be backported for some reason... It is rare, but does happen
On 4/27/2010 2:48 PM, Scott Silva wrote:
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine.
Does anyone else think it is extremely strange that Red Hat introduced an incompatible base library change late in the life of their enterprise OS? Or that VMware hasn't followed with a matching change in subsequent updates? I don't get it.
RedHat will post a change like that if the needed fixes cannot be backported for some reason... It is rare, but does happen
The breakage seems to be RH/Centos specific. Does no one else use that libc version?
On Tue, Apr 27, 2010 at 11:29 AM, Gary Greene ggreene@minervanetworks.com wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Brian Mathis Sent: Monday, April 26, 2010 7:06 PM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
[...]
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine.
Seeing as glibc is one of the most used and most critical libraries in the system, downgrading to an older version of it most certainly has the effect of downgrading almost every package on the system.
I'm not talking about whatever OS version (5.3, 5.4, etc...) you think you're running (that not a real thing anyway as packages all exist at different versions). If there's an update to glibc that's security related, by downgrading the system-wide version you're reintroducing the problem to all packages on the system. This is why it's better to isolate the downgraded library to just VMware until it gets fixed to use the updated
The version number of any package or OS is arbitrary -- you need to understand the effect of what you're doing beyond the version number.
On 4/27/10 9:53 AM, "Brian Mathis" brian.mathis@gmail.com wrote:
On Tue, Apr 27, 2010 at 11:29 AM, Gary Greene ggreene@minervanetworks.com wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Brian Mathis Sent: Monday, April 26, 2010 7:06 PM To: CentOS mailing list Subject: Re: [CentOS] vmware-server-console not installed
[...]
You don't need to downgrade for the whole OS, you can just do it for VMware. See the procedure in the first comment in this bug http://bugs.centos.org/view.php?id=3884. I have done that and it works fine. Just remember that if you update vmware, the edits to vmware-hostd will be undone, so you need to redo them.
I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine.
Seeing as glibc is one of the most used and most critical libraries in the system, downgrading to an older version of it most certainly has the effect of downgrading almost every package on the system.
I'm not talking about whatever OS version (5.3, 5.4, etc...) you think you're running (that not a real thing anyway as packages all exist at different versions). If there's an update to glibc that's security related, by downgrading the system-wide version you're reintroducing the problem to all packages on the system. This is why it's better to isolate the downgraded library to just VMware until it gets fixed to use the updated
The version number of any package or OS is arbitrary -- you need to understand the effect of what you're doing beyond the version number. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Please don't quote to me the "full effect" mantra you're going on about here, I don't need treated as though I'm some fresh college kid that only started using Linux. I've been doing Linux systems level programming and distribution development for a VERY long time, and have a fairly extensive knowledge about what _can_ and _cannot_ break a box with regards to downgrading core libraries.
The particular packages I rolled back to are the last set of packages for 5.3. The vulnerabilities that were fixed in GLibC for 5.4 were not too damaging as they require _local_ access anyway, and since NO VM host should ever be internet accessible (I did not say that the guest OS cannot be, only the host), this should be fine for now.
Based off the other emails in this thread, it is worrying to me that VMWare decided to drop the VMWare Server product. However, from a resources perspective, I can understand as ESXi shares much more code with current products than VMWare Server did.
On Mon, Apr 26, 2010 at 7:57 PM, Dan Irwin dan@jackies.com.au wrote:
So that's why the management interfaces from vmware 2 appear to keep crashing!
Also, the console plugin seems to work fine in Firefox on Fedora 12, for me anyway.
Firefox 3.5.x appears to be working. F3.6.x has some issues.
Agnello George wrote:
I had installed the vmware server ( VMware-server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
The console app is a Firefox plugin, but I extract the app and run it separately and find that solution (hack?) much better.
From memory, here is how you do that: 1. Get a copy of vmware-vmrc-linux-x86.xpi (mine was in /usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.16/webapps/ui/plugin/vmware-vmrc-linux-x86.xpi) 2. Rename the file to vmware-vmrc-linux-x86.xpi.zip 3. Unzip the file
Now run vmware-vmrc or pass some info like capitalized below: vmware-vmrc -h HOST:PORT -u USER -p PASSWORD
From memory, here is how you do that:
- Get a copy of vmware-vmrc-linux-x86.xpi (mine was in
/usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.16/webapps/u
i/plugin/vmware-vmrc-linux-x86.xpi)
- Rename the file to vmware-vmrc-linux-x86.xpi.zip
- Unzip the file
Now run vmware-vmrc or pass some info like capitalized below: vmware-vmrc -h HOST:PORT -u USER -p PASSWORD
That's really cool, and probably way more elegant than using the web browser plugin.
Cheers,
Dan
On Mon, Apr 26, 2010 at 8:18 PM, John Thomas gmane-2006-04-16@jt-socal.com wrote:
Agnello George wrote:
I had installed the vmware server ( VMware-server-2.0.1-156745.i386 ) on my CentOS 5 box how ever i am not able to to find the command vmware-server-console . Do i need to install that RPM separately .
The console app is a Firefox plugin, but I extract the app and run it separately and find that solution (hack?) much better.
From memory, here is how you do that: 1. Get a copy of vmware-vmrc-linux-x86.xpi (mine was in /usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.16/webapps/ui/plugin/vmware-vmrc-linux-x86.xpi) 2. Rename the file to vmware-vmrc-linux-x86.xpi.zip 3. Unzip the file
Now run vmware-vmrc or pass some info like capitalized below: vmware-vmrc -h HOST:PORT -u USER -p PASSWORD
:D
Awesome!!! Just tried it and it works wonderfully. Now I don't need to boot into that XP partition anymore... Thank you!
-
Agnello George -
Benjamin Franz -
Brian Mathis -
Dan Irwin -
Gary Greene -
John Thomas -
JohnS -
Joseph L. Casale -
Kwan Lowe -
Les Mikesell -
Rainer Duffner -
rainer＠ultra-secure.de
-
Scott Silva