From: Reindl H. <h.r...@th...> - 2011-11-23 14:56:01
Attachments:
signature.asc
|
hi currently there seems to be no way to get open-vm-tools compiled with recent 2.6.41-kernels of Fedora 15 and rpmfusion seems to have totally dropped there packages F14 support is ending this month so in december users are forced updating to F15 which is a disaster without vmware-tools on recent ESXi-Envirnoemnts with active HA is there any plan to get this solved? ________________ CAUTION: 2.6.40 / 2.6.41 are the 3.0/3.1 kernels for fedora i patched the VMware-Workstation 8.0.1 module sources and after that the modules where compiled, the same snippet is in theopen-vm-tools source-package, not sure if this is the only issue here, i will try to get the last version through rpmbuild, but totally unsure how to handle the kernel-modules [root@srv-rhsoft:/usr/lib/vmware/modules/source]$ cat vmware-2.6.41.patch --- vmnet-only/compat_netdevice.h 2011-11-14 08:16:55.000000000 +0100 +++ vmnet-only-patched/compat_netdevice.h 2011-11-20 14:11:04.168217852 +0100 @@ -104,7 +104,7 @@ int size = sizeof *dev + priv_size; /* - * The name is dynamically allocated before 2.4.0, but + * The name is dynamically allocated before 2.4.0, but * is an embedded array in later kernels. */ #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 4, 0) @@ -161,7 +161,7 @@ # if LINUX_VERSION_CODE < KERNEL_VERSION(2, 4, 0) dev->name = (char*)(dev + 1); # endif - strcpy(dev->name, mask); + strcpy(dev->name, mask); } return dev; } @@ -183,7 +183,7 @@ * so let's add back ones we care about. */ #if !defined(HAVE_NET_DEVICE_OPS) && \ - LINUX_VERSION_CODE >= KERNEL_VERSION(3, 0, 0) + LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 41) # define HAVE_NET_DEVICE_OPS 1 #endif |
From: Marcelo V. <mv...@vm...> - 2011-11-23 18:58:30
|
Hi Reindl, I have an update to 8.8.x open-vm-tools that should provide a fix for that; but it will probably need adjustments since Fedora is messing with the kernel version numbers. I'm planning to post the update later today. On 11/23/2011 06:55 AM, Reindl Harald wrote: > hi > > currently there seems to be no way to get open-vm-tools compiled with > recent 2.6.41-kernels of Fedora 15 and rpmfusion seems to have totally > dropped there packages -- - Marcelo |
From: Reindl H. <h.r...@th...> - 2011-11-24 11:09:27
Attachments:
signature.asc
|
why not patching the sources? there is nothing messing in fedora devel-kernel 2.6.40 was renamed to 3.0 from linux so fedoras 2.6.40 is 3.0 and fedoras 2.6.41 is 3.1 and since upstream > 2.6.39 was never released this is safe the original comment above my changed line speaks about 3.1 and in the source is KERNEL_VERSION(3, 0, 0), wrong comment or bug, anyways 2.6-41 is correct for fedora [root@buildserver64:~]$ cat /rpmbuild/SOURCES/open-vm-tools-2.6.41.patch --- open-vm-tools-original/modules/linux/shared/compat_netdevice.h 2011-10-27 20:57:11.000000000 +0200 +++ open-vm-tools-patched/modules/linux/shared/compat_netdevice.h 2011-11-23 16:57:55.814275389 +0100 @@ -184,7 +184,7 @@ * so let's add back ones we care about. */ #if !defined(HAVE_NET_DEVICE_OPS) && \ - LINUX_VERSION_CODE >= KERNEL_VERSION(3, 0, 0) + LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 41) # define HAVE_NET_DEVICE_OPS 1 #endif Am 23.11.2011 19:58, schrieb Marcelo Vanzin: > Hi Reindl, > > I have an update to 8.8.x open-vm-tools that should provide a fix for that; > but it will probably need adjustments since Fedora is messing with the kernel > version numbers. > > I'm planning to post the update later today. > > On 11/23/2011 06:55 AM, Reindl Harald wrote: >> hi >> >> currently there seems to be no way to get open-vm-tools compiled with >> recent 2.6.41-kernels of Fedora 15 and rpmfusion seems to have totally >> dropped there packages -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm |
From: Marcelo V. <mv...@vm...> - 2011-11-28 18:09:18
|
On 11/24/2011 03:09 AM, Reindl Harald wrote: > why not patching the sources? That's a side-effect of how VMware adds support for newer distros. Right now I don't believe brand new distros (or recent distros that have had kernel updates) are officially supported by the current released products; that reflects in open-vm-tools, since we sync the stable branch to those stable releases. If you look at the master branch a few of these issues might have been fixed already. As our QA starts testing new distros / updates to existing distros, we'll fix things in the development branch, and in some cases the stable branch will pick up those changes. That will generally come out after some delay, since update releases have to go through our internal development and QA cycle. Sometimes, while preparing open-vm-tools updates, I'll cherry-pick a few changes from development that I consider "safe". But I'm not comfortable doing that for all types of changes. > there is nothing messing in fedora devel-kernel 2.6.40 was renamed to 3.0 > from linux so fedoras 2.6.40 is 3.0 and fedoras 2.6.41 is 3.1 If, as your diff suggests, Fedora is changing the LINUX_VERSION_CODE macro, they are messing with the version number. So our checks, which are made for the official kernel versions, would have to be adjusted for Fedora's "unofficial version" kernels. That will happen once that Fedora / kernel combination becomes officially supported by VMware, but it doesn't seem to be the case now. Until then, you may keep your private patches, or also monitor changes to the master branch looking for fixes for newer kernels that might affect your Fedora kernel. -- - Marcelo |
From: Reindl H. <h.r...@th...> - 2011-11-28 19:21:33
Attachments:
signature.asc
|
Am 28.11.2011 19:09, schrieb Marcelo Vanzin: > On 11/24/2011 03:09 AM, Reindl Harald wrote: > If you look at the master branch a few of these issues might have been fixed > already. As our QA starts testing new distros / updates to existing distros, > we'll fix things in the development branch, and in some cases the stable > branch will pick up those changes. i took the snapshot open-vm-tools-2011.11.20-535097.tar.gz > If, as your diff suggests, Fedora is changing the LINUX_VERSION_CODE macro, > they are messing with the version number. So our checks, which are made for > the official kernel versions, would have to be adjusted for Fedora's > "unofficial version" kernels it's ok for me, this is really the only line to change i tested vmware-data-recovery (backup, probe-restore, real restore) as also HA with forced kernel crash, all fine * echo 1 > /proc/sys/kernel/sysrq * echo c > /proc/sysrq-trigger so i am satisfied with my "private" patch and glad to have provided here since others may neeed it tooo |