open-vm-dkms is unable to build drivers on Precise currently for both
the stock 3.2 kernel and the newer HWE
(https://wiki.ubuntu.com/Kernel/LTSEnablementStack) kernels.
For those needing an HWE kernel in your Precise installation, the Saucy
or newer HWE kernels are supported by a new
Just as a note, the new kernels are not only needed on LTS for hardware
enablement (and I'm guessing relatively few people need hardware
enablement in a VMware guest), but also to run Docker, which I suspect
affects more people (me included).
--
You received this bug notification because you are
** Also affects: open-vm-tools (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu)
Status: Confirmed = Invalid
** Changed in: open-vm-tools (Ubuntu Precise)
Status: New = Confirmed
** Changed in: open-vm-tools (Ubuntu Precise)
getting error in saucy
Setting up open-vm-dkms (2013.04.16-1098359-0ubuntu1) ...
Loading new open-vm-tools-2013.04.16 DKMS files...
First Installation: checking all kernels...
Building only for 3.11.0-9-generic
Building for architecture x86_64
Building initial module for 3.11.0-9-generic
Error!
In saucy, it appears that vmxnet and vmblock are not needed (nor is
vmci). The vmxnet3 is distributed with the kernel, and in fact if you
use the installer from the latest vmware-tools ISO, it does not build
vmxnet since the installer script knows this.
vmblock required a bit of changes to work
This problem also affects 12.04 LTS, after installing linux-generic-lts-
raring-eol-upgrade for upgrading to a newer kernel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
** Summary changed:
- open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed
to build
+ open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed
to build [error: implicit declaration of function ‘d_alloc_root’]
--
You received this bug notification
Let me just note, this update is on hold for now. I want to get the
Saucy package fix submitted first (as soon as I get a new upstream
release, or a patch to fix the 3.11 build failures).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Branch linked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm-
tools.quantal-modules.backport2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
Thanks for the patch!
Unfortunately, the patch is incomplete for the following reasons:
- it is simply a patch and does not update the packaging that is suitable for
SRU. Please see https://wiki.ubuntu.com/StableReleaseUpdates for details on how
to get your patch sponsored
- performing 'quilt
Patch for the backport
** Patch added: 04-quantal-module-backport.patch
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+attachment/3717422/+files/04-quantal-module-backport.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team,
The attachment 04-quantal-module-backport.patch seems to be a patch.
If it isn't, please remove the patch flag from the attachment, remove
the patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
** Branch linked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm-
tools.quantal-modules.backport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms
Would it not be safer to only backport the relevant code to allow the
modules to build against the 3.5 kernel, given that this has to be an
SRU? I see your new upstream in the branch you proposed, but I do wonder
whether updating to a new upstream release is a bit heavy handed, and I
am not sure
This is what's included in the proposal:
Upstream package: Raring
Debian folder: Precise
I tried using the whole Raring package and downgrading as needed. and
didn't work.
I have tested it (with a Precise machine), it does work
--
You received this bug notification because you are a member of
** Branch linked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm-
tools.raring-precise.backport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms
** Branch unlinked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm-
tools.raring-precise.backport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
Update:
The proposed update will be upstream packaging from the Raring upload, with the
Precise config. I tried the whole Raring packaging and add/remove stuff, but
it was being a pain.
The proposal will be submitted in a week or so (after I test it with the
3.2 Precise kernel) should have
** Branch linked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm-
tools.raring-precise.backport-mix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
** Branch linked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm-
tools.raring-precise.backport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms
I've started work on the Raring backport. It should give support
through 3.7 (3.8 with the patches). There's still stuff to downgrade
back to what it looked like for Precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I believe a DKMS package can be set up for different module sources
depending on the kernel version it is being built against (using
patches). Does this help you?
** Description changed:
-
Package ist really outdated for kernel 3.5.0 (lts backport to precise)
Modules not build: vmxnet
You mean I have to revert the (/debian) DKMS files from Raring-Precise.
Yeah I figured that out.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms
Looking at my notes I have to add some stuff back to the DKMS files.
Make a few changes to debian/control.
My goal is to make this update the first upload as the official
maintainer of the package, I just have to send e-mails to sponsors for
testimonials. Timetable: a month, testimonials will
My plan is to backport the Raring packaging. I plan to start working as
soon my CVE fix gets approved for raring, as well as my Saucy proposal.
It's gonna be a good amount of work because there's stuff in the
Quantal/Raring packages that won't work in Precise. So basically it'll
be a little bit
I can confirm this is happening on my setup as well, but I pretty much
have the same setup as the op. 12.02, 64bit and all that so I think my
bug report would be pretty much a repeat of what was already posted.
Is this problem fixed, or not a problem in the first place on 12.10 or
13.04 releases?
Oops, sorry I meant to type 12.04, 64bit and not 12.02, 64bit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms 2011.12.20-562307-0ubuntu1:
** Changed in: open-vm-tools (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms 2011.12.20-562307-0ubuntu1:
** Tags added: hwe-dkms
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module
failed to build
This is one of the reasons I want to start backporting the newer
packages to versions like 12.04. This is part of my Saucy blueprint.
But first I want to finish up my work (and proposal) on the Saucy
update, as well as submit my developer application.
But we have to be really careful, or we'll
Happening on fresh install of 12.04 32-bit Desktop as of 2013-03-07.
Sorry if this was already known, I'm new to Ubuntu and launchpad.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
No updates to this issue? Still happening on a fresh install of latest
12.04 64-bit LTS server
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms
Seems vmware tools have to be installed from the vmware ISO, since the
packages.vmware.com binaries are also broken for 12.04LTS with 3.5
kernel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
** Changed in: open-vm-tools (Ubuntu)
Status: New = Confirmed
** Changed in: open-vm-tools (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1083719
Title:
open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module
35 matches
Mail list logo
