Add CirrOS 0.3.5 support

[nvgoldin]

1. Disable ec2/cloud-init lookup on boot.
2. Fake 'bash' redirect to 'ash', as the CirrOS busybox is configured
   with CONFIG_FEATURE_BASH_IS_NONE=y

Only problem saw so far on boot:

Starting logging: OK
modprobe: module virtio_blk not found in modules.dep
modprobe: module virtio_net not found in modules.dep
WARN: /etc/rc3.d/S10-load-modules failed

Signed-off-by: Nadav Goldin [email protected]

[mykaul]

So what disks does it see? I'd be VERY surprised if it doesn't see both virtio-blk and virtio-scsi disks.

[nvgoldin]

So what disks does it see? I'd be VERY surprised if it doesn't see both virtio-blk and virtio-scsi disks.

Any idea how to check that? That is what I can get from lsblk:

# lsblk --fs -o NAME,KNAME,FSTYPE,LABEL,MODEL,SIZE,MODE,TYPE
NAME   KNAME FSTYPE LABEL         MODEL   SIZE MODE       TYPE
vda    vda                               39.2M brw------- disk
`-vda1 vda1  ext3   cirros-rootfs        31.4M brw------- part
# 

I also tried adding a secondary scsi device, but it would not "see" it, no kernel message errrors I could spot either.

2 more problems found:

1. Running 'virt-customize' and then running 'virt-sysprep'(like our bin/build.py script does) for some reason causes some of the operation done in 'customize' to disappear, urgh.
2. It takes too long to boot(imo) - I think there is some network timeout misconfigured. This is not the ec2/configdrive datasources this time though.

[nvgoldin]

Opened https://bugs.launchpad.net/cirros/+bug/1700330