Is there any known issues when trying to run CentOS (x86 or x64) on a fresh install of vmware 4.1? Details as to why I am asking are here in the CentOS forums: https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&order=D...

Vmware, no. I have been using it for many release including yours for some time and I only use x64. The only difference is the hardware, that's a newer box than I have at any location and its amd, mine are all Intel. ESXi doesn't emulate a consistent proc, it passes it in. If the underlying hardware is problematic so is the vm. I didn't bother to check, but I would assume that platform is supported for RHEL 5 but possibly the combination is bad.

My only two suggestions:

1. I wouldn't run asterisk in a vm if my life depended on it, tried many times and it always came around sooner or later to remind me it didn't want that malarkey.

2. Slap your 299.00 down on a single incidence at vmware, you'll almost feel ripped off on how fast you will likely get the right answer. That's a big company dealing w/ very elaborate and large setups, someone will have been there and done that, I can assure you.

Email back your reso, I am curious to know. jlc

On Sun, 2010-10-24 at 16:03 -0500, Drew Kollasch wrote:

Is there any known issues when trying to run CentOS (x86 or x64) on a fresh install of vmware 4.1?

Details as to why I am asking are here in the CentOS forums: https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&order=D...

Thanks! -Drew

Reading that thread...

Is the kernel panic during install or during first boot?

Assuming first boot, there are a few options. 1. Use an older install disc. This was the suggested resolution. 2. Use a kickstart file to update during install (%post), before first boot. 3. Use the install disc as a rescue disc to update the system after install, before first boot. I like this option for the simplicity in a single instance install. 4. Setup a local repository, with updates, and install from there using the net install disc. I like this option for multiple installs. I'm heading in this direction except with PXE instead of physical discs.

If while booting the install disc, 1. See option 1 in previous section. 2. Create your own updated install disc. This option has very little to recommend it as it is significant effort for little gain. The pro is that you will have a very good understanding of how the install disc is put together.

Also, that issue appears to be AMD related? If you have another virt server that uses Intel, you could create the VM, install, update and then move it.

All in all, using a CentOS 5.4 install disc and upgrading seems to be the simplest for your one off. That should be possible with AsteriskNow if you use an older disc of theirs.

As far as Asterisk goes, I don't restrict myself to VoIP, due to 911 requirements. In the event of power failure or Internet issue, my POTS line works more reliably. By having a UPS on my Asterisk system and PoE for my phones in conjunction with a POTS line, I have a system that is more survivable during external issues. Since I run independent VoIP and data networks, it makes sense on several levels to maintain my primary Asterisk system on bare metal. Though, in the event of failure, I have no problem running the backup on my virt server. I use Elastix, which is also CentOS 5 based. I modify the kickstart file to do updates at the end of %post. I use PXE, but it should be straightforward to modify the disc image before burning.