Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have an VMWare ESX Server v3.5 with a few virtualized Debian Lenny VMs (kernel 2.6.22 with vmi) running Apache Tomcat 5.5. I enabled paravirtualization, and Disk IO increased from about 240MB/s to 380MB/s, making me a happy admin.

The problem now is that my apache tomcat becomes deadlocked during startup, running with 200% CPU (I have 2 CPUS assigned to the VM), and don't know how to get both: A stable system and a fast system.

I somewhere heared that paravirtualization is legacy anyway and won't be available on newer ESX servers. Is there a replacement for this seemingly performance-improving option, or is it discontinued becauses it is just unstable? What is the state of paravirtualization? Should I ignore it completely?

Thanks for all answers in advance.

share|improve this question

3 Answers 3

Para-virtualization is not going anywhere. The future direction of all Hypervisor platforms is to combine the benefits of hardware virtualization (for both CPU's and IO subsystems) with para-virtualization where that is possible. VMware now have extensive support for para-virtualized drivers for most guests, Hyper-V has always used paravirtualization extensively as has Xen.

Given that you are doing this on ESX 3.5 I'd suggest that you test the configuration on ESX(i) 4.1 and see if the problem has been resolved there.

Paravirtualization involves some trade offs - a key one is that there are components (at the driver\kernel level) re-written to enable the Hypervisor to more directly manage some aspect of the Guest's behaviour but this also runs the risk of introducing bugs, and it looks like you may have found one.

share|improve this answer
2  
I don't know about the other hypervisor vendors, but VMware is in the process of discontinuing their VMI paravirtualization stuff. See my answer. –  ThatGraemeGuy Jan 11 '11 at 11:18
    
Well you learn something every day. :) The elimination of VMI makes sense though as it is a lot harder to support than paravirtualized driver layers, which I'm pretty sure is not going anywhere. Given that the question was about VMI though, I'll take any downvotes with good grace. –  Helvick Jan 11 '11 at 11:35
1  
+1. Paravirt is not going away anytime soon. It's not just because VMWare is dropping it that it's going away. –  Antoine Benkemoun Jan 11 '11 at 11:54
    
@Antoine: The concept of paravirtualization may not be going away, but the question relates to VMware implementation (VMI), which is most certainly going away. –  ThatGraemeGuy Jan 12 '11 at 12:06
    
You are right :-) –  Antoine Benkemoun Jan 12 '11 at 13:10

In respect to VMware, yes they discontinue VMI support, however if you noticed they introduced paravirtualized i/o and network drivers in ESX(i) v4.x. So, they continue to use paravirtualization to improve performance, they simply do it in a different way.

share|improve this answer
    
Yes I agree with you Dmitri, in all of your deployed VM if possible use Paravirtualization virtual hardware for best performance. –  Albert Widjaja Feb 22 '11 at 1:41

VMware's VMI is on the way out.

Here's the official article: Migrating VMI-enabled virtual machines to platforms that do not support VMI.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.