Comment # 3 on bug 1161331 from Ancor Gonzalez Sosa

We are using this bug report (instead of bug#1161678 or bug#1120859) to handle
the problems of the installer defining an automatic proposal on top of a
virtual disk defined using PERC.

Shivani and Nanda, I'm adding you both in NEEDINFO because we would appreciate
to have some information to know how do you expect such proposal to look.

As a base case, we are using a disk layout inspired in bug#1120859 which is:

A disk "/dev/sda" with a total size of 220 GiB and GPT partition table
  It contains a single "/dev/sda1" partition of 100 GiB

A disk "/dev/sdb" with a total size of 910 GiB and GPT partition table
  It contains no partitions

A disk "/dev/sdc" with a total size of 440 GiB and GPT partition table
  It contains a single "/dev/sdc1" partition of 100 GiB

A software RAID1 called "/dev/md/VirtualDisk01" formed by sda1 and sdc1

As you know, right now such setup ends up in an infinite loop. But let's ignore
that for the time being and assume things work.

If you would run the "Guided Setup" you would see the screen saying "Select one
or more hard disks". Since the RAID1 is absolutely empty, that screen would
offer two options.
  - /dev/sdb
  - /dev/md/VirtualDisk01

Let's say you select only VirtualDisk01. The current proposal (ignoring the bug
that we will fix) will propose this:

- Create a /dev/sda2 partition of type bios_boot.
- Create a /dev/md/VirtualDisk01-part1 partition for "/"
- Create a /dev/md/VirtualDisk01-part2 partition for "/home" (if requested)
- Create a /dev/md/VirtualDisk01-part3 partition for swap

The bios_boot partition is needed for the system to boot. The proposal
allocates it in /dev/sda because such partition needs to be in a real disk, it
cannot be inside a RAID1.

Let's assume now another scenario.

A disk "/dev/sda" with a total size of 220 GiB and GPT partition table
  It contains a single "/dev/sda1" partition using all the space

A disk "/dev/sdb" with a total size of 220 GiB and GPT partition table
  It contains a single "/dev/sdb1" partition using all the space

A software RAID1 called "/dev/md/VirtualDisk01" formed by sda1 and sdb1

The proposal would say in that case that it cannot propose a valid setup on top
of VirtualDisk01. As in the previous case, a bios_boot partition is needed and
it needs to be in a real disk. But in this case, there is no room in any of the
real disks to allocate such partition.

So my question is: do my explanations fit your expectations about how the
proposal should work on top of "virtual disks"?