I can't quite tell if subsequent patches papered over the gaps we identified in the accepted fix. Parts of the problem were fixed, but seemingly not all.
#Ubuntu vmware image 17.10 Patch#
I've looked into the latest Linux kernel sources, and it seems that the patch that we supplied was never fully accepted, despite all the effort we put into root-causing it and providing the patch. SATA disks were unaffected, as were other virtualization platforms and probably the vast majority of physical systems with SCSI disks. it was caused by a set of perfectly-valid characteristics that our emulated SCSI disks happened to have and that the Linux kernel handled improperly. It was not due to any defect in our emulation (despite the incorrect comments to the contrary in that discussion thread). That was a bug in the Linux kernel's block layer which just happened to only have an effect when writing to VMware's emulated SCSI disks. this reminds me somewhat of a Linux kernel bug for which we posted a fix for back in 2014: Linux-Kernel Archive: Do not silently discard WRITE_SAME requests My first thought is that we have many (MANY) users running Kali inside VMware Workstation and Fusion - it's a very popular combination for security work - and this is the first I've heard of this happening. That doesn't explain the Kali situation, though. We would spend far too much time chasing bugs that aren't ours. Ubuntu 17.10 may itself contain severe data-loss bugs at this stage of its development cycle, which is one of the reasons we don't try to claim compatibility or interoperability at this stage. Please also note that Ubuntu 17.10 is very early pre-release software, and as such it is nowhere near being qualified for use with VMware Workstation. I'll go against my gut instinct and try to assist anyway In return, I'd appreciate if you could put your emotions aside and work with us on understanding the problem. I appreciate you are frustrated, but please do remember that the VMware engineers and volunteers here in the forum are all humans, and your tone of writing here would make it much less likely that anyone will assist. I'm sorry that we appear to be failing to meet your expectations, while also being somewhat honored that you hold us to such high standards.
0 kommentar(er)
