Hi,
I know this has been spoken about but I am hoping someone can give me some further help into deciding which is the best for us, and limitations of each one.
For me the fact there is no boot console in openvz, and no iSCSI support really makes me lean towards KVM.
However we are running this as our PBX server and therefore throughput and hardware timing is crucial. Yes you can get around hardware timing issues with KVM via paravirtualisation, but how about the throughput. Is it really noticeably faster for linux hosts under openVZ compared with KVM?
Is there any way at all to get around the iSCSI and high availability with openVZ or is it simply no - use KVM if you require that?
I mean can you not just create a mount point for the iSCSI target in the host os and then sym link the openVZ folders to there?
And any way to get the boot console side of things working with openvz or just have to manually go through the logs for debugging etc?
Cheers and thanks in advance for any help advice etc?
I know this has been spoken about but I am hoping someone can give me some further help into deciding which is the best for us, and limitations of each one.
For me the fact there is no boot console in openvz, and no iSCSI support really makes me lean towards KVM.
However we are running this as our PBX server and therefore throughput and hardware timing is crucial. Yes you can get around hardware timing issues with KVM via paravirtualisation, but how about the throughput. Is it really noticeably faster for linux hosts under openVZ compared with KVM?
Is there any way at all to get around the iSCSI and high availability with openVZ or is it simply no - use KVM if you require that?
I mean can you not just create a mount point for the iSCSI target in the host os and then sym link the openVZ folders to there?
And any way to get the boot console side of things working with openvz or just have to manually go through the logs for debugging etc?
Cheers and thanks in advance for any help advice etc?