Re: [CentOS] CentOS 5.2 VMI support
On Thu, 2008-07-10 at 17:31 -0700, nate wrote: No it requires changes to the kernel itself, changes which I don't think Red Hat will introduce in a minor release as their current VM stuff is Xen based which has it's own paravirtualization support in the existing kernel(pre VMI). I read that Red Hat is moving towards KVM though, I don't have any knowledge on that project, maybe it uses VMI as well. There's a big splash on Redhat's home page. Take a look at http://www.ovirt.org. That uses libvirt. Dave ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 5.2 VMI support
I'm using VMWare Server 2 RC1 to on top of CentOS 5.2 x86_64 running a CentOS 5.2 i386 guest. I have enabled VMI in VMware, so I guess it won't let me install if VMI wasn't available in the kernel? How do I know whether VMI is supported/enabled and what performance benefits can I expect from it? I'm still not getting full hard drive speeds (only getting about 1/3 when using hdparm -t ). Russ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.2 VMI support
Ruslan Sivak wrote: I'm using VMWare Server 2 RC1 to on top of CentOS 5.2 x86_64 running a CentOS 5.2 i386 guest. I have enabled VMI in VMware, so I guess it won't let me install if VMI wasn't available in the kernel? How do I know whether VMI is supported/enabled and what performance benefits can I expect from it? I'm still not getting full hard drive speeds (only getting about 1/3 when using hdparm -t ). I don't believe it is supported in CentOS 5.x. I am using Fedora Core 8 for VMI support. [EMAIL PROTECTED]:~]# dmesg | grep -i vmi VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0 vmi: registering clock event vmi-timer. mult=7809995 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=1862048 Time: vmi-timer clocksource has been installed. I suspect it will be in RHEL/CentOS 6.x nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.2 VMI support
nate wrote: Ruslan Sivak wrote: I'm using VMWare Server 2 RC1 to on top of CentOS 5.2 x86_64 running a CentOS 5.2 i386 guest. I have enabled VMI in VMware, so I guess it won't let me install if VMI wasn't available in the kernel? How do I know whether VMI is supported/enabled and what performance benefits can I expect from it? I'm still not getting full hard drive speeds (only getting about 1/3 when using hdparm -t ). I don't believe it is supported in CentOS 5.x. I am using Fedora Core 8 for VMI support. [EMAIL PROTECTED]:~]# dmesg | grep -i vmi VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0 vmi: registering clock event vmi-timer. mult=7809995 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=1862048 Time: vmi-timer clocksource has been installed. I suspect it will be in RHEL/CentOS 6.x nate _ Does it just require a kernel recompile? Is there maybe one available somewhere? Would it give me improved disk access speed? Russ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.2 VMI support
Ruslan Sivak wrote: Does it just require a kernel recompile? Is there maybe one available somewhere? No it requires changes to the kernel itself, changes which I don't think Red Hat will introduce in a minor release as their current VM stuff is Xen based which has it's own paravirtualization support in the existing kernel(pre VMI). I read that Red Hat is moving towards KVM though, I don't have any knowledge on that project, maybe it uses VMI as well. Would it give me improved disk access speed? I doubt it. I'm planning on using it mainly so I can run a couple of NTP servers in VMs. Even though it's still not officially supported my experience shows that NTP *will never sync* in VMWare with normal virtualization. But with VMI/paravirtualization I've had a ntp daemon synced for weeks so far. I don't plan to use VMI for anything other then a couple bare bones VMs to run NTP. Then the rest of the VMs will run ntpdate every minute against them, and the non VMs will run ntp daemons and sync with them. The internal vmware time sync(at least in ESX) doesn't work too well in my experience so I just turn it off and use ntpdate instead. Disk access speed is limited to the speed of the I/O subsystem. VMware has recently demonstrated a ESX system being able to sustain 100,000 I/Os per second (maxing out ~500 15k RPM disks), and that wasn't using paravirtualization. If you can get 100k IOPS with normal virtualization... nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
