> If you wish to undertake "Guest Customization" reliably then you must > interact correctly with the interfaces provided by the guest OS. These will > of course change from release to release of the guest OS, so in general it is > always necessary to adapt interactions as required by new guest OS releases. > Therefore your customers should not expect any new guest OS release to > function correctly with your Guest Customization feature prior to receiving > such an update from you. > It sounds like this problem will go away as soon as you release your fixed > vSphere update?
When "Guest Customization" fails due to a guest os change, we will work with guest os team to see how to resolve it. The fix could be either on vSphere side or on guest os side. Such failure can be caught before guest os release since we always test new guest os daily/beta build before it's released. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and upgrade to it. If the fix is on guest side(at least in guest os GA build), then customer need NOT upgrade vSphere to get the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
