Manual partitioning does not allow multiple LV created in VG

[Anakin]

Description: Ubuntu 14.04.1 LTS
Release: 14.04

ubiquity:
  Installed: (none)
  Candidate: 2.18.8.1
  Version table:
     2.18.8.1 0
        500 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
     2.18.7 0
        500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

All details found in http://ubuntuforums.org/showthread.php?t=2241507

This is not a technical bug per se, but not being able to create multiple Logical Volumes in a Volume Group is a bit of a short-coming? If this was submitted wrongly, please guide me to the right location.

What I expected was to be able to create multiple LVs in a VG (as I had done so before on RH-based installs)

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 167,7G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 244M 0 part /boot
└─sda3 8:3 0 167G 0 part
  └─sda3_crypt (dm-0) 252:0 0 167G 0 crypt
    ├─xubuntu--vg-root (dm-1) 252:1 0 20G 0 lvm /
    ├─xubuntu--vg-swap_1 (dm-2) 252:2 0 7,9G 0 lvm [SWAP]
    ├─xubuntu--vg-home (dm-3) 252:3 0 15G 0 lvm /home
    └─xubuntu--vg-virtual (dm-4) 252:4 0 124,1G 0 lvm /virtual

What happened instead:

-- When I use automatic partitioning (with encryption and LVM tagged) it makes 1 VG and creates 1 big filesystem / and 1 for swap. Makes sense, I merely used this just to show that it does in fact work.
-- When I manually partition in the installer, I cannot create multiple LV's in a single VG. Each filesystem needs to be on its own Physical Volume. After reboot this resulted in having to enter the same encryption password (can only set it once) multiple times.
-- When I manually partition in the installer without LVM, all filesystems on separate encrypted partitions, it fails at creating/mounting the XFS filesystem. This is possibly/most likely a separate bug which I'll investigate on a different (virtual) machine.
-- When I manually partition using parted, then assign filesystem/mount-point in the installer WITHOUT encryption, it works fine. Makes sense, I merely used this just to show that it does in fact work.
-- When I manually partition using parted, then assign filesystem/mount-point in the installer WITH encryption, it fails to copy the dm-crypt.ko into the bootloader (the file is physically not present in /boot/lib), does not create /etc/crypttab, Hooks are not present (no idea on that) and grub is not updated with proper "root=" setting. At boot init fails because crypt-device (in all cases /dev/sda3) cannot be found, dumps me to the prompt, where the command cryptsetup is not found.

Worked around it by using the automatic partitioning (so all the libs and configs are present) and alter the setup from LiveCD after completion.

I do not have installer-logs available. If needed I could reproduce in a VM fairly easily.