With the stable package in trusty/utopic I am going to close this bug.
** Changed in: open-vm-tools (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
With the stable package in trusty/utopic I am going to close this bug.
** Changed in: open-vm-tools (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269985
vmci_* symbols should be provided by vmw_vmci kernel module
(CONFIG_VMWARE_VMCI), is it enabled in kernel config? You should also
enable CONFIG_VSOCKETS and CONFIG_VMWARE_VMCI_VSOCKETS. That of course
leaves the normal kernel API churn that needs to be dealt with in hgfs
driver as being the only
I agree with John. It looks like you have built the package without
specifying --without-kernel-modules option to configure. Given that
all the kernel modules except vmhgfs have been upstreamed to the Linux
kernel, you need to tell configure to exclude kernel modules from the
build you intend to
Also the lack of frequent (monthly) updates, also forced me to delay
filing paperwork to give me upload (maintainer) rights for the package
during the Saucy. Which probably would've given me a voice when moving
to Stable (to stop it).
--
You received this bug notification because you are a
Ravindra,
It is built with --without-kernel-modules, I had to check the revision
changelog, it stayed.
Also, I've linked the Saucy branch to this bug, so you can see my
previous changes.
Another reason I'm still kind of fighting is because the Ubuntu-specific
changes made, still might not be
** Branch linked: lp:ubuntu/saucy/open-vm-tools
--
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/1269985
Title:
Revert package back to Devel release
To manage notifications
Nate,
We would definitely advise against using the monthly releases in shipped
products as they are and always been developer preview type of release
and receive very limited testing as opposed to stable releases which go
through much more rigorous testing.
That said if you have changes to the
Nate,
Looking at dkms files I still see references to vmblock and vmxnet,
which are obsolete. You also seem to be building vsock out of open-vm-
tools, but it has been accepted in the kernel proper so should be
comping from there.
Thanks,
Dmitry
--
You received this bug notification because
Dmitry (#8),
As you are well aware, Ubuntu uses the bleeding edge kernels, and one of
the nice things about devel packages was that, when they were being
released on a more frequent rate), the devel releases where more quicker
to adapt to the newest (release candidate) kernels.
I know stable
Dmitry (#9),
All the modules are being compiled (except ones that have caused build
failures), but only vmxnet and vmhgfs are being installed/used.
Speaking of vmxnet, I assume the pcnet32 is recommended over vmxnet. If
so, I can just remove vmxnet from the install.
I think Debian only
Dmitry,
I don't think we're using the built in-kernel vmblock. That's what's
one of the reasons I wanted to keep the Devel package (for the moment)
is because I had some specific changes for Ubuntu, that weren't in
Debian. Some other ones were removing manpages of modules that have
been removed
Nate,
The other distributions are fine with using stable releases recommended
by us as they see it as the least risky options, especially since these
are versions that we intend to support. RHEL and Fedora actually have
policy against using out of tree drivers, so their requirement was to
compile
vmci_* symbols should be provided by vmw_vmci kernel module
(CONFIG_VMWARE_VMCI), is it enabled in kernel config? You should also
enable CONFIG_VSOCKETS and CONFIG_VMWARE_VMCI_VSOCKETS. That of course
leaves the normal kernel API churn that needs to be dealt with in hgfs
driver as being the only
I agree with John. It looks like you have built the package without
specifying --without-kernel-modules option to configure. Given that
all the kernel modules except vmhgfs have been upstreamed to the Linux
kernel, you need to tell configure to exclude kernel modules from the
build you intend to
** Branch linked: lp:ubuntu/saucy/open-vm-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269985
Title:
Revert package back to Devel release
To manage notifications about this bug go to:
Also the lack of frequent (monthly) updates, also forced me to delay
filing paperwork to give me upload (maintainer) rights for the package
during the Saucy. Which probably would've given me a voice when moving
to Stable (to stop it).
--
You received this bug notification because you are a
Ravindra,
It is built with --without-kernel-modules, I had to check the revision
changelog, it stayed.
Also, I've linked the Saucy branch to this bug, so you can see my
previous changes.
Another reason I'm still kind of fighting is because the Ubuntu-specific
changes made, still might not be
Nate,
We would definitely advise against using the monthly releases in shipped
products as they are and always been developer preview type of release
and receive very limited testing as opposed to stable releases which go
through much more rigorous testing.
That said if you have changes to the
Nate,
Looking at dkms files I still see references to vmblock and vmxnet,
which are obsolete. You also seem to be building vsock out of open-vm-
tools, but it has been accepted in the kernel proper so should be
comping from there.
Thanks,
Dmitry
--
You received this bug notification because
Dmitry (#8),
As you are well aware, Ubuntu uses the bleeding edge kernels, and one of
the nice things about devel packages was that, when they were being
released on a more frequent rate), the devel releases where more quicker
to adapt to the newest (release candidate) kernels.
I know stable
Dmitry (#9),
All the modules are being compiled (except ones that have caused build
failures), but only vmxnet and vmhgfs are being installed/used.
Speaking of vmxnet, I assume the pcnet32 is recommended over vmxnet. If
so, I can just remove vmxnet from the install.
I think Debian only
Dmitry,
I don't think we're using the built in-kernel vmblock. That's what's
one of the reasons I wanted to keep the Devel package (for the moment)
is because I had some specific changes for Ubuntu, that weren't in
Debian. Some other ones were removing manpages of modules that have
been removed
Nate,
The other distributions are fine with using stable releases recommended
by us as they see it as the least risky options, especially since these
are versions that we intend to support. RHEL and Fedora actually have
policy against using out of tree drivers, so their requirement was to
compile
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) = Robert Jennings (rcj)
--
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/1269985
Title:
Revert package back to
Nick,
I am sorry for the betrayl; the sync was not done maliciously or with
malintent. Rather, as part of the work to bring open-vm-tools into main
(Bug #1220950), the sync was done.
Can you share the failures that you are seeing?
I have identified that the vmhgfs fails to load:
[386915.338195]
I think the problem is related to including the kernel modules from
open-vm-tools that are not necessary because VMware is contributing the
kernel modules upstream directly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) = Robert Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269985
Title:
Revert package back to Devel release
To
Nick,
I am sorry for the betrayl; the sync was not done maliciously or with
malintent. Rather, as part of the work to bring open-vm-tools into main
(Bug #1220950), the sync was done.
Can you share the failures that you are seeing?
I have identified that the vmhgfs fails to load:
[386915.338195]
I think the problem is related to including the kernel modules from
open-vm-tools that are not necessary because VMware is contributing the
kernel modules upstream directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
30 matches
Mail list logo
