This bug was fixed in the package open-vm-tools -
2010.04.25-253928-2+ubuntu2
---
open-vm-tools (2010.04.25-253928-2+ubuntu2) maverick; urgency=low
* Add 03-vmxnet.patch and 04-vsock.patch.
Fixes building on Maverick kernels (LP: #598542)
-- Nate MuenchMon, 19 Jul 2010 18:0
Nate: Hardcoding this to /mnt/hgfs seems wrong. /mnt is not generally
used by packages. However, I have zero knowledge of this package :)
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, whi
One thing I've noticed with the new upstream release, it's that even
with the config coming from Debian, the existing vmxnet, and my adjusted
vsock patch. It appears we lose the vmci/vmhgfs modules which means no
shared folders. Which I want to make a note of.
After you install open-vm-tools on
Any news on that latest PPA Nate?Or on an Open VM Tools upgrade? Using
GRUB_GFXPAYLOAD_LINUX=text in my GRUB Configuration now, which sort of
works. Started a thread here
http://ubuntuforums.org/showthread.php?t=1531620 .
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/59
** Branch linked: lp:~n-muench/ubuntu/maverick/open-vm-tools/open-vm-
tools-fix-598542
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Branch linked: lp:~n-muench/ubuntu/maverick/open-vm-tools/open-vm-
tools-fix-598542
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Branch linked: lp:~n-muench/ubuntu/maverick/open-vm-tools/open-vm-
tools-fix-598542
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Branch linked: lp:~n-muench/ubuntu/maverick/open-vm-tools/open-vm-
tools-fix-598542
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
My Build went successfully with some issues.
I manually installed the deb files from the build, but I got errors
saying I had better modules installed (or something). I completely
uninstalled the modules, rebooted, and manually installed everything
again, it went fine.
So because of that error I'
I've added an updated patch for vsock. Almost everything from the old
vsock patch was added in the new release (the June 16th one). The only
needed to add "compat_" to section that says "sk_sleep(sk)" The VMXNET
patch is still needed.
So Noel, I needed your input on this new vsock patch.
I'm a
** Tags added: patch
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
I have taken the liberty to rebuild open-vm-tools package available in
Maverick, this time I included the patches available in this report.
Launchpad's Build was successful and the building of the modules using
module assistant was also successful. I've added (or copied, from one of
my other PPAs,
I agree, Evan. Anyone who is running into the problem now can grab my
patches, which apply to either the current or newer upstream drops. And
I also agree that I've done a quick, version specific, patch without
doing the extra #if defined work that should be done in the "real" code.
f there's a
Note that it's not impossible for Ubuntu to pull the newer upstream
release of open-vm-tools without Debian doing so first, it's just not
how packages typically get maintained. If the upstream version solved
the bug, I'd have no qualms pulling it in in advance of Debian.
I'd prefer to wait for the
And similarly for vmxnet, you may need to manually change the hardware
to test the vmxnet driver. The default is e1000, but after changing
that, I can verify that the fixed vmxnet driver is working.
So we can get the latest upstream code, apply my patch for vmxnet
(already submitted upstream), an
Ignore the noise regarding vmxnet3: http://sanbarrow.com/vmxnet3.html
It is working fine after changing the virtual h/w manually.
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Yes, the new tools appear to build and work, with the vmxnet patch (mind
you, neither vmxnet driver is providing a connection, so we use e1000).
vmsync 3992 0
vsock 44947 0
vmhgfs 60011 0
vmci 47215 2 vsock,vmhgfs
vmware_ba
I do need to correct, as an aside, that vmxnet3 is not coming from open-
vm-tools. It is now provided with the kernel (still does not work,
though).
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubun
The new build still have the same failure in vmxnet:
Using 2.6.x kernel build system.
make[2]: Entering directory
`/home/noel/open-vm-tools-2010.06.16-268169/modules/linux/vmxnet'
make -C /lib/modules/2.6.35-5-generic/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. \
MODULEBUILDDIR=/home
Not, yet, Evan. I was just going to post that there is a new upstream
version (
http://sourceforge.net/mailarchive/message.php?msg_name=4C1BE732.1090903%40vmware.com),
but haven't pulled and checked it yet. Doing so now.
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/5
Noel: There was a recent new upstream release of open-vm-tools (open-vm-
tools-2010.06.16-268169, available at http://sourceforge.net/projects
/open-vm-tools/files/) that Debian (and therefore Ubuntu) hasn't picked
up yet. I was hoping to pull a package together for testing, but have
you checked to
Also reported at http://communities.vmware.com/thread/273917
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Second patch to fix vsock. Corrects all references of
somevar->sk_compat_sleep to compat_sk_sleep(somevar)
** Attachment added: "vsock.patch"
http://launchpadlibrarian.net/50911407/patch-2
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug n
Patch to allow vmxnet to compile. vmxnet still doesn't appear to *work*
(AMD64), but I don't believe that is the fault of this patch. Both
vmxnet and vmxnet3 load, but neither provide a usable network connection
when restarting the network layer. The same is true of the official
vmxnet3 driver p
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50908577/Dependencies.txt
--
Open VM Tools FTBS on Maverick 2.6.35
https://bugs.launchpad.net/bugs/598542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
25 matches
Mail list logo
