From: Reindl H. <h.r...@th...> - 2012-05-17 21:57:52
|
Am 17.05.2012 23:40, schrieb Dmitry Torokhov: > On Thursday, May 17, 2012 07:48:35 PM Reindl Harald wrote: >> but it is since a long time in the upstream linux kernel >> as "vmw_balloon" like also "vmxnet3" and "vmw_pvscsi" >> >> hopefully sometimes "vsock", "vmci" > > We are presently working on getting VMCI (and later vsock) upstream. cool, what is exactly the need of "vsock" "vmci" is AFAIK used for "VMware HA" and the most important thing beside vmxnet3 in vSphere custers >> and "vmsync" will also be included > > vmsync will not be upstreamed since newer kernel provide FIFREEZE/FITHAW > functionality needed to quiesce the filesystems in order to perform consistent > backup. If VMware Tools detect that kernel supports these ioctls then vmsync > driver is not used. if i understand you right i can thow away "kernel/drivers/misc/vmsync.ko" in my open-vm-tools packages on Fedora with 3.3.x kernels and VMware DataRecovery will still work? |