Maybe I just like trying to do things the hard way, but I have installed loaded and playing with running OpenVZ inside of VMware workstation.
Here is the proof:
This isn’t for the faint of heart, but it was much easier then the last time I installed Openvz, completly over SSH. Nothing is worse then having a box reboot, and not get back up remotely. I was stuck having it reloaded a few times, but finally got it running. With VMware, the only issue I had was forgetting to choose the correct kernel on reboot. It was simple, easy, and ran pretty well. If you have any particular questions I’m sure willing to try and answer them.
March 26th, 2007 at 4:29 pm
Hi, I have been doing this too, inside VM workstation.
I would like to discuss some issues with you if you have time to email me.
Thanks,
Peter
May 11th, 2007 at 12:20 am
I just came across openvz today, im really interested in what you guys are doing.
My scenario is this.
2 servers running CentOS 5, with VMWare Server and Windows 2003 VMs running Exchange.
DRBD and heartbeat being used.
Im using scripts to start up the other vmware instance manually, when the heartbeat detects a fault with the primary machine.
Its currently in a lab now, but soon will be in production.
I’d be interested in knowing, what kind of performance degregation there is in using OpenVZ and running VMWare Server.. If there isnt, for me. This would be a better choice.
October 14th, 2007 at 3:58 pm
I also tried to use OpenVZ in Vmware and got everything up and running smoothly. However there´s one problem I can´t solve. Pinging a OpenVZ-VE inside a Vmware-VE does work pretty fine, but pinging the OpenVZ-VE from the Host or another Vmware-VE doesnt work. Im using bridged-Networking. By the way I can ping all Vmware-VEs (from Host to VE or VE to VE). Do you know how I can solve this problem?
Regards
Norman