On Thu, 2008-06-26 at 06:04 -0700, Akemi Yagi wrote:
This bug report: http://bugs.centos.org/view.php?id=2189 seems to suggest
clocksource=pit and divider=10 will crash kernels and I did not see it's
fixed in the release notes.
Right, so, if you do not need the clocksource= option, you
On Mon, 2008-06-30 at 16:32 +0200, Tru Huynh wrote:
kernel-vm are a workaround for the current issue on the regular
kernel.
No one forces you to use them :)
But if I do use them, am I able to avoid any kernel cmdline params games
(like clock=, noapic, etc etc)?
It's sounding a bit like every
All,
I've updated the open-vm-tools packages that have been floating around
to the latest release - 4/25/2010 - for those that are interested.
There is quite a bit of new additions/changes over the past year such as
the addition of a fuse driver for vmblock devices, vmxnet3, pvscsi, etc.
SRPMS
On 05/19/2010 09:15 AM, compdoc wrote:
Are these tools useful for KVM?
I don't believe so. KVM/QEMU would be using the virtio based modules
rather than the VMware vmxnet3/pvscsi stuff.
___
CentOS-virt mailing list
CentOS-virt@centos.org
On 05/19/2010 09:30 AM, compdoc wrote:
I think iSCSI is easier to implement and is certainly fast, but I'm unclear
about the number of iSCSI clients that can access a volume (iSCSI target) at
the same time. So, I use it with only one client at a time.
iSCSI does allow multiple initiators to
