I accepted all the default settings when creating the VM (which for Fusion was 20 GB disk, 1 GB memory, single processor).
On Fusion at least It is important to do the manual install: select installation method / more options / create a custom VM, mount the CD, set as boot device, bot up, go through the Ubuntu installer, accept the default to use LVM. If you go through select installation method / install from disc it does not take you through the Ubuntu installer UI, and it does not use LVM. At least that's what I see in Fusion; can't say for sure about Workstation. I reproduced it on VMWare Fusion, a customer reproduced it on VMWare ESXi (versions listed in original description). The kernel versions where it has been reproduced are also listed above next to the Ubuntu distro version. Some more information: * was able to reproduce the problem on Fedora 20 Fedora 20 (3.11.10-301, with LVM) * did not reproduce the problem on Centos 7.0 (3.10.0-123, with LVM) So so far all repros have been on 3.11 kernels or later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
