open-vm-dkms doesn't detect vmxnet and vsock properly during install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
open-vm-tools (Ubuntu) |
Fix Committed
|
Medium
|
Nate Muench (Mink) |
Bug Description
I'm in the process of getting the August release ready, but I just wanted to get a few things out the way first.
I'm using Ubuntu Oneiric Alpha 3, and I'm using open-vm-tools from the Main Oneiric Repo. During the install, I get some warnings during the DKMS install stage (It's dated but it's still there).
Loading new open-vm-
make: *** vmxnet: No such file or directory. Stop.
make: *** vsock: No such file or directory. Stop.
First Installation: checking all kernels...
Building only for 3.0.0-7-generic
Building for architecture i686
Building initial module for 3.0.0-7-generic
make: *** vmxnet: No such file or directory. Stop.
make: *** vsock: No such file or directory. Stop.
I know it's dated, but I was hoping that this was a bug in the source packaging, but it isn't (because it's gotten worse in the August packaging).
After using Google to find a solution (using the generic query "No such file or directory. Stop."), I have found that this is an issue with the 3.0.0 kernel (I think, the results pointed to a kernel issue)
I'm looking for a patch for the open-vm-tools packaging.
Related branches
Changed in open-vm-tools (Ubuntu): | |
assignee: | nobody → Nate Muench (Mink) (n-muench) |
status: | Confirmed → Fix Committed |
Thanks Nate for looking into this. A number of packages had to have fixes which rely on '2.6' being the kernel version, so it would not surprise me if if this one of them.